CAcert Code Development list.

[Ian G <iang AT iang.org>]

On 17/03/2010 22:41, Andreas Bäß wrote:

> If there is anybody volunteering to make a suggestion what this means to
> the org-assurance policy feel free to make a draft :-) I won't today as
> I have other priorities.


This is the problem I have too.  I have never seen an Orga assurance, 
I've never seen the forms, and I've never had the feeling that anyone 
knows enough about it to describe what happens.  The teaching seems to 
be p2p with no written doco.

The only thing I can think of is to find the people who claim they know 
it, get them together, then train some new guys.  And watch and 
document.  Then, the watchers and documentors test the new guys, 
independently.  Not to to test them, but to test their doco.

Without some process like that, I would not know where to start.  No 
practices docs, and a policy that is demonstrably out of line with practice.

One hates to be the wet blanket here, but we are now a policy driven 
organisation.  No clear policy, no doco, means we shouldn't be doing it. 
 It only takes one dispute, and an Arbitrator will pull the plug, 
because he has no foundation to declare what was done as good, bad or 
indifferent.

iang