No answer to easy bug policy

[drago01]

On Mon, Jul 14, 2008 at 6:08 PM, Patrice Dumas <pertusus at free.fr> wrote:
> On Tue, Jul 15, 2008 at 02:29:40AM +1200, Nigel Jones wrote:
>>>
>> bugzilla get to the 'frontpage.cgi' (which imo is damn useful) and go
>> "what the, when was THAT bug reported" and notice that it was slipped in
>> the middle of a batch of gnome bugs.
>>
>> So please give maintainers a break from fearing of missing an 'easy
>> bug', we make mistakes (honest), we miss things, we forget to tell
>> people that the reason why the bug isn't fixed is because we are working
>> on getting brand new version y packaged that'd fix it better than a one
>> line patch, heck, we are humans!
>
> The policy tries to respect that, while still being effective. I have
> put 3 weeks before the procedure is started, a first comment, a
> remainder after 2 weeks and then 2 weeks before the procedure of
> orphaning which will still leave time for the packager to react and will
> put the issue in the public arena. This can certainly be improved, just
> propose. The delay can be expanded, for example, the issue is more, in
> my opinion to have those bugs tracked than to have those fixed in a
> given time.

Can we just add them to a tracker "easy bugs" and maintainers can just
go there and fix this bugs as long as the ACLs are open?
If a maintainer does NOT want this he shouldn't have enabled open ACLs at all.
"Everybody can access my packages, but don't dare to touch them" is
just plain stupid.