Skip to content

OSDC-Code-Maven/osdc-2023-03-azrieli

BranchesTags

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

159 Commits
.github/workflows
.github/workflows
 
 
mentors
mentors
 
 
participants
participants
 
 
.gitignore
.gitignore
 
 
LICENSE
LICENSE
 
 
README.md
README.md
 
 
course.json
course.json
 
 

Repository files navigation

OSDC 2023.03 Azrieli

  • site

  • Start day: 2023.03.09

  • Meetings: Every Thursday 12:15-14:45

  • Last meeting: 2023.06.22

TOC

Videos

Session 1: Welcome, Version Control, Journal, Slack

  • Welcome

  • About the course:

    • Goal: Become familiar with tools and processes used for software development both in the industry and in the academic institutions through contribution to open source projects.
    • List of tools we learn, they are all used in both academy and corporation, they could be used better in both places.
    • Overview of the course
      • Slack
      • git
      • GitHub
        • Issues
        • Pull Request
        • Pages
        • Actions
      • (GitLab)
      • Markdown (journal, issues, etc.)
      • Docker
      • Testing
      • Static analysis
    • End results:
      • Blog posts (journal entries)
      • Personal web site
      • Issues (tickets) opened on various projects
      • Pull-Requests sent to various projects
      • Development of a personal open source project

  • About myself:

    • Self employed
    • Training
    • Introducing testing, CI etc. to teams in corporations.

  • Assignments:

    • Will be in some public GitHub or GitLab repositories.
    • At the end of each assignment you'll write a report - a blog post / journal entry.
    • You will add the link of your blog post to your personal JSON file and send a Pull-Request with the change. (We'll learn these soon)
    • Video timestamping: Every week two people have to "timestamp" the videos. You can pick a video you'd like to do. If no-one volunteers to do one of the videos I'll pick from the names so by the end of the semester everyone will do approximately the same number of videos.
    • First few assignments will be to my projects. This allows for quick feedback and integration.
    • Then to each others projects. This still allows for quick feedback.
    • Then we'll find you open source projects maintained by other people. For these I might be able to give feedback, but I cannot integrate them.

  • Grades:

    • Grades are based on the work done during the course.
    • There is no end-project or exam at the end.
    • Each week you'll get a grade of 0-100 and we'll have an average of them at the end of the semester.

  • How and why to blog/journal?

    • DEV.to
    • Use Markdown.
    • Use visual editor of DEV (Switch at Customization / Writing)
    • Create series.
    • Add #osdc tag
    • The importance of linking and link anchors.

  • Why use version control?

  • What is JSON.

  • Pull request to add JSON, show drawing.

  • Use the cm-demo account to add entry to participant.

  • About GitHub Actions: they are programs triggered by some action. In this case by a pull request.

  • Video 1-1: (Yael Levy)

    • 00:00 About the course
    • 04:28 Overview of the course
    • 18:46 About Gabor Szabo
    • 20:15 Assignments
    • 23:05 Video timestamping
    • 31:20 Grades
    • 35:20 Blog posting
    • 35:49 Dev.to
    • 36:15 Post editor
    • 39:18 Published
    • 39:39 Description
    • 40:10 Tags
    • 48:28 Text in markdown

  • Video 1-2: (Eliyahou Levy)

    • 00:00 Forem issues to solve bug
    • 06:50 Inbound links
    • 08:44 Version control
    • 11:22 Json
    • 14:36 Add json participant by pull request
    • 16:30 Fork
    • 25:35 Create pull request
    • 27:40 Workflow
    • 28:40 Approve pull request
    • 30:00 Error handling
    • 36:30 Squash and merge pull request
    • 37:43 Actions
    • 39:02 Exercise definition-send pull request
    • 42:50 Add comment

Assignment 1

  • Create GitHub account if you don't have one yet.

  • Add an image or an avatar to your GitHub account.

  • Add your JSON to our repository to the `participants/' folder.

  • List interesting projects in the JSON file.

  • Follow this git repository. Follow a number of other GitHub repositories that you find interesting or that you use.

  • Write a blog post about this on DEV.to

  • Include the link of the article in the JSON file.

  • Dead-line: 2023.03.14 midnight.

Session 2: Finding projects, git workflows, ci, yaml

2023.03.16 12:15-14:30

  • Go over all the PRs people opened and the Issue I opened on our GitHub repository.

    • Fix issue in PR instead of opening new one (show it)
    • Mentioning commits in issues and issues in commits.

  • Blogging: linking, more details!

  • Ask to get the Video timestamping earlier.

  • Show how to follow projects on GitHub to get notifications.

  • The structure of a Github URL : https://github.com/(username|organization)

  • How to find a git repo of a project?

  • What are yaml files See the repo and the site

  • Video 2-1: (Freddy Adiv)

    • 00:00 Recap of last session
    • 07:25 Dev.to - navigation using tags
    • 15:57 Opening issues in git
    • 19:00 Issues and pull requests
    • 30:55 Sample for real project interaction for Forem
    • 42:10 Git project concepts, Forking and committing

  • Video 2-2: (Freddy Adiv)

    • 00:00 Locking files in version control - pros and cons
    • 02:50 Following a project and notifications in Git
    • 05:35 Ranking mechanism of projects
    • 06:10 Structure of Git URLs, projects/ organizations/ repos
    • 15:01 3rd party packages registry
    • 17:45 Open source by organizations
    • 21:35 YAML file format
    • 31:15 Adding a new organization using YAML
    • 50:22 Assignments

Assignment 2

  • Add (more) projects you are interested in.

  • Follow our project

  • Follow my projects

  • Follow each other's projects.

  • Convert 5 more organizations to yaml files.

  • Find more organizations. (more github organizations belonging to governments, universities, or corporations that are not even in the md files yet. I realize that converting the md files to yaml files should be probably the priority for this project so it might be better to do a few more of that.)

  • Write a blog post (tag with #osdc, notes, links, etc.)

  • Send a PR to add your blog post to your JSON file.

  • Dead-line: 2023.03.21 midnight.

Session 3: Github Pages; Markdown

Date: 2023.03.23 13:30-14:30

  • Create Github pages.

  • Markdown.

  • Introduce git client.

    • Setup local git configure, clone, add, commit, etc.

  • Download and install the git client from git-scm

  • In Windows, start the git-bash application

  • On Github create the USERNAME.github.io repository (with your USERNAME)

git clone [email protected]:cm-demo/cm-demo.github.io.git
cd cm-demo.github.io

mkdir docs
    Create the file docs/index.md
git add .
git commit -m "first file"

Configure the git client (if it is not configured yet)

git config --global --add user.name "Foo Bar"
git config --global --add user.email [email protected]

cat ~/.gitconfig

Create private/public key pair. put the public key in your github account.

ssh-keygen

git commit --amend --reset-author -m "first commit"

git log

git status
git add docs/index.md
git commit -m "add more content"
git push
  • Video 3-1: Ran Moshe
    • 00:00 Windows - Oracle VM VirtualeBox
    • 07:40 Back to local linux PC
    • 07:50 Create repository for Github pages site (on Github)
    • 09:11 Clone for create repository locally (on PC)
    • 13:00 Download and install the git client from git-scm
    • 15:05 In Windows, git-bash application
    • 17:24 Setup local git configure (add, commit, config, etc.)
    • 29:35 Create private/public key pair
    • 35:10 Push changes (git push)
    • 39:45 Config github.io repository (on Github-settings)
    • 42:38 Creating the Github page using Markdown
    • 44:30 Push more changes (git status, add, commit, log. etc.)
    • 47:50 The Github page after changes
    • 48:45 Adding images to our Github page (add another file)
    • 52:00 Push images and more changes (git status, add, commit, etc.)
    • 54:23 Jekyll (from Markdown to Github)
    • 55:30 Assignments

Assignment 3

  • Create a web site using GitHub pages, with cv, image, projects. Link to the course site, link to your blog. Use this to show a lot more interesting information about yourself to both your future employer, but also to friends and family. Check out what others in the other course did for inspiration.

  • Write a blog post about what you did, link it to the course web site, to your own new web site, to the pull-requests you made.

  • Update your JSON file with the new blog post and also add an entry of "github_page": true to your JSON file if it is not there yet.

  • Dead-line: 2023.03.28 midnight.

Session 4: PyDigger, updating meta data of a Python project

Date: 2023.03.30 13:30-14:30

  • We looked at the PyDigger web site and the Stats page from where we had links to

  • projects have link to VCS but no license field

  • projects have link to VCS but no author field

  • projects have link to VCS but no summary

  • projects where PyDigger did not find VCS

  • We looked at pypi page of numpy

  • We sent this Pull-Request

  • We found that the mrflagly project was missing the author field from the meta-data.

  • We went to its GitHub repository, found that it was using pyproject.toml and found the name and email of the author.

  • pyproject.toml file specification

  • We also looked at pglib and saw that it is hosted on GitLab.

  • The licenses page on PyDigger was fixed a few hours before the lecture.

  • OSI approved Open Source licenses.

  • I mentioned the recommended books listed at the bottom of the OSDC main page. Especially I mentioned the one I am reading now Uncurled by Daniel Stenberg, author of curl.

  • Video 4-1: Ran Moshe

    • 00:00 PyDigger and pypi.org (Introduction)
    • 03:00 last updates of pypi (show in CLI- use grep & ack to get the relevant url)
    • 04:45 PyDigger-Statistics
    • 06:30 No VCS (PyDigger-Statistics)
    • 07:50 CI (PyDigger-Statistics)
    • 09:30 Has VCS (PyDigger-Statistics)
    • 11:05 Has VCS license (PyDigger-Statistics)
    • 12:35 Has VCS author (PyDigger-Statistics)
    • 13:30 mrflalgy (example-Has VCS but no author)
    • 14:40 pyproject.toml author field
    • 20:00 Explain about pyproject.toml file & sending PR (mrflalgy- example)
    • 32:20 types-pytz (example-Has VCS but no author)
    • 34:50 pglib (example-Has VCS but no author (GitLab & setup.cfg file))
    • 37:00 Has VCS summary (PyDigger-Statistics)
    • 41:00 Adyen (example-Has VCS but no license)
    • 41:56 Details Licenses page (PyDigger-Statistics)
    • 45:10 Recommended books listed
    • 46:10 open source initiative
    • 51:00 searchkit (example-no VCS)
    • 55:15 Assignments

Assignment 4

Find 5 (was 10) projects via PyDigger that have no author, not license, or no VCS. Add the missing information and send a pull-request. In the Pull-Request mention that you found the package missing this information via PyDigger, that you are sending it as part of the OSDC, and mention me as well: @szabgab

  • Dead-line: 2023.03.28 midnight.

Session 5

Date: 2023.04.13 12:15-14:30

  • We need Better projects (e.g. projects you use at your work) we discussed what are GitHub organizations and what are repositories.

  • How to update a PR that was not accepted yet.

    • We created a new PR via the Web interface of GitHub that failed the CI and the owner also commented on it.
    • Then we found the fork and the branch in the fork and updated the file.
    • It automatically updated the PR and started the CI again.

  • We discussed this PR that needs a fix.

  • We discussed (in theory) how to handle a case when we plan to create a change for an open source project that might take us a month.

    • How to avoid breakage caused by changes created on the main project that conflict with the change we make.
    • The answer is that we cannot totally avoid those conflicts, but we can reduce their impact by communication and by frequently aligning our work with that of the main branch.
    • I mentioned rebase. We will see it in action later.

  • We briefly discussed if people get paid for their open source work.

  • Video 5-1: Ran Moshe

    • 00:00 Meetups
    • 03:20 Meetup - Code Mavens
    • 04:45 Meetup - PyWeb-IL
    • 06:50 Find a better open source projects
    • 09:00 Find a better open source projects - metacpan
    • 15:40 Find a better open source projects - perl5-dbi
    • 17:05 Find a better open source projects - forem
    • 18:50 Find a better open source projects - psf/requests
    • 20:55 requirements.txt file
    • 28:20 dependabot.yml file
    • 34:00 constraints.txt file
    • 36:40 Find better open source projects - pyflakes
    • 39:55 How to update a PR that was not accepted yet
    • 44:20 How to update a PR that was not accepted yet - create a new PR

  • Video 5-2: Ran Moshe

    • 00:00 How to update a PR that was not accepted yet - CI failed and the owner commented
    • 03:00 How to update a PR that was not accepted yet - find fork and branch to update PR
    • 05:50 How to update a PR that was not accepted yet - automatically updated the PR & started the CI again.
    • 11:55 Explain for failed git push
    • 17:00 How to avoid breakage caused by changes created on the main project by us - in organizations
    • 22:05 How to avoid breakage caused by changes created on the main project by us - in open source project
    • 34:20 rebase
    • 43:00 Assignments
    • 44:00 Assignments - projects in szabgab, OSDC-Code-Maven, Kantoniko and GitHub Topic
    • 51:40 Do people get paid for their open source work
    • 57:00 Previous and future assignments explained

Assignment 5

  • Fix the PRs that are problematic. (Where the CI failed or where the owner asked for an update)

  • Add better projects to your JSON (that are not ours)

  • Send more pull-requests, preferably not just for the author filed to make it more interesting and more challenging to you too.

  • Ideas for PR besides the one we discussed in the previous session:

    • Makes sure the README (or CONTRIBUTION) file in a project has clear instructions how to set up the local development environment and how to run the tests locally. (pick a project that has no, or very few stars)
    • If you can find any open source project with something you feel you can already fix, feel free to do that.
    • Check out my projects in szabgab or OSDC-Code-Maven or Kantoniko Feel free to send a PR for them, or even just to discuss open issues.

  • In those new PRs, include a better explanation of why this change is useful. If you are not sure what to write, ask on our Slack.

  • Dead-line: 2023.04.30

Session 6: Docker

Assignment 6

  • Setup the local development environment of 5 open source projects - in your preferred programming language.

    • They could taken from the ones where you already sent a PR with some other change that was already accepted.

  • Describe the steps and send a PR to add them to the slides: Source of the Open Source examples

  • Send PR to the project itself adding the same information to its README file.

    • Think about the point of view of the developer of the project. Make the title and the explanation in the PR clear as why s/he would want to accept this.

  • Write a blog post describing your experience and what you learned.

  • Dead-line: 2023.05.02

Session 7: Docker, part 2

Date: 2023.04.27 12:15-14:30

  • Write blog posts that have actual text that a random person can read, not just a bunch of links.

  • Explain what you learned from the lecture, from the assignments, and from the way the project owners responded to your PRs.

  • Include links to the issues you opened, the pull-requests you sent.

  • Follow-up on the issues and pull-requests if the owner asks for an updates. We already learned how to update a PR.

  • Use Markdown to add titles to the links so they won't be just URLs pasted.

  • See for example TD (OSD700)

  • blog posts

  • GitHub + DEV Hackathon

  • tomlkit

  • Video 7-1: Freddy

    • 00:00 Docker with CentOS
    • 22:13 Installing CentOS packages
    • 30:35 Bash Configuration
    • 31:16 Adding and changing users
    • 40:40 Which command
    • 49:40 Grep command
    • 01:01:10 Find
    • 01:02:15 Manual pages
    • 01:03:30 Pipelines

  • Video 7-2: Freddy

    • 00:00 Pipelines continued
    • 15:38 Creating container for Python's tomlkit
    • 28:10 Running tests
    • 41:30 Creating image from container

Assignment 7

TBD.

Session 8: git-scm on Windows, GitHub contribution workflow

Date: 2023.05.04 12:15-14:30

  • git-scm configure the default editor

  • Windows install (again), process of clone/fork/pull

  • workflows

  • git-scm

  • ~/.gitconfig global config

  • .git/config config for each repository

  • ssh-keygen

  • ls -l ~/.ssh/

  • cat ~/.ssh/id_ras.pub

git init
git add
git commit
  • Create repo in GitHub and follow the instructions there to push out the repository
git clone
git checkout -b branch-name
git add
git commit
git push


git checkout main
git pull origin main
git checkout branch-name
git rebase main
git push --force

A few notes for he lecture yesterday:

For each thing you change create a separate branch from the default branch (usually "master" or "main"). So for example yesterday Ran Moshe found out that the generate command in the README does not work. First of all Ran, you should have opened the two issues right away

  1. with the error message for this command python generate.py github/bioinform.yaml github/calgaryml.yaml failing
  2. that the python generate.py` is failing that you already opened since then: OSDC-Code-Maven/open-source-by-organizations#79

Then when fixing you create a branch and sent a PR to fix the first issue and I have accepted it. Already before I accepted it you could go back to the "main" branch and create a new branch for some other changes you might want to make.

Now that I've already accepted the PR, you can update your main branch from my main branch (as I showed yesterday) and then

  1. start your new branch from there.
  2. if you already have a branch that you started from main you can rebase that branch to "main" and be up to date (as we saw yesterday)
  • Video 8-1: Yael
  • 00:00 Topics we will talk about
  • 04:35 git client installation(git-scm)
  • 12:20 bash window basic commands
  • 15:54 create new file
  • 17:35 find command
  • 20:00 edit file with vim
  • 21:04 create project
  • 21:45 readme file
  • 23:29 git init
  • 24:25 git add
  • 25:00 identification user config
  • 28:58 commit Author
  • 32:26 configuration commands
  • 35:00 git commit add README
  • 36:54 github create new repository
  • 38:46 git remote add
  • 44:16 git branch main
  • 45:16 public key
  • 50:00 push
  • 53:00 repository permissions
  • 54:30 git push -u
  • Video 8-2: Eliyahou
  • 00:00 delete repository
  • 03:20 git clone
  • 08:05 create new branch
  • 09:50 create new file
  • 10:58 git add
  • 12:00 git log
  • 13:25 create fork
  • 15:15 git push
  • 19:00 merge
  • 20:34 send PR
  • 22:30 fix PR
  • 25:32 update readme file
  • 28:56 rebase / merge
  • 36:34 reset
  • 37:28 push rejected
  • 39:31 force push
  • 43:42 merge
  • 46:10 delete last commit
  • 47:37 rebase benefits
  • 51:30 Assignment

Assignment 8

Session 9: GitHub Actions

Date: 2023.05.11 12:15-14:30

Assignment 9

Find a project that has some tests but does not have any type of continuous integration. Set up GitHub Action to run the tests. Before you send the PR to the project owner show the results to @szabgab.

Session 10: Dockerfile; Playground; GitHub Actions for Java, Open Source

Date: 2023.06.01 12:15-14:30

Session 11: Testing with PyTest

  • Date: 2023.06.08 12:15-14:30

  • Testing Demo

  • Testing Python with pytest

  • Video 11-1: Zohar Asulin

    • 00:00 testing with pytest
    • 05:27 test methods
    • 06:37 testing demo tools in python
    • 08:13 AUT-application under test
    • 10:30 Regression test
    • 13:07 doctest
    • 26:14 unittest
    • 30:50 pytest
    • 45:46 and unittest pytest run doctest
    • 46:25 test coverage
    • 54:13 pytest setup
    • 55:37 examples test

  • Video 11-2: Zohar Asulin

    • 00:00 pytest expected exception
    • 06:37 pytest change text
    • 07:37 pytest missing exception
    • 08:14 exception raised
    • 10:20 exercise-test exceptions
    • 10:57 multiple failures
    • 12:30 selective running of test functions
    • 13:24 stop on first failure
    • 15:55 expect a test to fail
    • 23:15 –rx
    • 24:17 skip test
    • 27:37 –rs skip test
    • 28:15 show extra test –r
    • 28:30 verbose mode
    • 28:39 quiet mode
    • 28:49 STDOUT STDERR
    • 31:30 using classes
    • 32:06 module Home assignment - create test for open source project
    • 34:32 Travis CI
    • 35:06 pytest.mark.parametrize
    • 43:13 testing flask
    • 44:15 Anagram in CMD
    • 48:44 examples function test
    • 50:35 Fixtures
    • 1:00:12 Home assignment

Assignment 11

Find an open source project, generate a test coverage report for it, write some tests for a part of the code that did not have tests. Send it as a Pull-Request. It can be a project you already contributed to or any other project. It can be in Python or any other language.

Session 12: Which project to work on; Docker compose

  • Date: 2023.06.15 12:15-14:30

  • Which project to contribute to?

  • Docker commands

  • docker-compose

  • PyDigger is using it.

  • Linode

  • Digital Ocean

  • Video 12-1: Yael Levi

    • 00:00 Input order bug
    • 06:10 Which project to contribute
    • 12:12 Git log to watch commits on the project
    • 13:08 gitk, gitg
    • 15:02 tig
    • 17:17 A well-known projects
    • 24:25 Django
    • 35:49 search recent updates
    • 37:31 A project missing something
    • 37:50 cpan digger
    • 41:54 Desktop app, API, dependencies
    • 43:07 awesome list
    • 47:11 Type of project
    • 51:00 Web application
    • 51:42 databases
    • 01:01:00 in the OSDC
    • 01:01:02 Points for improvement

  • Video 12-2: Eliyahou Levi

    • 00:30 Bot to telegram
    • 03:00 Docker commands
    • 05:40 Docker tag, update & publish
    • 08:39 Docker Compose
    • 11:08 docker-compose.yml
    • 13:02 swarm mode warning
    • 15:29 Docker exec
    • 16:42 2 services example
    • 17:40 docker-compose up
    • 18:52 example with 2 docker files
    • 19:13 redis - key value db
    • 23:36 docker compose stop
    • 25:04 docker rm redis
    • 27:00 Docker Solr
    • 27:41 MongoDB
    • 29:01 PostgreSQL
    • 29:30 Compose for Perl
    • 30:40 pydigger docker-compose.yml
    • 35:57 update pydigger
    • 37:43 docker-compose.yml example
    • 40:00 docker compose override.yml
    • 48:50 Linode
    • 52:17 Exercise

Assignment 12

  • Start writing a project and pushing it out to a repository on GitHub. The programming language used is not important and the project can be any "toy" project, but it needs to show the various things we learned. It has to have at least one test and there has to be Github Actions configured to run it.

Session 13: Overview of well-known open source projects

Videos so far:
    Yael Levi        18CD
    Eliyahou Levi    18CD
    Freddy Adiv      2277
    Ran Moshe        3455
    Doron Chapnitsky 6699
    Zohar Asulin     AABB

About

OSDC at Azriel College starting in 2023.03

osdc.code-maven.com/osdc-2023-03-azrieli/

Topics

github git

Resources

Readme

License

View license
Activity
Custom properties

Stars

4 stars

Watchers

5 watching

Forks

5 forks
Report repository

Contributors 8