[Webmin-maintainers] Project members

Jaldhar H. Vyas Jaldhar H. Vyas" <jaldhar@debian.org
Tue, 7 Dec 2004 01:19:29 -0500 (EST)


On Wed, 1 Dec 2004, Thomas Hood wrote:

> On Wed, 2004-12-01 at 13:56, Finn-Arne Johansen wrote:
> > Is this project intended to also maintain the package
>
>
> I assume so; otherwise the project would have been named 'pkg-webmin'.
>

Aargh sorry I keep disappearing like this.  Yes, the goal of this project
is to take over maintainence.  I assume future uploads will have the
maintainer set to this mailing list as other groups have done.

Perhaps you would like to begin by looking at the bug reports for the
following source packages:

webmin
webmin-optional
webmin-extra
webmin-cluster
webmin-contrib
usermin
usermin-contrib
webmin-virtual-server
webmin-exim
webmin-snort

There are also new upstream versions of webmin and usermin that need to be
packaged.

Also several modules could be integrated better into Debian.

Let me explain a little bit about how the packages are laid out.
Originally there was just one source package for webmin which matched
upstreams tarball.  The trouble is Jamie also introduces updates to
specific modules inbetween releases which were awkward to manage with
the one source package approach.  So then I moved to a  one source package
per module scheme.  This made things easier for me as each module could be
updated independently but people complained that it made it very difficult
to match the contents of the upstream tarball.  So the present scheme is a
compromise that tries to group modules which are updated at the same rates
into the same source package.

webmin          -- consists of the binary packages webmin (the basic
                   framework) and webmin-core (a core set of modules.)

webmin-optional -- modules which are priority optional

webmin-extra    -- modules which are priority extra

webmin-cluster  -- modules related to clusters.  They tend to be updated
                   together.

webmin-contrib  -- modules which have to go into contrib  because they
                   depend on non-free packages.

The upstream source is split into these 5 manually each time.  I did have
a script to do it automatically but it didn't actually save that much
time.

Also I should mention that there are several modules included in the
upstream tarball which are not packaged at all either because they do not
apply to Linux (e,g, sgiexports, hpuxexports) or they are for software
which is not included in Debian (e.g. majordomo)

usermin is mainly the same as the upstream tarball except
the contrib modules are split out into their own source package.

The other webmin modules are third-party ones so each has its own source
package.

I hope this gives you enough information to be able to take over. Please
feel free to ask me any questions and I am available to sponsor uploads
for non-DDs.

-- 
Jaldhar H. Vyas <jaldhar@debian.org>
La Salle Debain - http://www.braincells.com/debian/