bugmap license?

[Greg Ward]

On Mon, Dec 13, 2010 at 2:03 PM, Haszlakiewicz, Eric
<EHASZLA at transunion.com> wrote:
> I'm thinking of working on some improvements to your bugmap.py extension to help it work better with numerous clones, to not require a database, even if using a database to not require developers have direct access to it, and other things.
> I'll provide details for those ideas once I sort them out a bit.
>
> However, before I start working on this I'm wondering:
> What is the license on that extension?  Is it GPLv2 like Mercurial itself, or something else?

Undefined.  I wrote it on work time for my employer's specific
requirements, and have not asked anyone if I can release it publicly.
The code is useful as a starting point for others, but hardcodes a lot
of policy specific to us.  I do not consider refactoring bugmap into a
super-duper general-purpose extension a good use of my time, since
doing that would result in a system approximately as flexible as
Python or Mercurial.

> Also, is the extension stored on any publicly available repository (e.g. github) or should I base my work off of the version that you posted to the mailing list on 2010/07/08?

Nope, no public repo.  However, I've just written a stupid little
shell script to extract the history of bugmap from our internal
build-tools repo.  Bundle attached.  Make of it what you will.  If it
breaks, you get to keep *both* pieces!  ;-)

Good luck --

Greg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bugmap.hgbundle
Type: application/octet-stream
Size: 50165 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20101213/7fb8f995/attachment.obj>