You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Craig Russell <ap...@gmail.com> on 2017/08/06 22:52:28 UTC
Updating ip-clearance web site
Can anyone here tell me what the life cycle is for ip-clearance?
The guidelines at https://incubator.apache.org/guides/website.html say that ip-clearance is maintained in svn.
The web page has a typo: https://incubator.apache.org/ip-clearance/index.html (search for "concensus")
So I corrected the typo in index.xml and committed it. [1]
But the change has not shown up on the web site after several hours.
What happens now? Is the process to publish it documented anywhere?
Thanks,
Craig
[1] ------------------------------------------------------------------------
r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
Fix typo in ip-clearance
Index: index.xml
===================================================================
--- index.xml (revision 1804261)
+++ index.xml (revision 1804262)
@@ -34,7 +34,7 @@
simply the repository of the needed information. Once a PMC directly
checks-in a filled-out short form, the Incubator PMC will need to
approve the paper work after which point the receiving PMC is free to
- import the code. <strong>Note</strong> that only lazy concensus is
+ import the code. <strong>Note</strong> that only lazy consensus is
required. The <a href='ip-clearance-template.html'>IP clearance template</a>
contains more details of this process.</p>
<p>For new IP clearance forms, start with our XML <a
Craig L Russell
clr@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Updating ip-clearance web site
Posted by sebb <se...@gmail.com>.
On 7 August 2017 at 00:14, Craig Russell <ap...@gmail.com> wrote:
> Hi John,
>
> Thanks for clarifying.
>
> I would like to confirm that ip-clearance web site is generated from three source documents in two repositories:
>
> git https://git-wip-us.apache.org/repos/asf/incubator.git
>
> pages/guides/ip_clearance.ad
> generates http://incubator.apache.org/ip_clearance.html
I think that should be
http://incubator.apache.org/guides/ip_clearance.html
>
> svn https://svn.apache.org/repos/asf
>
> incubator/public/trunk/content/ip-clearance/index.xml
> generates http://incubator.apache.org/ip-clearance/index.html
>
> incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml
> generates http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The information in these three documents needs to be consistent, which is my goal.
>
> Thanks,
>
> Craig
>
>
>> On Aug 6, 2017, at 4:07 PM, John D. Ament <jo...@apache.org> wrote:
>>
>> From that page:
>>
>> Commits to the git repo trigger builds automatically, and the website
>> builds daily for other changes.
>>
>>
>> Basically, I don't have a way yet to trigger a build on change to either
>> repo. I do think I have a way though, need to switch the job to multiple
>> SCMs and that should work.
>>
>> So for now, please login to Jenkins and trigger it, otherwise wait for the
>> nightly build.
>>
>> John
>>
>> On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com> wrote:
>>
>>> Can anyone here tell me what the life cycle is for ip-clearance?
>>>
>>> The guidelines at https://incubator.apache.org/guides/website.html say
>>> that ip-clearance is maintained in svn.
>>>
>>> The web page has a typo:
>>> https://incubator.apache.org/ip-clearance/index.html (search for
>>> "concensus")
>>>
>>> So I corrected the typo in index.xml and committed it. [1]
>>>
>>> But the change has not shown up on the web site after several hours.
>>>
>>> What happens now? Is the process to publish it documented anywhere?
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>> [1]
>>> ------------------------------------------------------------------------
>>> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
>>>
>>> Fix typo in ip-clearance
>>>
>>> Index: index.xml
>>> ===================================================================
>>> --- index.xml (revision 1804261)
>>> +++ index.xml (revision 1804262)
>>> @@ -34,7 +34,7 @@
>>> simply the repository of the needed information. Once a PMC
>>> directly
>>> checks-in a filled-out short form, the Incubator PMC will need to
>>> approve the paper work after which point the receiving PMC is
>>> free to
>>> - import the code. <strong>Note</strong> that only lazy concensus
>>> is
>>> + import the code. <strong>Note</strong> that only lazy consensus
>>> is
>>> required. The <a href='ip-clearance-template.html'>IP clearance
>>> template</a>
>>> contains more details of this process.</p>
>>> <p>For new IP clearance forms, start with our XML <a
>>>
>>>
>>> Craig L Russell
>>> clr@apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Updating ip-clearance web site
Posted by Craig Russell <ap...@gmail.com>.
IP Clearance depends a lot on other licensing questions. I'm thinking of adding a few more FAQ to http://apache.org/foundation/license-faq.html and then I could refer to the FAQ when discussing IP clearance in the context of what IP means.
In particular, http://apache.org/foundation/license-faq.html#PatentScope and
http://www.apache.org/licenses/#clas and
http://www.apache.org/licenses/#submitting
Craig
> On Aug 6, 2017, at 5:30 PM, Craig Russell <ap...@gmail.com> wrote:
>
> My idea is to put all of the common stuff into one document and have the others refer to it. Then if we need tweak anything, we can do it in one place. Your suggestion of guides/ip_clearance.ad makes sense. I'll see what I can come up with.
>
> Less time spent by volunteers (IPMC members and legal counsel) reviewing and discussing it.
>
> Craig
>
>> On Aug 6, 2017, at 4:19 PM, John D. Ament <jo...@apache.org> wrote:
>>
>> Craig,
>>
>> Yep, that's correct. And I personally appreciate the time spent to make
>> these consistent. I'm wondering - would it just make sense to move the
>> content around how TLPs request IP Clearance into guides/ip_clearance.ad ?
>>
>> John
>>
>> On Sun, Aug 6, 2017 at 7:14 PM Craig Russell <ap...@gmail.com> wrote:
>>
>>> Hi John,
>>>
>>> Thanks for clarifying.
>>>
>>> I would like to confirm that ip-clearance web site is generated from three
>>> source documents in two repositories:
>>>
>>> git https://git-wip-us.apache.org/repos/asf/incubator.git
>>>
>>> pages/guides/ip_clearance.ad
>>> generates http://incubator.apache.org/ip_clearance.html
>>>
>>> svn https://svn.apache.org/repos/asf
>>>
>>> incubator/public/trunk/content/ip-clearance/index.xml
>>> generates http://incubator.apache.org/ip-clearance/index.html
>>>
>>> incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml
>>> generates
>>> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>>>
>>> The information in these three documents needs to be consistent, which is
>>> my goal.
>>>
>>> Thanks,
>>>
>>> Craig
>>>
>>>
>>>> On Aug 6, 2017, at 4:07 PM, John D. Ament <jo...@apache.org> wrote:
>>>>
>>>> From that page:
>>>>
>>>> Commits to the git repo trigger builds automatically, and the website
>>>> builds daily for other changes.
>>>>
>>>>
>>>> Basically, I don't have a way yet to trigger a build on change to either
>>>> repo. I do think I have a way though, need to switch the job to multiple
>>>> SCMs and that should work.
>>>>
>>>> So for now, please login to Jenkins and trigger it, otherwise wait for
>>> the
>>>> nightly build.
>>>>
>>>> John
>>>>
>>>> On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com>
>>> wrote:
>>>>
>>>>> Can anyone here tell me what the life cycle is for ip-clearance?
>>>>>
>>>>> The guidelines at https://incubator.apache.org/guides/website.html say
>>>>> that ip-clearance is maintained in svn.
>>>>>
>>>>> The web page has a typo:
>>>>> https://incubator.apache.org/ip-clearance/index.html (search for
>>>>> "concensus")
>>>>>
>>>>> So I corrected the typo in index.xml and committed it. [1]
>>>>>
>>>>> But the change has not shown up on the web site after several hours.
>>>>>
>>>>> What happens now? Is the process to publish it documented anywhere?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Craig
>>>>>
>>>>> [1]
>>>>> ------------------------------------------------------------------------
>>>>> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
>>>>>
>>>>> Fix typo in ip-clearance
>>>>>
>>>>> Index: index.xml
>>>>> ===================================================================
>>>>> --- index.xml (revision 1804261)
>>>>> +++ index.xml (revision 1804262)
>>>>> @@ -34,7 +34,7 @@
>>>>> simply the repository of the needed information. Once a PMC
>>>>> directly
>>>>> checks-in a filled-out short form, the Incubator PMC will need
>>> to
>>>>> approve the paper work after which point the receiving PMC is
>>>>> free to
>>>>> - import the code. <strong>Note</strong> that only lazy
>>> concensus
>>>>> is
>>>>> + import the code. <strong>Note</strong> that only lazy
>>> consensus
>>>>> is
>>>>> required. The <a href='ip-clearance-template.html'>IP clearance
>>>>> template</a>
>>>>> contains more details of this process.</p>
>>>>> <p>For new IP clearance forms, start with our XML <a
>>>>>
>>>>>
>>>>> Craig L Russell
>>>>> clr@apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>
>>> Craig L Russell
>>> Secretary, Apache Software Foundation
>>> clr@apache.org http://db.apache.org/jdo
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>
Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Updating ip-clearance web site
Posted by Craig Russell <ap...@gmail.com>.
My idea is to put all of the common stuff into one document and have the others refer to it. Then if we need tweak anything, we can do it in one place. Your suggestion of guides/ip_clearance.ad makes sense. I'll see what I can come up with.
Less time spent by volunteers (IPMC members and legal counsel) reviewing and discussing it.
Craig
> On Aug 6, 2017, at 4:19 PM, John D. Ament <jo...@apache.org> wrote:
>
> Craig,
>
> Yep, that's correct. And I personally appreciate the time spent to make
> these consistent. I'm wondering - would it just make sense to move the
> content around how TLPs request IP Clearance into guides/ip_clearance.ad ?
>
> John
>
> On Sun, Aug 6, 2017 at 7:14 PM Craig Russell <ap...@gmail.com> wrote:
>
>> Hi John,
>>
>> Thanks for clarifying.
>>
>> I would like to confirm that ip-clearance web site is generated from three
>> source documents in two repositories:
>>
>> git https://git-wip-us.apache.org/repos/asf/incubator.git
>>
>> pages/guides/ip_clearance.ad
>> generates http://incubator.apache.org/ip_clearance.html
>>
>> svn https://svn.apache.org/repos/asf
>>
>> incubator/public/trunk/content/ip-clearance/index.xml
>> generates http://incubator.apache.org/ip-clearance/index.html
>>
>> incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml
>> generates
>> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>>
>> The information in these three documents needs to be consistent, which is
>> my goal.
>>
>> Thanks,
>>
>> Craig
>>
>>
>>> On Aug 6, 2017, at 4:07 PM, John D. Ament <jo...@apache.org> wrote:
>>>
>>> From that page:
>>>
>>> Commits to the git repo trigger builds automatically, and the website
>>> builds daily for other changes.
>>>
>>>
>>> Basically, I don't have a way yet to trigger a build on change to either
>>> repo. I do think I have a way though, need to switch the job to multiple
>>> SCMs and that should work.
>>>
>>> So for now, please login to Jenkins and trigger it, otherwise wait for
>> the
>>> nightly build.
>>>
>>> John
>>>
>>> On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com>
>> wrote:
>>>
>>>> Can anyone here tell me what the life cycle is for ip-clearance?
>>>>
>>>> The guidelines at https://incubator.apache.org/guides/website.html say
>>>> that ip-clearance is maintained in svn.
>>>>
>>>> The web page has a typo:
>>>> https://incubator.apache.org/ip-clearance/index.html (search for
>>>> "concensus")
>>>>
>>>> So I corrected the typo in index.xml and committed it. [1]
>>>>
>>>> But the change has not shown up on the web site after several hours.
>>>>
>>>> What happens now? Is the process to publish it documented anywhere?
>>>>
>>>> Thanks,
>>>>
>>>> Craig
>>>>
>>>> [1]
>>>> ------------------------------------------------------------------------
>>>> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
>>>>
>>>> Fix typo in ip-clearance
>>>>
>>>> Index: index.xml
>>>> ===================================================================
>>>> --- index.xml (revision 1804261)
>>>> +++ index.xml (revision 1804262)
>>>> @@ -34,7 +34,7 @@
>>>> simply the repository of the needed information. Once a PMC
>>>> directly
>>>> checks-in a filled-out short form, the Incubator PMC will need
>> to
>>>> approve the paper work after which point the receiving PMC is
>>>> free to
>>>> - import the code. <strong>Note</strong> that only lazy
>> concensus
>>>> is
>>>> + import the code. <strong>Note</strong> that only lazy
>> consensus
>>>> is
>>>> required. The <a href='ip-clearance-template.html'>IP clearance
>>>> template</a>
>>>> contains more details of this process.</p>
>>>> <p>For new IP clearance forms, start with our XML <a
>>>>
>>>>
>>>> Craig L Russell
>>>> clr@apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> clr@apache.org http://db.apache.org/jdo
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Updating ip-clearance web site
Posted by "John D. Ament" <jo...@apache.org>.
Craig,
Yep, that's correct. And I personally appreciate the time spent to make
these consistent. I'm wondering - would it just make sense to move the
content around how TLPs request IP Clearance into guides/ip_clearance.ad ?
John
On Sun, Aug 6, 2017 at 7:14 PM Craig Russell <ap...@gmail.com> wrote:
> Hi John,
>
> Thanks for clarifying.
>
> I would like to confirm that ip-clearance web site is generated from three
> source documents in two repositories:
>
> git https://git-wip-us.apache.org/repos/asf/incubator.git
>
> pages/guides/ip_clearance.ad
> generates http://incubator.apache.org/ip_clearance.html
>
> svn https://svn.apache.org/repos/asf
>
> incubator/public/trunk/content/ip-clearance/index.xml
> generates http://incubator.apache.org/ip-clearance/index.html
>
> incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml
> generates
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The information in these three documents needs to be consistent, which is
> my goal.
>
> Thanks,
>
> Craig
>
>
> > On Aug 6, 2017, at 4:07 PM, John D. Ament <jo...@apache.org> wrote:
> >
> > From that page:
> >
> > Commits to the git repo trigger builds automatically, and the website
> > builds daily for other changes.
> >
> >
> > Basically, I don't have a way yet to trigger a build on change to either
> > repo. I do think I have a way though, need to switch the job to multiple
> > SCMs and that should work.
> >
> > So for now, please login to Jenkins and trigger it, otherwise wait for
> the
> > nightly build.
> >
> > John
> >
> > On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com>
> wrote:
> >
> >> Can anyone here tell me what the life cycle is for ip-clearance?
> >>
> >> The guidelines at https://incubator.apache.org/guides/website.html say
> >> that ip-clearance is maintained in svn.
> >>
> >> The web page has a typo:
> >> https://incubator.apache.org/ip-clearance/index.html (search for
> >> "concensus")
> >>
> >> So I corrected the typo in index.xml and committed it. [1]
> >>
> >> But the change has not shown up on the web site after several hours.
> >>
> >> What happens now? Is the process to publish it documented anywhere?
> >>
> >> Thanks,
> >>
> >> Craig
> >>
> >> [1]
> >> ------------------------------------------------------------------------
> >> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
> >>
> >> Fix typo in ip-clearance
> >>
> >> Index: index.xml
> >> ===================================================================
> >> --- index.xml (revision 1804261)
> >> +++ index.xml (revision 1804262)
> >> @@ -34,7 +34,7 @@
> >> simply the repository of the needed information. Once a PMC
> >> directly
> >> checks-in a filled-out short form, the Incubator PMC will need
> to
> >> approve the paper work after which point the receiving PMC is
> >> free to
> >> - import the code. <strong>Note</strong> that only lazy
> concensus
> >> is
> >> + import the code. <strong>Note</strong> that only lazy
> consensus
> >> is
> >> required. The <a href='ip-clearance-template.html'>IP clearance
> >> template</a>
> >> contains more details of this process.</p>
> >> <p>For new IP clearance forms, start with our XML <a
> >>
> >>
> >> Craig L Russell
> >> clr@apache.org
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: Updating ip-clearance web site
Posted by Craig Russell <ap...@gmail.com>.
Hi John,
Thanks for clarifying.
I would like to confirm that ip-clearance web site is generated from three source documents in two repositories:
git https://git-wip-us.apache.org/repos/asf/incubator.git
pages/guides/ip_clearance.ad
generates http://incubator.apache.org/ip_clearance.html
svn https://svn.apache.org/repos/asf
incubator/public/trunk/content/ip-clearance/index.xml
generates http://incubator.apache.org/ip-clearance/index.html
incubator/public/trunk/content/ip-clearance/ip-clearance-template.xml
generates http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The information in these three documents needs to be consistent, which is my goal.
Thanks,
Craig
> On Aug 6, 2017, at 4:07 PM, John D. Ament <jo...@apache.org> wrote:
>
> From that page:
>
> Commits to the git repo trigger builds automatically, and the website
> builds daily for other changes.
>
>
> Basically, I don't have a way yet to trigger a build on change to either
> repo. I do think I have a way though, need to switch the job to multiple
> SCMs and that should work.
>
> So for now, please login to Jenkins and trigger it, otherwise wait for the
> nightly build.
>
> John
>
> On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com> wrote:
>
>> Can anyone here tell me what the life cycle is for ip-clearance?
>>
>> The guidelines at https://incubator.apache.org/guides/website.html say
>> that ip-clearance is maintained in svn.
>>
>> The web page has a typo:
>> https://incubator.apache.org/ip-clearance/index.html (search for
>> "concensus")
>>
>> So I corrected the typo in index.xml and committed it. [1]
>>
>> But the change has not shown up on the web site after several hours.
>>
>> What happens now? Is the process to publish it documented anywhere?
>>
>> Thanks,
>>
>> Craig
>>
>> [1]
>> ------------------------------------------------------------------------
>> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
>>
>> Fix typo in ip-clearance
>>
>> Index: index.xml
>> ===================================================================
>> --- index.xml (revision 1804261)
>> +++ index.xml (revision 1804262)
>> @@ -34,7 +34,7 @@
>> simply the repository of the needed information. Once a PMC
>> directly
>> checks-in a filled-out short form, the Incubator PMC will need to
>> approve the paper work after which point the receiving PMC is
>> free to
>> - import the code. <strong>Note</strong> that only lazy concensus
>> is
>> + import the code. <strong>Note</strong> that only lazy consensus
>> is
>> required. The <a href='ip-clearance-template.html'>IP clearance
>> template</a>
>> contains more details of this process.</p>
>> <p>For new IP clearance forms, start with our XML <a
>>
>>
>> Craig L Russell
>> clr@apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Updating ip-clearance web site
Posted by "John D. Ament" <jo...@apache.org>.
From that page:
Commits to the git repo trigger builds automatically, and the website
builds daily for other changes.
Basically, I don't have a way yet to trigger a build on change to either
repo. I do think I have a way though, need to switch the job to multiple
SCMs and that should work.
So for now, please login to Jenkins and trigger it, otherwise wait for the
nightly build.
John
On Sun, Aug 6, 2017 at 6:52 PM Craig Russell <ap...@gmail.com> wrote:
> Can anyone here tell me what the life cycle is for ip-clearance?
>
> The guidelines at https://incubator.apache.org/guides/website.html say
> that ip-clearance is maintained in svn.
>
> The web page has a typo:
> https://incubator.apache.org/ip-clearance/index.html (search for
> "concensus")
>
> So I corrected the typo in index.xml and committed it. [1]
>
> But the change has not shown up on the web site after several hours.
>
> What happens now? Is the process to publish it documented anywhere?
>
> Thanks,
>
> Craig
>
> [1]
> ------------------------------------------------------------------------
> r1804262 | clr | 2017-08-06 12:24:38 -0700 (Sun, 06 Aug 2017) | 1 line
>
> Fix typo in ip-clearance
>
> Index: index.xml
> ===================================================================
> --- index.xml (revision 1804261)
> +++ index.xml (revision 1804262)
> @@ -34,7 +34,7 @@
> simply the repository of the needed information. Once a PMC
> directly
> checks-in a filled-out short form, the Incubator PMC will need to
> approve the paper work after which point the receiving PMC is
> free to
> - import the code. <strong>Note</strong> that only lazy concensus
> is
> + import the code. <strong>Note</strong> that only lazy consensus
> is
> required. The <a href='ip-clearance-template.html'>IP clearance
> template</a>
> contains more details of this process.</p>
> <p>For new IP clearance forms, start with our XML <a
>
>
> Craig L Russell
> clr@apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>