<div dir="ltr"><div>I have given your suggested changes due consideration, and I have decided to implement the majority of them. Ciprian, please inform me if there is anything else that lacks clarity.<br><br>For anyone who has come into the discussion late, please note that the updated file is available at <a href="http://piratepad.net/gopher">http://piratepad.net/gopher</a><br><br></div>Edward Matavka<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 31 December 2014 at 06:07, Ciprian Dorin Craciun <span dir="ltr"><<a href="mailto:ciprian.craciun@gmail.com" target="_blank">ciprian.craciun@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Dec 29, 2014 at 10:15 PM, Nick Matavka<br>
<<a href="mailto:n.theodore.matavka.files@gmail.com">n.theodore.matavka.files@gmail.com</a>> wrote:<br>
> I now believe that consensus *can* be established and therefore I re-submit<br>
> the same link. Please edit it and comment to the best of your ability. I<br>
> hope to actually submit this in the near future.<br>
><br>
> <a href="http://piratepad.net/gopher" target="_blank">http://piratepad.net/gopher</a><br>
<br>
<br>
</span>I've given the document a quick read, and made a few comments (and<br>
proposals) that I think would fit nicely in an updated Gopher RFC.<br>
They can be found at the following link:<br>
<br>
<a href="http://wiki.volution.ro/CiprianDorinCraciun/Notes/Public/Gopher/RfcUpdateProposal" target="_blank">http://wiki.volution.ro/CiprianDorinCraciun/Notes/Public/Gopher/RfcUpdateProposal</a><br>
<br>
<br>
(Disclaimer: I didn't have internet access (or a computer) during the<br>
"golden age" of Gopher, I'm not a frequent user of Gopher, neither do<br>
I actively run a Gopher server. However I did read Gopher's history,<br>
and early web, and followed this mailing list since a few years back.<br>
Moreover I just wrote a Go-based Gopher server, soon to be released,<br>
and I do have a computer-science / research background.)<br>
<br>
<br>
Regarding the text format of the proposal, I think it's quite hard to<br>
follow, especially in the EtherPad coloured version. Perhaps the<br>
document can easily be changed to use RestructuredText, and then<br>
exported to HTML for readability. Moreover the sections (and / or<br>
actual paragraphs) could be numbered to allow referencing to them<br>
while commenting (without modifying the actual text). (Obviously when<br>
removing an entire paragraph its identifier should not be reused.)<br>
<br>
Regarding the "workflow", perhaps using a versioning system like Git<br>
or Mercurial would work better as the editors would have access to<br>
proper diffs, history, and especially merges. Moreover using<br>
something like GitHub or BitBucket allows both "on-line" editing and<br>
automatic rendering (of RestrucutredText) as HTML for reading.<br>
<br>
(I could offer to solve the last two problems of formatting to<br>
RestructuredText, splitting the text into one file per section, and<br>
preparing a Git repository, plus the needed Make script to export the<br>
document as HTML.)<br>
<br>
Hope it helps,<br>
Ciprian.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"> /^\/^\<br> \----|<br> _---'---~~~~-_ <br> ~~~|~~L~|~~~~<br> (/_ /~~--<br> \~ \ / /~<br> __~\ ~ / ~~----,<br> \ | | / \ <br> /| |/ | |<br> | | | o o /~ | <br> _-~_ | || \ /<br> (// )) | o o \\---'<br> //_- | | \ <br>// |____|\______\__\<br>~ | / | |<br> |_ / \ _|<br> /~___| /____\ <br></div>
</div>