The Public Lab Developers group is an open group for Public Lab related (or -interested) programmers and developers. Float ideas, solicit feedback, get involved in existing PL programming projects, or start your own!

Sign up using the form to the left, or visit the Google Group directly

How to contribute

First, please read: http://publiclab.org/wiki/contributing-to-public-lab-software

Current major projects include:

• PublicLab.org - https://github.com/publiclab/plots2
• MapKnitter.org - https://github.com/publiclab/mapknitter (some issues here)
• SpectralWorkbench.org - https://github.com/publiclab/spectral-workbench (some issues here)
• Infragram.org - https://github.com/p-v-o-s/infragram-js/
• MapMill.org - https://github.com/publiclab/mapmill

Public Lab is on Github at: https://github.com/publiclab

Google Summer of Code

Lots of development on Public Lab software happens as part of the GSoC program, supported generously by Google. Looking at the GSoC Ideas list is a great place to find projects which our community really needs to get done, whether or not you're in the program.

Read more at http://publiclab.org/wiki/gsoc, and review recent GSoC proposals/projects at http://publiclab.org/tag/gsoc

Testing server

We have a plots2 testing server available for testing larger code changes and database migrations; please contact web@publiclab.org for details, and submit a public key for access. General testing procedure is as follows:

• thoroughly test on local copy, with seeded database

• get ssh access to test.publiclab.org

• reimport db if needed (web@ can help with this)

• create new git branch in /home/warren/sites/test.publiclab.org/
• pull in new changes
• rake db:migrate etc if needed
• run rake test
• run ./restart from rails root dir
• manually compare with publiclab.org
• wash, rinse, repeat
• check with web@ about deployment to production once you're ready!

Installation videos