I feel the same way about codes of conduct for open source projects as I do about codes of conduct for events. You can absolutely run a totally safe and effective event without one, but by having one you make very clear what your expectations are – and in turn this manages the expectations of the people attending that event. Continue reading
Tag Archives: joindin
Joind.in at the PHPNW Hackathon
Joind.in is one of the featured projects and I’m one of the maintainers, so I’ll be at the hackathon and I’m hoping that we’ll get quite a few things done during the evening. Joind.in is an ideal project for events like this since it’s easy to get started with it, and we have a development platform virtual machine (that we’ll have already downloaded onto USB sticks so no conference wifi delay) so you can be up and running in no time. We also have a specific label on our bug tracker for items that we think are manageable for people who don’t already know the system, so chances are that if you want to, you’ll be able to contribute to an open source project with something finished by the end of the night. Continue reading
Joind.in at PHPNW’s Hackathon
This year will be no exception: PHPNW’s Hackathon is on the Friday evening – you need a conference ticket, and you need to tick the “hackathon ticket” box. Joind.in will be there and we’ve got a very big todo list so if you are looking for something to hack on, then look no further! Continue reading
Running Pull Request Builds with Jenkins
DimpleJs Bubble/Scatterplots and Joind.in Data
Joind.in at the PHPNW Hackathon
Do Open Source with Git and Github
Often I find absolutely competent programmers, who aren’t involved in open source, either because they don’t know how to approach a project, or because they just aren’t sure how the process even works. In this article we’ll look at one example, the conference feedback site joind.in, and how you can use GitHub to start contributing code to this project. Since so many projects are hosted on github, this will help you get started with other projects, too.
The tl;dr Version for the Impatient
- Fork the main repo so you have your own github repo for the project
- Clone your repo onto your development machine
- Create a branch
- Make changes, commit them
- Push your new branch to your github repository
- Open a pull request
This article goes through this process in more detail, so you will be able to work with git and github projects as you please.
Continue reading