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

Support github and updated boilerplate #416

Closed
marcoscaceres opened this issue Mar 25, 2015 · 2 comments
Closed

Support github and updated boilerplate #416

marcoscaceres opened this issue Mar 25, 2015 · 2 comments

Comments

@marcoscaceres
Copy link
Member

People that don't use mailing lists (that's me!) should be able to list a GH repo as the primary way to provide feedback about a spec.

As @AFBarstow proposes:

The boiler plate asking for feedback via GH and the Status section
asking for feedback via p-webapps is certainly suboptimal. AFAIK,
PubRules mandates the comment list. If we can't get that restriction
lifted, I recommend the relevant text in the SotD clearly state using GH
for comments/bugs/issues is strongly preferred and the list should
only be used as a last resort.

@plehegar
Copy link
Member

@marcoscaceres
Copy link
Member Author

Mailing lists are no longer required by the w3c + we now have github option.

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