Any discussion and volunteer efforts to collect that information is welcome of course. But as I see it (interpreting @how’s ultimatum) there’s a stark choice within 4 weeks time of:
-
Either a community team steps up with a Community Plan that @how feels comfortable transferring custodianship to, before stepping away from that role with P.S.
-
Or there is no viable plan and team, and @how with P.S. is tasked with responsible shutdown.
What is a viable plan, what is a viable community then? Well, again my opinion, but there is no need at all to be broadly interesting, relevant to a large group, or targeting the entire dev ecosystem. A community team may choose any niche area to focus on. It is up to them. Viable in my book means first of all:
- There is a team willing to take the commitment, and @how approves on the (transition) plan.
After that happens then I think it is important that the new team has free reign to do whatever they want to forge healthy community in whatever direction, scope and audience they want to serve/explore. They should be able to revitalize, reposition and foster the community as they think is best. They are now sole custodians of that, the ones making the fresh start. The “Why?” and “What to do about it?” may not be all that relevant against their new direction, the mission and vision of this new team.
I’d personally definitely reposition, and can imagine many different directions that might be interesting for a community to explore..
-
“We are W3C SocialCG and want to have a more informal discussion space, while reserving the mailing list to official spec-related comms.”
-
“We want to optimize the bottom-up grassroots standardization process, so that the dev ecosystem becomes more empowered to innovate the social web, overcome the inertia.”
-
“We want to focus on improving the developer experience for newcomers that is still deplorable to this day. We will dedicate on lowering barriers to entry of the fediverse as much as possible.”
-
“We focus on bringing the qualities and benefits of linked data to the forefront, in ways that still appeals to JSON-only crowds. We’ll bridge gaps with other linked data standards.”
-
“We focus on becoming a portal that collects feedback from fedizens, whose voices are insufficiently heard, in the developer-oriented release processes of individual apps.”
-
“We will focus on collecting all the highly innovative ideas around decentralized networking, and give space for people to think out of the box, be creative and unrestricted by what’s currently possible.”
-
“We want to emphasize the ‘social’ in social hub, and give minority group a stronger voice in the developer community. We will actively reach out to developers other than those ‘from the West’ who dominate the scene.”
-
“We will focus on the C2S side of the fediverse, which we consider to be the path to future of social networking.”
-
“We are interested in the Discourse AP pluging, and want to make Discourse software as native as possible to the fediverse as a community platform.”
-
“We think it is currently fine as it is, and will gladly support that from now on.”
-
" … [ add your dream community plan here ] … "