Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

3.   Review technical implementation plan

Next, the ArchivesSpace Tech Lead (Laney McGlohon)developers, the Core Committers group, and relevant community members will review your implementation plan. This does not need to be a formal written plan, but there should be information on some or all of the following items when submitting a feature for consideration from a technical perspective:

  • Coding approach and standards for development (developers are strongly urged to review the Guide for Code Contributors at https://archivesspace.atlassian.net/wiki/download/attachments/19202114/ArchivesSpaceContributorsGuide20170404.docx?version=1&modificationDate=1494867177188&cacheVersion=1&api=v2 for guidance on ArchivesSpace best practices and expectations).
  • Indication of any anticipated data model changes
  • The impact, if any, on the master branch and other enhancements/bug fixes currently being worked on
  • Testing level, including how and for what automated testing will be implemented
  • Names of participating developer(s)
  • Links to Github repositories for the developers or that are being used for the feature
  • Information about plans for sprints, and whether ArchivesSpace Program Team or community members would be welcome to attend as observers or commenters
  • Timeline for development
  • Anticipated date for inclusion into master branch

...

Once the feature has been determined to be appropriate for the core code, the specifications and technical plans have been vetted by ArchivesSpace and the community, and a timeline is in place, the feature will be included on the ArchivesSpace technology and development roadmap (https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/18710568/Road+Map) and progress on it announced via monthly updates or in posts to the listservs as appropriate. Regular updates on progress, to both the ArchivesSpace Program Team and the community, will be greatly appreciated. Depending on the timeframe for development, we suggest quarterly updates, at minimum.

If you’ve made it through Step 5, congratulations, and thank you! We look forward to receiving your feature for inclusion in the core code. The following steps will complete the process.

6.   Develop your feature and test it

...