Sally = purple

...

1. Make sure that you have completed an Individual Contributor License Agreement, or that your institution has completed an Corporate Contributor License Agreement.

2. Find or create a bug report or feature request ticket in JIRA GitHub (to make sure you’re not duplicating work and document the intent of your contribution). It helps to explain both the existing behavior and the desired behavior that your change will implement.

3. Set up a GitHub account if you have not done so before.

4. Fork the ArchivesSpace repository on GitHub.

5. Create a feature branch.

6. Make changes in your fork. We advise contributors to follow these guidelines to expedite the contribution review process.

1. Follow established style guidelines

1. Rails: https://github.com/bbatsov/rails-style-guide

2. JRuby: https://github.com/jruby/jruby/wiki/JRubyStyleGuide

3. RSpec: http://betterspecs.org/

2. Include unit tests sufficient to cover the feature(s) you add or bug(s) you fix, and make sure the test suite passes. (Can we rely upon Travis or a Jenkins instance for this, or should we suggest that contributors run tests locally?)

3. If you’re adding a feature or otherwise changing documented behavior, modify the documentation to reflect your changes.

7. Once your work is done, squash the commits in your branch — see One Commit per Pull Request for some guidelines — and rebase it on the latest in the upstream master branch. We appreciate succinct but explanatory commit messages.

8. Push your updated branch to your fork.

9. Create a Pull Request on GitHub.

10. Respond to feedback as the community reviews your contribution.

...

https://github.com/archivesspace­labs/

I wrote something up here: https://docs.google.com/document/d/1a_4AEgXHHZnbKWwjRcEVw8FWdme1cldKWvII9cLRYxI/edit?usp=sharing

Purpose: contains proof of concepts, examples and experimental projects. There is no official
support from the Program Team for anything in labs. The projects are not guaranteed to be up
to date with the latest release and are used on a at­your­own­risk basis. Program Team and
other “official” committers can contribute to labs but that does not confer official support to any
project. Note - Labs branding should make it clear that none of the projects are officially supported. 

...

•  Sally Vermaaten (Unlicensed) to polish / borrow text to flesh out code guidelines (group to review afterwards)
  
•  Max Eckard to polish / borrow text re. Labs area 
  
•  All to discuss updated text and continue to flesh out other areas in next meeting - Sally Vermaaten (Unlicensed) to send out Doodle for next time
  

...