Re: RFC: Using git/collab-maint/PET for debian-mentors.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 13/06/10 10:05, Tim Retout wrote:
> Proposal
> ========
>
> I am considering creating a new workflow for my sponsoring:
>
> * Maintaining packages in git in collab-maint. (I don't think we
> want a separate pkg-mentors repository, because once people
> graduate from mentors they would feel compelled to move away.)
> * Using PET or similar to show which packages need review, and
> keep track of bugs/upstream versions. (Minor issue: I don't know
> how easy this is without putting the whole of collab-maint into
> PET.)
> * Optionally co-ordinating on IRC in #debian-mentors, as well as
> via notes at the top of debian/changelog.
>
> This would then require my mentees to do some things they don't do at
> the moment:
>
> * Register for an alioth account.
> * Learn how to maintain packages in a VCS.
> * Use the 'UNRELEASED/unstable' method of changelog management
> (and probably stop bothering with the RFS mails).
>
> It would also allow potential contributors to collaborate on packaging
> work in a team, rather than every sponsored package being worked on by
> exactly one person.
>
> I would most likely enforce the use of short dh7 rules files as well,
> and go all out on the 'lintian -iI --pedantic' warnings, same as I do
> with regular sponsorship. And of course, any packages which belong in
> other teams should be sent there - the steps above should have lowered
> the barrier to entry to the rest of Debian.
Information that is likely to become relevant for different sponsors
(like VCS in use, debian/rules style [dh/cdbs/debhelper]) could be shown
on the PET page. Different sponsors are likely to have different
requirements.
The only problem I see is that PET does not really scale well to lots of
packages, the page gets quite cluttered. So I don't know if pulling the
whole collab-maint area will be of any use.
- --
Saludos,
Felipe Sateler
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCAAGBQJMFtQMAAoJEKO6uuJAjdbPKioP/0P8ufyVc//HTliJ8Xs+K4Do
HZ7we1v+a5WnsIaBLDsIaZuDUfwJ5BfnGmL+kmVIv4f/XkAkkhQVHmqDm0EnqSvQ
Luob721sr6QlROsRkVNWsKXZ/D9AOjF/KBFcgUjVnvpOvEDjgcCoqTpRQ9CIvQWl
WMDNQ0J5gdBWNyP94TQ9pxAOfbnGOgVKKGeZvIn8/WoO2xiSpa+4stupQlrA/DZk
EQL/QFfHoBhfIQ+7zogRy/jydedZp+9Cig5ijLXvTrIjbuKzRVSNaNhmUs5D0jbu
1zQaGPAY1x5i3UNKwGKnvEgZEqinuJG+k72l/ctFpXmxhR/OqlCcO/RkslqopTNy
u8+KVSzSACLy6cg8QSqYpZ8Dc7rar9JW8wb3J2PJ/HM+pQRBFQyKQpnt+vLiU2We
ekVrSB7tudvbOtv4hbCEeBm6fvdDtkQYeQCL1wZx33B3CUiQLCXcByS+WAz6qZBu
wB+KUnO+qwmE256zCizFemiwuKdXwMh/vgl08cQ7axbnbr8SjUMlPn45IlhpLaLh
Ze/qmaD7xnUTR6h2myQdgWwnwNl+/DavR09T6didMRmSeNmReueSXaUOVQIGFPb+
H3WyDhuZvULrBtorihxJxkppgvz/kMYwG01gj/T6jnIHgCvByEBTp9Gr+xG/ffCX
/P7q+B9PhJVtYURKT/Vr
=zlkJ
-----END PGP SIGNATURE-----
Reply to: