we’re dealing with a larger network of different servers now and hopefully that will continue. Any foundation, legal or not, should be related to that, not the Diaspora software.
Why? The federation is about the protocol. diaspora* is the software. That’s fine. Nginx and Apache are both http servers. There is a foundation to manage both project. Of course, there is also another entity to manage the http standard itself. You think a foundation is needed to manage the protocol using the name “The Federation”. This could be a good idea and I support you. But I don’t see why we can’t have a diaspora* foundation, as well as a Redmatrix foundation, and maybe to see both collaborate on “The federation” (which may or may not need a legal structure, I don’t know).
moving the project official account for Diaspora to something that is called foundation imho is wrong.
It’s wrong only if the foundation aims to manage The Federation. If it manages the diaspora* software, I don’t see what’s wrong.
To me, it looks like everything can be summarize to this point: do we want to have a “foundation” (held by FSSN or directly by ourselves) to manage the diaspora* software, or do we want to jump directly to the next step and create an official structure to promote and work on a decentralized protocol called The Federation.
In my opinion, we should start small with diaspora* itself. Maybe the current situation is even enough? We didn’t talk about the FSSN and how things are going for a while (time to relaunch IRC meetings?).
Anyway, I don’t see why we can’t have both: a structure for diaspora* (maybe only managed by FSSN, maybe more, but which will be described on diasporafoundation.org anyway) and a structure for The Federation (you could use the-federation.info that you already own to give more explanation about it).
If we are in that case, then it seems logical that diasporaHQ, the account which gives news about the diaspora software, should be on diasporafoundation.org.