On Tue, Oct 08, 2013 at 08:24:33AM +0200, Ralf Corsepius wrote:
> On 10/08/2013 08:02 AM, David Tardon wrote:
> >On Sat, Oct 05, 2013 at 03:29:57AM +0000, "Jóhann B. Guðmundsson" wrote:
> >>Shall we talk about how Red Hat employees have been granted all
> >>kinds of privileges within our community without as even bother to
> >>introduce themselves to the community even to the extent that fesco
> >>is now judging people if they are "socially ready" for proven
> >>packagers while Red Hat employees walk around and are granted those
> >>privileges freely?
> >That is an utter fabrication. Red Hat packagers have to go exactly
> >through the same process to became packagers as anyone else (well, it
> >may be easier for them to find a sponsor, but sponsored they must be);
> >they have to go through the same process to became proven packagers etc.
> In fedora's history, there have been many examples which demonstrate
> the contrary. There have been many cases, where RH teams where
> mutually approving their team mates as packagers,
> where RH supervisors where approving their subordinates as proven
> packagers, and where RH office/team mates rushed through package
> reviews "ping pong style".

Which is not what he is saying. It is sad that such things happen at
all, but he claims they happen routinely, as a matter of fact. That is
an accusation I strongly object to.

Btw, proven packagers are approved by FESCo. I fail to see how any Red
Hat supervisor could go around that.

Btw, these things are hardly limited to Red Hat. E.g., who is to stop
two packagers trying to get a set of packages into Fedora from
perfunctorily reviewing each others packages?

> 
> 
> >I respectfully suggest that you be silent if you do not know the facts.
> >Your credibility is diminishing rapidly with every untrue statement you
> >put forth.
> I respectfully disagree with you.

Suit yourself.

D.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Reply via email to