Difference between revisions of "WormBase Staff Resources"
| Line 3: | Line 3: | ||
= Accounts = | = Accounts = | ||
| − | WormBase uses a number of tools provided by Google Apps to facilitate collaboration, increase transparency, and decrease administration requirements. | + | WormBase uses a number of tools provided by Google Apps to facilitate collaboration, increase transparency, and decrease administration requirements. This list includes WormBase documents (Docs), email (Gmail), a project calendar, discussion lists (Google Groups), collaborative chat, and contact information for all team members. |
| − | |||
| − | This list includes WormBase documents (Docs), email (Gmail), a project calendar, discussion lists (Google Groups), collaborative chat, and contact information for all team members. | ||
Project members with a '''you@wormbase.org''' account automatically have access to core documents, contact information across the project, and automatic privileges on the new WormBase site. | Project members with a '''you@wormbase.org''' account automatically have access to core documents, contact information across the project, and automatic privileges on the new WormBase site. | ||
| − | Interested users can request an account from Todd. | + | Interested users can request an account from Todd. Uninterested users can subscribe to things like the mailing lists but won't benefit from the seamless integration of these collaborative tools. |
= Discussion Groups (Mailing Lists) = | = Discussion Groups (Mailing Lists) = | ||
Revision as of 22:31, 23 November 2010
This document describes collaborative tools available to WormBase team members.
Contents
Accounts
WormBase uses a number of tools provided by Google Apps to facilitate collaboration, increase transparency, and decrease administration requirements. This list includes WormBase documents (Docs), email (Gmail), a project calendar, discussion lists (Google Groups), collaborative chat, and contact information for all team members.
Project members with a you@wormbase.org account automatically have access to core documents, contact information across the project, and automatic privileges on the new WormBase site.
Interested users can request an account from Todd. Uninterested users can subscribe to things like the mailing lists but won't benefit from the seamless integration of these collaborative tools.
Discussion Groups (Mailing Lists)
WormBase uses a number of mailing lists for discussion. You can manage subscriptions yourself, add posts, view threads, and search the archive all from the web.
Creating your own discussion group
With your wormbase.org account, you can also create your own groups, a perfect way to support new projects. One advantage of this approach over using ad-hoc distribution lists in your email client is the ability to archive discussions and made searchable to wormbase.org account holders or to the wider web. This option can be disabled if desired.
See the groups main page for details.
Calendar
*@wormbase.org account holders can add and edit events on the official WormBase calendars.
There are two calendars:
- WormBase Details -- a calendar of project events, including conference calls, build deadlines, etc
- WormBase Public Events -- a calendar listing public events like meetings
Documents
WormBase documents are available at:
*@wormbase.org account holders can access email at:
If desired, email can be forwarded to a secondary account.
Contacts
Social Media
Blog
The official WormBase blog is called "M9":
This is our primary vehicle for communication with users. You can subscribe to the blog via email at:
Our Twitter account is:
We have a secondary account for source code commits:
Issue Tracker
WormBase has a single unified issue tracker. Be sure to sign up as a follower of the project so that you can track and follow through on issues you report!
General policies:
- Don't worry if something warrants reporting. If in doubt, report it!
- Report issues related to web development to Todd for triage.
- Include as much detail as necessary to explain the issue.
- Keep track of issues you report; if there isn't progress, "bump" the issue or leave a comment.
Source Code
Source code is currently maintained in Mercurial (hg):
