On 22/05/10 00:35, Graham Cobb wrote:
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.
Yes, it is a proposal for Core.
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.
I agree and I did think about it - I wanted it to be shorter but... :)
I feel that during the coming months the policy needs to grow and change
quickly and in order to support this I proposed a rapid response -
essentially I wanted to be able to change policy before the next weekly
'release'.
Nothing stops us all listening to reasonable debate and responding to
change requests; updating a change should not be problematic.
Would you like to wait to see if the time allowed to comment turns out
to be a problem and then propose an extended period - I expect that to
happen over time - or propose an extension now?
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!
OK.
I didn't want to be too restrictive and I know discussion will happen in
many places: irc, email, meeting rooms, conferences...
The key is that the discussion should come back to a proposal on the
-devel mailing list; maybe we should clarify that that is the place to
consolidate debate. Oh, and whilst there is debate I didn't want it to
be an open democracy - the packaging team (who?) have the final say.
A final general point - the docs as they stand are very .... fresh :)
I worry slightly that if we are overly formal then we risk being
paralysed by having to produce high quality updates to them - that takes
a lot more time than making an incremental improvement. So rather than
insist that the docs are fully correct and self-consistent after every
proposed change I would rather see them 'improved'; and by that I simply
mean less inconsistent or richer in content.
David
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
