From: | Bdale Garbee <bdale(at)gag(dot)com> |
---|---|
To: | Filipus Klutiero <chealer(at)gmail(dot)com>, spi-general(at)lists(dot)spi-inc(dot)org |
Subject: | Re: Issue #2 - Allow contributions to website from browser |
Date: | 2016-08-19 02:53:02 |
Message-ID: | 87shu1v59t.fsf@rover.gag.com |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
Filipus Klutiero <chealer(at)gmail(dot)com> writes:
> While having to learn a new syntax is already quite a disadvantage, at
> least for me
It is for all of us... which is exactly why we moved to the ikiwiki+git
combination... because at least at the time it used technology and
skills that all of the board members were comfortable with, and enabling
ourselves to be able to more easily contribute to the web content was a
higher priority than enabling "others" who might not have the same
skills to do so.
It's entirely possible to enable in-place editing of ikiwiki content
through a browser interface, retaining the git revision control back
end. There are some security implications for enabling this
functionality, as there is with just about any web-server based access
mechanism. Whether the SPI admin team thinks they are acceptable risks
is something only they can answer.
Frankly, though, the fact that anyone can install the ikiwiki processor
locally and apply it to a checked out copy of the web content git
repository means that it may just be a better plan to assume that anyone
who wants to contribute will be willing to "figure things out"...
Bdale
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2016-08-19 14:40:49 | Re: Issue #2 - Allow contributions to website from browser |
Previous Message | Filipus Klutiero | 2016-08-19 01:51:49 | Re: Issue #2 - Allow contributions to website from browser |