publishes documents that define #Web technologies. These documents follow a process designed to promote #consensus, fairness, public accountability, and quality. w3.org/Consortium/Process/
1
's publication process follows strict rules enforced by publication rules (aka, pubrules) w3.org/pubrules/ and depends on the webmaster's availability. This often introduces delays in the publication that Echidna can reduce.
1
Echidna was built to speed up the process as much as possible by removing tasks that can be automated by a machine. This way, @w3c's #WorkingGroups can easily publish and make sure /TR shows an updated view of their work.
1
1
Since the beginning of July, it is possible to publish #CandidateRecommendation with Echidna. nitter.vloup.ch/marcosc/status/1…
Jul 24, 2018 · 2:04 PM UTC
1
Transitions requests should be submitted to github.com/w3c/transitions/i… and approved by the Directors and the W3C Communication team beforehand.
1
After submitting a document, Echidna runs a couple checks (quality, security, etc.) before publishing. @w3c's Echidna makes it easy to publish a new version of specifications after each modification. This way, readers are getting up-to-date documents.
1
In the future, we expect Echnida to support more types of @w3c specifications. See the full list of documents' transitions at w3.org/pubrules/doc
1
1
1
Echidna is also an open source project hosted on #github: github.com/w3c/echidna. We welcome any contributions/suggestions!
1
2