Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of kevan.miller@gmail.com
 designates 74.125.46.28 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:from:to:in-reply-to:content-type:mime-version:subject:date:references:x-mailer;
        b=LQGLIKnaB49MqNHcQVotqGeLdrMbLGWgwLggnIZ9BSSL2H9Xiv8K8T508GIXcDXIApXB2aQ3KemoKJ70dL1xUfhYkjypsrpuAWiCbfVk22o9k5/E7Ros+D5Ecw1sF63POFu+VMpMsurQntRGAFzpmK7eUFjwcuNgOfOTQnCtBWY=
Message-Id: <D0C24259-B8E4-40C2-9DC4-BB8EB7D0C6D0@gmail.com>
From: Kevan Miller <kevan.miller@gmail.com>
To: dev@geronimo.apache.org
In-Reply-To: <4815D912.2030505@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-17--821308297
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Doc IP Clearance (was Re: [DISCUSS] Policy for granting write
 access to our Wiki)
Date: Mon, 28 Apr 2008 16:22:05 -0400
References: <4E1CC14F-B064-40D8-9ACA-1E84DACA66CF@gmail.com>
 <3B641173-E128-4C75-B8C7-D8A96539AE17@visi.com>
 <6533347D-CB05-4579-BEA0-55802E6DA852@gmail.com>
 <26E60EE5-4532-48A7-B8C7-8A12AFB8CEFF@visi.com>
 <23EA6384-4396-41D1-89BC-6AEAF6A7768C@visi.com>
 <73a75e430804212047r7a1fe552pda725b10a2d02a23@mail.gmail.com>
 <517F18EE-120A-4DB2-AED4-3097A3FD6391@visi.com>
 <526194FD-E6F8-4908-8FD9-0C996AF64665@yahoo.com>
 <CBF81570-44EB-4185-82FB-E4967480FAF2@gmail.com> <4815D912.2030505@gmail.com>


--Apple-Mail-17--821308297
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit


On Apr 28, 2008, at 10:02 AM, Hernan Cunico wrote:

> Guys we need to wrap up this discussion. I'm not sure where are we  
> standing but still have a bunch of questions.

Hi Hernan,
Agreed. Sorry I've been out due to some family health issues...

>
> A few things that look clear to me thus far
> - We'll request every contributor to submit a CLA. Filing  
> instructions are provided in the Individual Contributor License  
> Agreement itself available here http://www.apache.org/licenses
> - Every contributor will have to expressly communicate intention for  
> contributing with the project's documentation sending a email to dev@geronimo.apache.org

I'd be happy with that.

>
>
> Some things still pending
> - Having a CLA on file will suffice to grant edit access to the doc  
> or we'll seek PMC voting?

I don't think a vote is necessary.

>
> - Although a CLA is ASF wide we should provide access to only those  
> interested in contributing to Geronimo's documentation. Do we  
> already keep a separate list?

Not that I know of.

>
> - When do we make effective such access restriction?

As soon as we have a decision.

>
> - What Confluence spaces will be affected?
> - How do we deal with existing content? We can not apply this  
> retroactively.

We can investigate what our risks are. Ask for old contributors to  
submit a CLA and document their past submissions are licensed to the  
ASF. I don't really know what are options will be. Anyone care to find  
out?

>
> Once all these are sorted out I'll update the Apache Geronimo  
> Policies on the web site (http://geronimo.apache.org/project-policies.html 
> ) to reflect these changes

Sounds good.

--kevan
--Apple-Mail-17--821308297
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Apr 28, 2008, =
at 10:02 AM, Hernan Cunico wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">Guys we =
need to wrap up this discussion. I'm not sure where are we standing but =
still have a bunch of questions.</blockquote><div><br></div><div>Hi =
Hernan,</div><div>Agreed. Sorry I've been out due to some family health =
issues...</div><br><blockquote type=3D"cite"><br>A few things that look =
clear to me thus far<br>- We'll request every contributor to submit a =
CLA. Filing instructions are provided in the Individual Contributor =
License Agreement itself available here <a =
href=3D"http://www.apache.org/licenses">http://www.apache.org/licenses</a>=
<br>- Every contributor will have to expressly communicate intention for =
contributing with the project's documentation sending a email to <a =
href=3D"mailto:dev@geronimo.apache.org">dev@geronimo.apache.org</a></block=
quote><div><br></div><div>I'd be happy with that.</div><br><blockquote =
type=3D"cite"><br><br>Some things still pending<br>- Having a CLA on =
file will suffice to grant edit access to the doc or we'll seek PMC =
voting?</blockquote><div><br></div><div>I don't think a vote is =
necessary.</div><br><blockquote type=3D"cite"><br>- Although a CLA is =
ASF wide we should provide access to only those interested in =
contributing to Geronimo's documentation. Do we already keep a separate =
list?</blockquote><div><br></div><div>Not that I know =
of.</div><br><blockquote type=3D"cite"><br>- When do we make effective =
such access restriction?</blockquote><div><br></div><div>As soon as we =
have a decision.</div><br><blockquote type=3D"cite"><br>- What =
Confluence spaces will be affected?<br>- How do we deal with existing =
content? We can not apply this =
retroactively.</blockquote><div><br></div>We can investigate what our =
risks are. Ask for old contributors to submit a CLA and document their =
past submissions are licensed to the ASF. I don't really know what are =
options will be. Anyone care to find out?</div><div><br><blockquote =
type=3D"cite"><br>Once all these are sorted out I'll update the Apache =
Geronimo Policies on the web site (<a =
href=3D"http://geronimo.apache.org/project-policies.html">http://geronimo.=
apache.org/project-policies.html</a>) to reflect these =
changes<br></blockquote></div><br><div>Sounds =
good.</div><div><br></div><div>--kevan</div></body></html>=

--Apple-Mail-17--821308297--