Require a mailing list (+ archive) or a github issue list #631
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
plehegar
reviewed
May 19, 2017
| @@ -45,8 +45,8 @@ exports.check = function (sr, done) { | |||
| if (!foundRepo) { | |||
There was a problem hiding this comment.
if this is a REC, we ought to require a Repo rather than allowing the use of mailing list. This will align with the maintenance discussion within the AB.
There was a problem hiding this comment.
That means changing the requirements for RECs. Can we do that without consulting spec-prod before?
There was a problem hiding this comment.
we should let spec-prod know but this is a necessary change however.
There was a problem hiding this comment.
Btw, this will be part of the transition requirements update at https://w3c.github.io/transitions/?profile=REC
tripu
approved these changes
May 24, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #629