[Pkg-shadow-devel] Reviving the maintenance of shadow?

Nicolas François nicolas.francois at centraliens.net
Sat Sep 29 19:08:16 UTC 2007


Following the email from Christian [0], here is a proposal for the
maintenance of shadow.

I propose to continue the maintenance of shadow on Alioth, in what is
currently the Debian shadow package repository.

The repository layout will be:
pkg-shadow/upstream/trunk   (with the history of the previous shadow releases
                   |         + snapshot of the last PLD shadow CVS repository
                   |         (2/2/2007?))
                   `tags    (populated based on the previous shadow releases)
pkg-shadow/debian/trunk     (populated from the previous trunk)
                  branches  (populated from the previous branches)
                  tags      (populated from the previous tags)

The pkg-shadow-devel at lists.alioth.debian.org mailing list will be used for
the upstream development.

The pkg-shadow-commits at lists.alioth.debian.org mailing list will be used
for commit messages (of the whole repository. Just tell me is a separate
mailing list must be setup to avoid noise from debian specific commits)

A new pkg-shadow-debian at lists.alioth.debian.org mailing list will be used
for the debian package development.

The contact information (at least in debian/control) need to be updated
for Debian (it is currently pkg-shadow-devel at lists.alioth.debian.org).
I don't expect a lot of mails in the interim period anyway.

All these mailing lists are opened, with low traffic, and receive spams.

The releases will be handled in the Alioth interface.

I don't really like the Alioth tracker, but I guess it would be better to
activate it than to expect people to report bugs on the Debian BTS.

The #shadow (on freenode) IRC channel will be a communication channel to
contact upstream.

I will setup a small webpage to display these information on

I will add a directory with the previous releases.

Note for the previous releases (and for the SVN history): they are coming
from Internet, I did not audit them.

I will just audit the diff from the current used in Debian and
the last CVS snapshot.

I can give access to the SVN repository if you want.

I will try to look at the existing patches in Debian, RedHat and Gentoo to
see what could be relevant for upstream, and maybe make a release next
month (depending on the current changes in the CVS snapshot).

PS: The repository will be setup with the attached script,
    most probably next weekend (October, 6)

[0] http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/2007-July/005965.html

Kind Regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: inject.sh
Type: application/x-sh
Size: 3575 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-shadow-devel/attachments/20070929/e3ff85c7/attachment.sh 

More information about the Pkg-shadow-devel mailing list