Since I learned that CoderGlue is not a well-enough name…
Via FedisHospEx I bumped into a software that can be used to vote on names, that I wanted to mention. Here’s the brainstorm for FediHospEx on Ukuvota: https://ukuvota.world/#/app/63841ecc-fba4-1a57-6360-29f6a69fc6a2/collect
Organization structure: Umbrella project + sub-projects
Other than that (and this might warrant a separate topic) there’s the consideration that FedeProxy might not be a single initiative + project, but an ‘umbrella’ of multiple subprojects / initiatives. FedeProxy can keep its name as-is then, and it is these subprojects that can be separately named and ‘branded’.
This organization structure would align with a modular approach to projects + architecture. Having both organization and architecture ‘modularized’ is a good way to ensure you take the requirements that flow from that into account.
Maybe (merely brainstorming) what we already have is:
- FedeProxy: Umbrella organization (or initiative / movement / community)
- Core module: DVCS, AP federation, “the plumbing”
- Social module: Boundless collaboration, Diversity
These modules can have distinctive names / ‘brands’, be separate sub-projects. The latter one is what I would call “CoderGlue: Let’s code together”, atm (and a better name can be ideated).