Java packages, guidelines, ...

[Kevin Kofler]

Jason L Tibbitts III <tibbs <at> math.uh.edu> writes:
> KK> If what we have now is good enough for all the existing packages,
> 
> It isn't.

We have general guidelines in the absence of application/language-specific 
ones.

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.

        Kevin Kofler