CAcert Code Development list.

[Alex Robertson <alex-uk AT cacert.org>]

One wonders whether the CAP form is even necessary - they're useful for 
handling assurances away from a computer, but otherwise they only seem 
to cause issues - seven year retention and return to an arbitrator if 
leaving etc. i would have thought it might be time to remember that we 
are in the 21st century; it is no longer politically correct to use huge 
amounts of "dead trees". This may not be the best forum for discussion 
of this - but it may be worth considering before going to a lot of time 
and trouble fixing the CAP forms.

@Ted (and any committee members here as DRO) - has anything been done 
about getting hold of CAP forms from Uli and all the other people who 
have resigned over the past couple of years???


Regards

Alex (UK)



On 18/01/2019 21:45, Bernhard Fröhlich wrote:
> Hi Brian,
>
> as a follow-up to our discussion on IRC:
>
> I would not consider the spelling issues with the CAP forms that were 
> found during recent tests a blocking issue for bug-1305. The problems 
> do not relate to the new roots, and probably have been there for quite 
> a long time already.
>
> Nevertheless, if they can easily be fixed it would be nice to include 
> them in the fix. The CAcert/Cacert issue most probalby fall in this 
> category, whereas the non-codepage 1252 characters won't. The latter 
> one has its own bugtracker case 1039 and should be handled as an 
> isolated issue once we're done with bug 1305.
>
> Kind regards
> Ted
> ;)

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus