Subject: Policy-Discussion
List archive
- From: Ian G <iang AT cacert.org>
- To: cacert-policy AT lists.cacert.org
- Subject: Re: improving p20100306 - minor changes (TRIAL POST)
- Date: Thu, 21 Feb 2013 20:23:59 +0300
Having discussed, read responses, and
thought about it for a few days, I am thinking now that the answer
lies in policy.
Because we have been challenged [0] on an issue of Policy, we should get the Policy right. Therefore, I'm thinking in terms of copying p20100306 straight into the appropriate place in PoP: ======================ADD at end of PoP#2: 2. Basic Model: ... 2.n+1 Editors may make the following changes, where it is clear that the change does not change the policy: * fixes to errors in grammar and spelling, * anchors, HTML errors, URLs & formatting, * COD numbers and formatting, and * other minutiae, as agreed under 2.3. Such changes are to be notified to the policy group, and are to be folded into effect, etc, without further ado. ========================END OF ADDITION. With some improvement of course :) How do people feel about that? iang [0] Cost-wise, it looks like we are going to spend around 2-4 weeks on this regardless of how we deal with it. We have been told to spend time writing down stuff we already know, we have consensus on, and is established practice over many years. A.k.a. bureaucracy. Which will hold up our policy work. Either way, we don't get out of the challenge without *at least a vote* . Which is expensive, dammit! Which we should make count... Therefore, let's turn this into an opportunity and fix it in the policy. This way, we lead. On 20/02/13 06:30 AM, Ian G wrote: Software Assessment in its last telco meeting declined to take some new policy changes with links modifications, according to p20100306: |
- improving p20100306 - minor changes, Ian G, 02/20/2013
- Re: improving p20100306 - minor changes, Guillaume ROMAGNY, 02/20/2013
- RE: improving p20100306 - minor changes, Alex Robertson, 02/20/2013
- RE: improving p20100306 - minor changes, Alex Robertson, 02/20/2013
- RE: improving p20100306 - minor changes, Megan C. Robertson, 02/20/2013
- Re: improving p20100306 - minor changes (TRIAL POST), Ian G, 02/21/2013
- RE: improving p20100306 - minor changes (TRIAL POST), Megan C. Robertson, 02/21/2013
- Re: improving p20100306 - minor changes (TRIAL POST), Guillaume ROMAGNY, 02/21/2013
- RE: improving p20100306 - minor changes (TRIAL POST), ulrich, 02/22/2013
- Re: improving p20100306 - minor changes (TRIAL POST), Guillaume ROMAGNY, 02/22/2013
- Re: improving p20100306 - minor changes (TRIAL POST), Ian G, 02/22/2013
- RE: improving p20100306 - minor changes (TRIAL POST), ulrich, 02/22/2013
- Re: improving p20100306 - minor changes (TRIAL POST), Guillaume ROMAGNY, 02/21/2013
- RE: improving p20100306 - minor changes to PoP, ulrich, 02/23/2013
- RE: improving p20100306 - minor changes to PoP, ulrich, 02/23/2013
- Re: improving p20100306 - minor changes to PoP, Ian G, 02/23/2013
- RE: improving p20100306 - minor changes to PoP, ulrich, 02/23/2013
- RE: improving p20100306 - minor changes (TRIAL POST), Megan C. Robertson, 02/21/2013
- <Possible follow-up(s)>
- RE: improving p20100306 - minor changes, Peter Williams, 02/21/2013
- Re: improving p20100306 - minor changes, Ian G, 02/22/2013
Archive powered by MHonArc 2.6.16.