OT: Distributed bug tracking?

[Francesc Esplugas]

I created a few months a Rails application that was doing exactly the  
same but using the external tool Trac.

The idea is that you create a new repos and this creates also the Trac  
setup for you, it even adds custom domains. And more.

If someone wants to see it working or continue the development let me  
now.

Best,

Francesc

On Jan 5, 2008, at 12:53 PM, Tane Piper wrote:

> Hey folks,
>
> Just to let you know Myself and another developer are working on a new
> tool called hgfront.
>
> It's a Django application that is coming along rather nicely, although
> is still in early development:
>
> http://sharesource.org/project/hgfront/
>
> Feel free to grab it and have a look, although there are currently no
> docs.  At the moment we have:
>
> * User registration
> * Creation of projects (i.e. directory with hgwebdir.cgi and  
> hgweb.config file)
> * Creation of new and cloned repositories (also writes out the hgrc  
> file)
> * Basic database-backend issue tracker
> * Basic wiki pages for each project
>
> Currently there is support for setting the style as well, and I'm
> currently working on adding extension support too.  Although the
> application provides control over projects and repositories, at the
> moment you still need to set up a vhost to point to the hgwebdir.cgi
> file
>
> The idea is to provide a simple trac-like functionality built around
> hg, while not replacing hgweb but complementing it.  We also want to
> provide custom views within our app, so you can build your own simple
> views around repositories.
>
> If anyone does get it running without docs, please feel free to
> provide some feedback.  And I'm hoping to get a demo up soon.
>
>
> On Jan 4, 2008 7:46 PM, Micah Elliott <mde at micahelliott.com> wrote:
>> On 2008-01-04 Dmitriy Morozov wrote:
>>
>>> I think the case where Mercurial is used by a single (or maybe
>>> a couple of) developers for a project for which they need to
>>> somehow keep track of (read: organize nicely) the issues
>>> involved, and perhaps save an occasional bug report from an
>>> occasional user, is common enough to where it explains the
>>> interest that this thread has raised.
>>
>> I've enjoyed following this thread and all the great ideas that
>> have been brought up.  I too really like the notion of a bug
>> tracker integrated into the code base.  I tried to get something
>> related to this working in the form of Codetags
>> (http://www.python.org/dev/peps/pep-0350/), but my implementation
>> never got further than personal use.  I suppose the idea of
>> separate dirs per bug is cleaner than the codetag approach, but
>> just thought I'd add another perspective.
>>
>> --
>>                          _ _     ___
>>                          |V|icah |- lliott
>>                          " "     """
>> mde at MicahElliott.com            <><             http://MicahElliott.com
>> PGP: 0x7C07CBF0          ICQ: 369060435      Linux/Ubuntu:  
>> 417195/12440
>> HackerKey:  
>> v4sw6YUPCJhw5ln5pr7OPck2ma9u8Lw3m5l6Ui2e7t3b8LDMOen6a3XsMRr5
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFHfo0H+PTVh3wHy/ARAq1IAJ9rDh0FHbMUJ0y8QJ/BDSMl66PPrQCfZEJE
>> VoaUw1ozWCI7sBLQrBTCIKo=
>> =fLB9
>> -----END PGP SIGNATURE-----
>>
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial
>>
>>
>
>
>
> -- 
> Tane Piper
> Blog - http://digitalspaghetti.me.uk
> Wii: 4734 3486 7149 1830
>
> This email is: [ ] blogable [ x ] ask first [ ] private
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial

--
name. Francesc Esplugas i Martí
voice. +34 678.681.603