Next Jubilee: Fermat | Fork: Nov 10th | Starts: Nov 12th
It is fairly common to see this constellation of issues come up in the PHP developer community:
- "I'm not a Junior dev, but I don't know where to start when it comes to contributing to projects."
- "I don't know what projects need what help, or how to find them."
- "I'm still learning PHP. I want to work on an open source project to help learn, but don't know the 'good' from the 'bad'."
- "I have a project that I would like help on, but don't know where to find it."
The group will decide from a list of PHP projects a new project to contribute to every two weeks.
Every two weeks, the org will fork the new repo on github. Everyone that has joined the org will have write access to the forked repo. They will of course also be able to fork it themselves if they want, but particularly because this could be helpful for novice developers that want a way to get their feet wet, development should primarily be from the Org's fork.
Each user will create their own feature branch, the org will create it's own issues list and assign them out, and we will provide the project maintainer with one pull request per issue we close (on our end).
The whole idea of this would be to roll through the PHP community and for one project every two weeks "forgive their technical debt": thus, Jubilee.
The kinds of things that we would (primarily) be looking to help with, in order of importance:
- Helping the project close existing bug issues.
- Helping to report (and fix if possible) new bug issues.
- Increasing unit test coverage, and improving the quality of those tests.
- Ensuring that the code has DocBlock comments so that IDEs can work easily with the project.
- Identify areas of the project that need to be fixed for best practices & coding style (as specified by the project itself).
Jubilee Project Schedule | Sprint Process | GIT Practices & Branching Strategy
Leave a comment here.
By leaving a link to it here. It must be on github, and must be open source.