OpenWetWare:Steering committee/Goals

From OpenWetWare

(Difference between revisions)
Jump to: navigation, search
(Publishing results)
(Short term goals (6 months))
Line 29: Line 29:
*Suggestions?  I think having the defined goals might help, because it will provide obvious places for people to plug in.
*Suggestions?  I think having the defined goals might help, because it will provide obvious places for people to plug in.
*Welcoming committee - would help our overall retention of new people on the site, as well as more easily identify very excited folks and point them to SC-sponsored projects so they can get involved.
*Welcoming committee - would help our overall retention of new people on the site, as well as more easily identify very excited folks and point them to SC-sponsored projects so they can get involved.
 +
 +
===Improved technical infrastructure===
 +
*Based on the recent extended downtime of OWW, a top priority should be the implementation of better backend support for the site.
==Medium term goals (1-1.5 years)==
==Medium term goals (1-1.5 years)==

Revision as of 20:44, 9 August 2006

  • Jasonk 03:09, 9 August 2006 (EDT): At the retreat we decided that the steering committee would be responsible for prioritizing the areas where OWW would expend resources (whether time or $). To serve this I think we need to have a list of short-term goals. (and probably a long-term vision as well). I put this page up just to get the ball rolling, please add/edit anything and post comments.


Contents

Short term goals (6 months)

  • Since we are putting in place an organizational structure for the next 6 months, it seems like that is a good time frame for some short term goals.

Define a long-term organizational structure for OWW leadership

  • The new structure will be decided upon in December, and new officers will be elected in January.

Encourage the growth of (a wide variety) of communities on OWW

  • The reasoning here is that the most important thing is to continue to build a critical mass of users who are comfortable using the site in their daily research. Then if we want to role out more complicated things in the future we’ve got a user base to actually try them out with (and a userbase to suggest/develop new things in the first place). I think Jay's point at the retreat about wikis being included in OS 12, and the follow up discussion about how OWW is not principally a tool site supports this focus - the strength of OWW will be in the community of users that we've grown.
  • List of communities that would fit on OWW and brief examples of projects we could prioritize in support of them.
    1. Labs
      • tutorial for adding custom recent changes for your lab
    2. Courses
    3. Research fields (e.g. fanconi anemia, synthetic biology)
      • Improved discussion areas?
      • Lab RSS feeds
    4. Institutions
      • Could build up the MIT institution page (e.g. list all shared equipment, etc) as an example for other institutions to model after
    5. Resource Centers (e.g. MIT flow facility, Caltech Microfluidic Foundry)
      • Provides a great opportunity for the user community of a resource center to troubleshoot, share protocols, and interact with the employees of the center. The caltech foundry has already expressed some interest in this, and I think it would be a great fit for the MIT flow facility as well.
  • Recruiting new groups - advertising?
  • Lucks 07:23, 9 August 2006 (EDT): I might suggest that we do a survey of how current users use OWW and see if that gives us clues into how to expand the community. I thought the brief one we did at the beginning of the retreat already showed a variety of uses that were interesting and could be expanded upon. I also think that there are a number of users that could be encouraged to use the site more (myself one of them), and it would be nice to know the reasons why they are not using it more. Perhaps the SC could undertake this survey.
    • Kathleen 08:57, 9 August 2006 (EDT): Austin set this page up a while ago for testimonials, although no one has contributed to it yet. Maybe we could put this in a more visible place and encourage contribution to the page.
      • Lucks 10:10, 9 August 2006 (EDT): Maybe we can ask specific questions that will be easier to aggregate as well as allowing the open testimonials. In order to get a response, it might be better to set up an online survey that pops up on people's talk pages so that when they are using OWW they see the message until they do the survey.

Recruit superusers

  • Suggestions? I think having the defined goals might help, because it will provide obvious places for people to plug in.
  • Welcoming committee - would help our overall retention of new people on the site, as well as more easily identify very excited folks and point them to SC-sponsored projects so they can get involved.

Improved technical infrastructure

  • Based on the recent extended downtime of OWW, a top priority should be the implementation of better backend support for the site.

Medium term goals (1-1.5 years)

Shared resources

  • Encourage users to contribute to shared resources pages (protocols, materials, etc).
    • Tools for tagging/categorizing protocols so that they are automatically collected.
    • Improved mechanism for creating a new protocol or material page (e.g. go through a form that automatically creates links from common areas, things like that).

Long term goals(2-3 years)

Publishing results

  • Put in place mechanisms for users to share results in a way that enables them to receive credit (e.g., firm authorship, DOIs?). This would be moving into the territory of alt publishing models.
  • Would be helped by a universal author ID and mechanisms/metrics for measuring contribution to the site.
    • Austin 15:33, 9 August 2006 (EDT): There is an extension and may be incorporated into the MediaWiki core an OpenID module. I'm not clear about details, but it appears similar to a universal ID that you can use anywhere.
Personal tools