[SeasonOfDocs] How should we focus OSGeo training within SeasonOfDocs?

[Jared Morgan]

On the subject of learning git _concepts_ rather than commands, check out
https://riedmann.dev/2019/06/02/GitGud.html

It gives you the fundamentals about why you do what you do in git, rather
than just "Run this command, because..."

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.


On Wed., 29 May 2019, 22:56 matteo, <matteo.ghetta at gmail.com> wrote:

> Hi Jared,
>
> >     One thought would be implementing some type of Git Flow for Docs.
> >     I've posted a question on Write the Docs to see if there is any
> >     prior art on using Git Flow for docs contributions. From what I
> >     understand about the project, all docs changes end up in GitHub, so
> >     if this is an actual barrier for new folks, we'll need to fix that.
> >
> >     Git Flow might be a possible answer to this. It is most likely not
> >     the only answer.
>
> are you sure git flow is an answer to the workflow difficulties? I'm
> afraid we are putting other entropy in the system that might be
> difficult to manage (installing other software, conflicts, etc). From my
> point of view the most difficult part for new comers is to handle plain
> text (+images, rst syntax with links, substitution..) and of course git.
>
> the complexity of the whole framework guarantees us a clean history and
> I'm afraid we have to deal with this entrance barrier.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/seasonofdocs/attachments/20190605/99c57368/attachment.html>