Open source PPNZ
In the spirit of promoting open source activity with the Pirate Party, I have created a organisation on GitHub for party-related projects. I invite anyone that would like to contribute to PPNZ to make use of this organisation. Send an email to [email protected] for an invitation to the organisation. Anyone, regardless of membership status within the party or the GitHub organisation, is welcome to contribute.
Teams and working groups
People that are interested in working on a particular project or idea should form a working group. Each group will be assigned their own team inside the GitHub organisation which will allow them to create and contribute directly to their own repositories.
Guidelines for contributing
- Fork the repository you would like to contribute to
- Make changes in your fork
- If you're working on a new feature then make the changes in a new branch
- Send a pull request
- Wait for your changes to be reviewed and merged
- All is good
Guidelines for reviewing changes
We should strive to produce high-quality content as much as possible.
Where appropriate at least one criticism should be provided for every pull request as a part of the review. When a pull request is fixing small errors such as typing errors or spelling mistakes it does not make sense to provide a critique, however larger pull requests should be carefully checked for these small things since they are more likely to have been missed by the pull request contributor.
The first project that I would like to open-source is the re-vamp of the main PPNZ website.
The project will be split across two repositories: one will contain Markdown files that will represent the content each page and the other will be a simple Ruby on Rails application to parse and render the markdown content. Instead of running a site that a select few individuals log in to and administer, anyone that is willing to participate can make changes, send a pull request, and their changes will automatically be reflected in the live site. Since the GitHub website also renders Markdown content it will be easy to preview page content before it is published to the live website. It is likely that the website theme will be separated into yet another repository to make the rendering code more generic, and to allow re-use of the theme on other websites.
You can view the repository for the website content here.
I have no idea what license is for an organisation like PPNZ so I suggest we discuss that here. Specifically for content (not code) I propose CC-BY 4.0 and have applied this to the website content repository - we can change this later if we want to.