-
Notifications
You must be signed in to change notification settings - Fork 52
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
Feedback email in addition to GitHub #1910
Comments
I think the original idea was that since the spec is being develop on GH, we want to have a central place to gather feedback instead of having comments spread all over the place. See #629 and #408. /cc @plehegar |
Indeed, we removed the requirement several years ago because of less of our groups are using their mailing list. For those, sending an email will likely get missed. |
CC: @iadawn @daniel-montalvo @ruoxiran I understand the rationale. And I still think it's exclusionary. For WAI docs, we will want to avoid that - and provide an email option. Request:Would it be OK to provide a template format to include GitHub and email, and just not make it a requirement? draft suggestion for Feedback section that includes both: Preferred: GitHub w3c/ai-web-impact — new issue, pull requests, open issues Related info:Example with email address (with wonky text formatting): https://www.w3.org/reports/identity-web-impact/ Here's an example of what we say in email announcements,:
|
Note that some groups are already using that format in the list of feedback options, e.g. https://www.w3.org/TR/rdf12-concepts/. Pubrules only checks that a link to the repository issues is provided. Other ways are optional and I don't think we want/can force groups to provide a mailing list. |
PubRules currently states:
I propose that we also provide an email address for feedback.
Rationale: Not everyone uses GitHub. It can comes across as exclusionary if the only way to provide feedback that is listed is GitHub — which is the opposite of what we want to convey.
An example that includes email: https://www.w3.org/reports/identity-web-impact/
The text was updated successfully, but these errors were encountered: