Open source PPNZ

Ben Vidulich Public Seen by 126

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 enquiries@pirateparty.org.nz 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
1. 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.

First project

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.

Licensing

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.

Hubat McJuhes Sun 19 Apr 2015 12:23PM

Regarding the First project, the website:

Looking at it today after not have been visiting it for a long time is a great relieve: so many embarrassing anachronisms have been removed and replaced against meaningful content.

To those who have done the good work: Thank you all

I will try to find time to produce some pull requests on gitHub in the following days myself. Tank you, ben, for having set that all up.

One thing (despite the broken links to the CiviCRM) needs quick-fixing on the page, though, that is not covered by the files in the repository:
On the NEWS tab is a widget on the right hand side with button-links being labelled:

Get Informed about our topics and visions!
Support us with your engagement!
Become a Pirat! Subscribe to the pirate party

All those links point to pages of the german PP, which doesn't seem right.

Can we simply remove this widget for now until we can provide our ow proper content for them?

Ben Vidulich Tue 21 Apr 2015 9:20AM

One thing (despite the broken links to the CiviCRM) needs quick-fixing on the page, though, that is not covered by the files in the repository

Nothing in that repository is live yet. That's for the new website that I'm hoping to get working some day!