Developers
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
We are actively seeking contributors, so please introduce yourself on the developers list and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members!
Start by reading our contribution guidelines
Public Lab Software
| Project | Description | Source Code |
|---|---|---|
| MapKnitter | Assemble aerial images into maps. | github:publiclab/mapknitter |
| Spectral Workbench | Material analysis using DIY spectrometry. | github:spectral-workbench |
| Leaflet.Illustrate | Leaflet plugin built for MapKnitter. Enables text annotations on Leaflet maps. | github:manleyjster/Leaflet.Illustrate |
| Leaflet.DistortableImage | Leaflet plugin built for MapKnitter. Enables images to be distorted. | github:publiclab/Leaflet.DistortableImage |
| publiclab.org | This very website! | github:publiclab/plots2 |
| Infragram | Analyze plant health with infrared imagery. | github:p-v-o-s/infragram-js |
| MapMill | Upload and collaboratively rank large batches of aerial imagery. | github: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!