Java packages, guidelines, ...

[Jesse Keating]

On Tue, 2008-03-18 at 01:58 +0000, Kevin Kofler wrote:
> How do you decide what needs a guideline? Because someone writes up a draft? So 
> if I write a draft guideline for, say, GNOME packages, and then let it bitrot, 
> will you block all GNOME packages until someone finalizes my broken guideline? 
> This would be a very broken process and allow anyone to sabotage Fedora just by 
> coming up with useless "draft guidelines".
> 
> We have general guidelines, we apply these for all new packages where no 
> specific one exists, I don't see why the mere existence of a draft guideline 
> would suddenly change that.

In this case we need specific Java guidelines because without them,
these packages would /fail/ the general guidelines.  That's what
specific guidelines often end up being, pre-approved exceptions to
general guidelines.

-- 
Jesse Keating
Fedora -- All my bits are free, are yours?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20080317/bf5fd751/attachment.sig>