[xen-tools-discuss] Bug Tracking System / Commit access for others / Git or Hg?

[Steve Kemp]

On Sat Apr 10, 2010 at 15:14:17 +0200, Axel Beckert wrote:

> Basically because I want to choose hosting and bugtracker based on
> needs and preferences not based on number of hosted projects,
> publicity or age of the hoster.

  Definitely the best way forward.

> Distributed within the VCS/SCM:
>
> * bugs-everywhere (http://bugseverywhere.org/)
> * ditrack (http://www.ditrack.org/)

  Once upon a time I wrote a simple bug tracker which allows bugs
 to be stored as simple text files within a repository:

    http://steve.org.uk/Software/milli/

  I've evaluated several of the existing ones, and in general I find
 (even with my own thing) that the idea of distributed bugs is better
 than the existing implementations - but that I expect this to change.

> I must admit that the main reason for tending to hosted VCS/SCM
> hosting is that I have not much expererience with hosting repositories
> where arbitrary people have commit access.

  I generally just use groups.  So I'd create group "xt" and allow
 the project to be read/write/execute by group.  Then add a few  local
 Unix accounts with restricted shells and make their primary group
 xt.

  It's not difficult to setup, but I can appreciate you might prefer to
  outsource it, and that's not necessarily a bad thing.

> And those experiences I made (with Subversion) were always covered
> with Unix permission hassles. (And I do not like to create local Unix
> accounts on my server for every committer anyway.)

  I guess that rules out my solution...

> Yeah. If we'd have a developer ML I probably would have asked there
> instead of on the general discussion ML.

  :)

Steve
--