Release 0.3 - PR2

Internal project - Seneca Blackboard Extension

As I mentioned in previous blog post, for this release I had a chance to become a maintainer of the internal project and its repository - Seneca Blackboard Extension.

After creating the basic file structure from “refined Twitter” extension example we started to work.

As a maintainer of the repo I needed to control the issues and pull requests, but it was challenging. One of the reason is a couple of collisions - some people started to work on the same issues and I decided to create the rules for contributing to the repo, to avoid such collisions.


The main rule of our repo is: 
"FOR THIS REPOSITORY IT IS MANDATORY TO CREATE ISSUE OR COMMENT UNDER EXISTING ISSUE BEFORE CREATING THE PULL REQUEST." (CONTRIBUTING.md)
After creating the rules it was much easier to assign issues to different students and accept pull requests according to the rules.

Closer to the deadline of the Release 0.3 I faced the other problem that many repo maintainers may face. This problem is resolving merge conflicts. Due to the high number of pull requests in the small amount of time (because of the deadline) there were many JavaScript and manifest.json files fixes, and my problem was that I checked & accepted pull request in the wrong order (from most recent to the oldest ones), that caused many merge conflicts that I needed to resolve.

At the end of the day, right now (23 November, 2018) we have the following:

  • Working 0.1 version of the extension is on the GitHub, anybody can download it from GitHub and use it in their Google Chrome
  • 44 out of 48 (91 %) pull requests accepted (2 of them need to be fixed by its contributors due to the merge conflicts)
  • 38 out of 47 (80 %) issues solved and closed
To sum it up, as a maintainer of one of the internal projects of release 0.3 I did the following:
  • Cleaning the issues & communicating with contributors about issues
  • Reviewing & accepting the pull requests, communicating with contributors about PRs
  • Resolving lots of merge conflicts
  • Some settings & Repository cleaning
As a contributor, for the second PR of release 0.3 I did the following:
  • Removing all left useless sections of the Blackboard
  • Small coding style fixes around files
  • Bug with changing the text font size found; code commented; contributor informed under the issue of GitHub
  • Small ReadMe fixes done according to 0.1 version of extension

 Blog about this repo and extension will be continued in the next release :)

Comments

Post a Comment

Popular posts from this blog

Hacktoberfest Final Blog Post

Hacktoberfest 2018 During this October in my Seneca course I had a chance to participate in a big Open Source event called Hacktoberfest. My task was to do 5 pull requests to open source repositories on GitHub. For the first PR I chose to add a hello world program in Pascal language For the second PR I chose to fix css and html in survey form project For the 3rd, 4th, 5th PRs I chose to add different math and string algorithms and tests to one of the standard algorithms repo in JavaScript Issues: https://github.com/piyush97/HelloWorld/issues/5 https://github.com/yirano/surveyForm-v1/issues/5 https://github.com/manrajgrover/algorithms-js/issues/10 (Find Divisors) https://github.com/manrajgrover/algorithms-js/issues/8 (Longest common substring) https://github.com/manrajgrover/algorithms-js/issues/10 (Inverse of first 'n' numbers) Pull Requests: https://github.com/piyush97/HelloWorld/pull/58 https://github.com/piyush97/HelloWorld/pull/57 https://github.com/yirano/surveyForm-...
Read more

Release 0.3 - PR1

Beginning of the internal project For this release I had a chance to become a maintainer of the  internal project and its repository - Seneca Blackboard Extension. After creating a repo on GitHub, our team decided to develop an extension for Google Chrome, then we filed around 15 issues(we had 2 types of issues - new features/design and deleting useless parts), created the basic file structure from “refined Twitter” extension example and started to work. As a maintainer of repo and student of DPS909 I needed to do both sets of tasks - maintaining a repo and contributing to code. Here are the things that I finished in first PR: Contributor's tasks:  Basic file system created with small fixes  How to contribute section with rules added  Small ReadMe fixes done Repository maintainer's tasks:  Cleaning the issues & communicating with contributors about issues  Reviving & accepting the pull request, communicating with contr...
Read more