On 14/05/2008, Santiago Gala <[EMAIL PROTECTED]> wrote:
> El mar, 13-05-2008 a las 12:53 -0700, Stefano Mazzocchi escribió:
>
> > William A. Rowe, Jr. wrote:
>  > > Santiago Gala wrote:
>  > >> El mar, 29-04-2008 a las 07:45 +0100, Robert Burrell Donkin escribió:
>  > >>> On 4/29/08, Santiago Gala <[EMAIL PROTECTED]> wrote:
>  > >>>> Additionally an email must be sent somewhere to tell about the fact. I
>  > >>>> sent it for shindig, so I can look into the details if needed, but I
>  > >>>> don't have it to check right now.
>  > >>> The chair needs to send the mail
>  > >>
>  > >> Yeah, I think it is different for incubator; because of the number of
>  > >> podlings it is done by mentors instead. Not sure about labs, which is
>  > >> somehow similar to incubator.
>  > >
>  > > No, the chair should always send that email.  Think about 'good crypto'
>  > > vs something the BIX determines to be 'bad crypto' (wtf that would be).
>  > > The chair has additional support of and protection from being a corporate
>  > > officer of the ASF.  But it's simplest for all if others can help the
>  > > chair by updating license/exports/index.html.  That entry provides the
>  > > chair with everything they need to know to fire off that notice.
>  >
>  > Hmm, the chair just got back from his honeymoon and lab's crypto was not
>  > exactly very high on his priority list.
>
>
> :) congrats! I understand about priorities...
>
>
>  >
>  > So, what email are we talking about?
>  >
>
>
> I was asking for specifics about incubator, in the email you quote. But
>  in the case being discussed here, BadCA and vysper are using encryption
>  technologies, so the procedure at
>
> https://svn.apache.org/repos/asf/infrastructure/site/trunk/xdocs/licenses/exports/index.xml
>
> should be followed, as Bernd Fondermann pointed Apr 29th in the email
>  that started this thread.
>
>  Bertrand Delacretaz pointed at
>
> https://issues.apache.org/jira/browse/TIKA-118
>
> to see the whole procedure outlined.
>
>  Basically the work involved is:
>  * assessment of the crypto used
>  * NOTICE in the lab code with the details

AFAIK, the notice does not normally go in the NOTICE file (which is
for attributions only), but in a README file.

>  * adding notes to the first URL (Bernd's email)
>  * the chair sending an email to whatever authority pointing them to the
>  URLs.
>
>  Regards
>  Santiago
>
> --
>
> Santiago Gala
>  http://memojo.com/~sgala/blog/
>
>
>  ---------------------------------------------------------------------
>
> To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to