On Mon, Apr 16, 2012 at 01:41:58PM -0700, Brendan Conoboy wrote: > Basically, I think the guidelines MJG has put together are good > principles; they just need some procedural blanks filled in so SA > teams know how to apply them and communicate with the greater Fedora > community. I think a better way to think about this might be lie the packaging guidelines - they provide a set of technical constraints, but they don't tell you how to be part of the packaging community. I see SAs in the same kind of way. Secondary architecture maintainers should be active members of the greater Fedora community. You should be talking about what you're doing, providing regular status updates on devel@, actively involving yourself in other technical discussions to make sure that decisions aren't made without consideration of your constraints. Basically, behave as if you're a primary architecture. If you manage that then I think most of the problems you're worried about go away. It'll be obvious to everyone whether or not you're ready to be a primary architecture at any given point. Don't worry about the details. Just be part of Fedora. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
