14
edits
(Added questions) |
|||
Line 8: | Line 8: | ||
==Patch generation and submission== | ==Patch generation and submission== | ||
Once editing is finished, a single button (with a Bugzilla login) should let you generate and submit a patch. This should include a human-written summary of the patch, with the patch itself and a link to preview what the docs will look like on MDN. | Once editing is finished, a single button (with a Bugzilla login) should let you generate and submit a patch. This should include a human-written summary of the patch, with the patch itself and a link to preview what the docs will look like on MDN. | ||
==Questions== | |||
* How will translations fit into this tool? | |||
* How to keep the process simple, make it easy for people to contribute? | |||
* Do we continue to document removed methods etc as we currently do? | |||
** If so how will the tool manage this? | |||
** It would probably be easiest to just generate documentation for each Gecko version individually and the site would allow selecting the Gecko version to view, and possibly a diff between versions. |
edits