[Archivesspace_Users_Group] new policies and documents related to contributing to ArchivesSpace development

[Christine Di Bella]

Hello ArchivesSpace members,



As an open source application, development for ArchivesSpace comes from many sources. As our community and application grow and mature, we're fortunate that more and more people want to get involved and make development contributions that make the ArchivesSpace application better for everyone. To make our processes for evaluating potential contributions more transparent, and to help people have a better idea of ways to get involved in development, we've put together some documents and policies that we hope will be helpful:



  *   ArchivesSpace Process for Evaluating Potential Feature Contributions to the Core Code<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/360546309/ArchivesSpace+Process+for+Evaluating+Potential+Feature+Contributions+to+the+Core+Code>
     *   applies to larger contributions such as new modules or significant changes or additions to existing features
  *   Getting Involved in Developing Features for ArchivesSpace<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/348094572/Getting+Involved+in+Developing+Features+for+ArchivesSpace>
     *   explains the options when developing features for ArchivesSpace
  *   Turning an ArchivesSpace Plugin into Core Code<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/349995159/Turning+an+ArchivesSpace+Plugin+into+Core+Code>
     *   provides some guidance and suggestions when considering turning a plugin into something more
  *   Pull Request Review Process<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/125861898/Pull+Request+Process>
     *   explains how big and small community pull requests are evaluated



We've also set deadlines for submitting pull requests to be considered for a particular release. In general, the pull request deadline is the third Friday of a month, with occasional exceptions when a release is intended to come out earlier in the month. For example, the deadline by which a pull request needs to be submitted for consideration for our January release is January 19. Submitting a pull request by the deadline does not guarantee that it will go into the next release, but it will help ensure that we have adequate time to review and test it before potentially putting it into a release. We've noted these deadlines on the annual overview view of our roadmap and will be sending various reminders via email and Github when a particular deadline approaches to help contributors with their planning.



We'll be promoting these links inside and outside the member community in various ways in the coming months, as well as adding information about particular JIRA issues and projects for which we're seeking community developers, but please also feel free to forward them to anyone you think might be interested.



We very much encourage you to get in touch with me, Laney, or with members of the Core Committers group<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/102893918/Core+Committers+Group> if you want to get involved in development, either by developing something yourself or working with a developer to do so. We look forward to many contributions and the participation of many contributors in 2018!



Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180108/6555587f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20180108/6555587f/attachment.jpg>