Subject: CAcert Code Development list.
List archive
- From: Alex Robertson <alex-uk AT cacert.org>
- To: Ian G <iang AT cacert.org>, Jan Dittberner <jandd AT cacert.org>, cacert-policy AT lists.cacert.org
- Cc: Eva Stöwe <eva.stoewe AT cacert.org>, Martin Gummi <martin.gummi AT cacert.org>, Benny Baumann <benbe AT cacert.org>, Felix Dörre <felix AT dogcraft.de>, cacert-devel AT lists.cacert.org
- Subject: Re: Jenkins setup for great good :-)
- Date: Fri, 06 Feb 2015 19:16:58 +0000
On 06/02/2015 10:16, Ian G wrote:
Whilst it is no longer a "contract", I'd suggest that it needs to be clarified exactly what the "binding" document actually is - it is possible that the manipulation of text as being discussed may create inconsistencies. It's probably of limited import except to arbitrators - but.....
Personally I would be very cautious about separating policy into "source" and "HTML". I don't see the need, and there are good reasons not to do this. Boring as it may seem, primitive as it may seem, we are trying to achieve "nothing up our sleeves" with policy which means there is a benefit in working in raw HTML.
I'd prefer this approach (ie bare html) until/unless this is clarified....
Alex
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
- Jenkins setup for great good :-), Jan Dittberner, 02/05/2015
- Re: Jenkins setup for great good :-), Benny Baumann, 02/06/2015
- Re: Jenkins setup for great good :-), Ian G, 02/06/2015
- Re: Jenkins setup for great good :-), Alex Robertson, 02/06/2015
Archive powered by MHonArc 2.6.18.