<html><head></head><body>Markdown for the win! See, my idea of preferring Markdown in my Gopher client update was a perfect choice. Considering RFCs are also written in a similar syntax. Markdown is just so easy to read regardless if it's rendered as rich text or plain text. I actually never knew RFC documents were markdown compatible. Learn something new everyday.<br><br><div class="gmail_quote">On December 31, 2014 10:43:40 AM MST, Nick Matavka <n.theodore.matavka.files@gmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<p dir="ltr">I took a look at your suggestions and I am putting them under due consideration, as regards content. This is less about bringing Gopher up to date than it is about bringing the spec up to current practice. Essentially, we are writing in Latin but speaking in French; the RFC is only meant to translate our original document to French.</p>
<p dir="ltr">As regards format, please note that this is a MARKDOWN formatted resource. I will not consider re-flowing the text in any other format, unless the Markdown format continues to be authoritative. First of all, RFCs are in modified Markdown and I have already started the RFC process with the international people. Second, putting it in LaTeX or any other markup language means that it will be EVEN harder to read for those of us who are vintage computing freaks (not me, although I do use one of the later VT100 series for some things).</p>
<div class="gmail_quote">On Dec 31, 2014 6:09 AM, "Ciprian Dorin Craciun" <<a href="mailto:ciprian.craciun@gmail.com">ciprian.craciun@gmail.com</a>> wrote:<br type="attribution" /><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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 />
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 />
<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 />
</blockquote></div>
<p style="margin-top: 2.5em; margin-bottom: 1em; border-bottom: 1px solid #000"></p><pre class="k9mail"><hr /><br />Gopher-Project mailing list<br />Gopher-Project@lists.alioth.debian.org<br /><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>