search

w3c / webappsec

Web Application Security Working Group repo
https://www.w3.org/groups/wg/webappsec/
Other
601 stars 148 forks source link

Which process version is the WG using? #599

Closed marcoscaceres closed 2 years ago

marcoscaceres commented 3 years ago

Hi Chairs and @samuelweiler! I'm having some issues with auto-publishing the Permission spec. Echidna complain that the WG is not yet using Process 2020 (still using Process 2017?).

Is that correct or we need to get the group information updated somewhere at the W3C?

mikewest commented 3 years ago

My understanding is that we're still using 2017, and that 2020 will come along with the charter refresh that's working its way through the AC and etc.

marcoscaceres commented 3 years ago

Yikes, ok... I updated the Bikeshed templates incorrectly then :( Will switch them to 2017 and we can revert once we are on 2020.

Um, nothing to see here 😅

wseltzer commented 3 years ago

@mikewest, @marcoscaceres the Patent Policy doesn't update until re-charter, but Process should be updated automatically when W3C adopts an update.

marcoscaceres commented 3 years ago

Ok cool. So, question: should I bother reverting the changes I made to Bikeshed? or do we expect the updates to happen quickly enough that this won't be an issue (e.g., in a week or two or are we looking at "months")?

wseltzer commented 3 years ago

The charter renewal is under discussion now, to see if we can resolve formal objections, so I'd expect ~month.

marcoscaceres commented 2 years ago

Ok, cool. Process 2021 might also be accepted by then. Will it be possible to have a lightweight transition path from 2020->2021 once we get charter approval?

wseltzer commented 2 years ago

As with Process 2020, I expect Process 2021 will be an automatic transition once approved by the AC and Director. The WG doesn't need to do anything but update documents.

marcoscaceres commented 2 years ago

That's great to hear. @wseltzer, sorry for my ignorance, but I'm guessing that "automatic transition" wasn't part of Process 2017. Is that why the group didn't transition automatically to Process 2020 already?

wseltzer commented 2 years ago

All groups and documents should have moved automatically to Process 2020 when it became operational 15 September, 2020. https://lists.w3.org/Archives/Member/chairs/2020JulSep/0076.html

Blame the team contacts (including me) if that didn't happen.

marcoscaceres commented 2 years ago

oh, ok! I see what happened now. The group was on the 2017 PP, which was not on track to be automatically updated with the new Patent Policy. That would require a recharter, as per the email above.

I'll update the Bikeshed templates.