[Pkg-ganeti-devel] Ganeti in Debian startup

[Guido Trotter]

Hi!

Sorry for the delay, I sent this message a couple of days ago, unfortunately to
the wrong list address! :/

So, it's time to get started with packaging Ganeti. The current situation is:

- leonardo has some packages available
- we have some internal ones

Should we start from leonardo's ones and work on them? The issues we might want
to discuss, before, are:

Revision Control System:
  We are currently using subversion, iustin proposed switching to hg or git,
  what do you think? I had applied for subversion because it's simple, and
  ganeti is using it, but on the other hand other systems might have some
  advantages (eg: the possibility of working with code reviews). We need to
  decide whether to bother the alioth admins again to change or not...

Licensing:
  What should we licence the Debian package under? I'm personally against using
  "GPL2 only" as it means we might have problems if ganeti switches to GPL3 at
  any point because we won't have control on all the debian part of the code...
  Nice options would be v2 or later, double licence under v2 and "the same
  licence as ganeti itself" or just use "the same licence as ganeti itself"...
  Or we could use BSD and forget about it... Any ideas? 

FHS:
  Before uploading we need to get rid of /srv/ganeti, which we cannot use for
  packages... Possibilities would be creating it at cluster init time/node add
  time if it doesn't exist, or moving to /var/share|lib/ganeti... Any other
  ideas?

Init/Cron:
  Ganeti ships scripts which are debian policy compliant, or should anyway...
  Shall we make debian/rules distribute those rather than copying them and use
  our own? We can still add patches should we need any!

Maintainer:
  I'd say "Ganeti Packaging Team <pkg-ganeti-devel at alioth.debian.org>" and the
  three of us listed as uploaders... Is that cool?

Ok, I'm done for now... Waiting for your feedback to start! Thanks!

Guido