The Wayback Machine - https://web.archive.org./web/20231006191310/https://github.com/w3c/strategy/issues/435
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restarting the Social Web Working Group #435

Open
1 task done
plehegar opened this issue Oct 6, 2023 · 6 comments
Open
1 task done

Restarting the Social Web Working Group #435

plehegar opened this issue Oct 6, 2023 · 6 comments

Comments

@plehegar
Copy link
Member

plehegar commented Oct 6, 2023

New charter proposal, reviewers please take note.

Charter Review

Charter

What kind of charter is this? Check the relevant box / remove irrelevant branches.

  • New
  • New WG

Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, and security. Also add a "card" for this issue to the Strategy Funnel.

Communities suggested for outreach:

Social Web CG.

Known or potential areas of concern:

lack of consensus within the Community on the scope of the charter.

Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)

For now, in the Social Web CG.

Anything else we should think about as we review?

@plehegar
Copy link
Member Author

plehegar commented Oct 6, 2023

Notes:

  • We may not need a Working Group
    • Are there any subtantive changes needed for the ActivityPub W3C Recommendations?
  • Social Web WG or ActivityPub WG ?
  • Maintenance-only or allow new features?
  • Make it an umbrella WG around a CG?

@plehegar
Copy link
Member Author

plehegar commented Oct 6, 2023

@gobengo
Copy link

gobengo commented Oct 6, 2023

@plehegar noting that at this time there have been two contributors to that document

@plehegar
Copy link
Member Author

plehegar commented Oct 6, 2023

[[
Note: If there is no Working Group chartered to maintain a Recommendation the Team cannot make substantive changes and republish the Recommendation. It can, however, informatively highlight problems and desirable changes using errata and candidate corrections and republish as described in the previous section.
]]
From 6.3.11.3. Revising a Recommendation: Substantive Changes

@AramZS
Copy link
Member

AramZS commented Oct 6, 2023

There's a lot of activity around what used to be the Social WG's maintained recommendation, presumably that would indicate that there is interest in more active maintenance from a broad set of participants. The potential spec work listed is quite large and many of those could indeed use more active work.

@capjamesg
Copy link

capjamesg commented Oct 6, 2023

I support the creation of a WG. There are several changes to be made to the ActivityPub specification that would require a WG. I thank @evanp for leading work as editor, and to the broader community -- particularly those involved with FEPs -- for helping to advance discussions on how ActivityPub can be improved.

There has also been interest in potentially working on jf2, Micropub, rel=me and IndieAuth. Any inclusion, however, would require an active editor (or, for larger specs, multiple editors) who have already worked on the specifications and can lend their expertise to the group.

I would prefer we have a single WG. I think we can work better as one group rather than managing cross-group communications, and we could have more social web experts in one place to support each other.

I have heard several concerns about new features in ActivityPub in particular but I don't know enough to have an opinion on whether AP should be allowed to have substantiative amendments in a prospective WG. With that said, a lot of work has been done on Micropub and IndieAuth that may introduce new functionality. If that is the case, I think denoting, by spec, whether the spec is in a "maintenance mode" or allows for larger changes would be beneficial. Thus, we could have ActivityPub in maintenance mode and IndieAuth, for example, in a more active editing mode.

I invite CG members (participation is free) to contribute to the prospective WG charter wiki page, where we are collating thoughts for a charter. This page has been sent for distribution across the mailing list, published on the w3.org website and mentioned in meetings. I would love to see more people help us advance these discussions! (The wiki page is a forum for brainstorming and does not represent any final position of the group.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants