Is Rawhide supposed to be useful?
Adam Jackson
ajax at redhat.com
Tue May 10 18:20:39 UTC 2011
On 5/10/11 1:41 PM, Casey Dahlin wrote:
> On Tue, May 10, 2011 at 01:07:22PM -0400, Adam Jackson wrote:
>> X being broken in rawhide was in who knows how many peoples' ways, and
>> even though it's provenpackager+ and even though all it would have taken
>> was a mass driver rebuild, nobody even tried. Where _are_ you people?
>> Why do I bother to open the ACLs on my packages if nobody's going to
>> take advantage of it?
>
> Its a hard problem in human psychology (see diffusion of
> responsibility/the bystander effect). It'd be nice if there were some
> place we could list all of these tasks and allow people to grab them,
> regardless of what they maintain (sounds a bit like bugzilla really) to
> at least deter the sense of "what if I do all this work and someone else
> fixes it before I commit?"
I can see that. My approach tends to be along the lines of:
- check bugzilla for anything that looks relevant
- take a quick read of the spec or source to see if I can grok it
- check with the maintainer, if around and it's not quite trivial
- jfdi
And if I get beat to the punch, oh well, at least I learned something
new about how something else is put together, and therefore I'll be
faster next time.
- ajax
More information about the devel
mailing list