Proposed - Lesson 1 - What is Open Source / GitHub

[jduckles]

Develop a "zero-entry" lesson that helps community members de-mystify jargon and terminology.

Additionally prepare them to make the first-steps toward being a contributor using GitHub.

Key Outcomes:

• Learners understand tools used within the Catalyst Community to organize effort and information (focusing quite a bit on GitHub)
• Learners have signed up for a GitHub account so they are able to contribute
• Learners are invited to make a simple contribution, (ie comment on an issue)

In order to improve this lesson, I have a few open questinons to Catalyst School community members:

• What are some other key outcomes you'd like to see from this lesson?
• What confused you about tooling when you entered the Catalyst community?
• What do you wish you had known about Git/GitHub that you had to figure out on your own?

(please enter your thoughts below in response to this issue)

[cauechianca]

What are some other key outcomes you'd like to see from this lesson? . .A mini-tutorial on how to explore projects (for experimenting until next lesson) . What confused you about tooling when you entered the Catalyst community? . .Not having a starting place to explore the basic. Information is disperse. . What do you wish you had known about Git/GitHub that you had to figure out on your own? . .The basic architecture on setting up a repository [Branches, Forks, etc...]. .

[mark-stopka]

Develop a "zero-entry" lesson that helps community members de-mystify jargon and terminology such as open source, Git, GitHub, Kanban, Trello Board, Jira, etc.

Terms like Kanban (Agile project management), Trello (software implementing kanban board), and Jira (closed source project management tool), have very little to do with open-source.

Other important topics such as licensing scheme (copyright vs. copyleft) should probably be explained. I also think it is much more important to explain people how to write a good bug report, as opposed to teaching them how make forks and branches in lesson one, as @cauechianca is suggesting.

Most people with some programming experince will already know how to do branches and forks, and those who lack that experince will have very little if any benefit from learning branching and forking, and would be better off spending a little time learning some basic coding, so then they can learn how to work with code in lesson 2 of the training.

This resource may help you get overview of most licenses out there.

[DanM3rcurius]

In order to improve this lesson, I have a few open questinons to Catalyst School community members: What are some other key outcomes you'd like to see from this lesson?

basic markdown syntax (and where to find more); understanding what a versioning control system is

What confused you about tooling when you entered the Catalyst community?

The huge amount of different communication channels

What do you wish you had known about Git/GitHub that you had to figure out on your own?

That I should never write texts, code or anything longer than 2 sentences directly into the web forms of GitHub, but use Git via console or GitHub Desktop or simply a text edit tool.