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.
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:
Blog about this repo and extension will be continued in the next release :)
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
- 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
- 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