w3process
w3process copied to clipboard
Member submissions: can anyone else object, and if so, can they object to acceptance?
In Member Submission the member who submitted can appeal a rejection.
But should it be possible for anyone else to appeal? And if a submission is accepted that other members see as problematic, should it be possible to appeal acceptance?
(These are 'cleaning up loose ends' questions, I am not aware of current or past problems)
Does the concept of a "member submission" still belong in the Process, considering the evolution of the patent policy, the near-universal use of "forkable" copyright licenses in web standards, and the use of community groups as the typical incubation mechanism? It would seem cleaner to just remove member submissions to the process than try to untangle the Director from yet another corner case.
The history suggests that they remain an active tool.
Well sure, if you expose a lever, people will yank on it. Are they doing anything with that lever they couldn't do if it were removed? Is repairing the mechanism the lever controls worth the trouble, considering you could just remove the lever?
As per the history that David cites, it has been useful particularly to get input from industry groups.
Again, what input are you getting via the submission process you couldn't get from normal participation in WGs, IGs or CGs?
I know from personal experience the Member Submission process was abused in the past to get the appearance of W3's imprimatur on "input from industry groups" that had no broad industry support or prospects of getting into a Recommendation. I don't know of that happening in the last 10 years or so, but I don't see many submissions that had a real impact since the FIDO submission in 2015 either.
This is a pretty minor nit in the Process so I don't really care what happens to this issue, but I am concerned that the Process is accreting ever more complexity to cover anachronistic corner cases. Assuming W3C survives the LE transition and the AB can focus on process and community issues next year, cleaning up this sort of legacy cruft might be worth some attention.
I tend to agree with Michael here - member submissions made sense pre-CG, much less so now.
If you want to suggestion removing Member submissions, please file a new issue. That's not this issue.
I proposed resolving the issue of how to appeal member submission decisions by removing member submissions🤷
If I have an issue with my appendix or gall bladder, my doctors won’t spend time trying to fix it, they will resolve the issue by removing the problematic organ.
@michaelchampion Say a group of folks that a not W3C members come up with a spec, and would like to continue the work in W3C, how would they get started?
Create a Community Group; have the CG publish the spec with an open copyright license and patent commitments from the contributors; build a community of users who have problems the spec solves, implementers who will support the standard in their products, tools, frameworks, etc.; then draft a charter for a new WG or discuss expanding the charter of an existing WG to put the “incubated”spec in scope.
Is there any way for the contribution, with the relevant patent commitments, to be directly accepted by a WG?
I don't see why not, but I haven't thought about this for a while. If someone writes a spec, joins a WG for which it is in scope thus making patent commitments to anything the WG takes to Rec, proposes it and the WG accepts it, I don't foresee any problems.
Member submissions historically were for situations where there wasn't an existing WG with the spec in scope, and before there were CGs with a patent policy designed to cover such incubation scenarios.
To be clear, I don't have strong feelings on whether member submissions should be removed from the process. I'm just suggesting the Process CG convince themselves that member submissions are worth fixing to work in a director-free world as opposed to just removing them from the Process so this issue doesn't arise.
As requested by the chair, I moved all the comments about removing member submissions from the Process into a new issue: #648. Please keep this discussion on topic.