Hi Clint, On Wed, 12 Mar 2008, Clint Adams wrote: > Why isn't dpkg in collab-maint on Alioth? Why should it be or not be?
dpkg has been maintained in various VCS repositories since 1999 (CVS, then arch, then SVN, and now Git), it's a natural choice for a software maintained and further developed by several persons. collab-maint's purpose is to work collaboratively on the _packaging_ of (upstream) software for Debian. Even though packaging sometimes involves modifying the software, it's not really comparable to the work done by the upstream author of a given software. Thus I believe that it's just right for dpkg to have its own repository. It's important to have quality and consistency in the work done on such a package and thus it's good that the maintainers in charge can selectively grant (and revoke) write rights to the repository. > As DPL, how would you react to the recent events concerning dpkg > development? Honestly, it's difficult to say as I'm too much involved. Maybe the opinion of Moritz and Lucas would be more interesting on this particular event. That said, (at the beginning) I was not directly concerned by the problem (which is mainly between Ian and Guillem): I jumped in because I want to see the triggers merged and I want(ed) Ian to be able to help us effectively. I invested lots of hours to explain to Ian how I have been able to join the dpkg team and what kind of interactions were expected/needed. In the latest discussions (see http://people.debian.org/~hertzog/debian-dpkg.log) I have been as far as telling him that I would support his inclusion on the team provided he respected some rules: - review with other members before merge of any big branch - proper git commit logs - rebase of small patches before pushing I believe I have tried my best to prevent the problem by talking both to Ian and to Guillem, obviously it has not been as successful as I hoped. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
