Public Lab welcomes and encourages community contributions to our open source software. This page is intended to

1. List software projects that Public Lab has incubated and provide links to source code.
2. Collect software development guidelines and best practices for Public Lab projects.
3. Help newcomers figure out how and where to start contributing!

Getting started

Quick tips for getting involved with the Public Lab codebases:

1. Set up a GitHub account and install git.

   If you're not familiar with git, a popular version control software, you can try it out at https://try.github.io.

   Speaking of GitHub...right now, all of Public Lab's open source code is located on GitHub, a website which hosts git repositories. Setting up a GitHub account is the first step to getting involved with Public Lab's code (and lots of other code).

2. Join the Public Lab developers mailing list

Contribution Guidelines

Public Lab software is written in many languages, and each project may have its own guidelines for contributors. These broad guidelines should serve as general principles to guide your approach to a new Public Lab codebase.

Contributing using git

• Always do development in a feature branch. This makes it much easier for project maintainers to merge your contributions into the trunk. The name of your branch is displayed when it is merged in to the main trunk, which means that it serves as built-in documentation for your feature. This works great when you give your feature branches descriptive names! Some example branch names:
  • donation-button-redesign
  • markdown-package-update
  • fix#44 (fixes GitHub issue #44 in this repository)

Contributing to Ruby projects

Contributing to JavaScript projects

Public Lab Software