OpenWetWare:Steering committee: Difference between revisions

From OpenWetWare
Jump to navigationJump to search
Line 65: Line 65:


===Contacts===
===Contacts===
*Principle contact: [[Reshma Shetty]]
[[Natalie Kuldell]], [[Reshma Shetty]]
*Other contributors: [[Natalie Kuldell]]


=Meetings=
=Meetings=
*[[OpenWetWare steering committee/Meeting - 1/6/06 |1/6/06]]
*[[OpenWetWare steering committee/Meeting - 1/6/06 |1/6/06]]

Revision as of 18:06, 9 January 2006

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. Please add yourself, or email any of the members for further information.

Members

Barry Canton
Austin Che
Drew Endy
Danielle France
Jeff Gritton
Jason Kelly
Sri Kosuri
Natalie Kuldell
Alex Mallet
Reshma Shetty
Devin Strickland
Ilya Sytchev

Projects

Software development

In order to facilitate user interactions with OpenWetWare, we would like to establish a UROP position to work on a variety of software tools:

  1. Tools to simplify data entry into the wiki
    • Word - word macro to convert formatting to wiki markup. Improve the html->wiki markup scripts
    • Excel - improve the CSV-> wiki markup converter. Add support for chart addition.
    • Powerpoint - Auto-image saving and uploading of slides. Transfer of slides to word files and then convert to wiki markup.
    • LaTeX - expanded math support. LaTeX->wiki converter.
    • Images - expanded image format support, automated uploading of sets of images.
    • For further information see this page on existing document converters.
  2. 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.
  3. Login
    • Add support for MIT certificates.
    • Write script to automatically create login accounts based on a list of email addresses in CSV format.
  4. 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).

People

Barry Canton, Austin Che, Sri Kosuri, Jason Kelly, Alex Mallet, Ilya Sytchev

Community Development

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.

Finally, we want to begin an OpenWetWare seminar series hosted at MIT. This series would discuss perspectives on open practices and communities in science. We feel this would be important for two reasons. First, it would highlight groups and individuals in science actively striving to accomplish some of the same goals as those of OpenWetWare (e.g. PLoS, Science Commons, etc.) Second, it would provide an amazing opportunity before every talk to introduce OpenWetWare to others.

People

Barry Canton, Danielle France, Jason Kelly, Sri Kosuri, Reshma Shetty

Promotional Material/Advertising

In order to help promote OpenWetWare, we will need a range of promotional material including business cards, information pamphlets, posters and banners. As I see it, we probably need a graphic artist for two jobs: a logo (for poster, banner, and business cards), and a full page design for the pamphlet cover.

Samantha suggested going with Painted Frog Studio who did the poster and logos for the Synthetic Biology 1.0 conference.

Contacts

Sriram Kosuri, Ty Thomson

Data management

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

Jeff Gritton, Jason Kelly, Sriram Kosuri, Reshma Shetty

Integration with laboratory classes

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 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.

Contacts

Natalie Kuldell, Reshma Shetty

Meetings