<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Jared, thanks for the links you have been finding. I've captured
your resources for helping reduce the barrier to entry under a new
section:</p>
<p><a
href="https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Reduce_writer_barrier_to_entry">https://wiki.osgeo.org/wiki/Season_of_Docs_Ideas_2019#Reduce_writer_barrier_to_entry</a></p>
<div class="moz-cite-prefix">On 5/6/19 7:12 am, Jared Morgan wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFCxV16FTrOq_iST09NiYJNm-AsbDGZNsAe5xb5FCGvo0qwYkw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div>On the subject of learning git _concepts_ rather than
commands, check out <a
href="https://riedmann.dev/2019/06/02/GitGud.html"
moz-do-not-send="true">https://riedmann.dev/2019/06/02/GitGud.html</a>
<div dir="auto"><br>
</div>
<div dir="auto">It gives you the fundamentals about why you do
what you do in git, rather than just "Run this command,
because..."</div>
<div dir="auto"><br>
</div>
<div dir="auto">Just found it today in my Twitter feed, and
I'm sharing it here to see if this type of resource would
help demystify git for new contributors.</div>
<br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed., 29 May 2019,
22:56 matteo, <<a href="mailto:matteo.ghetta@gmail.com"
moz-do-not-send="true">matteo.ghetta@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Jared,<br>
<br>
> One thought would be implementing some type of
Git Flow for Docs.<br>
> I've posted a question on Write the Docs to see
if there is any<br>
> prior art on using Git Flow for docs
contributions. From what I<br>
> understand about the project, all docs changes
end up in GitHub, so<br>
> if this is an actual barrier for new folks, we'll
need to fix that. <br>
> <br>
> Git Flow might be a possible answer to this. It
is most likely not<br>
> the only answer.<br>
<br>
are you sure git flow is an answer to the workflow
difficulties? I'm<br>
afraid we are putting other entropy in the system that
might be<br>
difficult to manage (installing other software, conflicts,
etc). From my<br>
point of view the most difficult part for new comers is to
handle plain<br>
text (+images, rst syntax with links, substitution..) and
of course git.<br>
<br>
the complexity of the whole framework guarantees us a
clean history and<br>
I'm afraid we have to deal with this entrance barrier.<br>
</blockquote>
</div>
</div>
</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>