If you want a tracker with a repository, while keeping administrative hassle to a minimum, I'd go for github. Lots of people already have a github account.

Also consider Trac  http://trac.edgewall.org/ -- integrated issue tracking, repository and wiki, easy to deploy and use, a large community, and tons of plugins.

/Peter

On Tue, Jan 10, 2012 at 12:13 AM, Corey A Harper <[log in to unmask]> wrote:

Still think Github makes sense, as we can use it to collaborate on
documents as well.

That said, I wasn't aware of Atlassian's Open Source License. Thanks
for mentioning that, Mark!

If DCMI thinks we might have the resources to set up & run JIRA,
here's info on where we might start:
http://www.atlassian.com/software/views/open-source-license-request

-Corey

On Mon, Jan 9, 2012 at 11:51 AM, Mark A. Matienzo <[log in to unmask]> wrote:
> +1 for Github, but +1 for possibility of JIRA if under Atlassian's
> free-for-open-source program.
>
> Mark
>
> On Mon, Jan 9, 2012 at 11:02 AM, Corey A Harper <[log in to unmask]> wrote:
>> I agree that Github seems like a great choice, particularly if DCMI is
>> already planning to use it for managing schema.org alignments &
>> perhaps other similar documentation.
>>
>> -Corey
>>
>> On Mon, Jan 9, 2012 at 10:49 AM, Jon Phipps <[log in to unmask]> wrote:
>>> I'd like to reiterate my github suggestion and also suggest maintaining
>>> related documents there. Github is free, the issues tracking interface is
>>> simple, effective, and nicely tied to documents hosted at github. Github
>>> itself is an excellent centralized document repository for distributed
>>> version control.
>>>
>>> https://github.com/blog/831-issues-2-0-the-next-generation
>>> https://github.com/blog/699-making-github-more-open-git-backed-wikis
>>>
>>> Jon
>>>
>>> I check email just a couple of times daily; to reach me sooner, click here:
>>> http://awayfind.com/jonphipps
>>>
>>>
>>>
>>> On Sun, Jan 8, 2012 at 1:11 PM, Thomas Baker <[log in to unmask]> wrote:
>>>>
>>>> On Wed, Jan 04, 2012 at 02:39:08PM +0100, Antoine Isaac wrote:
>>>> > That's quite many things, maybe some splitting would help. Btw wasn't
>>>> > there talks about an issue tracker?
>>>>
>>>> I agree.  This is getting urgent.  Can anyone out there help?
>>>>
>>>> There is a nice wiki page about issue tracking at W3C [1].  Tracker is
>>>> great,
>>>> but it is only available for use by W3C working groups [2].  The classic
>>>> Bugzilla is mentioned but characterized as "kind of a double-edged sword
>>>> in
>>>> that it provides very powerful tracking and query features for those who
>>>> are
>>>> willing to take the time to understand how it works, but it can be a bit
>>>> overwhelming and confusing for those who have not had opportunity to work
>>>> with
>>>> bug/issue tracking systems before or are not willing to take the time to
>>>> read
>>>> the documentation and understand how to use it" [3].
>>>>
>>>> Also mentioned in [1] is RoundUp [4] -- a ten-year-old Python project,
>>>> used to
>>>> track Python and IETF projects, which I hear is easy to install and easier
>>>> to
>>>> use than Bugzilla.
>>>>
>>>> I see in my notes that someone once suggested Assembla [5] -- a
>>>> cloud-based
>>>> service to which DCMI would need to subscribe.
>>>>
>>>> If anyone here can testify to the usability (and easy-installability) of
>>>> RoundUp, I'd be inclined to go with a system that is included with the
>>>> rest of
>>>> the DCMI Web archive.
>>>>
>>>> Suggestions, please!
>>>>
>>>> Tom
>>>>
>>>> [1] http://www.w3.org/wiki/TrackingIssues
>>>> [2] http://www.w3.org/2005/06/tracker/
>>>> [3] http://www.bugzilla.org/
>>>> [4] http://roundup.sourceforge.net/
>>>> [5] http://www.assembla.com/
>>>>
>>>> --
>>>> Tom Baker <[log in to unmask]>
>>>
>>>
>>
>>
>>
>> --
>> Corey A Harper
>> Metadata Services Librarian
>> New York University Libraries
>> 20 Cooper Square, 3rd Floor
>> New York, NY 10003-7112
>> 212.998.2479
>> [log in to unmask]



--
Corey A Harper
Metadata Services Librarian
New York University Libraries
20 Cooper Square, 3rd Floor
New York, NY 10003-7112
212.998.2479
[log in to unmask]