...
Time | Item | Who | Notes |
---|---|---|---|
25 min | Review interviews and next steps | All | What did we learn? What must still be done? How do we "finish" the asset inventory? |
25 min | Recommendation Process | All | How will we develop recommendations? |
10 min | Next meeting | All | When do we meet again? What do we need to have accomplished? |
Notes
- Updates on the asset inventory, questions, and/or work still to be done
- Mike – waiting to hear back from Chris, Lauren from Kristi, Alex from Stephen, and Jon from Miles
- Recommendations – what might become of some of these things, with the general notion that a little less would be a lot more
- General notion - abandoned sites are not good to leave up
- some can just go away
- others will have to be harvested before moving
- leaving a breadcrumb trail may be necessary in some cases, but with Google may not be necessary
- Sourceforge repository
- move to GitHub? eventually shut it down and move the whole thing – just moving files, and we're not encouraging people to use the old releases - more for us than for the community at that point
- use search functions
- better than having to poke around more than one site
- move to GitHub? eventually shut it down and move the whole thing – just moving files, and we're not encouraging people to use the old releases - more for us than for the community at that point
- Listservs
- several of them are most likely useful as CRM material – who had been engaged, when, for what – a tag in a CRM system
- several of them are most likely useful as CRM material – who had been engaged, when, for what – a tag in a CRM system
- General notion - abandoned sites are not good to leave up
Action items