<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Documentation forked here:
<a class="moz-txt-link-freetext" href="https://github.com/gridcf/gct-documentation">https://github.com/gridcf/gct-documentation</a><br>
<br>
<div class="moz-cite-prefix">On 12/07/2017 11:26 AM, Brian Lin
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:27658bda-dda5-5089-f46a-65033a02f629@cs.wisc.edu">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Hi,<br>
<br>
I agree. I don't think a vote is necessary and a simple fork will
do. I think the most important thing to do is just get the latest
version of the docs available since we can always trim
old/unnecessary information at a later date.<br>
<br>
We could always run whichever SSG we choose in Travis and push to
Github Pages. We use this strategy with mkdocs in the OSG.<br>
<br>
- Brian<br>
<br>
<div class="moz-cite-prefix">On 12/07/2017 09:56 AM, Mischa Salle
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20171207155635.br3gqqytqf2znuby@nikhef.nl">
<pre wrap="">Hi,
On Thu, Dec 07, 2017 at 11:58:26AM +0100, Frank Scheiner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Should we call for a vote about the adoption of the GT documentation or can
we consider this part of the original Globus Toolkit and hence agreement to
adoption is implicit?
</pre>
</blockquote>
<pre wrap="">I don't think anyone would disagree, so a vote seems not necessary.
</pre>
<blockquote type="cite">
<pre wrap="">## Fork ##
Anyway I suggest to fork the same way as it was done for the Globus Toolkit,
because then the search functionality on GitHub will also work in our forked
code base. Comes in handy sometimes.
</pre>
</blockquote>
<pre wrap="">We could make it a 'simple' fork directly from github (which will show
up as 'forked from' and provides info on 'X commits behind / ahead). Or
do it from a cmdline, and set the other as upstream, without github
knowing about that. For gct we did the latter I think (as in
<a class="moz-txt-link-freetext" href="https://help.github.com/articles/duplicating-a-repository/" moz-do-not-send="true">https://help.github.com/articles/duplicating-a-repository/</a>)
</pre>
<blockquote type="cite">
<pre wrap="">## Old/unneeded information ##
There might be some or even a lot of information in the
globus-toolkit-documentation that could be unneeded for our means, hence we
could start a new branch in our fork and just import the needed information
there. After everything is in shape, we could change the default branch for
this repo to the new branch.
</pre>
</blockquote>
<pre wrap="">I would probably do that: fork and make a new branch to work on.
</pre>
<blockquote type="cite">
<pre wrap="">## Resulting documentation ##
For the "finalized" documentation I'm yet undecided:
* GitBook
* ReadTheDocs
* GitHub pages
The first two have the advantage to include search functionality, but there
also seem to be "solutions" available that - with some manual work - provide
search functionality within GitHub pages, too, e.g. [Jekyll Tipue Search].
</pre>
</blockquote>
<pre wrap="">I think github + readthedocs is a relatively straightforward way. For
Argus some people have also done that, see
<a class="moz-txt-link-freetext" href="https://github.com/argus-authz/argus-documentation/tree/master/source" moz-do-not-send="true">https://github.com/argus-authz/argus-documentation/tree/master/source</a>
and
<a class="moz-txt-link-freetext" href="http://argus-documentation.readthedocs.io/en/stable/" moz-do-not-send="true">http://argus-documentation.readthedocs.io/en/stable/</a>
it seems relatively straightforward. I have no strong preference as long
as it is relatively mainstream, to make it easier for people to work
with it and to have some trust in sustainability.
I personally don't know whether you could do things as a organization, I
think you can, I could ask around...
Cheers,
Mischa
</pre>
<blockquote type="cite">
<pre wrap="">[Jekyll Tipue Search]: <a class="moz-txt-link-freetext" href="https://github.com/jekylltools/jekyll-tipuesearch" moz-do-not-send="true">https://github.com/jekylltools/jekyll-tipuesearch</a>)
In any case I created accounts on GitBook (gridcf as organization) and
ReadTheDocs (gridcf as personal account - no organizations possible or I
didn't find the relevant information) we can use.
Cheers,
Frank
On 12/06/2017 08:37 PM, Mátyás Selmeci wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Who's going to do this?
-Mat
On 11/30/2017 10:29 AM, Brian Lin wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Perfect, it sounds like we should fork this into the gct
organization! Once that's done, it should be trivial to generate the
HTML out of the asciidocs source and push them to github pages.
- Brian
On 11/30/2017 03:09 AM, Frank Scheiner wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 11/30/2017 10:07 AM, Oliver Keeble wrote:
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">"Translating" from AsciiDoc to Markdown should be even
easier, but where can the AsciiDoc sources be found?
</pre>
</blockquote>
<pre wrap="">In the docs git repo, e.g. the text files here;
<a class="moz-txt-link-freetext" href="https://github.com/globus/globus-toolkit-documentation/tree/master/toolkit/docs/6.0/gridftp" moz-do-not-send="true">https://github.com/globus/globus-toolkit-documentation/tree/master/toolkit/docs/6.0/gridftp</a>
</pre>
</blockquote>
<pre wrap="">
Thanks for the pointer. :-)
Cheers,
Frank
</pre>
</blockquote>
</blockquote>
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu" moz-do-not-send="true">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos" moz-do-not-send="true">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<pre wrap="">--
Frank Scheiner
High Performance Computing Center Stuttgart (HLRS)
Department Project User Management & Accounting
Email: <a class="moz-txt-link-abbreviated" href="mailto:scheiner@hlrs.de" moz-do-not-send="true">scheiner@hlrs.de</a>
Phone: +49 711 685 68039
</pre>
</blockquote>
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu" moz-do-not-send="true">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos" moz-do-not-send="true">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu" moz-do-not-send="true">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos" moz-do-not-send="true">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gt-eos mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gt-eos@mailman.egi.eu">Gt-eos@mailman.egi.eu</a>
<a class="moz-txt-link-freetext" href="http://mailman.egi.eu/mailman/listinfo/gt-eos">http://mailman.egi.eu/mailman/listinfo/gt-eos</a>
</pre>
</blockquote>
<br>
</body>
</html>