I was debating bringing a case to propose new stability communication 
norms for particular classifications of projects (i.e. Java libraries).  
Rather than debate the specifics of that case at this moment, I'd like 
to determine if this would be prudent procedurally.  I know the LSARC 
intends to use trove as a precedent setting case, but I suspect a longer 
discussion is warranted to solve the generic problem of:

FOSS ports that have no stability expectations expressed in any form (or 
do, but with a different taxonomy)
FOSS ports that have different user expectations for documentation. 
(i.e. man vs. Xdoc)

I'm basing this concern on the fact that there was no quorum during the 
vote (does this matter?), and it still seems like there's a bit of 
uncertainty in the opinion.

Should I attempt this, or should I let the Trove case ride?

Reply via email to