YuriTheHenrique I've had a discussion with an Ubuntu Budgie team member that made it pretty clear that they are excited to see how an EFL-based Budgie progresses, how they (or at least this specific member) can get involved (both for Budgie as well as helping the EFL ecosystem), etc. It was at least this team member's belief that the blog post detailed what many have been thinking about GNOME and GTK for a while, and while it of course does not necessarily reflect the entire viewpoint of the Ubuntu Budgie team, there is at least some in their neck of the woods that are at least understanding of this choice in direction.
This individual originally inquired about having a 1-to-1 meeting, however I instead proposed that there be a broader meeting between Solus and Ubuntu Budgie folks, as this would provide an opportunity to ensure that everyone's needs are known, assessed, and if possible worked on during the development process, to best ensure that they are able to best utilize Budgie going into the future. That team member said they would relay it to the Ubuntu Budgie team and get back to me on it. Not sure where that'll go (if anywhere) but I am being mindful of downstreams like them and would like to have constructive discussions with them on it, rather than this whole "let's just wait and see" viewpoint. Hell, if it could even be recorded and uploaded for posterity sake and increased transparency that'd be pretty dope too.
A fork of Budgie is not really necessary. While there will be more components related to Budgie Desktop to facilitate the more modular approach and ensure we have software like our own control center to best expose Budgie functionality in addition to other system integration, really only the graphical aspects of Budgie will "need" EFL (at least so far, that's the intent). While yes, Budgie panel, Raven, etc. plus a Control Center would be significant graphical applications to be using EFL, we are not in the business of making it harder for downstreams to pick whatever defaults they want for other applications (that would be silly and pointless) and would like to do what we can to make theming as painless as possible.
Of course, it is their right under both copyleft and permissive licensing to fork Budgie, however that would necessitate them rebranding and that level of divergence wouldn't really help them any.