Date
06
Attendees
Regrets
Goals
- Review, next steps
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 25 min | Review interviews and next steps | All | How do we "finish" the asset inventory? |
| 25 min | Recommendation Process | All | How will we develop recommendations? |
| Refinement of recommendations regarding email and forum | Jim, all | ||
| 25 min | Finishing the work of the task force | All | |
| 10 min | Next meeting | All | When do we meet again? What do we need to have accomplished? |
Notes
We had started talking about how to make recommendations on the last call, and shared the inventory at the beginning of the week – not surprisingly, with no feedback so far.
Thinking that the recommendations could follow the categories instead of the domains --
- One way : for example, should we focus on development as a domain – invest in this, stop doing that, tighten up development
- and we could similarly write recommendations about governance or training
- Alternative : look at the types of resources, such as email lists, and solve them across purposes based on the best solution for that type of communication
- Or deal with each asset
- Would it be helpful to establish goals or principles
- e.g., reduce redundancy to reduce maintenance and improve the ability for people to find things
- Paul – everything has to justify its ongoing existence – we have a baseline level of noise from having too many things out in the ether – everyone should be able to understand the overall structure so not only the most involved people know where things are
- May need some temporary resources, like the Hackathon email list – we just need to get rid of them when we're done, but would be valuable to preserve the knowledge that a person participated in a CRM function
Notes
- Jim presented some thoughts on sourceforge, email, email archives and forum software.
- The materials in sourceforge are mostly moveable. Some are obsolete and can be taken down without loss of function. Others would need to be moved.
- Email could move to Google Groups, but there is no clear path for the mail archives. Nabble http://www.nabble.com provides a possible solution for the mail archives.
- Discourse http://www.discourse.org/ appears to be a leading candidate for forum software. Open source with a reasonable hosting option. Active project. Good uptake. Simple interface.
- Possible that email could be used for digests, overviews, mass market type communication and forum software used for more in depth conversation. Similar to the distinction between the web site (lightweight use) and the wiki (more in depth use).
- Mike discussed a way forward for the task force to finish it's work
- Draft recommendations available here: https://goo.gl/vm343S
- Task force members review, revise, comment
- Comments incorporated and an improved version available for discussion for our next meeting June 1
- Document revised based on our meeting of June 3
- Document shared with community between June 6 and June 13. Mike will be at Open repositories and unavailable for a call on June 10.
- Task force incorporates and prepares "final" report for June 17 meeting.
- Report presented to Steering Group for their meeting on June 19.
- Task force work is concluded. If we were all in one place, we would have a beer or other beverage to celebrate
Action items
- All task force members review draft document, add comments, revisions in preparation for discussion
...
...