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

Re: No answer to easy bug policy



man, 14 07 2008 kl. 23:00 +0100, skrev Richard W.M. Jones:
> On Sat, Jul 12, 2008 at 02:04:47AM +0200, Patrice Dumas wrote:
> > If you don't answer after 2 weeks and one remainder lasting also at
> > least 2 week the package will be orphaned according to the policy stated
> > at <link>
> 
> So that's 4 weeks in all?
> 
> 2 weeks alone is way too short because people commonly go on holiday
> for that length of time & longer.

Maybe some kind of exception to the rule or clarification should be
added provided the maintainer is on the Vacation wiki page that this
draconian type of punishment doesn't apply or doesn't apply in full.

All this rule making seem to me though to be forgetting that most Fedora
contributors are doing this in their sparetime, out of the goodness of
their heart. Coating the progress of contributing in a continual thick
layer of rules and punishment might just make it unfunny to be part of
the community as such we might see a decline in our number of available
maintainers. Another fear to consider before imposing more rules is that
the more we force maintainers to do certain things, the less time they
will have available to expand their package count, help new contributors
learn the ropes and review packages in the end potentially causing grave
harm to Fedora as a whole. It also might pose a barrier of entry
considered much to tall for new contributors. 

Be careful not to regulate Fedora to death.

Don't get me wrong I am strongly in favor of fixing bugs, but I would
love an approach that was centered around creating and integrating tools
to help maintainers. Automating the gathering of information, marking of
duplicates and such things as provided by tools like Apport seems to be
the saner focus as opposed to regulation at least for the moment. Do all
that, then start worrying about making rules should easy bugs still slip
through the net.

- David Nielsen


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