: woensdag 22 februari 2012 23:18
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Issue Tracker Recommendations
On 2/22/2012 5:10 PM, Sebastian Karcher wrote:
Because Trac and Git have come up: Zotero has switched from Trac/SVN
to Git and I (and I think everyone else involved) much prefers git
Hi All,
We're looking at implementing an issue tracker for internal use, so
I'm looking for recommendations.
What's key:
1) minimal effort in install/setup i.e. ready to use out of the box
2) small scale is okay, we have a very small team
3) ideally, have an area for documentation and issue
On Wed, Feb 22, 2012 at 12:36, Cynthia Ng cynthia.s...@gmail.com wrote:
What's key:
1) minimal effort in install/setup i.e. ready to use out of the box
2) small scale is okay, we have a very small team
3) ideally, have an area for documentation and issue creation via email
What does your
Not Jira.
-Sean
On 2/22/12 12:36 PM, Cynthia Ng cynthia.s...@gmail.com wrote:
Hi All,
We're looking at implementing an issue tracker for internal use, so
I'm looking for recommendations.
What's key:
1) minimal effort in install/setup i.e. ready to use out of the box
2) small scale is
On 2/22/12 11:59 AM, Sean Hannan wrote:
Not Jira.
Not RT.
./fxk
--
I do not believe in the creed professed by the Jewish Church, by the Roman
Church, by the Greek Church, by the Turkish Church, by the Protestant
Church, nor by any Church that I know of. My own mind is my own Church.
On Wed, Feb 22, 2012 at 11:36 AM, Cynthia Ng cynthia.s...@gmail.com wrote:
1) minimal effort in install/setup i.e. ready to use out of the box
You might look into github for this. If you're doing something
internal with a small team, the $7 or $12/month plans might do well
for you.
-n
Most of our teams use Redmine. It's very lightweight. On smaller projects
we use the wiki for documentation. The markup has shorthand for linking
back to issues which comes in handy.
There are two ways to setup email issue creation/closing. If you use the
SMTP option, email is very easy to setup.
Web Systems Librarian, VCU Libraries
804-827-3552 | erwh...@vcu.edu | www.library.vcu.edu
From: Nate Vack njv...@wisc.edu
To: CODE4LIB@LISTSERV.ND.EDU
Date: 02/22/2012 01:08 PM
Subject:Re: [CODE4LIB] Issue Tracker Recommendations
Sent by:Code for Libraries CODE4LIB
Redmine would probably be a very good fit for what you want. It does
support email ticket creation.
We like Jira, but dialing it in can take a pretty substantial effort.
Cary
On Wed, Feb 22, 2012 at 9:36 AM, Cynthia Ng cynthia.s...@gmail.com wrote:
Hi All,
We're looking at implementing an
Unless your alternative is Footprints. Gah.
On 2/22/12 12:59 PM, Sean Hannan shan...@jhu.edu wrote:
Not Jira.
-Sean
On 2/22/12 12:36 PM, Cynthia Ng cynthia.s...@gmail.com wrote:
Hi All,
We're looking at implementing an issue tracker for internal use, so
I'm looking for recommendations.
On 2/22/12 12:05 PM, Nate Vack wrote:
On Wed, Feb 22, 2012 at 11:36 AM, Cynthia Ngcynthia.s...@gmail.com wrote:
1) minimal effort in install/setup i.e. ready to use out of the box
You might look into github for this.
Oh yeah! Clever!
If you're doing something
internal with a small team,
We have the heavyduty solution (JIRA/Greenhopper), but there's a lot
of nice relatively cheap web stuff that I think might fit your bill.
Just one of the many, many solutions out there:
Github for documentation/lightweight issue tracking
getdonedone can link to your github and has a lot more
On Feb 22, 2012, at 12:36 PM, Cynthia Ng wrote:
Hi All,
We're looking at implementing an issue tracker for internal use, so
I'm looking for recommendations.
What's key:
1) minimal effort in install/setup i.e. ready to use out of the box
2) small scale is okay, we have a very small team
I've been happy with Trac. It does have good SCM integration.
Many of the options listed have VMs available at places like
turnkeylinux.org or bitnami.org.
You might try out this custom google search I put together:
http://ontherhoads.org/brad/2012/02/vm-search-engine/
Cynthia Ng cynthia.s...@gmail.com
What does your institution use?
What do you like and dislike most about it?
Would you recommend it to others?
RT and Trac. RT has tons of features, is easy to extend and build
lots of dependencies on, which is why it's still in use, but it can be
a bit
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
@LISTSERV.ND.EDU] On Behalf Of Cynthia
Ng
Sent: Wednesday, February 22, 2012 3:46 PM
To: CODE4LIB@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
@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
@LISTSERV.ND.EDU] On Behalf Of Cynthia
Ng
Sent: Wednesday, February 22, 2012 3:46 PM
To: CODE4LIB@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
19 matches
Mail list logo
