 |
 |
Should we attempt to tackle the 4 together as a group moving through each one, or break into 4 groups with each group taking one use case? Does the WG have any preferences? karen On 12/8/11 11:09 AM, "Priscilla Caplan" <[log in to unmask]> wrote: >Ah ok, thanks. > >On 12/8/2011 11:04 AM, Owens, Trevor wrote: >> Thanks Priscilla, >> >> To clarify, I was thinking of this as taking on all four different >>situations Andrea described in the use cases PDF. >>http://www.loc.gov/extranet/wiki/osi/ndiip/ndsa/images/6/6d/Use_case.pdf >> >> So we would work out the questions for each of these (or some agreed >>upon subset or refinement of them) and invite discussion and feedback on >>the questions for each of the four use cases. >> >> From that doc: >> >> 1. Member needs to choose software solutions, potentially open source, >>for a project. >> 2. Member learns of an opportunity to participate in an existing >>project to collaboratively develop an open source software product. >> 3. Member sees an opportunity to initiate the development of a >>collaborative open >> source software product. >> 4. Member has locally-developed software that could be made open source >> >> >> -----Original Message----- >> From: The NDSA infrastructure working group list >>[mailto:[log in to unmask]] On Behalf Of >>Priscilla Caplan >> Sent: Thursday, December 08, 2011 10:41 AM >> To: [log in to unmask] >> Subject: Re: [NDSA-INFRASTRUCTURE] Proposed Sketch of Next >>Infrastructure Project >> >> This is fine but it only covers the issues involved in adopting open >>source software. I thought the scope also included issues in offering >>open source software -- e.g., I have this tool, application, whatever, >>should I release it under an OSS license? Use SourceForge or some other >>mechanism? Maintain control of the code or of commits? Etc. Is that a >>different project? >> >> p >> >> On 12/8/2011 8:09 AM, Karen Cariani wrote: >>> Trevor, >>> >>> What a great start to our next steps! >>> >>> I can already list some people to invite to present to us. How about >>> Jon Dunn from Indiana University, Tom Cramer of Stanford University, >>> someone from Univ of Virginia, Adam Wead of Rock and Roll Hall of Fame. >>> >>> I also think the schedule of activities is very manageable and will >>> help us move forward. >>> >>> What does everyone else think? >>> >>> Karen >>> >>> On 12/7/11 4:12 PM, "Owens, Trevor"<[log in to unmask]> wrote: >>> >>>> Fellow NDSA Infrastructure Working Group Members, >>>> >>>> I wanted to try and sketch out a way for us to practically tackle the >>>> next project we have started talking about. I would be thrilled to >>>> chat about how to either 1) refine this idea or 2) entertain >>>> alternative ways of framing the project. It would be great to go back >>>> and forth on the list about this idea a bit. >>>> >>>> I have also posted the following to the wiki at >>>> http://www.loc.gov/extranet/wiki/osi/ndiip/ndsa/index.php?title=Open_ >>>> Sourc >>>> e_Software >>>> >>>> *Title* >>>> 25 Questions to ask when considering open source software for digital >>>> stewardship and preservation >>>> >>>> *Goal* >>>> Refine a set of questions or a decision tree that we provided to help >>>> guide decisions around open source software's use in digital >>>> preservation and digital stewardship. >>>> >>>> *Process* >>>> We work off of Andrea's set of use cases and refine the cases into a >>>> set of questions to answer in each use case situation. Then we set up >>>> a series of calls with people we identify as having some particular >>>> insight and or expertise. We send them the revised document before >>>> hand, and then give them a chance to comment on the initial set of >>>> questions. They can offer stories of times when a given issue was >>>> particularly important, make suggestions for how they would >>>> prioritize these issues, remark on what they think should also be >>>> included or if there are some things that don't need to be included. >>>> We take significant notes on each of the calls and post those up on >>>> the wiki as we go. So, we would have monthly calls with one expert a >>>> month for, say five or six months. After each call we would tweak our >>>> document in light of the previous calls and organize our notes to >>>> keep track of things we will want to talk about in a final report >>>> that accompanies the final revised set of questions. At the end of >>>> this process we would have a set of organized questions that partners >>>> could use as a tool, we would then also produce a report that >>>> explained why these were particularly important questions based on >>>>our own experience and including commentary from those involved in the >>>>process. >>>> >>>> *Schedule* >>>> Here is a quick schedule I would suggest for working on this: >>>> 1.January we identify, contact, and schedule our conference call >>>> speaker/commenters 2.Feb through June we do monthly calls with >>>> speakers, taking notes and iteratively revising our set of questions. >>>> 3.July we share the questions and something reflecting on their >>>> development at the NDIIPP/NDSA partners meeting. >>>> 4.Aug-September, we draft the final report doc 5.October-December we >>>> would disseminate the resulting products and start planning our next >>>> project. >>>> >>>> I could imagine we would work with a mixture of speakers from inside >>>> and outside the NDSA. For example, several of the members are leading >>>> significant open source projects and many of the members are also >>>> doing a lot of decision making decisions about using, releasing, or >>>> participating in the development of open source systems. >>>> >>>> I am interested in your general thoughts about this, any comments and >>>> suggestions you have, or any alterative proposals for how you would >>>> like to go about this. >>>> >>>> Best, >>>> Trevor >>>> >>>> Trevor Owens >>>> Digital Archivist >>>> National Digital Information Infrastructure and Preservation Program >>>> Office of Strategic Initiatives The Library of Congress >>>> 101 Independence Ave SE >>>> Washington DC 20540-1300 >>>> 202.707.7217 >>>> >>>> ############################ >>>> >>>> To unsubscribe from the NDSA-INFRASTRUCTURE list: >>>> write to: >>>> mailto:[log in to unmask] >>>> OV >>>> or click the following link: >>>> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDS >>>> A-INF >>>> RASTRUCTURE&A=1 >>> ############################ >>> >>> To unsubscribe from the NDSA-INFRASTRUCTURE list: >>> write to: >>> mailto:[log in to unmask] >>> V >>> or click the following link: >>> http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA >>> -INFRASTRUCTURE&A=1 >>> >> ############################ >> >> To unsubscribe from the NDSA-INFRASTRUCTURE list: >> write to: >>mailto:[log in to unmask] >> or click the following link: >> >>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-IN >>FRASTRUCTURE&A=1 >> >> ############################ >> >> To unsubscribe from the NDSA-INFRASTRUCTURE list: >> write to: >>mailto:[log in to unmask] >> or click the following link: >> >>http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-IN >>FRASTRUCTURE&A=1 >> > >############################ > >To unsubscribe from the NDSA-INFRASTRUCTURE list: >write to: >mailto:[log in to unmask] >or click the following link: >http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-INF >RASTRUCTURE&A=1 ############################ To unsubscribe from the NDSA-INFRASTRUCTURE list: write to: mailto:[log in to unmask] or click the following link: http://list.digitalpreservation.gov/SCRIPTS/WA-DIGITAL.EXE?SUBED1=NDSA-INFRASTRUCTURE&A=1