OpenWetWare:Steering committee: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
No edit summary
 
(232 intermediate revisions by 29 users not shown)
Line 1: Line 1:
Right now this is a volunteer-based committee, if you want to help out please sign your name in one of the goal areas.  Currently the set of goals outlined are mapped from the [[ICampus Application for OWW|iCampus application for OWW]], so feel free to add or edit these but it seemed like a good starting point.
{{Template:Steering committee}}


=Goals=
{| cellspacing="3"
|-
|width="350px" class="green3" |


==Software development==
:<font size=3>'''Spotlight'''</font>
In order to facilitate user interactions with OpenWetWare, we would like to establish a UROP position to work on a variety of software tools:
:*[[OpenWetWare:Steering committee/Meeting - June 2008|Notes from June 2008 meeting]]
#Tools to simplify data entry into the wiki
:*[[OpenWetWare:Steering committee/Meeting - May 2008|Notes from May 2008 meeting]]
#*'''Word''' - word macro to convert formatting to wiki markup.  Improve the html->wiki markup scripts
:*[[OpenWetWare:Steering committee/Meeting - April 2008|Notes from Apr 2008 meeting]]
#*'''Excel''' - improve the CSV-> wiki markup converter.  Add support for chart addition.
:*[[OpenWetWare:Steering committee/Meeting - March 2008|Notes from Mar 2008 meeting]]
#*'''Powerpoint''' - Auto-image saving and uploading of slides.  Transfer of slides to word files and then convert to wiki markup.
:*[[OpenWetWare:Steering committee/Meeting - February 2008|Notes from Feb 2008 meeting]]
#*'''LaTeX''' - expanded math support.  LaTeX->wiki converter.
:*[[OpenWetWare:Steering committee/Meeting - January 2008|Notes from Jan 2008 meeting]]
#*'''Images''' - expanded image format support, automated uploading of sets of images.
:*[[OpenWetWare:Steering committee/Meeting - December 2007|Notes from Dec 2007 meeting]]
#* For further information see this [[Converting documents to mediawiki markup | page]] on existing document converters.
:*[[OpenWetWare:Steering committee/Meeting - November 2007|Notes from Nov 2007 meeting]]
#Tools to map wiki pages onto static websites.
#*Further automate the existing script.
#*Include CC license information on each dynamically created page.
#*Automatically set page width to an appropriate value.
#Login
#*Add support for MIT certificates. 
#*Write script to automatically create login accounts based on a list of email addresses in CSV format.
#Tools to integrate permanent and evolving documents.
#*Discussion pages for DSpace documents
#*Markup for DOI's (just as there is markup for urls and wiki pages)
Ideally, we hope to coordinate with the MediaWiki open source community on tools that are likely to be of general use to the community (MediaWiki is the open source software that OpenWetWare is based on).


===Contacts===
|width="350px" class="green3" |
*Principle contact:
*Other contributers:


==Cultivation of user base==
:<font size=3>'''Town Hall Meetings'''</font>
The success of OpenWetWare depends critically on cultivating and maintaining an active user base.  We plan to dedicate funds to enable tutorials, conference visits, advertising, and other mechanisms for recruiting new users to OpenWetWare.


===Contacts===
:* OWW Town Hall Meetings are held on the 2nd Thursday of every month. For information, visit the    [[OpenWetWare:Steering_committee/Town Hall Meeting|Town Hall Meeting]] page. (Note: to view the meeting page, click on the calendar date.)
*Principle contact: [[Sri Kosuri]]
*Other contributers: [[Jason Kelly]], [[Danielle France]], [[Barry Canton]], [[Reshma Shetty]]


==Data management==
:<font size=3>'''SC Mailing List'''</font>
In the long term, the success of OpenWetWare relies on the assumption that the number of users actively curating the information of OpenWetWare will scale with the amount of content generated.  However, there has been little work to examine how collaborative tools can best be used to develop information resources, such as the OpenWetWare protocol collection.  We believe the project would benefit dramatically from the active establishment of community standards for organizing content in OpenWetWare.  We will establish a UROP position to evaluate and implement templates and other methods for organizing information in OpenWetWare.


===Contacts===
:*This list has restricted membership and is unmoderated.  If you would like to help, please participate in the [[OpenWetWare:Steering committee]] activities. You can sign up [http://groups.google.com/group/openwetware-discuss here].
*Principle contact: [[Jeff Gritton]]
*Other contributers:


==Integration with laboratory classes==
:<font size=3>'''News'''</font>
To complement its mission to promote an open culture in biological science and engineering, OpenWetWare will be integrated into the curriculum of laboratory classes.  As a pilot experiment, MIT's [[BE.109 | BE.109 Laboratory fundamentals of biological engineering]] will be relying heavily on OpenWetWare to disseminate course content and to serve as a shared space for students, TA's and instructors to communicate.
:*April 17 2008: 12-1p EST OWW action hour.  Meet in the wiki chat room: http://openwetware.org/chat/.
.


===Contacts===
|-
*Principle contact: [[Natalie Kuldell]]
|}
*Other contributors: [[Reshma Shetty]]
=Specific Benchmarks for May 2006=
==Community Benchmarks==
*30 academic labs
*750 users
*3000 uniques visitors/day
(Each of these is ~3X the number currently on the site)
*Send representatives to 2 conferences (ASCB & ?)
==Content Benchmarks==
*Improve software tool to convert wiki->static webpage
*Design and implement protocol templates
*Integrate into BE.109 curriculum
*1400 content pages (2X current amount)


=Timeline=
The tasks of greatest initial importance lie in building the usage infrastructure of OpenWetWare; i.e., quantifying the current usage and developing the tools and guidelines that will be needed to continue its growth. This timeline is written with this initial output in mind. It is expected that many of the up-front analysis and development tasks will morph into more curative duties as the year progresses. Some tasks will be better suited to a time when more of the infrastructure is in place. For example, we might wait until the summer to begin merging OpenWetWare with fall class curricula.


Regular committments include monthly committee meetings.


12.2005:
__NOEDITSECTION__
*Advertise for two UROP positions: software development and usage statistics & analysis
__NOTOC__
*Compile initial observations of wiki usage, desired software improvements, and specific tasks for UROP positions
*Make initial advertising materials (business cards, advertising & lab invitation emails)
 
01.2006:
*Review findings of Usage/Data Management UROP
*Formulate usage guidelines and develop their implementation
*First recruitment/introductory tutorial luncheon
 
02.2006:
*Review protocol templates, conversion tools, links to static webpages
*Implement usable tools with current users
*Second recruitment/introductory tutorial luncheon
 
03.2006:
*Design set of advertising materials (posters, mailings, etc) and have printed
*Develop outreach strategy: identify relevant conferences & meetings, etc.
*Third recruitment/introductory tutorial luncheon
*Recruit at Bioengineering Department Retreat
 
04.2006
*Fourth recruitment/introductory tutorial luncheon
 
Summer.2006:
*Develop tutorials for integration with BE.109 and 7.02
*Hold large-scale 'brush-up' tutorial for all current users
*Usage/Data Management UROP develops strategy for integration with DSpace
*Attend Wikimedia conference: [http://meta.wikimedia.org/wiki/Wikimania_2006 Wikimania]
 
Fall.2006:
*Develop institution-specific information hubs
*Fifth recruitment/introductory tutorial luncheon
 
===Timeline 'enforcers'===
*Principle contact:
*Other contributers:
 
=Budget=
 
''A tentative budget, please revise.''
 
*$6000 for a UROP dedicated to software tools development
*$6000 for a UROP dedicated to data management
*$2000 for advertising materials
**OpenWetWare gathering in Boston
**poster and business card printings
**poster mailing
*$5000 for travel funds to conferences
**conference registration
**travel expense
**Additionally, students traveling to conferences to present research will also be able to spread information about OWW without requiring direct support.
**Which conferences? (please add!)
***[http://www.ascb.org/meetings/am2005/ ASCB] (Dec 10-14, 2005)
***[http://www.icsb2006.org/ ICSB] (June 18-21, 2006)
***[[Synthetic Biology:Conferences|SB2.0]] (May 20-22, 2006)
***[http://www.ibeweb.org/meetings/2006/index.cgi IBE] (March 10-12, 2006, Tucson, Arizona)
*$2000 to hold Boston-area OpenWetWare tutorial sessions
**travel to and from session
**refreshments
*$1000 for OpenWetWare steering committee administrative costs
*$5000 for sponsorship of weekly contributions to a 'big-name' blog
**Funds would be contingent on us having someone lined up by the mid-point meeting with iCampus.

Latest revision as of 13:59, 20 October 2008

The OpenWetWare Steering Committee is charged with leading the future direction of OpenWetWare. The steering committee is open to all OWW members, and we are actively seeking participants. You can add yourself to the discuss mailing list.

Members
Who's Involved?
Action List
Action items this month
Next Meeting
Suggested topics
Meetings
Agendas & Notes

Spotlight
Town Hall Meetings
  • OWW Town Hall Meetings are held on the 2nd Thursday of every month. For information, visit the Town Hall Meeting page. (Note: to view the meeting page, click on the calendar date.)
SC Mailing List
  • This list has restricted membership and is unmoderated. If you would like to help, please participate in the OpenWetWare:Steering committee activities. You can sign up here.
News

.