[Archivesspace_Users_Group] FW: Common script repository?

Mon Apr 25 13:53:38 EDT 2016

I tried to send this 3 weeks ago, but just realized it may not have gone through. Trying again.

Circling back around on this, it seems as though most people are in favor of managing this sort of information directly in Github somehow. I think we can run into some of the same problems (advertising the location of a github org, adding members, etc.) as we have on the Wiki, but github does make more sense to handle code.

As of right now I think there are two ends of the spectrum:

1.       Create a github.io page with links to separate github repos

2.       Create a github organization and have people fork their repos into this new organization

I'm sure there are some options in between the two if others more familiar with github have some ideas. I think both have their pros and cons. The github organization would require diligent updates to make sure the forked repos are actually the same as the original master branch if there are ever any updates.

Thoughts? Suggestions?

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Thursday, March 31, 2016 10:24 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Common script repository?

Dear Tom,

The FAQ on the ArchivesSpace website is still pretty accurate on this topic (see http://archivesspace.org/faq#memberbenefits). We could definitely add explicit mention of the wiki (http://wiki.archivesspace.org) there given that it's a point of confusion here. As far as the different channels go, the wiki itself is public and explains the various channels and tools we use for communication, development, and community interaction. When channels are only available to members, we mention that. If we don't mention it being closed, it's open.

Given the number of inquiries we get that way, I think most people realize that we do have a public email address (ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>) that reaches members of the program team. Lots of people use it to contact us with general and more specific questions about the application, membership, and other services and activities. While we can't provide much in the way of technical support through that channel for non-members, we do not distinguish between members and non-members in answering questions about the application and pointing people in the direction of other resources available to them, regardless of what they decide about membership.

But I know when there is confusion, there's a reason. We can definitely go over our online sites and materials we give out at conferences with an eye toward ways to make this clearer. If any of you have ideas or suggestions of what would help you or colleagues that have these concerns, we'd be very glad to have them.

Christine

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tom Cramer
Sent: Wednesday, March 30, 2016 1:50 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Common script repository?

Christine,

Thanks for this. Is there a concise summary somewhere of what ArchiveSpace resources and channels are publicly available, and which are restricted to members and/or ASpace governance groups? I am having a hard time grokking the current constellation-and it seems I might not be the only one.

Thanks,

- Tom

On Mar 30, 2016, at 4:22 AM, Christine Di Bella <christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>> wrote:

Not to sidetrack this discussion, but in case there is confusion here, most development and tech resources, including the ArchivesSpace wiki page mentioned in this thread, are not limited to members. The pages are public. (A Google search for "archivesspace plugins" brings up that wiki page as the first result.) That, of course, doesn't mean the current plugins page on the wiki is the best place to share these items. I'd prefer to have that page just point to a community-run repository on Github or somewhere else that the people doing the bulk of that dev work decide on and find easy to contribute to, since it sounds like the wiki isn't that place.

In the case of the wiki, anyone - member or nonmember - can request an account to edit community pages. In the case of the github documentation, anyone can join the archivesspace repository and submit a pull request to make the documentation better. There are people within the member community and program staff that have more responsibilities and editing/approval privileges than others, but most of the efforts themselves are open to all.

Just wanted to clarify that for people who may not realize. This is a great discussion and I'm looking forward to seeing what you decide.

Christine

Christine Di Bella
Community Outreach and Support Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905<tel:800.999.8558;2905>
678-235-2905<tel:678-235-2905>
cdibella13 (Skype)
<image001.png>

On Mar 30, 2016, at 4:06 AM, Chris Fitzpatrick <Chris.Fitzpatrick at lyrasis.org<mailto:Chris.Fitzpatrick at lyrasis.org>> wrote:

100% agree.

I think development and tech stuff should be moved on the other side of the paywall.

b,chris.

Chris Fitzpatrick | Developer, ArchivesSpace
Skype: chrisfitzpat  | Phone: 918.236.6048
http://archivesspace.org/

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Mayo, Dave <dave_mayo at harvard.edu<mailto:dave_mayo at harvard.edu>>
Sent: Tuesday, March 29, 2016 5:02 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Common script repository?

Also interested - I think it needs to be somewhere that's more publicly accessible than the ASpace wiki (I think Github more or less qualifies, as there's no money/institutional barrier to making a PR or editing wiki.

- Dave

From: <Suda>, Phillip J <psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Tuesday, March 29, 2016 at 9:55 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Common script repository?

Patrick,

                I was thinking of about this very thing this morning: where can I post some of my plugins or scripts to share with the larger community?

I personally like the Github org/repository idea.

Thanks,

Phil

Phillip Suda
Systems Librarian
Howard-Tilton Memorial Library
Tulane University
psuda1 at tulane.edu<mailto:psuda1 at tulane.edu>
504-865-5607

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Galligan, Patrick
Sent: Tuesday, March 29, 2016 8:51 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Common script repository?

Hi all,

Right before and during Code4Lib there was some talk about the best place to advertise the work different people have been doing with scripts related to ArchivesSpace, and the best way to collect or get the word out about the stuff we're doing.

I will preface this with saying that I am aware of the Plugins and Scripts pages on AS found here (https://archivesspace.atlassian.net/wiki/display/ADC/Plugins+and+Scripts<https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_wiki_display_ADC_Plugins-26-2343-3Band-26-2343-3BScripts&d=CwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=_Mv1dY22K7jvT5MD7xjbvGVzRDOUMhx4WYcnPSIzYnE&m=oK4sZVbMfDUF13TMY2f2OJ48vfRt-dMChBXE042QBaI&s=VR-b29Pf-vKdhZ3l0DyhsLdrtqIgQtAQqOf78mvBqLE&e=>), but it doesn't seem very comprehensive at all, and is primarily plugins. I just wanted to get the conversation started about the best way to get the word out and get people involved.

We could:
1.       Keep things the way they are, just be more vocal about advertising the wiki page to a wider audience
2.       Create a Github organization where people could add the repositories that they're working on. We would need a couple of people managing the org and adding anyone that requests membership.
3.       Something else?

I really just wanted to get the conversation started. Does anyone else know a better way to share the work we've been doing with a wider community?

Patrick Galligan
Rockefeller Archive Center
Assistant Digital Archivist
914-366-6386

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160425/ab7af83f/attachment.html>