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

[wg/webapps] Rechartering Web Applications Group Charter (closing Services Worker WG) #457

Open
plehegar opened this issue May 3, 2024 · 7 comments
Assignees
Labels
charter group charter Core

Comments

@plehegar
Copy link
Member

plehegar commented May 3, 2024

Evaluation

This would address 2 ongoing threads:

  1. The work on Service Workers Working Group has stalled and it's difficult to maintain the current Working Group. The idea is to merge the work on Service Workers within the Web Applications Working Group
  2. We also need to consider revising the success criteria section:
    [[
    In order to advance to Candidate Recommendation and to add features after reaching Candidate Recommendation, each feature is expected to be supported by at least two implementations, which may be judged by factors including existing implementations, expressions of interest, and lack of opposition.
    ]]
    from previous charter
    See also Add back old Success Criteria  webappswg#107

cc @siusin @ylafon @himorin @marcoscaceres @LJWatson

@plehegar plehegar added the charter group charter label May 15, 2024
@plehegar
Copy link
Member Author

plehegar commented Jun 5, 2024

(looks like item 2 is getting dropped)

@plehegar
Copy link
Member Author

plehegar commented Sep 3, 2024

@marcoscaceres will propose a TPAC breakout to follow up.

@plehegar
Copy link
Member Author

plehegar commented Sep 3, 2024

(some notes from ongoing conversations)

Splitting up WebApps WG into Smaller Focus Groups

  • easier for people to join
  • some specs are very active, such as Manifest, Gamepad, good leaders, running regular meetings
  • some specs like UIEvents, if we can have a dedicated group, it may attract more editing force
  • problem to solve: same as DAS, too many specs (IP review, refused to give IPR commitment if you are only interested in some of them), we can't chair it properly, not efficient to get consensus, difficult to keep an eye on everything

@siusin
Copy link

siusin commented Sep 16, 2024

We should remove the ARIA-related works from the scope, the ARIA WG agreed to take over those specs.
[[
The working group also maintains a specification for mapping HTML elements and attributes to platform accessibility APIs, and a separate specification that defines author conformance requirements for setting ARIA attributes. The Working Group does not expect to add any other specifications relating to this matter.
]]

@siusin
Copy link

siusin commented Sep 23, 2024

Notes from TPAC:

  • make Intersection Observer a joint-deliverable with CSSWG or move it to CSSWG
  • bring in Web Install as a deliverable or part of the Manifest spec

@plehegar
Copy link
Member Author

An other point I heard at TPAC: Service Workers might move to Web Performance Working Group.

@plehegar
Copy link
Member Author

Update: Moving to Web Performance Working Group doesn't work. We're back at trying to find an editor for the specification :(

@plehegar plehegar added the Core label Nov 12, 2024
@plehegar plehegar removed their assignment Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
charter group charter Core
Projects
Development

No branches or pull requests

3 participants