Re: SPI bylaws overhaul: new discussion draft

From: Luca Filipozzi <lfilipoz(at)emyr(dot)net>
To: Hilmar Lapp <hlapp(at)drycafe(dot)net>
Cc: spi-general(at)lists(dot)spi-inc(dot)org
Subject: Re: SPI bylaws overhaul: new discussion draft
Date: 2016-11-16 02:27:00
Views: Raw Message | Whole Thread | Download mbox
Lists: spi-general

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:
> 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


Browse spi-general by date

  From Date Subject
Next Message Joshua D. Drake 2016-11-16 02:58:26 Re: SPI bylaws overhaul: new discussion draft
Previous Message Andrew Tridgell 2016-11-14 22:16:59 error in paypal accounting