-
Notifications
You must be signed in to change notification settings - Fork 161
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
Need better workmode onboarding #296
Comments
"The PR template is nice, but we should have an issue template that points to the Working Mode" |
I agree we should do this, but it probably makes sense to track this over in whatwg/meta instead of here? Or do you think the SG should be involved in some way? What I'd like to do is patch https://github.com/whatwg/spec-factory so it can push this out everywhere as well as better READMEs. |
No, you're probably right; I was making sure I wouldn't forget about it. I'll move it to meta. |
Oh: @annevk you'll have to transfer it, or give me admin rights on meta. |
Thinking of what categories we want people to have templates for:
Thoughts? |
Would it be worth adding a template for implementer clarifications, that we might prioritise them differently (as they're likely coming from an implementer midway through work)? |
We should probably categorize those better when triaging, but I'm not sure it helps the flow for new contributors as they might not know the difference between the various options we could offer. I put an initial sketch up at https://github.com/annevk/temp-whatwg-new-issue/issues/new/choose (URL will disappear at some point). |
As proposed in whatwg/meta#296.
As proposed in whatwg/meta#296.
This has now been deployed on https://github.com/whatwg/url/issues/new/choose. https://github.com/whatwg/url/#readme is also somewhat new. I'll be rolling that out to the other standards soon. |
Remaining:
As noted in whatwg/spec-factory#3 (comment) there's a couple standards that need improved README's still. We could either do them manually or attempt to make them work better with spec-factory. I don't think this blocks closing this issue. #297 tracks the remaining Stages work. I don't think that blocks closing this issue either. |
All the issue templates have landed. See the above comment for README and Stages improvement tracking issues. |
(From suggestion by Mu-An at WHATUP)
We should ensure that feature drivers have clear pointers to the workmode, and then when/if we add the Spec Acceptance Stages that we inform feature developers of this new tool to help manage expectations.
The text was updated successfully, but these errors were encountered: