() joakim@verona.se
() Thu, 28 Mar 2013 08:53:01 +0100

   Heres my take:

   [...]
   - Incrementally produce a GNU-Git, which is maintained by GNU

   The initial versions of this new implementaiton could use libgit2,
   which is LGPLV2. Eventually the library could be rewritten as GPLV3
   if deemed necessary. (OTOH using libgit2 doesnt seem worse than using
   Python as bzr does), The new implementation could also use Guile,
   which would support an important GNU project.

Recently, Guile-SDL was accepted as a GNU project (transition wip,
announcement RSN).  It wraps libsdl (and friends) for Guile 1.4 and up.

I imagine the wrapping of libgit2 would entail similar work and hereby
volunteer to mentor anyone who steps forward on the techniques Guile-SDL
uses.  (The majority of the hair is Guile-version-specific shimming.)

Like Guile-SDL, i think Guile-Git (or whatever) would be best if started
as non-GNU and GPLv3+, and only after some refinement worry about being
accepted as GNU.  The important part is the GPLv3+.

   I only have very small resources to
   devote personally towards it though.

I know what you mean.  Everyone should be warned that my mentoring style
is best-suited for those who probably don't need a mentor.  :-D

Please, let's continue this on the guile-user list.

-- 
Thien-Thi Nguyen
GPG key: 4C807502