As the other thread seems to contain some unresolved stuff at the end. I’ve decided to start a new one. At the end of the wiki, @aschrijver details the following situation. Do we have any plan how to collect these?
Looking at the Account Migration, I was back to clicking myself through many places of documentation, i.e. in addition Mastodon, Mitra, Pixelfed, Lemmy.
It would be nice to have all this together somewhere. I might update these lists, and have them for some time.
This is a good “native” source Do-ocracy - Noisebridge with this reference in mind, am trying to find the connection between the title and the content of the thread.
Maybe it is this the is currently a growing stress between #WC3 working with formal consensuses and #socialhub working with a mixture of #NGO/ attempting grassroots/#mainstreaming process. Let’s try thinking of this positively as messy consensus
I think there is a consensus on socialhub that the #W3C path is ossified and slow, but we have no working consensus on how to be different. We do have #NGO grassroot small working parts, and libertarian cats fitting and purring.
NEXT STEP: Have we step up a meeting to talk to the WC3 about what we are trying to do? I have talked to some of them, they have wisdom to add to this.
Yes, as you describe it is the general idea. Combine the best of both approaches. The diagram in the wiki topic shows two branches coming from activitypub.rocks website, of for formal process, the other for grassroots. They are separate but can take all kinds of inspiration from each other and cross-pollination.
I just saw your toot about prepping fedidb.org for a launch. We discussed in the past ideas/plans you have to open up this initiative and get a community of collaborators going for its further improvement and extension.
It looks like there’s many points where fedidb.org can hook into the new initiative of @gabek and @j12t to launch fedidocs.org and crowdsource its contents. From a FediDB app entry you might jump into techdocs for that app at FediDocs, for instance.
Yesterday I suggested that the SWICG might need a process to close open issues in AS/AP W3C repositories on Github. Related to that…
Do we need a process to follow up on topics discussed in this forum? An action repository under https://codeberg.org/fediverse where issues are tracked, assigned and dealt with.
This forum is full of people suggesting actions, making proposals. Who’s following up on that? To whom are the proposal made? Well, to whom the glove fits in true DoOcracy fashion. But these action points are spread all over the place.
I’m unsure if tracking progress or non-progress for the Fediverse Enhancement Proposal Vocabulary would make the process smoother. I think the main problem currently with the process is that everybody gets distracted on technical details … The first goal of FEP-2e40 is:
Create a FEP Vocabulary based on identified best practices
If one would use issue tracking, this would be the first issue, all other issues are blocked until it is resolved. I’m not convinced this would get done. Also I’m not convinced people would then obey the best practices.
Side note: The vocabulary section of json-ld-bestpractices is still on “editor’s choice”:
But its relationship is unclear. Github allows a detailed markdown to be displayed on the profile page, and we could use that to provide all the necessary pointers to not only this forum, but the FEP on Codeberg, etc.
The ap-socialhub account was made to integrate the ActivityPub repository there with the #activitypub:issues conference here (which is restricted because I never managed to triage the issues and bring comments there…) I’m not sure how it came to point to Codeberg, but I guess it’s a good thing. Maybe @nightpool or @weex remember something about it.
Ah, it is not point to Codeberg. But independently of what existed on GH, the FEP emerged and was moved from Cory’s domain to fediverse organization on Codeberg. Since FEP is a major process that we at SocialHub should keep going and growing, we might make that relationship. A profile README can be used to attract attention to what SocialHub is all about…