Open source developement cource

I have participated the first 2 classes of an Open source developement cource, by @szabgab

Gabor SzaboFollow

Helping individuals and teams improve their software development practices. Introducing testing, test automation, CI, CD, pair programming. That neighborhood.

Here you can see the Cource descrioption

all the updates sit here in a github repo

And he also created a practice website which we can update

I recently posted some of the cource info Here, in hashnode, But ever since I realized that in dev.to you can write markdown, and easily tag people you know, I moved here.

I also reallized, that most of the cource participants are write here. so I guest most of our small comunity activities will be from here..

I think it is written in jekyll, but I am not sure yet..

Another participent in this class is @shulyavraham, and we sometimes assist eachother with homework. which is allot!!.

She wrote a wonderfull post, explaining the contents of this cource. you can click here to see her post

OSDC Course with Gabor

ShulyAvraham ・ Jan 9 ・ 1 min read

Here are another perspective about this cource from another participant

Thus The New Journey Begins

Alex M. Schapelle ・ Jan 11 ・ 1 min read

#opensource #leadership #learn

Here are some of the insights and concepts learned in the first 2 lessons:

• repository: is a collention of files and directories, kept in the cloud..
• git: a way to keep version controll for changes in a repository. each repository has an owner and right and read permission settings
• branch: a division for new version for new developement
• commit: any change made and uploaded to the repository, each commit is saved and can be restored
• fork: a copy of another owner's repository, to a personal repository

• pull request: once you want to make changes in someone elses repo, you need to commit it to your own fork,and then send a pull request to the original repo

• github: it is a web ui that helps managing repositories

• issue: a list of comments created by users , stating issues that need to be resolved

• commit hashkey: when creating an issue, you can link a specific commit, identified by it's hashkey, so other users can know what is is about.

• issue-id: same as commit hashkey, you can link an issue while commenting in a commit, so users can know the issue is taken care of in this commit.

Comments

[kobkob2018]

In this article, she writes interesting stuff about pull requests:

osdc-2023-assignment1

anatlavitzkovitz ・ Jan 9 ・ 2 min read

#git