[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: git bikeshedding (Re: triggers in dpkg, and dpkg maintenance)

Ian Jackson wrote:
> Raphael Hertzog writes ("Re: triggers in dpkg, and dpkg maintenance"):

>> FWIW, you do have access to the repository but I would request you to be
>> removed from the team if you made usage of it in a way that doesn't
>> conform to the rules of the team. This includes having meaningful commit
>> logs and using private rebased branches for most of the work except when
>> we have a public branch where multiple persons of the team cooperate (such
>> as what happens with the sourcev3 branch currently).
>> http://wiki.debian.org/Teams/Dpkg/GitUsage
> This development model has been imported from the Linux kernel.  It
> may be appropriate when there are hundreds or thousands of people
> generating huge quantities of patches, all trying to get their changes
> committed, with no organisational connection to the handful of people
> picked by the original author who need to act as gatekeeper.
> It is not appropriate for a project which has about four people
> submitting any significant number of patches, all of whom are fully
> signed-up members of a shared governance infrastructure, and where the
> gatekeepers are just the people in that project whose hands the code
> has most recently fallen into.

What's the intention of discussing dpkg package team's internals on the
debian-devel list?



Reply to: