[Archivesspace_Users_Group] Supporting community-based ArchivesSpace development

[Brad Westbrook]

Hi, Mary,

Thank you for this timely and helpful message.  Standing up a development hub is a very good idea, and Chris and I will be willing to explore that and report back options.

At the moment, due to increasing staff and the recent release of v1.1.0, we are composing a 12-month development plan which we will be vetting soon, initially with the Advisory Councils and then with the general membership.  The development plan will consolidate and prioritize feature requests, bug reports, and chores currently logged into the ArchivesSpace Pivotal Tracker (at https://www.pivotaltracker.com/n/projects/386247), as well as those culled from reports recently received from Harvard and UIUC and at various workshops over the past several months.  We expect the review process to take several weeks to complete.

All best,

Brad W.

Bradley D. Westbrook
Program Manager
brad.westbrook at lyrasis.org<mailto:brad at archivesspace.org>
800.999.8558 x2910
678.235.2910
bradley_d_westbrook (Skype)
[cid:image003.png at 01CE734E.FD759D30]





From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Caldera, Mary
Sent: Thursday, November 13, 2014 2:18 PM
To: archivesspace at googlegroups.com; archivesspace_users_group at lyralists.lyrasis.org
Cc: Peter Carini (Peter.Carini at dartmouth.edu)
Subject: [Archivesspace_Users_Group] Supporting community-based ArchivesSpace development

Dear Brad,
As you are aware Yale University, like others, is actively developing ArchivesSpace to ensure  it meets our (and potentially other users') needs prior to implementation. We have contracted with Hudson Molonglo to enhance AS accessions, search, and container management functions-information about our development plans can be found on our Web site<http://guides.library.yale.edu/archivesspace>.  You and the other members of the ArchivesSpace team have been incredibly helpful and encouraging, but we realize that we would benefit from broadening the communication. As we move forward with our plans and  think about additional development areas, it would be incredibly helpful to get some  additional guidance and support from AS and are requesting the following:
A development hub maintained by AS that includes:

  *   AS development plans (clearly stated and with target timelines)--this will ensure that users do not embark on development that is already planned (it is difficult to get a clear picture from Pivotal Tracker);
  *   a more formal process for submission of development requests, including a promise that submissions will be addressed with follow-up;
  *   centralized place where community member development plans can be vetted and shared--the AS listserve and GoogleGroup and great for communication but not tracking development.
AS guidelines regarding core code and plug-in development, including

  *   process by which AS reviews core and plug-in development requests;
  *   development of best practices (are there things folks can do to increase the likelihood that the enhancement can be integrated to the core code if deemed valuable to the community?); and
  *   recommendations for vendors.
We believe guidelines and a development hub will facilitate community development and engagement and will maximize the benefit of individual development goals for all members and users. Thank you for your consideration.

On behalf of the  Yale ArchivesSpace Committee<http://guides.library.yale.edu/archivesspace>,
Mary Caldera and Mark Custer
Co-Chairs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141113/0b0b811c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7640 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20141113/0b0b811c/attachment.png>