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

Keeping track of best practises / policy changes with tracking -devel


I'm finding that I can't keep up with devel but I would like to be able
to see a summary of consensuses (consensii?) that result from the
discussions, as well a final summaries of best practices (and changes
to them.  Also a neat changelog of policy changes I should be aware of.

Basically I want to make sure I package well, but I don't
want to track -devel, because it is way too busy.

Anything that can help?

Also, is there any codification of best practices anywhere?  (and
what's the deal with the new package/patch format?)

I've read NM guide and Policy, but what I see on -devel is a bunch of
other technical information and considerations that aren't codified
anywhere I can find, but following the mailing list to keep track is
taking so much time that in the past few days I've read mail and done
no work on actual development.

And that's my crabbing done for the day.  Got it out of the way early, 
now I have the rest of the afternoon to sniff fragrant tea-roses or 
strangle cute bunnies or something.   -- Michael Devore
GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C      http://gnupg.org

Attachment: signature.asc
Description: PGP signature

Reply to: