Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 98902 invoked from network); 18 Jul 2006 04:09:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Jul 2006 04:09:43 -0000 Received: (qmail 14247 invoked by uid 500); 18 Jul 2006 04:09:42 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 14206 invoked by uid 500); 18 Jul 2006 04:09:42 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 14195 invoked by uid 99); 18 Jul 2006 04:09:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 21:09:42 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of cliffschmidt@gmail.com designates 64.233.166.178 as permitted sender) Received: from [64.233.166.178] (HELO py-out-1112.google.com) (64.233.166.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Jul 2006 21:09:40 -0700 Received: by py-out-1112.google.com with SMTP id b36so1652455pyb for ; Mon, 17 Jul 2006 21:09:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=sGsav7+NhkvWHGJ+iktP8eg9oI3EXJ5PhDScc7tWPAglNmLkrz2mhQei/7G+yANFxqFyTARJR0Y7zBso+fTolmH+qRPScKRPDNEJQcEFAAthWrtWkIX3seGyIror4bQNEQuM/3lpLWFuktgzbl5CSP0wyVNsqrCg4P82NAHPh90= Received: by 10.35.106.15 with SMTP id i15mr4982975pym; Mon, 17 Jul 2006 21:09:16 -0700 (PDT) Received: by 10.35.47.20 with HTTP; Mon, 17 Jul 2006 21:09:16 -0700 (PDT) Message-ID: Date: Mon, 17 Jul 2006 21:09:16 -0700 From: "Cliff Schmidt" To: dev@apr.apache.org Subject: Re: Crypto FAQ Cc: colm@stdlib.net, "Justin Erenkrantz" , "Branko ?ibej" , "William A. Rowe, Jr." , "Roy T. Fielding" , "Garrett Rooney" , "David Reid" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44AFACBE.9000002@xbc.nu> <5c902b9e0607080647x41d60bb3t2a0a77c71d68077d@mail.gmail.com> <20060708214053.GA4501@dochas.stdlib.net> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I've just done a major update to the crypto docs page. Take a look and tell me what problems you see: http://apache.org/dev/crypto.html. Here's what I changed: - added the FAQ that I stared this thread with, slightly reworded - added a few additional follow-on Q&As from this thread - re-ordered the steps that need to be taken to make a bit more sense - restructured the page to look like other legal pages I've been working on (with a section on "purpose & intended audience", "overview", and "notification of updates to page") - referenced David Reid's work on project-specific RDF files that end up building an ASF-wide exports page, and changed the NOTIFICATION line to the single 'exports.html' page - added specific details about exactly what info needs to be on the exports page (primarily to help with the designing the RDF system). It's a little clunky in its hierarchical presentation, but it's just temporary until we have a system up and running. - noted that ASF source URLS might include releases on archive.apache.org as well as code being committed in /trunk - added a line to the README text to refer users to http://www.wassenaar.org/ So, in parallel with dealing with whatever problems I've created with these changes =-o , I think the last thing to do before calling this final is to help David Reid get this RDF build system done. I'll focus on this tomorrow. Cliff