Re: Issue Tracker Recommendations

From: Sarr, Nathan <nsarr_at_nyob>
Date: Wed, 22 Feb 2012 15:52:51 -0500
To: CODE4LIB_at_LISTSERV.ND.EDU
You might want to take a look at asana:

http://asana.com/

-Nate

Nathan Sarr
Senior Software Engineer
River Campus Libraries
University of Rochester
Rochester, NY  14627
(585) 275-0692
nsarr_at_library.rochester.edu



-----Original Message-----
From: Code for Libraries [mailto:CODE4LIB_at_LISTSERV.ND.EDU] On Behalf Of Cynthia Ng
Sent: Wednesday, February 22, 2012 3:46 PM
To: CODE4LIB_at_LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Issue Tracker Recommendations

Thanks for all the responses, everyone. If there are any more, I'd still like to hear them.

Should probably add that
4) it's more for issue tracking/documentation i.e. code versioning/repository is not a priority right now (though it's great if it has that feature)

There will be discussions with the rest of the team and we'll have to talk to the programmer/server admin to see what he thinks is easier to implement, but we're likely to go with Redmine or Trac based on recommendations/needs.
Received on Wed Feb 22 2012 - 15:54:32 EST