Re: Standard description file about maintainer groups
Quoting Ola Lundqvist ([EMAIL PROTECTED]): > A common way is to list the contact address for the group > as maintainer and each person responsible for uploads in Uploaders. > You miss non official Debian developers this way though. This is the way d-i packages are handled. This is also the way I have chosen for the shadow package maintenance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
Ola Lundqvist dijo [Mon, Mar 28, 2005 at 10:37:33AM +0200]: > > * Sean Perry [Sun, 27 Mar 2005 18:36:49 -0800]: > > > > > Source: mysource > > > Maintainer: Bob <[EMAIL PROTECTED]> > > > Maintainers: Bob <[EMAIL PROTECTED]>, George <[EMAIL PROTECTED]> > > > > > I left the Maintainer in place to allow for some backwards > > > compatibility. This could be the 'captain' of the project. > > > > Or a list. See the Maintainer field of e.g. lintian, exim4, kde. > > And wrt 'Maintainers', there is 'Uploaders' already. > > A common way is to list the contact address for the group > as maintainer and each person responsible for uploads in Uploaders. > You miss non official Debian developers this way though. In the pkg-perl group, I often list a non-DD as an uploader, even if he cannot formally upload - He is a comaintainer anyway. Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)1451-2244 / 5554-9450 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
#include * Frank Küster [Tue, Mar 29 2005, 02:25:03PM]: > Eduard Bloch <[EMAIL PROTECTED]> wrote: > > Some people call that file MAINTAINERS, some README.svn or similar, and > > some do not do this at all, so someone needs to ask somebody or get a > > crystal ball to learn about the repository of the maintainers. And the > > first way is annoying and your mail with stupid question may be posted > > on their development mailing list, which is not always the best thing. > > Which *problem* do you want to address with that suggestion? Isn't Improvements of visibility of how maintainer group works, to make the life easier for someone who comes along and tries to reach a hand. > one of the main points of group maintenance that any outsider just > contacts the group address, and the insiders decide who is going to be > responsible for a problem? So shouldn't we rather establish a policy This depends on how each team internaly works. This is desirable for groups with few packages but not neccessarily for others, with many packages where different subset of group members care about specific subsets of the packages. > that every group-maintained package should have a mailing list in its > maintainer field?n This is already beeing done where people see it appropriate. > Furthermore, listing *current* contributors in a file might be not so > easy - how often do you need to post to a list to be "allowed in"? Is I did not talk only (or primarily) about the contact address, it is still up to the group how the communication inside and with outsiders is regulated. What I meant is a list of various things that are important to possible contributors: repositories, status web sites. Regards, Eduard. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
Eduard Bloch <[EMAIL PROTECTED]> wrote: > Hello fellow maintainers, > > with organisation in groups becoming more and more popular, IMO it is now > time to find some convention for declaring the group members and > guidelines inside of the Debian source package. > > Some people call that file MAINTAINERS, some README.svn or similar, and > some do not do this at all, so someone needs to ask somebody or get a > crystal ball to learn about the repository of the maintainers. And the > first way is annoying and your mail with stupid question may be posted > on their development mailing list, which is not always the best thing. Which *problem* do you want to address with that suggestion? Isn't one of the main points of group maintenance that any outsider just contacts the group address, and the insiders decide who is going to be responsible for a problem? So shouldn't we rather establish a policy that every group-maintained package should have a mailing list in its maintainer field?n Furthermore, listing *current* contributors in a file might be not so easy - how often do you need to post to a list to be "allowed in"? Is it sufficient to suggest features or implementations, or do we count only people who send patches? To me it seems this might even discourage newbies. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: Standard description file about maintainer groups
* Ola Lundqvist [Mon, 28 Mar 2005 10:37:33 +0200]: > A common way is to list the contact address for the group > as maintainer and each person responsible for uploads in Uploaders. > You miss non official Debian developers this way though. Nothing mandates that the Uploaders field is DD-only, AFAICT. And I believe that Uploaders really is meant to mean Co-Maintainers. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 I don't want to achieve immortality through my work. I want to achieve immortality throguh not dying. -- Woody Allen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
On Monday 28 March 2005 12:30, David Schmitt wrote:
> On Monday 28 March 2005 00:04, Eduard Bloch wrote:
> > I suggest debian/README.Debian.Maintainers as the filename.
>
> Hmm .. Following from README to README.Debian, wouldn't AUTHORS.Debian make
> more sense?
>
> Also, often this list is already present in debian/copyright ("packaged
> by ...")
Any worries having copyright as follow:
This package was originally debianized by First Last on
Group-maintained by:
name1
...
nameN
It was downloaded from:
ftp/http/cvs/svn/arch url's follow...
Upstream Author: name
Copyright:
follows
--
pub 4096R/0E4BD0AB 2003-03-18
fingerprint1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB
pgpdw08us4umY.pgp
Description: PGP signature
Re: Standard description file about maintainer groups
On Monday 28 March 2005 00:04, Eduard Bloch wrote:
> I suggest debian/README.Debian.Maintainers as the filename.
Hmm .. Following from README to README.Debian, wouldn't AUTHORS.Debian make
more sense?
Also, often this list is already present in debian/copyright ("packaged
by ...")
Regards, David
--
- hallo... wie gehts heute?
- *hust* gut *rotz* *keuch*
- gott sei dank kommunizieren wir über ein septisches medium ;)
-- Matthias Leeb, Uni f. angewandte Kunst, 2005-02-15
Re: Standard description file about maintainer groups
Hello On Mon, Mar 28, 2005 at 07:45:31AM +0200, Adeodato Simó wrote: > * Sean Perry [Sun, 27 Mar 2005 18:36:49 -0800]: > > > Source: mysource > > Maintainer: Bob <[EMAIL PROTECTED]> > > Maintainers: Bob <[EMAIL PROTECTED]>, George <[EMAIL PROTECTED]> > > > I left the Maintainer in place to allow for some backwards > > compatibility. This could be the 'captain' of the project. > > Or a list. See the Maintainer field of e.g. lintian, exim4, kde. > And wrt 'Maintainers', there is 'Uploaders' already. A common way is to list the contact address for the group as maintainer and each person responsible for uploads in Uploaders. You miss non official Debian developers this way though. Regards, // Ola > -- > Adeodato Simó > EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 > Listening to: Paco de Lucía y Ricardo Modrego - El emigrante > > Experience is something you don't get until just after you need it. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
* Sean Perry [Sun, 27 Mar 2005 18:36:49 -0800]: > Source: mysource > Maintainer: Bob <[EMAIL PROTECTED]> > Maintainers: Bob <[EMAIL PROTECTED]>, George <[EMAIL PROTECTED]> > I left the Maintainer in place to allow for some backwards > compatibility. This could be the 'captain' of the project. Or a list. See the Maintainer field of e.g. lintian, exim4, kde. And wrt 'Maintainers', there is 'Uploaders' already. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: Paco de Lucía y Ricardo Modrego - El emigrante Experience is something you don't get until just after you need it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Standard description file about maintainer groups
Eduard Bloch wrote: So I suggest to set a kind of soft policy: every package maintained by a group should keep a file (with a common filename) in the Debian diff, which tells all neccessary things: - who are members of that group - which person from this group is responsible for exactly this package - homepage, project page (alioth/Sourceforge/Berlios/...) - where is the repository and how can you get it, not too much, but enough information for average skilled maintainer to get it running I suggest debian/README.Debian.Maintainers as the filename. seems logical. Do we really need the 'README.' part? Does this need to be installed in /usr/share/doc or will this only be found in the source. Personally, I see no reason to put it in the deb. Another choice would be in the source section of the control file. Source: mysource Section: blah Priority: extra Maintainer: Bob <[EMAIL PROTECTED]> Maintainers: Bob <[EMAIL PROTECTED]>, George <[EMAIL PROTECTED]> Project-Home: http://alioth.debian.org/mysource Build-Depends: whatever Standards-Version: 3.6.1 Obviously, this is more invasive but if it is truly as widestread then perhaps the project tools should catch up. I left the Maintainer in place to allow for some backwards compatibility. This could be the 'captain' of the project. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Standard description file about maintainer groups
Hello fellow maintainers, with organisation in groups becoming more and more popular, IMO it is now time to find some convention for declaring the group members and guidelines inside of the Debian source package. Some people call that file MAINTAINERS, some README.svn or similar, and some do not do this at all, so someone needs to ask somebody or get a crystal ball to learn about the repository of the maintainers. And the first way is annoying and your mail with stupid question may be posted on their development mailing list, which is not always the best thing. So I suggest to set a kind of soft policy: every package maintained by a group should keep a file (with a common filename) in the Debian diff, which tells all neccessary things: - who are members of that group - which person from this group is responsible for exactly this package - homepage, project page (alioth/Sourceforge/Berlios/...) - where is the repository and how can you get it, not too much, but enough information for average skilled maintainer to get it running I suggest debian/README.Debian.Maintainers as the filename. Regards, Eduard. -- Everything is illusion. Constructs of language, light, metaphor; nothing is real. -- Babylon 5, Season 4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
