Since the policy is now in Markdown and in GitHub, could future changes be described in a pull request on GitHub rather than just a prose description on the Mozilla wiki? A pull request on GitHub would still allow for prose description of changes, but would also provide a nicely rendered diff of the changes.
As an example of this sort of thing for policy changes: https://github.com/GSA/https/pull/108 The "Commits" and "Files changed" tab each provide helpful information to quickly mentally parse the changes, and to see the granular history of why each thing changes. The Mozilla wiki could still document the history of changes, but by linking over to GitHub rather than embedding the changes directly. -- Eric On Wed, Nov 18, 2015 at 2:21 PM, Kathleen Wilson <[email protected]> wrote: > All, > > The work-in-progress for version 2.3 of Mozilla's CA Certificate Policy is > in github: > > master repo: https://github.com/mozilla/ca-policy > > The changes made so far are listed here: > > https://wiki.mozilla.org/CA:CertificatePolicyV2.3#Changes_Made_to_DRAFT_Version_2.3 > > Additionally, the policy has been converted to Markdown. > > To see what the updated policy looks like so far: > http://mozilla.github.io/ca-policy/ > > Kathleen > _______________________________________________ > dev-security-policy mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-security-policy > -- konklone.com | @konklone <https://twitter.com/konklone> _______________________________________________ dev-security-policy mailing list [email protected] https://lists.mozilla.org/listinfo/dev-security-policy
