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

Role of the W3C staff and core process? #3

Closed
iherman opened this issue Dec 27, 2015 · 1 comment
Closed

Role of the W3C staff and core process? #3

iherman opened this issue Dec 27, 2015 · 1 comment

Comments

@iherman
Copy link
Member

iherman commented Dec 27, 2015

Although the proposal makes it explicit in a relevant section that the goal is not to rubber stamp, do see a possible problem with the lack of W3C staff presence. Indeed, at present, the staff is not supposed to spend much time in Community Groups. There is a danger that if the bulk of the spec work is done in the incubation period without staff participation than the genuine issues raised in that section will come "too late" for the proposers who would lobby against (some of) those (because "the job is already done"). Warning against such problems may be one of the jobs of the staff.

Maybe an approach is to set up a "early warning" mechanism whereby a CG would contact the W3C staff early enough in the process with the message that "we would like an extra interest from W3C because we plan to submit this technology for standardization in 6 months" (or something like that). That would allow early check/review against potential problems, staff participation in finalizing the proposals, etc.

(The situation does not occur with Interest Groups which do have staff contacts.)

@michaelchampion
Copy link

I believe I've resolved this as you suggested in 7d21e4b . Please re-open the issue if you disagree.

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

No branches or pull requests

2 participants