SPO600 Lab1

As part of this lab we were to find two projects with different licenses and do an analysis on their processes.

For this assignment I have chosen a project with an MIT license (React) and Apache License 2.0 (Kubernetes). In terms of differences between the licenses there isn't much actually although Apache is much much more verbose, both are pretty permissive except Apache requires users to maintain a modification notice of all changes they have made to the original software.

React
Filing issue

1. Create issue on project's github - , describe if issue is a bug or feature request. If it is a bug, describe the current behavior and ways to replicate issue, describe expected behavior. Provide version of React user is using, browser that caused issue and OS. Provide any details on regression.
2. A React JS core team member will take a look at issue and assign appropriate labels

Pull Requests

1. Create pull request referencing issue, the bot for the repo will check for a signed CLA from the github user
2. A bot called sizebot will do an analysis of different between code in master branch and PR 
3. Code review for PR will be assigned to two other React JS core team members, only one approval is needed
4. React team member merges commit

Kubernetes

Filing issue

1. Create issue on project's github - https://github.com/kubernetes/kubernetes/issues, describe in detail regarding issue: environment, version, error logs and ways to reproduce issue
2. Assign appropriate labels to issue
3. Members will then check the issue and categorize by adding an area specific label and ping appropriate user to take a look at the issue

Pull Requests

1. Create pull request referencing issue, the bot for the repo will automatically assign labels such as do not merge and assign code review to two members. Users are required to assign type of fix PR addresses and priority.
2. If it passes code review, the PR is then assigned to the kubernetes patch release team
3. Final approval from two senior contributors on the project and a maintainer
4. Repo's bot will merge the commit while running tests

I personally like Kubernetes a lot more as it is a lot more automated with the K8bot they have in the repo handling merging and labeling.