I discussed in the past the possible role of FedeProxy server instances with @dachary which imho go far beyond a technnical proxy component between existing forge projects / products. It inspired me to write the idea of:
What follows is once again a far-future idea for FedeProxy direction…
So FedeProxy offers the ability for FOSS projects to be freed from the shackles of a particular forge, right? It liberates a FOSS community that way, and uses a technical protocol (DVCS) and a social protocol (ActivityPub) under the hood. The latter allows it to be broadly integrated in a whole host of other social apps that exist or will exist some day on the Fediverse.
FedeProxy exists to serve inclusive FOSS communities.
Let’s consider this a bit more holistically. In the following it doesn’t matter whether FedeProxy is an application integrated on a forge, or a self-host instance (a platform). Consider this question:
“Why doesn’t FedeProxy facilitate the creation, hosting and management of FOSS Communities?”
The whole she-bang as a federated social platform where many people can extend this platform with their own modules (similar to how NextCloud works in a different space).
Starting a FOSS community has many ins and outs, best-practices and pitfalls to avoid, management and procedures, community-building processes. All of these aspeccts need to be given proper attention to increase the likelyhood of the community being successful and its projects to take flight.
And this is also the weakness that many of technical-oriented people (mostly developers) have, when starting a project + community. How do you get contributors? How do you do marketing? Where to find designers? How to become a diverse community? How dow I get funding? Numerous things to address, and many different skills involved.
FedeProxy might be the social platform that helps to significantly ease all this, decrease the burden and increase chances for success.
I will just depict some vague notions of how things might work, to hopefully inspire.
- Start a new Community by selecting from pre-configured templates.
- Guided community wizard takes you through an onboarding process.
- Provide a bunch of metadata (description, objectives, team, etc.)
- Define community organization (channels, repositories, toolstack, etc.)
- Configure software process elements (teams, procedures, artifacts, templates)
- Community is bootstrapped by the platform.
- Project website placeholder generated in appropriate location (maybe hosted on FedeProxy platform itself).
- Social fediverse integrations are set up.
- Aggregated Software Knowledge channels are set up.
- Community dashboards are prepared.
- Preparation phase starts.
- The team starts working on providing details for all templates, fine-tunes configs, provides website information, etc.
- Launch of FOSS community
- Platform helps manage the announcement and markeing via social integrations.
And now the new FOSS community is up and running