David, A few questions/comments:
1) It is not clear whether this is policy for Meego core packages or for community packages (or both). I assume it is Core, as that is all that exists at the moment. And if we end up with multiple community repositories there may well end up with multiple policies. 2) Four days is not long to spot, review and comment on a proposal if one is not a paid developer. For example, I have been travelling doing my day job all this week and have had no time to look at this list since Monday. If this is just Core policy that is probably fine -- all Core package maintianers are expected to be paid developers, who track the mailing list as part of their job. 3) You really need to be clear where/how discussion is expected to happen (this is separate from the issue fo where the approved policy is published). Personally I would prefer the mailing list (proposed content changes may be in a Wiki page but discussion should be on the list). That is probably partly becuase I have yet to discover how I tell the Wiki to email me on changes to a particular page! Graham _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
