On Thu, Jul 9, 2015 at 8:25 AM, Peter Stuge <pe...@stuge.se> wrote: > Rich Freeman wrote: >> I suspect that trying to force it would basically end up putting >> the entire distro on hold until most of the current devs quit, > > I think you're right. I also think those developers should quit right > here and now. I don't think they will. >
The thing is that if a bunch of devs want to create a review-only Gentoo fork they can just do it. The result would be about the same. Trying to force it on Gentoo would just result in most of the Gentoo devs changing the name and proceeding basically as it is, and Gentoo would just become another XFree86. The way you change an FOSS project is to influence the current contributions, or to make contributions of your own. Trying to order people around doesn't really change anything in the end. Hence my suggestion to try something like this out in a project where there is interest. Build from success, and win people over. In the end the "hard" power of a body like the Council is just the power to halt progress, not create it. That power should be focused on situations where the "progress" is self-destructive. Obviously a body like the Council also has "soft" powers like leadership/etc, but that really isn't enough to just order change by fiat. Plus, we're all elected for our ability to generally represent the will of the developer community, so you shouldn't be too surprised when we don't try to push policies that most devs disagree with. In any case, to some extent the review workflow already exists on the proxy maintainer project. There is no limit to the number of packages they can maintain, or the number of reviewers they can have. -- Rich
