Difference between revisions of "WormBase Staff Resources"

From WormBaseWiki
Jump to navigationJump to search
Line 7: Line 7:
 
== Why wormbase.org accounts? ==
 
== Why wormbase.org accounts? ==
  
You might wonder what the benefit is of another account, particularly if you already have an email account.  Unifying resources like documents and calendars under wormbase.org '''facilitates collaboration'''.  It increases '''project transparency'''.  And it '''decreases administration overhead'''.
+
Perhaps you already have a caltech, oicr, google, or account on some other serviceBut a '''wormbase.org''' account is fundamentally different.  It's about collaboration.
  
With a wormbase.org account, you will automatically be granted access to project calendars, documents, a contact list of team members, subscriptions to mailing lists.  '''You''' can manage your own account information. As people matriculate onto the project they can quickly integrate with other team members and be brought up to speed with a shared corpus of documentation.  They'll have immediate access to remote members via Google Chat or Voice, too.
+
Unifying resources like documents and calendars under wormbase.org '''facilitates collaboration'''.  It increases '''project transparency'''.  And it '''decreases administration overhead'''.
 +
 
 +
With a wormbase.org account, you will automatically be granted access to project calendars, documents, a contact list of team members, subscriptions to mailing lists.  '''You''' can manage your own account information. Moreover, a '''*.wormbase.org''' account instantly grants additional privileges on the new WormBase website.  As people matriculate onto the project they can quickly integrate with other team members and be brought up to speed with a shared corpus of documentation.  They'll have immediate access to remote members via Google Chat or Voice, too.
  
 
This seamless integration is provided by Google Apps and includes the following services:
 
This seamless integration is provided by Google Apps and includes the following services:
Line 19: Line 21:
 
* Google Chat
 
* Google Chat
 
* Shared Contacts
 
* Shared Contacts
 
Moreover, a '''*.wormbase.org''' account instantly grants additional privileges on the new WormBase website.
 
  
 
== What if you want a wormbase.org account but want to, say, read your email elsewhere? ==
 
== What if you want a wormbase.org account but want to, say, read your email elsewhere? ==

Revision as of 22:50, 23 November 2010

This document describes collaborative tools available to WormBase team members.

Accounts

It's strongly encouraged that all team members of WormBase request a wormbase.org account.

Why wormbase.org accounts?

Perhaps you already have a caltech, oicr, google, or account on some other service. But a wormbase.org account is fundamentally different. It's about collaboration.

Unifying resources like documents and calendars under wormbase.org facilitates collaboration. It increases project transparency. And it decreases administration overhead.

With a wormbase.org account, you will automatically be granted access to project calendars, documents, a contact list of team members, subscriptions to mailing lists. You can manage your own account information. Moreover, a *.wormbase.org account instantly grants additional privileges on the new WormBase website. As people matriculate onto the project they can quickly integrate with other team members and be brought up to speed with a shared corpus of documentation. They'll have immediate access to remote members via Google Chat or Voice, too.

This seamless integration is provided by Google Apps and includes the following services:

  • Gmail
  • Google Docs
  • Calendars
  • Discussion Groups
  • Google Chat
  • Shared Contacts

What if you want a wormbase.org account but want to, say, read your email elsewhere?

No problem. Log on to your account once and set your email to forward to your secondary account. Done. Note that you will still need to send email to the discussion lists (see below) using the account to which you are subscribed.

What if you don't want a wormbase.org account?

Fine. You can still subscribe to things like mailing lists. But you won't benefit from the seamless integration of these collaborative tools and you'll be less accessible to other members of the team.

Discussion Groups (Mailing Lists)

WormBase uses a number of mailing lists for discussion provided by Google Groups. 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. This is a perfect way to support new side projects. One advantage of this approach over using ad-hoc distribution lists in your email client is the ability to create searchable archives of discussions, available to the entire web or only subscribed members.

See the groups main page for details.

Calendar

*@wormbase.org account holders can add and edit events on the official WormBase calendars.

http://calendar.wormbase.org/

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:

http://docs.wormbase.org/

Any new documents created under your wormbase.org account can be easily shared with all other wormbase.org account holders.

Email

*@wormbase.org account holders can access email at:

http://mail.wormbase.org/

If desired, email can be forwarded to a secondary account.

Contacts

Social Media

Blog

The official WormBase blog is called "M9":

http://blog.wormbase.org/

This is our primary vehicle for communication with users. You can subscribe to the blog via email at:

http://feedburner.google.com/fb/a/mailverify?uri=wormbase&loc=en_US

Twitter

Our Twitter account is:

http://twitter.com/wormbase

We have a secondary account for source code commits:

http://twitter.com/wormbase-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!

https://bitbucket.org/tharris/wormbase/issues?status=new&status=open

General policies:

  1. Don't worry if something warrants reporting. If in doubt, report it!
  2. Report issues related to web development to Todd for triage.
  3. Include as much detail as necessary to explain the issue.
  4. 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):

https://bitbucket.org/tharris/wormbase