Re: Should the specs be forked and maintained elsewhere?

We’ll have a bunch of implementors in the same place and time on-line next week at Fediforum, e.g. for software demos:.

https://fediforum.org/demos/

Chances are somebody is going to call a session on ActivityPub anyway, it’s an unconference.

Would it make sense to take one session slot to start this discussion? Say Wednesday or Thursday 10am pacific? (I’m an organizer, I can provide access.)

Best,




Johannes Ernst
Blog: https://reb00ted.org/
FediForum: https://fediforum.org/
Dazzle: https://dazzle.town/



> On Mar 21, 2023, at 15:55, Evan Prodromou <evan@prodromou.name> wrote:
> 
> Regular meetings would be great.
> 
>> On Mar 21, 2023, at 5:25 PM, Bob Wyman <bob@wyman.us> wrote:
>> 
>> I've seen several suggestions that, due to inactivity in this group, it would make sense to fork either or both of the ActivityStreams and ActivityPub specs with the intent to develop them further and maintain them elsewhere. The most recent suggestion <https://socialhub.activitypub.rocks/t/should-we-fork-as-ap-specs-to-codeberg-create-vnext-drafts/3022> that I've seen was made in one of the forums on the ActivityRocks site.
>> 
>> My personal feeling is that the proper forum for maintenance of these W3C specs is within this community. Am I correct? However, I sympathize with others who feel that maintenance is simply not happening. There are now 55 open issues <https://github.com/w3c/activitypub/issues> on ActivityPub's GitHub repository and 58 open issues <https://github.com/w3c/activitystreams/issues> on the ActivityStreams repository. Who is responsible for addressing those issues, closing them, or taking action on them? What is the process by which these decisions will be made?
>> 
>> Other W3C groups that I've worked with have regular Zoom or Jitsi meetings to discuss issues. Why doesn't this group ever have such meetings?
>> 
>> bob wyman
>> 
>