Sally = purple
...
ArchivesSpace Committers Calls are monthly meetings of the developers of ArchivesSpace, who discuss modifications and innovations in the code, and review new and open tickets. Calls are open to interested
...
Make sure that you have completed an Individual Contributor License Agreement, or that your institution has completed an Corporate Contributor License Agreement.
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.
Set up a GitHub account if you have not done so before.
Fork the ArchivesSpace repository on GitHub.
Create a feature branch.
Make changes in your fork. We advise contributors to follow these guidelines to expedite the contribution review process.
Follow established style guidelines
RSpec: http://betterspecs.org/
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?) → would be good to run travis locally
If you’re adding a feature or otherwise changing documented behavior, modify the documentation to reflect your changes.
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.
Push your updated branch to your fork.
Create a Pull Request on GitHub.
Respond to feedback as the community reviews your contribution.
...
- Esmé Cowles (Unlicensed) to add links Hydra to code contribution guidelines to guidelines
- Update Contribution to ArchivesSpace page to reflect current
- Create separate 'clean' doc?
- current status of tools etc
- Sally Vermaaten (Unlicensed) to create cleaned up re-org proposal doc
Possible to stage implementation? - Yes
...
- re-organization could be done first - would basically need Mark's original spreadsheet & descriptions of groups - ready to
...
- core committer
...
- group – would probably want to wait for Tech Lead to be put into place
Overall Plan:
- Complete committer group definitions and process for adding members; policies etc.
- Get agreement from 4 -5 people to act as a starter group of core committers
- When ready announce plan to mailing list.
- Create the organizations.
- Transfer repositories to assigned org per:
- https://docs.google.com/spreadsheets/d/1S5C217M3JUZfHSlLarQjAUqCofJ9jMi_C2VIGvyT8KA
- /edit
- Announce to list.