- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Sep 2022 18:38:11 +0000
- To: public-css-archive@w3.org
For new PostCSS plugins I have indeed adopted a `csstools-` prefix. But even within our org (csstools) we lack a guideline for this and plugins are still created that do not have this prefix. `-csstools-` as prefix that follows browser vendor prefix standards would also work, but we are not a browser vendor. This is not a popular choice and the first thing users do is open an issue requesting us to drop this prefix. But it is the right thing to do for the ecosystem. ------ I think the CSS WG is best suited to create general guidelines because it has the most reach and the best insights into these types of issues. If I create guidelines for the csstools org it only solves issues we create where I would like to see a more general solution. -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7150#issuecomment-1243019414 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 11 September 2022 18:38:12 UTC