View Single Post
  #9   Spotlight this post!  
Unread 26-06-2004, 21:16
Timothy D. Ginn's Avatar
Timothy D. Ginn Timothy D. Ginn is offline
I check here maybe once a year.
no team
 
Join Date: Apr 2003
Rookie Year: 2002
Location: Port Perry, ON. Canada
Posts: 247
Timothy D. Ginn is a name known to allTimothy D. Ginn is a name known to allTimothy D. Ginn is a name known to allTimothy D. Ginn is a name known to allTimothy D. Ginn is a name known to allTimothy D. Ginn is a name known to all
Send a message via ICQ to Timothy D. Ginn Send a message via AIM to Timothy D. Ginn Send a message via MSN to Timothy D. Ginn Send a message via Yahoo to Timothy D. Ginn
Re: Website Team Communication

Quote:
Originally Posted by robot180
Thanks for that information. I don't think that any of those will help in our situation, but maybe it helped someone else. I think that instant messaging is the most effective way to communicate. Unless everyone has Yahoo with voice chat or if they can use Netmeeting or something.

Thanks again.
I don't know how big your team is, but you may want to consider using CVS in conjunction with a mailing list. That way all the changes that you make are communicated to the other web team members and theirs to you. SF.net has a syncmail script (if you can't find it, I can send it to you) that helps with this (it's written in Python :-)). If you end up using CVS then you can add a quick little note to the change (or leave it blank) so, depending on what it is you were communicating it can make changes a lot faster (ie anyone would be able to make the change and if someone else were working on the same file in a different place, their changes could be merged together too).

CVS is what we use for the openFIRST project. It's pretty easy to setup, and will work on both UNIX-based and Windows systems (as a client and server). If you decide to go the CVS route, I'd suggest looking at SmartCVS http://www.smartcvs.com for the client side, as it's pretty straight forward. http://www.openfirst.org/cvs/smartcvs/ has a graphical tutorial for the setup (tailored to openFIRST, but it's a source for some more screen shots, at the very least)

A favourite thing to do now (for those of us who've graduated and now play mainly administrative roles for openFIRST in order not to cause potential conflicts with the "student designed and built website" rule) is add <!-- TODO: ... --> comments in the source.
__________________
Alumni of FRC Team 1006
Former mentor of Full Lego Alchemist (FLL 5621) - Sempar School / Computing Students' Association of Queen's University