[Development] abandoning stale changes on gerrit

André Pönitz andre.poenitz at mathematik.tu-chemnitz.de
Thu Jan 31 21:07:06 CET 2013


On Thu, Jan 31, 2013 at 01:08:11PM +0100, Oswald Buddenhagen wrote:
> On Thu, Jan 31, 2013 at 10:58:13AM +0000, Rutledge Shawn wrote:
> > I question your right to unilaterally decide to put the kibosh on
> > other people's patches, automatically, across the whole project, even
> > when they are not on your own review list.
> >
> as i stated before, i'm driving forward a process to decide the
> execution details of a previously made decision.

I am asking for reconsideration, in the current context, with 
people currently involved. 

> > You've had enough feedback from others too about _that_ idea.
> > 
> so how many people was it? two? three? sorry, not relevant with the
> arguments given.

As far as I can see approximately half, if not even the majority
of people who responded opposed the move. Declaring the result as
"consensus" _for_ the move seems a bit of a stretch.

I don't think you properly rebutted any of the arguments.

I have not seen any reasoning beyond "I ignore what you say" why
abandoning any change that is _not_ on your dashboard would help to
solve the problem you have with the size of your dashboard.

I have not seen any reasoning how an automated process can help you
to weed out items that _are_ on your dashboard when - as you claim
- you have an interest in all of them and feel unable to make a
an educated guess from which ones you can unsubscribe yourself.

In case you want to make a point that there are in general too many
changes in a somewhat dubious state on gerrit and you would
appreciate the help of every contributor to improve the situation
by having a look at his changes and abandon the hopeless ones we
might want to ask someone from the doc team to help to formulate
that suggestion. They have a passion for finding the right words to
make complex issues easy to understand.

Andre'



More information about the Development mailing list