I’m looking into using a issue tracking system for our programming team. Has anyone done this or something related to it on the their team? I know this might be an unnecessary complicated step for small teams, but what about larger teams, ones that have several programmers.
Issue Tracker(http://en.wikipedia.org/wiki/Issue_tracking_system) – An issue tracking system (also called trouble ticket system or incident ticket system) is a computer software package that manages and maintains lists of issues, as needed by an organization.
P.S. I have been messing around with Eventum, pretty fancy.
Mantis/SVN/MediaWiki. The integration is slightly tricky to get working, but there are companies that use this internally for a pretty decent tracking/versioning/documentation system.
I would say something simple available on Github is enough. However, I set up Trac on my server and the few programmers we had used it crafty enough for it to help. We set up milestones for deadlines for specific assignments and used it as a webpage where we could look at all the commit activities. I’d say that teams should move to Git or Hg (Mercurial) and use Github/Bitbucket which both have good web interfaces for very basic, but useful, issue tracking.
I would love to use a issue tracking and a version control system, but the lack of a usable internet at school limits us from what we can use. Other than having a dedicated computer for hosting and having a small wireless network to host such programs for the one desktop (which I guess could be the host) with two laptops.
Though I think a bug tracker is bit overkill, though I could see it being useful with some complicated code.
Do you mean usable internet as in open ports and such? If you use Mercurial (Which I HIGHLY recommend, and use Bitbucket.com - they let you 150MB Private Repository with multiple users) you can push your commits over HTTP. It’s basically a HTTP request over port 80 which is EXACTLY like another web page… If your school won’t even allow that, either have an internal computer be acting as Mercurial host, etc.
Bug tracker with milestones and assignees and level of complication and threaded comments, like Trac, might be overkill but go ahead and try out Github’s. I feel that it’s pretty useful. Even just as a “todo” list.
Keehun
P.S. If you ever need Git/Mercurial/SVN/Web hosting, I’ll be here to help you out, either giving you web space/repositories or helping you set up on your own hardware. (Hosting at Tier-4 rated datacenter in a network hub downtown LA)
Eh, meaningful like they (the county) won’t let us connect anything that isn’t county property to the internet. I don’t really consider is usable as if you, for example, want to upload a code file to the internet, it would involve copying it to a thumb drive and then shuffle over to a school desktop to copy over and upload. It’s not exactly a easy process and knowing me, I wouldn’t do it as often as it should be done.
Origo looks interesting. Definitely something to bookmark.
Perhaps you should consider talking to your team & mentors to propose to the school board that you be allowed one specific domain (github.com or bitbucket.com, etc). I proposed to my school to open a port (for SVN) but they turned it down saying that an open port is too big of a security risk, but I think allowing TCP connections to one IP address (for more security, just outbound) could be more realistic in terms of a proposal…
I think if nothing like that works out, you should definitely try to have one of the computers be the host for Git or Mercurial. (Host can also be the dev/client)
I like using fancy solutions as much as the next guy but last year I used a white board in the room (it was used exclusively by us) Simple, easy to set up and everyone could see where things were. It also has great time and resource management capabilities. Of course, we had one student programmer and 2 mentors helping him and everyone had different schedules. Having an extremely visible (purple marker on a white board) system was the most effective for us because it allowed us to communicate despite some of us being there from 11-1am while others were there more normal hours.