(resend - first post rejected as list is closed) (2nd resend - 2nd post seemed to go to /dev/null)
A conversation earlier today got me the action to submit a request for the TSG: http://wiki.meego.com/Technical_Steering_Group_meetings#Backlog_of_Proposed_Topics The intention is simply to clarify that the wiki policy is authoritative and mandatory and formalise that we shouldn't change the packaging policy on a whim. Since the meeting is tomorrow I've rushed this out for feedback. The text below also appears at http://wiki.meego.com/Packaging/Policy This is currently a proposal touching on MeeGo packaging, policy, Bugs and reporting. Objective The objective of this policy is to improve consistency and quality of packaging for MeeGo. Justification * Consistency in packaging is an obvious goal and requires guidelines. * It is not clear that failure to adhere to the guidelines is actually a bug in a package (or the guidelines). * At the moment the wiki policy simply reflects 'random' contributions (eg: some of which I, David Greaves, unilaterally inserted); this is not appropriate for a policy document. Policy: * The MeeGo packaging policy on the wiki is authoritative and can be changed using the process outlined below. http://wiki.meego.com/Packaging/Guidelines * Bugs raised against packages for failure to meet policy are valid Update process: For updates to the packaging policy I suggest an open and lightweight process that allows community involvement: * The process to change policy is to submit a proposed amendment to the -devel mailing list (maybe -pkg eventually). * 4 working days are allowed for comments from the community and responses from the packaging team. * Packaging team members can approve their own proposals. * The proposal should justify the changes. * The proposal is accepted with: o A single ACCEPT from a packaging team member providing no other team REJECTs/RETRYs are received; otherwise o A quorum of ACCEPTs (?) * A RETRY is essentially an ACCEPT but asks for some changes to be made. * The proposal is rejected with: o A single REJECT from a packaging team member providing no other team ACCEPTs/RETRYs are received; otherwise o A quorum of REJECTs (?) * A REJECT should explain (and justify) the reason for the rejection. * If there is no response a repeat email should be sent every 2 days. After 4 repeats the policy change is accepted. The packaging team consists of? Anas, David, Sasha... David Greaves _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
