Public Lab is an open community which collaboratively develops accessible, open source, Do-It-Yourself technologies for investigating local environmental health and justice issues.
[Public Lab software](#Projects), including this website, is written collaboratively by a community of contributors. _Above: a diagram of the various [Public Lab software projects](https://publiclab.org/notes/warren/05-22-2019/draft-of-a-public-lab-software-roadmap-comments-welcome)_
**We're so happy to meet you! This page is to welcome new contributors.**
We especially welcome contributions from people from **groups under-represented** in free and open source software!
Our community aspires to be a respectful place. Please read and abide by our [Code of Conduct](/conduct).
## How to contribute
**We are actively seeking contributors**, so please **[visit our welcome page](https://code.publiclab.org#r=all)** and ask about how you can help keep these free and open source software projects working (and improving) for our thousands of community members!
### First-timers only
If this is your first time, **welcome**! We're so happy to meet you! This page is to welcome new contributors looking to get involved in coding with Public Lab.
We especially welcome contributions from people from groups *underrepresented in free and open source software!*
Please see [our welcome page](https://code.publiclab.org).
If you'd like to quickly jump into an issue, see the following list for any available [first-timers-only issues](https://code.publiclab.org#r=all):
<iframe src="https://code.publiclab.org/examples/embed.html#l=first-timers-only&r=plots2&o=publiclab" style="border:none;overflow:scroll;" width="100%" height="300px"></iframe>
Read more about our [software outreach work here](/software-outreach)!
<td><b>Ruby on Rails</b> This very website!PublicLab.org - a collaborative knowledge-exchange platform.</td>
<td><b>Ruby on Rails</b> Assemble aerial images into maps.</td>
<td><a href="https://spectralworkbench.org/">Spectral Workbench</a></td>
Public Lab is on Github at: https://github.com/publiclab
## First time contributors
New to open source/free software? Here are some resources to get you started:
Our welcome page for newcomers looking to get involved in coding:
#### Getting started
* A very in-depth guide: https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github
* Lots on Ruby, Rails, databases and more: https://www.theodinproject.com/courses
#### Pull requests
* the basic GitHub Flow workflow: https://guides.github.com/introduction/flow/
* Rebasing step by step: https://thinkup.readthedocs.io/en/latest/contribute/developers/devfromsource.html#workflow-diagram
* guidance on rebasing: https://www.atlassian.com/git/tutorials/merging-vs-rebasing
* revert a single file to a specific revision in Git: https://stackoverflow.com/questions/215718/reset-or-revert-a-specific-file-to-a-specific-revision-using-git
* @warren: I've found if I get in real trouble rebasing, sometimes I'll try to squash my feature branch commits /without rebasing/ before then rebasing just one commit: https://gist.github.com/n00neimp0rtant/9515611
### Contributing for non-coders
Not interested (or not yet interested) in coding, but still want to help out? Have a project you really need to get your work done, and trying to encourage coders to tackle it?
You can still help out; in fact, **helping to clearly describe and document problems and new feature proposals is at least as important as writing the code itself**.
When creating or editing an issue, try to:
1. Clearly describe the problem, linking to pages where it can be observed, or where a new feature might live. Include screenshots to be very specific!
2. (for bugs) If you don't know the problem, do what you can to help others narrow it down: provide contextual information like your browser, OS, and what you were doing when it happened. Did it used to work? Does it still, but only sometimes? Help them reproduce it!
3. Propose a solution. Whether or not you code, describing what **should** or **could** happen, or even what you expected to happen is always helpful to someone looking to fix it. This can be as simple as "It should show a notification." or "There should be a way to hide it."
Once an issue is well documented, we can tag it with `help-wanted` to get the word out that we're looking for someone to try to fix it. If you're not sure if it's ready, ask [on the plots-dev list](#Sign+up)
Finally, if your issue is well documented, try to get involved in some outreach to new contributors to match someone with the project! Tell them what it'll help you achieve and why you'd appreciate help. And coordinate with the [plots-dev discussion list](#Sign+up) to get the word out.
### Preparing issues for newcomers
Related to the above, even if you are a coder, we need help "rolling out the red carpet" (as the [Hoodie project](http://hood.ie) calls it) for new contributors, to grow our contributor base. The steps in [Contributing for non-coders](#Contributing+for+non-coders) are a good starting point, but as a coder, you can also deep-link to the relevant lines of code, with Github links and pointers like:
This is especially great for attracting coders who are not only new to our code but new to coding in general!
Learn more about [how to make a good `first-timers-only` issue here](/notes/warren/10-31-2016/create-a-welcoming-first-timers-only-issue-to-invite-new-software-contributors).
Mentoring for [Summer of Code programs](/gsoc) has a lot in common with being a software "reviewer" with Public Lab throughout the year; to welcome and support our community of coders, we need to:
* always be kind and respectful! (remember our [Code of Conduct!](/conduct))
* help people to become better coders and don't make them feel bad
* encourage people to open a PR with their work even if it's not finished
* go through recent PRs to help people who are stuck
* use emojis!
Some specific things you can do:
* add links to relevant lines of code to help people see where to start, or for an example of a similar feature
* suggest writing a test to *protect your work* from future issues
* tag things as `break-me-up` if it's possible to do a project in separate simpler parts
Here are some guides to different ways to help others contribute:
## Summer of Code Activities
## Summer of Code
Lots of development on Public Lab software happens as part of the [Rails Girls Summer of Code and Google Summer of Code programs](/soc), that latter supported generously by Google.
Looking at the [GSoC Ideas list](/wiki/gsoc-ideas) 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 our [Summer of Code page](/soc)!
Note that we encourage the use of external libraries -- it's certainly easier and more maintainable than developing our own code -- but we also encourage very clear links to such libraries' documentation, source code, and of course, attribution.