<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>While TheGoodDocs project will be selecting Markdown for its main
writing templates, this is because they are both widely used and
the most limiting of formats (so we can service other markdown
types more easily.)<br>
</p>
<p>However, from my experience with the OSGeoLive project, I've
noticed that all, or (or almost all) of the OSGeo stack of
software use RST, which is a richer format. As GeoNetwork is often
bundled with other projects (such as within GeoNode), I'd suggest
continuing to use the same RST format as others in order to
support doc integration.</p>
<p>At the very least, consult with the other projects first before
moving.</p>
<p>Cheers, Cameron<br>
</p>
<div class="moz-cite-prefix">On 8/11/19 2:55 am, Byron Cochrane
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:55CAC213-11AB-478B-86B4-04ECD34D29E9@openwork.nz">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Sorry I missed the meeting.
<div>Bit crazy around here. Will catch you next time </div>
<div><br>
</div>
<div>Byron <br>
<br>
<div id="AppleMailSignature" dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
On 7/11/2019, at 11:58 PM, Jo Cook <<a
href="mailto:jo.k.cook@gmail.com" moz-do-not-send="true">jo.k.cook@gmail.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div dir="ltr">
<div>Hi List,</div>
<div><br>
</div>
<div>We had a short meeting about the GeoNetwork Season of
Docs project today, attended by myself and Paul van
Genuchten. <br>
</div>
<div><br>
</div>
<div>Main topics:</div>
<div><br>
</div>
<div>* Discussions about switching the GeoNetwork
documentation from re-structured text format to
markdown. There are pros and cons to both- markdown is
generally easier for new contributors, but has less
functionality. Switching will also mean losing the
current document history. It would need to happen at a
key release (eg GeoNetwork 4) to minimise problems in
this regard. <br>
</div>
<div><br>
</div>
<div>* Good ways to mark up limitations in the current
documentation- I've been creating issues for pages that
need attention, titled (for example) "Changelog Review
(3.x): [Page] with [problem]". It's important to tie
this in to the review spreadsheet that Byron put
together.</div>
<div><br>
</div>
<div>Next meeting date: November 21st- here's the meeting
link: <a
href="https://calendar.google.com/event?action=TEMPLATE&tmeid=NXA0dG9lYTJwaWc1bm8xYm5rZnE0NGY0dWtfMjAxOTExMjFUMTAwMDAwWiBqby5rLmNvb2tAbQ&tmsrc=jo.k.cook%40gmail.com&scp=ALL"
moz-do-not-send="true">https://calendar.google.com/event?action=TEMPLATE&tmeid=NXA0dG9lYTJwaWc1bm8xYm5rZnE0NGY0dWtfMjAxOTExMjFUMTAwMDAwWiBqby5rLmNvb2tAbQ&tmsrc=jo.k.cook%40gmail.com&scp=ALL</a></div>
<div><br>
</div>
<div>Regards</div>
<div><br>
</div>
<div>Jo<br>
</div>
<div><br>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">------------------------<br>
<a href="http://about.me/jocook" target="_blank"
moz-do-not-send="true">http://about.me/jocook</a></div>
</div>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr"><span>_______________________________________________</span><br>
<span>SeasonOfDocs mailing list</span><br>
<span><a href="mailto:SeasonOfDocs@lists.osgeo.org"
moz-do-not-send="true">SeasonOfDocs@lists.osgeo.org</a></span><br>
<span><a
href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs"
moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a></span><br>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
SeasonOfDocs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SeasonOfDocs@lists.osgeo.org">SeasonOfDocs@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/seasonofdocs">https://lists.osgeo.org/mailman/listinfo/seasonofdocs</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Cameron Shorter
Technology Demystifier
Open Technologies and Geospatial Consultant
M +61 (0) 419 142 254</pre>
</body>
</html>