Do you want to change the future of scientific communication? Are you looking for a unique opportunity to empower scientists to openly share information? OpenWetWare.org (OWW) is a community of thousands of scientists from around the world that openly share their research, tools, and practices. The project has been a volunteer effort to date and we are now looking to hire our first two employees.
Chief executive officer
The principle responsibility of this position is to shepherd OWW’s transition from a volunteer, academic initiative, to a self-sustaining community over a 3 year timeframe. The position would require seeking partnerships with other organizations or funding agencies and aiding in the development of self-sustaining business models. Other responsbilities will include actively cultivating the growth of new communities on OWW and supporting existing ones.
Applicants should have:
- Excellent communication, writing, organizational, and management skills.
- Previous experience in business development or funding academic initiatives.
- Most importantly, an enthusiasm for helping OpenWetWare improve how scientists share information, learn, and collaborate. \
Senior software engineer
- Develop MediaWiki software extentions based on recommendations by the community
- Interface and manage other developers and volunteers on production of shared software resources. This may include integration with scientific databases,
- Manage server responsibilities (i.e., resource allocation, backups, etc) across various projects.
Successful applicant should be proficient in LAMP environments (Linux, Apache, MySQL and PHP). Experience with both system administration and web programming is ideal. Familiarity with MediaWiki software is a large plus. Ability to work independently and interface with open-source communities.
Notes from Meeting
(feel free to add)
- Possible positions:
- Technical Administrator / Extension Developer
- Responsibilities would include server maintenance, updating Mediawiki distribution, OS, etc. Would be nice to have capability to develop custom extensions as well (though there was some concern about the how those would be maintained long-term).
- Community Developer
- Responsible for cultivating the growth of communities on the site. These would include things like technical communities, new-user admin/welcoming, information management (e.g. consensus protocols), etc.
- Founding CEO / Evangelist
- Responsible for raising money, talking to the press, etc.
- Suggested that before we can get this person we need to have a tighter description of the long-term mission of the site (since we would need someone who was very passionate about it).
- Technical Administrator / Extension Developer
- Comments on why a Community Developer would be useful.
- There was concern that by focusing too much on the specific things we would like an employee to work on (e.g. a new extension or a help page) we would be creating a non-scalable system for getting these things done in the long term. (and also a system with an expiration date when the finding for the employee ends in a year).
- Alternatively, we should could focus on hiring someone who would cultivate volunteer communities from the OWW user community. They would essentially be there to facilitate the growth of many of these groups rather than take on leadership of any particular one.
- we decided to specify the job descriptions for the technical/admin and community developer positions and wait on the CEO position for the time being.
- It was also suggested that we should pursue supplemental funding if we find a person we want but can't afford. (the thought was that it would be easier to get additional funds since we have some now, and we'll have a clear target for its use)
- Possible short-term goal: Develop a more open (as in making what OWW offers and how one can help more obvious than Community Portal) community in order to find motivated users to be recruited as "Community Developer(s)". Possible way is to have a page of "OpenWetWare Services" listed like Google Products. I will start working on this in the next week and present my material by the next meeting. -- Jenny
Brainstorming for job description
Figured this might be a good way to start to specify the things we'd like an OWW employee to work on. (in no particular order - please add!)
- Upgrades to Mediawiki
- Testing compatibility of extensions and addons (UMS, mailing lists, etc)
- Installing new extensions and their prerequisites
- Disk, CPU and memory usage
- Security: intrusion attempts, etc
- Capacity planning
- Hardware and software benchmarking/tuning
- Server migration
Development of new technical tools
- Being able to develop MediaWiki extensions would be a 'nice-to-have'
- OWW software distribution / private wiki roll-out
- how to integrate with existing/future tools
Development of new wiki content
- Tutorial pages (how to start a new lab)
- Help pages
- Maintain a calendar of conferences, workshops and events relevant to OWW community (calendar idea mentioned during last SC)
- Develop the Directory of people and improve visibility on available ressources/skills within OWW community (maybe linked to categorization)
- Foster a community
Organization of existing content
- Information management
- Categorization, Semantic web
- User Management
- Deleting pages
Spokesperson / CEO
- Getting more funding
- writing OWW concept paper for circulating with potential sponsors.
- Spokesperson for interacting with media / external parties
- Surveys, 'market research,' figure out what people want/need
- "Facts on the ground" - how much funds do we have available and what are the going salaries for the type of people we'd be looking to hire. (jason)
- Prioritize the list above
- Sketch up a rough draft of a job description
As decided at the last SC meeting, we'll be holding a seperate meeting to talk about hiring someone to work on OWW full/part time using the money available from the NIH grant. We'll need to decide what sort of background we're looking for / can reasonably find. If you're interested in contributing to the discussion but can't make the meeting, please write me (jasonk at mit dot edu) an email with your thoughts.
The meeting date will be Dec 5: Noon-1pm EST in Room 68-151. If you would like to call in please contant jasonk at mit dot edu. Thanks.