Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Dec 2004 19:02:04 -0500
From:      "Haulmark, Chris" <chris@sigd.net>
To:        "Kris Kennaway" <kris@obsecurity.org>, <ports@FreeBSD.org>
Subject:   RE: "Being a port maintainer" document
Message-ID:  <6FC9F9894A9F8C49A722CF9F2132FC22029EB1E8@ms05.mailstreet2003.net>

next in thread | raw e-mail | index | archive | help
Someone broke the silence:=20

> At the moment, too many of our ports have no maintainer.  This means
> that there's no-one available to fix problems that occur with the
> ports or to deal with user support questions.  In some cases this is
> probably because no-one actually uses the software in question any
> more, but in other cases it's probably just because no-one in the user
> community has come forward to take over.
>=20
> I'd like to put out a general call for people to volunteer to maintain
> our unmaintained ports -- this is a great way for users to "give
> something back" to FreeBSD and help out the project -- but we need
> some form of document we can show them that lists the rights and
> responsibilities of port maintainers, so they have an idea of what's
> expected from them.  The porters' handbook does a good job of
> describing the details of constructing a port, but not the
> higher-level aspects of being a port maintainer.
>=20
> e.g.
>=20
> * Updating the port when a new version is released
>=20
> * Pushing local changes back upstream to the original authors
>=20
> * Fixing port errors reported by the package build cluster
>=20
> * Dealing with user support requests, at least by pointing them to the
> upstream developers for cases where it's not clearly a FreeBSD
> port-specific problem.=20
>=20
> * Evaluating PRs submitted against the port
>=20
> * Responding to change requests in a timely manner (2 weeks).
>=20
> * ...
>=20
> Can someone write up such a document?
>=20
> Kris

I have an interest.  There are several ports that come to mind that I
believe that I can be capable of.

Chris



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6FC9F9894A9F8C49A722CF9F2132FC22029EB1E8>