On Sun, Nov 13, 2016 at 11:36:52AM -0500, Hilmar Lapp wrote: > One thing I’d submit for consideration that could be learned from this and > change is to take the opportunity to put the text into Markdown (or LaTeX) > format and host it in version control. Then the version control system does > the diff, and presenting them, for you without any additional effort. > > Here’s an example from the most recent bylaws changes for OBF: > https://github.com/OBF/obf-docs/pull/28 > https://github.com/OBF/obf-docs/pull/29 > > I understand that many in SPI have strong reservations about Github, but > obviously Github is far from the only platform that allows doing this.
I think that the salient points, here, are: - use a plain text 'source' format for the input - use a source code management system to capture revisions and produce deltas - publish the deltas so that the members can easily review the proposed changes - use a formatter to 'compile' the input into published representation We can achieve the above wthout having to use github. I'm perfectly happy to use Markdown and I'd prefer it to LaTeX. -- Luca Filipozzi http://www.crowdrise.com/SupportDebian _______________________________________________ Spi-general mailing list Spi-general@lists.spi-inc.org http://lists.spi-inc.org/listinfo/spi-general
