Re: Fwd: libkolab* in debian
Paul Klos <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab |
|---|---|
| Message-ID | <1604968.0dBEZ9kt0K__11455.4735868753$1365445476$gmane$org@apollo> |
Op woensdag 27 maart 2013 11:33:26 schreef Christoph Wickert: > So for me the situation is quite clear: We definitely want the packages in > Debian and we want somebody who is involved both in Kolab and in Debian to > maintain them. This makes you a good candidate. If possible, we could have > multiple owners (or at least uploaders), but I'm not sure about the exact > details of the Debian policies. Debian policy states this: ===== Quote from http://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer ===== The maintainer must be specified in the Maintainer control field with their correct name and a working email address. The email address given in the Maintainer control field must accept mail from those role accounts in Debian used to send automated mails regarding the package. This includes non-spam mail from the bug-tracking system, all mail from the Debian archive maintenance software, and other role accounts or automated processes that are commonly agreed on by the project.[7] If one person or team maintains several packages, they should use the same form of their name and email address in the Maintainer fields of those packages. The format of the Maintainer control field is described in Maintainer, Section 5.6.2. If the maintainer of the package is a team of people with a shared email address, the Uploaders control field must be present and must contain at least one human with their personal email address. See Uploaders, Section 5.6.3 for the syntax of that field. ===== End quote ===== So either the Maintainer needs to be a person or we can put in a group as Maintainer, along with (at least one) individual Uploaders. We already have "Debian Kolab Maintainers <[email protected]>", how about we use this address for maintainer? If I add at least the current Maintainer to the Uploaders field, everybody who is involved with a package can continue working with it without any issues, if they need to. Cheers, Paul PGP: 8FE6E0BD _______________________________________________ Kolab-devel mailing list [email protected] https://www.intevation.de/mailman/listinfo/kolab-devel
signature.asc
(application/pgp-signature, 836 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQIcBAABCAAGBQJRYwtTAAoJEHtCjbaP5uC9J10P/2lTSYAUERqJg4iR4EydrtDC yWPM/wpFjl2fxgGLawuAyY6O9XwknH+kTcPa4goiHhT6rAMCsRipVeYJZecaDlB8 R8sTdX4Lu2/aJQXfWde0QYTGIdJzuDAO5VRj8tUMg3nXIeMb7VzLaj2xSdi6Qwot 3Jx+CmOAuHHc3Pn+LOiGl7DPSBHY4N22aJq+6LMp+LgOHdN66M9X4D3FV+wbVY65 iPQhoIn1xEWmWqLL/VUjb+tf6mhF7IUxv1+nc+9dBZEjexWJJMJRI+nuwp5XNg3U /a1nUnzRZrHmr3xBdajEUC2RbMcvlBGan1Qkc3Vc6MYRsTDx58wlIO0dQnqKs2SK H63YmSFVoWDBUC4s7QPu4rql5g+JmNNrTWBxcv3ApXSI8MzC01dAFcGgqDt24cXB KHNINNu3S/KAl+RfP4yNbdd8ax4VG4T69W0vz6+pD0vtJYGVIWJz8oDdAGruLpsI IgxZHVwMdmwhXQ/Hnwnx/XLSGrGmS4w8hL8nnKIduYzY4AYA9aK8sFDBUV+FOAUC Crq5IbITw+yvkCoQ08f9MqebK69VYkRJwdF/Kevok1s51RD5IY+DU0xw0Qapxz5b VRSzOA70q8h4qcCs54IEJiyLyGiRD23l0lePiKQ1Dswd3hKW/z9QNRV/REv9BJP1 LxphDwIGTdQd5QartyXb =txrL -----END PGP SIGNATURE-----