MJM: community group uses markdown
... but potentially barrier to others?
... EOWG uses a form to make it easier
... that involves programming
KE: like the idea of providing a template
... not sure it needs to be a form but that would be easier
TB: is markdown a barrier because of the syntax or for validation issues?
MJM: syntax mostly
KE: think many people are intimidated by GitHub
SAZ: strongly recommend to reuse the same markdown as the CG, as the basis
... (1) it has been tested and a lot of thought went into it
... (2) the CG is probably the primary group to contribute rules at the start
... (3) we may be able to reuse scripts and functionality from the CG
... may be able to reuse the script from EOWG to have a form that translates entries into that markdown for those not comfortable with markdown
MJM: yes, script created markdown as an issue in GitHub
SAZ: can get in touch with Eric on that script
KE: doc is difficult?
SAZ: would need someone to translate that into markdown, HTML, or such
... or a script inside the doc
KE: understand we need to use GitHub but agree need to "hide" it as much as possible
TB: maybe a small script that can parse doc files
SAZ: something you can do?
TB: definitely can parse doc using Python
... not sure about the pull request or such
SAZ: will find out about the script and send out the information
... seems we should be able to have a web form at least
... if we are lucky, maybe also a doc parsing script
... also may be able to re-use documentation from the CG
<maryjom> https://www.w3.org/WAI/policies/submission/
<maryjom> That link is the submission form for accessibility laws and policies.
MJM: expecting issues and discussion for each rule
SAZ: think rule providers will be re-submitting rules
... that is, think less active development in this group
... trying to keep development outside (eg. community group or vendor etc.)
JC: Joe Croning, work for Amazon
... working on internal tools
... relevant group for me
MJM: standards program manager for IBM
... have internal tools too
KE: work for US Access Board
... develop of Trusted Tester
TB: work with MITRE
... more on the developer side but do some testing
SAZ: W3C staff contact for this group
MJM: mailing list we can use?
SAZ: easy to setup but probably want as much automation as possible
MJM: can we just have things uploaded, or do they need to be checked (eg. for virsus etc.)?
TB: check extensions and avoid .exe, .zip, etc.
SAZ: maybe can split and focus on HTML with subset of assets (eg. images, audio, video, etc.)
... opening up to all formats could get quite complex
... rules with other types of formats would need to go through a different route
https://github.com/w3c/wai-policies-prototype/blob/master/_policies/submission.php
MJM: already discussed, somewhat
MJM: typo
... editorial change
... but otherwise seems ready to go