- From: Kevin Babbitt via GitHub <sysbot+gh@w3.org>
- Date: Mon, 19 May 2025 22:07:55 +0000
- To: public-css-archive@w3.org
My observations: - The only consistent convention I've seen with issue naming is to prefix with the shortname(s) of the relevant spec(s) in brackets. One might argue that GitHub tagging is a cleaner way to relate issues to specs, though I do find it convenient to have shortnames in issue titles when I'm scanning email notifications. - I've seen issues that introduce new ideas or features both labeled "Proposal" and not. It doesn't appear to have a specific meaning other than when it's used to introduce a "proposed resolution" meaning "thing the author would like the working group to resolve on." I think a "good issue" contains the following elements: - Link to and/or quote of relevant existing spec text, where applicable - Description of what the author would like added, clarified, or changed, and why - Suggested changes if the issue author has something in mind already - Markup snippets / test cases / example renderings are usually quite helpful -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12200#issuecomment-2892399533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 19 May 2025 22:07:56 UTC