You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@training.apache.org by "Johannes Tigges (JIRA)" <ji...@apache.org> on 2019/08/01 13:56:00 UTC

[jira] [Commented] (TRAINING-19) Github Beginner Level Training material

    [ https://issues.apache.org/jira/browse/TRAINING-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898105#comment-16898105 ] 

Johannes Tigges commented on TRAINING-19:
-----------------------------------------

Thanks to [~isabel] for pointing me at this slide-set.

I took a look at it, compared it my personal experiences in that area and came up with a bunch of suggestions.
 * Slide 11: Material that enables people to think about READMEs, possble content and wishes potential readers could have turned out to be rather useful at my site. The workshop approach is better though. Maybe preparing something that enables people to do such a small "workshop" would also be useful.
 * Slide 17,18,19: Had internal links.
 * Slide 23-30:
 ** That would really have been useful. 29+30 could use some additional explanatory notes, either in the speakers notes or on the slides, depending on the use case.
 ** Explaining the motivation of why it can be advantageous to not give everyone complete access rights but work with forks and cross-fork PR's should be explicitly given and explained. I had this questions repeatedly (could be e.g. scaling due to less administrative mess)
 *** Sometimes people used the mental model of SVN on Git and used it accordingly. Sometimes they were only partially interested in what Git actually is and how it works. Thus, explicitly give the difference and why that is an advantage to them that they would want in their daily lives. Sell it like its mid/late 2000s. ;)
 *** Also, broken organizational artefacts can lead to people using it a la SVN. Try to understand what brought them there and what keeps them.
 *** SVN isn't bad, it's just not Git and dissimilar in many of the concepts underpinning it.
 ** Slide 32-42 are great but to make these slides more useful for people not entirely aware of what happens there or what to tell having notes in the speakers notes would be great. Subtitles if you will ;)
 ** Slide 45+46: Great, I would give a few wors about the semantics of indexing from HEAD~. You have that in Slide 63.
 ** Slide 68: There used to be external review tools for GitHub. The internal ones evolved quite a lot. Do people still use the external ones to a relevant degree? I still like some aspects of Gerrit review workflow and GitLab has a few nice extra points, but maybe some of them will find their way into GitHub over time.
 ** Slide 70: For CLI purposes I like [Jonas' tig|https://github.com/jonas/tig], for GUI purposes the IDE internal tooling would come to mind and the great but totally non-OSS SourceTree from Atlassian. Maybe point to a list of existing tools. Is there a maintained awesome-list for these tools?
 ** Slide 82: an -> and: Typo. Also, I would illustrate the magic keyword function with a screenshot.

Overall:
 * A very cool slide set.
 * I would consider adding a slide that mentions the existence of the other similar systems (GitLab, Gitea) and their similarity in concept.
 ** One could briefly mention that there are more different but on a higher-level similar tools such as Gerrit.
 * Also I would add a slide welcoming additions or modifications for other GitHub equivalent systems such as Gitea or GitLab.

> Github Beginner Level Training material
> ---------------------------------------
>
>                 Key: TRAINING-19
>                 URL: https://issues.apache.org/jira/browse/TRAINING-19
>             Project: Apache Training
>          Issue Type: New Feature
>            Reporter: Isabel Drost-Fromm
>            Priority: Major
>
> A couple weeks ago we ran a Github training at Europace. As most of what we explained there is based on the concept of Inner Source which itself is fairly close to the Apache Way I thought it might make sense to submit an adapted version here.
> Caveat: Slides currently live in Google Slides. So we'd need to figure out how best to convert them into a format the works for you.
> Caveat 2: Most of the Slides contain only graphics.
>  
> I'll need to go over them and translate from German to English anyway, however I'd rather do that only once ;)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)