Re: Wiki conflict for March report

[Mark Thomas]

On 07/03/18 01:55, John D. Ament wrote:
> Thanks Mark.  I went through the changes from when the conflict was
> introduced to now, I don't see anything missing.  I also privately pinged
> the culprit.

Thanks for the double check.

Mark


> 
> On Tue, Mar 6, 2018 at 7:34 PM Mark Thomas  wrote:
> 
>> All,
>>
>> I have just spent rather longer than I would have liked cleaning up a
>> conflicted edit in this month's report.
>>
>> I have two requests.
>>
>> 1. If you have submitted your report, please check I didn't accidentally
>> remove content. I tried hard not to but the report was a mess and
>> something might have slipped through the net.
>>
>> 2. If you are editing the report please, please, please take care not to
>> create edit conflicts and if you do manage to create please clean up
>> your own mess rather than leaving it for others to do it for you.
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wiki conflict for March report

[William Guo]

I am not sure why griffin report was updated to previous version, so I
just updated it manually for our report.

I guess other incubator sections might impact as well, please check
your own section in case some conflicts were not detected.


Thanks,
William
On behalf of Apache Griffin PPMC


On Wed, Mar 7, 2018 at 4:03 PM, Mark Thomas  wrote:
> On 07/03/18 01:55, John D. Ament wrote:
>> Thanks Mark.  I went through the changes from when the conflict was
>> introduced to now, I don't see anything missing.  I also privately pinged
>> the culprit.
>
> Thanks for the double check.
>
> Mark
>
>
>>
>> On Tue, Mar 6, 2018 at 7:34 PM Mark Thomas  wrote:
>>
>>> All,
>>>
>>> I have just spent rather longer than I would have liked cleaning up a
>>> conflicted edit in this month's report.
>>>
>>> I have two requests.
>>>
>>> 1. If you have submitted your report, please check I didn't accidentally
>>> remove content. I tried hard not to but the report was a mess and
>>> something might have slipped through the net.
>>>
>>> 2. If you are editing the report please, please, please take care not to
>>> create edit conflicts and if you do manage to create please clean up
>>> your own mess rather than leaving it for others to do it for you.
>>>
>>> Mark
>>>
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>>>
>>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache ServiceComb Service-Center (incubating) version 1.0.0-m1

[Mohammad Asif Siddiqui]

Hi All,  
  
We are Cancelling this vote as there are some issue we need to handle related 
to LICENSE and NOTICE file.  
  
We have fixed these issues and we will re-intiate a seperate VOTE Thread for 
second release candidate.  
  
Thanks all for your support.  
  
Regards  
Asif  

On 2018/02/28 13:25:19, Mohammad Asif Siddiqui 
 wrote: 
> Hello All,
> 
> This is a call for vote to release Apache ServiceComb Service-Center 
> (Incubating) version 1.0.0-m1.
> 
> Apache ServiceComb (Incubating) Community has voted and approved the release.
> 
> Vote Thread: 
> https://lists.apache.org/thread.html/b2d87628d019c069f478c56cadaf794112add210c504e3ac4c3056e5@%3Cdev.servicecomb.apache.org%3E
> 
> Result Thread: 
> https://lists.apache.org/thread.html/527a77d1467880602a7d679bd21d281b58fb365fa29b18a96a2a3676@%3Cdev.servicecomb.apache.org%3E
> 
> Release Notes: 
> https://github.com/apache/incubator-servicecomb-service-center/blob/master/docs/release/releaseNotes.md
> 
> Release Candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/incubator-servicecomb-service-center/1.0.0-m1/
> 
> Release Tag: 
> https://github.com/apache/incubator-servicecomb-service-center/releases/tag/1.0.0-m1
> 
> Release CommitID:  8d40fc3b10e99c9084a7b62504226007660ad6de
> 
> Keys to Verify the Release Candidate: 
> https://dist.apache.org/repos/dist/dev/incubator/servicecomb/KEYS
> 
> Guide to build the release from Source: 
> https://github.com/apache/incubator-servicecomb-service-center/tree/master/scripts/release
> 
> Voting will start now(Wednesday, February 28, 2018) and will remain open for 
> next 72 hours, Request all IPMC members to give their vote.
> 
> [ ] +1 Release this package as 1.0.0-m1.
> [ ] +0 No Opinion.
> [ ] -1 Do not release this package because...
> 
> Regards
> Asif
> 
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Bertrand Delacretaz]

Hi,

On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
> = Source and Intellectual Property Submission Plan =
> ...The Dr. Elephant source code is already licensed under
> Apache License Version 2.0. Going forward, we will continue to have
> all the contributions licensed directly to the Apache Software
> Foundation through our signed Individual Contributor License
> Agreements for all of the committers on the project

Note that whoever owns the code (LinkedIn IIUC) will have to submit a
Software Grant to donate it to the ASF:

https://www.apache.org/licenses/software-grant.txt

I think it's prudent to verify that the owners of the code are ready
to sign and submit that document, and mention that in the above
section, before entering incubation.

-Bertrand

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Wiki conflict for March report

[John D. Ament]

William,

You may want to circle back on your dev list.  It seems that someone else
posted the report [1].

John

[1]:
https://lists.apache.org/thread.html/7f4f07379a98f2a51613a8704a8b0da9b359dfacd7a117b55d335cab@%3Ccvs.incubator.apache.org%3E


On Wed, Mar 7, 2018 at 3:44 AM William Guo  wrote:

> I am not sure why griffin report was updated to previous version, so I
> just updated it manually for our report.
>
> I guess other incubator sections might impact as well, please check
> your own section in case some conflicts were not detected.
>
>
> Thanks,
> William
> On behalf of Apache Griffin PPMC
>
>
> On Wed, Mar 7, 2018 at 4:03 PM, Mark Thomas  wrote:
> > On 07/03/18 01:55, John D. Ament wrote:
> >> Thanks Mark.  I went through the changes from when the conflict was
> >> introduced to now, I don't see anything missing.  I also privately
> pinged
> >> the culprit.
> >
> > Thanks for the double check.
> >
> > Mark
> >
> >
> >>
> >> On Tue, Mar 6, 2018 at 7:34 PM Mark Thomas  wrote:
> >>
> >>> All,
> >>>
> >>> I have just spent rather longer than I would have liked cleaning up a
> >>> conflicted edit in this month's report.
> >>>
> >>> I have two requests.
> >>>
> >>> 1. If you have submitted your report, please check I didn't
> accidentally
> >>> remove content. I tried hard not to but the report was a mess and
> >>> something might have slipped through the net.
> >>>
> >>> 2. If you are editing the report please, please, please take care not
> to
> >>> create edit conflicts and if you do manage to create please clean up
> >>> your own mess rather than leaving it for others to do it for you.
> >>>
> >>> Mark
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>>
> >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: 404 issues

[John D. Ament]

.htaccess support should still work.  I would recommend following up with
infra if you're seeing something not quite right.

John

On Wed, Mar 7, 2018 at 1:54 AM Hen  wrote:

> Apologies for my rustiness :(
>
> Are we still able to manage a mod_rewrite configuration per project, or did
> that go away?
>
> Thanks,
>
> Hen
>
> -- Forwarded message --
> From: Aaron Markham 
> Date: Mon, Mar 5, 2018 at 3:54 PM
> Subject: 404 issues
> To: d...@mxnet.incubator.apache.org
>
>
> I've been notified by several parties about 404s for files that are
> now longer available on the site.
> https://github.com/apache/incubator-mxnet/issues/9917
>
> This page returns 404:
> https://mxnet.incubator.apache.org/api/python/module.html
>
> It was moved here:
> https://mxnet.incubator.apache.org/api/python/module/module.html
>
> There are many other examples of moved content. Some are temporarily
> "fixed" via adding a meta-refresh tag in the html source for the old
> pages. For example the meta tag is being used to redirect to faq, the
> new location for the how_to docs.
>
> It would seem a better solution for us is to use htaccess files and
> publish persistent redirects for the new location(s) of content.
>
> Do we have a way of pushing a config to the Apache infra to facilitate
> this? I think we'd need config access if we're to put up some custom
> 404 pages too (which would be nicer than what we have now.)
>
> Also, is there a good way to access the log files to get a better idea
> of the 404 situation?
>
> Cheers,
> Aaron
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
https://github.com/linkedin/dr-elephant/blob/master/LICENSE

Regards,
KAM

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
> > = Source and Intellectual Property Submission Plan =
> > ...The Dr. Elephant source code is already licensed under
> > Apache License Version 2.0. Going forward, we will continue to have
> > all the contributions licensed directly to the Apache Software
> > Foundation through our signed Individual Contributor License
> > Agreements for all of the committers on the project
>
> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
> Software Grant to donate it to the ASF:
>
> https://www.apache.org/licenses/software-grant.txt
>
> I think it's prudent to verify that the owners of the code are ready
> to sign and submit that document, and mention that in the above
> section, before entering incubation.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: 404 issues

[John D. Ament]

Infra would be the best to get these questions asked.

On Wed, Mar 7, 2018 at 9:52 AM Aaron Markham 
wrote:

> Ah ok thanks! We will try it out.
> Regarding log access or reporting on logs, is that available? Would like
> some more capability on spotting 404s, and doing reverse dns reporting so
> we can track organization level traffic.
>
> Cheers,
> Aaron
>
> On Mar 7, 2018 04:13, "John D. Ament"  wrote:
>
>> .htaccess support should still work.  I would recommend following up with
>> infra if you're seeing something not quite right.
>>
>> John
>>
>> On Wed, Mar 7, 2018 at 1:54 AM Hen  wrote:
>>
>>> Apologies for my rustiness :(
>>>
>>> Are we still able to manage a mod_rewrite configuration per project, or
>>> did
>>> that go away?
>>>
>>> Thanks,
>>>
>>> Hen
>>>
>>> -- Forwarded message --
>>> From: Aaron Markham 
>>> Date: Mon, Mar 5, 2018 at 3:54 PM
>>> Subject: 404 issues
>>> To: d...@mxnet.incubator.apache.org
>>>
>>>
>>> I've been notified by several parties about 404s for files that are
>>> now longer available on the site.
>>> https://github.com/apache/incubator-mxnet/issues/9917
>>>
>>> This page returns 404:
>>> https://mxnet.incubator.apache.org/api/python/module.html
>>>
>>> It was moved here:
>>> https://mxnet.incubator.apache.org/api/python/module/module.html
>>>
>>> There are many other examples of moved content. Some are temporarily
>>> "fixed" via adding a meta-refresh tag in the html source for the old
>>> pages. For example the meta tag is being used to redirect to faq, the
>>> new location for the how_to docs.
>>>
>>> It would seem a better solution for us is to use htaccess files and
>>> publish persistent redirects for the new location(s) of content.
>>>
>>> Do we have a way of pushing a config to the Apache infra to facilitate
>>> this? I think we'd need config access if we're to put up some custom
>>> 404 pages too (which would be nicer than what we have now.)
>>>
>>> Also, is there a good way to access the log files to get a better idea
>>> of the 404 situation?
>>>
>>> Cheers,
>>> Aaron
>>>
>>

Re: 404 issues

[Aaron Markham]

Ah ok thanks! We will try it out.
Regarding log access or reporting on logs, is that available? Would like
some more capability on spotting 404s, and doing reverse dns reporting so
we can track organization level traffic.

Cheers,
Aaron

On Mar 7, 2018 04:13, "John D. Ament"  wrote:

> .htaccess support should still work.  I would recommend following up with
> infra if you're seeing something not quite right.
>
> John
>
> On Wed, Mar 7, 2018 at 1:54 AM Hen  wrote:
>
>> Apologies for my rustiness :(
>>
>> Are we still able to manage a mod_rewrite configuration per project, or
>> did
>> that go away?
>>
>> Thanks,
>>
>> Hen
>>
>> -- Forwarded message --
>> From: Aaron Markham 
>> Date: Mon, Mar 5, 2018 at 3:54 PM
>> Subject: 404 issues
>> To: d...@mxnet.incubator.apache.org
>>
>>
>> I've been notified by several parties about 404s for files that are
>> now longer available on the site.
>> https://github.com/apache/incubator-mxnet/issues/9917
>>
>> This page returns 404:
>> https://mxnet.incubator.apache.org/api/python/module.html
>>
>> It was moved here:
>> https://mxnet.incubator.apache.org/api/python/module/module.html
>>
>> There are many other examples of moved content. Some are temporarily
>> "fixed" via adding a meta-refresh tag in the html source for the old
>> pages. For example the meta tag is being used to redirect to faq, the
>> new location for the how_to docs.
>>
>> It would seem a better solution for us is to use htaccess files and
>> publish persistent redirects for the new location(s) of content.
>>
>> Do we have a way of pushing a config to the Apache infra to facilitate
>> this? I think we'd need config access if we're to put up some custom
>> 404 pages too (which would be nicer than what we have now.)
>>
>> Also, is there a good way to access the log files to get a better idea
>> of the 404 situation?
>>
>> Cheers,
>> Aaron
>>
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Craig Russell]

If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is part of 
the incubation process, although as Bertrand notes, it's good to know ahead of 
time whether all of the current owners of the code are willing to grant an 
explicit license to Apache. 

Please see http://www.apache.org/licenses/#provenance for details.

If Dr. Elephant is only *used* as a dependency by an Apache project, no SGA is 
needed.

Craig

> On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail  wrote:
> 
> I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
> https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> 
> Regards,
> KAM
> 
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> 
> On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
> 
>> Hi,
>> 
>> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
>>> = Source and Intellectual Property Submission Plan =
>>> ...The Dr. Elephant source code is already licensed under
>>> Apache License Version 2.0. Going forward, we will continue to have
>>> all the contributions licensed directly to the Apache Software
>>> Foundation through our signed Individual Contributor License
>>> Agreements for all of the committers on the project
>> 
>> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
>> Software Grant to donate it to the ASF:
>> 
>> https://www.apache.org/licenses/software-grant.txt
>> 
>> I think it's prudent to verify that the owners of the code are ready
>> to sign and submit that document, and mention that in the above
>> section, before entering incubation.
>> 
>> -Bertrand
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Craig Russell]

Also note that if rights to Dr. Elephant are completely owned by LinkedIn, 
either an SGA or CCLA with Dr. Elephant named in Schedule B can be used.

Craig

> On Mar 7, 2018, at 10:55 AM, Craig Russell  wrote:
> 
> If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is part of 
> the incubation process, although as Bertrand notes, it's good to know ahead 
> of time whether all of the current owners of the code are willing to grant an 
> explicit license to Apache. 
> 
> Please see http://www.apache.org/licenses/#provenance for details.
> 
> If Dr. Elephant is only *used* as a dependency by an Apache project, no SGA 
> is needed.
> 
> Craig
> 
>> On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail  wrote:
>> 
>> I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
>> https://github.com/linkedin/dr-elephant/blob/master/LICENSE
>> 
>> Regards,
>> KAM
>> 
>> --
>> Kevin A. McGrail
>> Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> 
>> On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
>> bdelacre...@codeconsult.ch> wrote:
>> 
>>> Hi,
>>> 
>>> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
 = Source and Intellectual Property Submission Plan =
 ...The Dr. Elephant source code is already licensed under
 Apache License Version 2.0. Going forward, we will continue to have
 all the contributions licensed directly to the Apache Software
 Foundation through our signed Individual Contributor License
 Agreements for all of the committers on the project
>>> 
>>> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
>>> Software Grant to donate it to the ASF:
>>> 
>>> https://www.apache.org/licenses/software-grant.txt
>>> 
>>> I think it's prudent to verify that the owners of the code are ready
>>> to sign and submit that document, and mention that in the above
>>> section, before entering incubation.
>>> 
>>> -Bertrand
>>> 
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>> 
>>> 
> 
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
> 

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

Fair enough but it would be procedural not legal.  Who would sign said
SGA?  LI or representatives of the GH project?

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell  wrote:

> If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is part
> of the incubation process, although as Bertrand notes, it's good to know
> ahead of time whether all of the current owners of the code are willing to
> grant an explicit license to Apache.
>
> Please see http://www.apache.org/licenses/#provenance for details.
>
> If Dr. Elephant is only *used* as a dependency by an Apache project, no
> SGA is needed.
>
> Craig
>
> > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> wrote:
> >
> > I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
> > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> >
> > Regards,
> > KAM
> >
> > --
> > Kevin A. McGrail
> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> >> Hi,
> >>
> >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
> >>> = Source and Intellectual Property Submission Plan =
> >>> ...The Dr. Elephant source code is already licensed under
> >>> Apache License Version 2.0. Going forward, we will continue to have
> >>> all the contributions licensed directly to the Apache Software
> >>> Foundation through our signed Individual Contributor License
> >>> Agreements for all of the committers on the project
> >>
> >> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
> >> Software Grant to donate it to the ASF:
> >>
> >> https://www.apache.org/licenses/software-grant.txt
> >>
> >> I think it's prudent to verify that the owners of the code are ready
> >> to sign and submit that document, and mention that in the above
> >> section, before entering incubation.
> >>
> >> -Bertrand
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[John D. Ament]

On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail  wrote:

> Fair enough but it would be procedural not legal.  Who would sign said
> SGA?  LI or representatives of the GH project?
>

LinkedIn.  And it is a legal need.  Right now, the source files have
Copyright LinkedIn on them.  The SGA grants us the ability to remove that
copyright header.  The CCLA would allow the individual contributors to
submit the code to us with the appropriate header.  Hence why either works
in this case.


>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
>
> On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
> wrote:
>
> > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is part
> > of the incubation process, although as Bertrand notes, it's good to know
> > ahead of time whether all of the current owners of the code are willing
> to
> > grant an explicit license to Apache.
> >
> > Please see http://www.apache.org/licenses/#provenance for details.
> >
> > If Dr. Elephant is only *used* as a dependency by an Apache project, no
> > SGA is needed.
> >
> > Craig
> >
> > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> > wrote:
> > >
> > > I do not believe an SGA is needed as Dr. Elephant is licensed under
> ASF.
> > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> > >
> > > Regards,
> > > KAM
> > >
> > > --
> > > Kevin A. McGrail
> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> > >
> > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > > bdelacre...@codeconsult.ch> wrote:
> > >
> > >> Hi,
> > >>
> > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
> wrote:
> > >>> = Source and Intellectual Property Submission Plan =
> > >>> ...The Dr. Elephant source code is already licensed under
> > >>> Apache License Version 2.0. Going forward, we will continue to have
> > >>> all the contributions licensed directly to the Apache Software
> > >>> Foundation through our signed Individual Contributor License
> > >>> Agreements for all of the committers on the project
> > >>
> > >> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
> > >> Software Grant to donate it to the ASF:
> > >>
> > >> https://www.apache.org/licenses/software-grant.txt
> > >>
> > >> I think it's prudent to verify that the owners of the code are ready
> > >> to sign and submit that document, and mention that in the above
> > >> section, before entering incubation.
> > >>
> > >> -Bertrand
> > >>
> > >> -
> > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > >>
> > >>
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > c...@apache.org http://db.apache.org/jdo
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

Sorry, I missed the copyright and checked only the LICENSE.  Agree
completely with you and Craig an SGA is needed.

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament  wrote:

> On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
> wrote:
>
> > Fair enough but it would be procedural not legal.  Who would sign said
> > SGA?  LI or representatives of the GH project?
> >
>
> LinkedIn.  And it is a legal need.  Right now, the source files have
> Copyright LinkedIn on them.  The SGA grants us the ability to remove that
> copyright header.  The CCLA would allow the individual contributors to
> submit the code to us with the appropriate header.  Hence why either works
> in this case.
>
>
> >
> > --
> > Kevin A. McGrail
> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> >
> > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
> > wrote:
> >
> > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
> part
> > > of the incubation process, although as Bertrand notes, it's good to
> know
> > > ahead of time whether all of the current owners of the code are willing
> > to
> > > grant an explicit license to Apache.
> > >
> > > Please see http://www.apache.org/licenses/#provenance for details.
> > >
> > > If Dr. Elephant is only *used* as a dependency by an Apache project, no
> > > SGA is needed.
> > >
> > > Craig
> > >
> > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> > > wrote:
> > > >
> > > > I do not believe an SGA is needed as Dr. Elephant is licensed under
> > ASF.
> > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> > > >
> > > > Regards,
> > > > KAM
> > > >
> > > > --
> > > > Kevin A. McGrail
> > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > > Chair Emeritus Apache SpamAssassin Project
> > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> <(703)%20798-0171>
> > > >
> > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > > > bdelacre...@codeconsult.ch> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
> > wrote:
> > > >>> = Source and Intellectual Property Submission Plan =
> > > >>> ...The Dr. Elephant source code is already licensed under
> > > >>> Apache License Version 2.0. Going forward, we will continue to have
> > > >>> all the contributions licensed directly to the Apache Software
> > > >>> Foundation through our signed Individual Contributor License
> > > >>> Agreements for all of the committers on the project
> > > >>
> > > >> Note that whoever owns the code (LinkedIn IIUC) will have to submit
> a
> > > >> Software Grant to donate it to the ASF:
> > > >>
> > > >> https://www.apache.org/licenses/software-grant.txt
> > > >>
> > > >> I think it's prudent to verify that the owners of the code are ready
> > > >> to sign and submit that document, and mention that in the above
> > > >> section, before entering incubation.
> > > >>
> > > >> -Bertrand
> > > >>
> > > >> 
> -
> > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>
> > > >>
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > c...@apache.org http://db.apache.org/jdo
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Carl Steinbach]

Hi Roman,

Currently Dr. Elephant only supports YARN, but we are excited at
the prospect of extending it to support other schedulers likes Mesos.

- Carl

On Tue, Mar 6, 2018 at 3:33 PM, Roman Shaposhnik 
wrote:

> On Tue, Mar 6, 2018 at 3:17 PM, Mike Drob  wrote:
> > Why does Dr. Elephant make sense as a separate project instead of
> > contributing to Hadoop directly?
> >
> > What is the relationship between Dr. Elephant and the (now seemingly
> > defunct) Hadoop Vaidya?
>
> A different way to ask the same question would be: how closely is it tied
> to YARN as a scheduler? Does it support other schedulers (as in running
> Spark on Mesos for example)?
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Carl Steinbach]

I will followup with LinkedIn's legal team regarding getting an SGA. I don't
think this will be a problem since the same team has already reviewed Dr.
Elephant
and approved it for contribution to the Apache incubator.

- Carl

On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
wrote:

> Sorry, I missed the copyright and checked only the LICENSE.  Agree
> completely with you and Craig an SGA is needed.
>
> --
> Kevin A. McGrail
> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
> On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
> wrote:
>
> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
> > wrote:
> >
> > > Fair enough but it would be procedural not legal.  Who would sign said
> > > SGA?  LI or representatives of the GH project?
> > >
> >
> > LinkedIn.  And it is a legal need.  Right now, the source files have
> > Copyright LinkedIn on them.  The SGA grants us the ability to remove that
> > copyright header.  The CCLA would allow the individual contributors to
> > submit the code to us with the appropriate header.  Hence why either
> works
> > in this case.
> >
> >
> > >
> > > --
> > > Kevin A. McGrail
> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > Chair Emeritus Apache SpamAssassin Project
> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> > >
> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
> > > wrote:
> > >
> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
> > part
> > > > of the incubation process, although as Bertrand notes, it's good to
> > know
> > > > ahead of time whether all of the current owners of the code are
> willing
> > > to
> > > > grant an explicit license to Apache.
> > > >
> > > > Please see http://www.apache.org/licenses/#provenance for details.
> > > >
> > > > If Dr. Elephant is only *used* as a dependency by an Apache project,
> no
> > > > SGA is needed.
> > > >
> > > > Craig
> > > >
> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> > > > wrote:
> > > > >
> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed under
> > > ASF.
> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> > > > >
> > > > > Regards,
> > > > > KAM
> > > > >
> > > > > --
> > > > > Kevin A. McGrail
> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > > > Chair Emeritus Apache SpamAssassin Project
> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > <(703)%20798-0171>
> > > > >
> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > > > > bdelacre...@codeconsult.ch> wrote:
> > > > >
> > > > >> Hi,
> > > > >>
> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
> > > wrote:
> > > > >>> = Source and Intellectual Property Submission Plan =
> > > > >>> ...The Dr. Elephant source code is already licensed under
> > > > >>> Apache License Version 2.0. Going forward, we will continue to
> have
> > > > >>> all the contributions licensed directly to the Apache Software
> > > > >>> Foundation through our signed Individual Contributor License
> > > > >>> Agreements for all of the committers on the project
> > > > >>
> > > > >> Note that whoever owns the code (LinkedIn IIUC) will have to
> submit
> > a
> > > > >> Software Grant to donate it to the ASF:
> > > > >>
> > > > >> https://www.apache.org/licenses/software-grant.txt
> > > > >>
> > > > >> I think it's prudent to verify that the owners of the code are
> ready
> > > > >> to sign and submit that document, and mention that in the above
> > > > >> section, before entering incubation.
> > > > >>
> > > > >> -Bertrand
> > > > >>
> > > > >> 
> > -
> > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > >> For additional commands, e-mail: general-help@incubator.apache.
> org
> > > > >>
> > > > >>
> > > >
> > > > Craig L Russell
> > > > Secretary, Apache Software Foundation
> > > > c...@apache.org http://db.apache.org/jdo
> > > >
> > > >
> > > > 
> -
> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > > For additional commands, e-mail: general-h...@incubator.apache.org
> > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Carl Steinbach]

I also wanted to add that we are looking for more mentors.
Please email me if you are interested.

Thanks.

- Carl

On Wed, Mar 7, 2018 at 12:46 PM, Carl Steinbach  wrote:

> I will followup with LinkedIn's legal team regarding getting an SGA. I
> don't
> think this will be a problem since the same team has already reviewed Dr.
> Elephant
> and approved it for contribution to the Apache incubator.
>
> - Carl
>
> On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
> wrote:
>
>> Sorry, I missed the copyright and checked only the LICENSE.  Agree
>> completely with you and Craig an SGA is needed.
>>
>> --
>> Kevin A. McGrail
>> Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>> On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
>> wrote:
>>
>> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
>> > wrote:
>> >
>> > > Fair enough but it would be procedural not legal.  Who would sign said
>> > > SGA?  LI or representatives of the GH project?
>> > >
>> >
>> > LinkedIn.  And it is a legal need.  Right now, the source files have
>> > Copyright LinkedIn on them.  The SGA grants us the ability to remove
>> that
>> > copyright header.  The CCLA would allow the individual contributors to
>> > submit the code to us with the appropriate header.  Hence why either
>> works
>> > in this case.
>> >
>> >
>> > >
>> > > --
>> > > Kevin A. McGrail
>> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> > > Chair Emeritus Apache SpamAssassin Project
>> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> <(703)%20798-0171>
>> > >
>> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
>> > > wrote:
>> > >
>> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
>> > part
>> > > > of the incubation process, although as Bertrand notes, it's good to
>> > know
>> > > > ahead of time whether all of the current owners of the code are
>> willing
>> > > to
>> > > > grant an explicit license to Apache.
>> > > >
>> > > > Please see http://www.apache.org/licenses/#provenance for details.
>> > > >
>> > > > If Dr. Elephant is only *used* as a dependency by an Apache
>> project, no
>> > > > SGA is needed.
>> > > >
>> > > > Craig
>> > > >
>> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail > >
>> > > > wrote:
>> > > > >
>> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed
>> under
>> > > ASF.
>> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
>> > > > >
>> > > > > Regards,
>> > > > > KAM
>> > > > >
>> > > > > --
>> > > > > Kevin A. McGrail
>> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>> > > > > Chair Emeritus Apache SpamAssassin Project
>> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>> > <(703)%20798-0171>
>> > > > >
>> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
>> > > > > bdelacre...@codeconsult.ch> wrote:
>> > > > >
>> > > > >> Hi,
>> > > > >>
>> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
>> > > wrote:
>> > > > >>> = Source and Intellectual Property Submission Plan =
>> > > > >>> ...The Dr. Elephant source code is already licensed under
>> > > > >>> Apache License Version 2.0. Going forward, we will continue to
>> have
>> > > > >>> all the contributions licensed directly to the Apache Software
>> > > > >>> Foundation through our signed Individual Contributor License
>> > > > >>> Agreements for all of the committers on the project
>> > > > >>
>> > > > >> Note that whoever owns the code (LinkedIn IIUC) will have to
>> submit
>> > a
>> > > > >> Software Grant to donate it to the ASF:
>> > > > >>
>> > > > >> https://www.apache.org/licenses/software-grant.txt
>> > > > >>
>> > > > >> I think it's prudent to verify that the owners of the code are
>> ready
>> > > > >> to sign and submit that document, and mention that in the above
>> > > > >> section, before entering incubation.
>> > > > >>
>> > > > >> -Bertrand
>> > > > >>
>> > > > >> 
>> > -
>> > > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > > > >> For additional commands, e-mail: general-help@incubator.apache.
>> org
>> > > > >>
>> > > > >>
>> > > >
>> > > > Craig L Russell
>> > > > Secretary, Apache Software Foundation
>> > > > c...@apache.org http://db.apache.org/jdo
>> > > >
>> > > >
>> > > > 
>> -
>> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > > > For additional commands, e-mail: general-h...@incubator.apache.org
>> > > >
>> > > >
>> > >
>> >
>>
>
>

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Yi JIN]

Hi IPMC members,

I dropped MD5 checksum files from this candidate following Groeten's
comment. I'm now sure if we can continue this vote or I have to move back
to PPMC to generate another candidate.

Best,
Yi Jin (yjin)

On Wed, Mar 7, 2018 at 5:43 PM, Makoto Yui  wrote:

> Groeten,
>
> Thanks for clarification.
>
> Makoto
>
> 2018-03-07 15:27 GMT+09:00 Henk P. Penning :
> > On Wed, 7 Mar 2018, Makoto Yui wrote:
> >
> >> Date: Wed, 7 Mar 2018 07:15:15 +0100
> >> From: Makoto Yui 
> >> To: general@incubator.apache.org
> >> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
> >>
> >>> Recently the "release policy" [1] changed ; it (now) says :
> >>
> >>
> >> Good to know about it.
> >>
> >>> MUST supply at least one (SHA or MD5) checksum file,
> >>> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).
> >
> >
> >> This sounds confusing. Could be "MUST supply SHA checksum file(s)," (?)
> >
> >
> >   See RFC 2119 : https://www.ietf.org/rfc/rfc2119.txt
> >
> >   "MUST", "SHOULD", "SHOULD NOT" etc are technical terms.
> >   RFC 2119 explains what they mean.
> >
> >   Hint :
> >
> > MUST   == obligation ; a strict requirement
> > SHOULD == recommendation ;
> >
> >   Note : the policy can't say "MUST supply SHA checksum",
> >   because many projects have older releases in /dist/
> >   that are MD5-only ; under "new policy", that is
> >   frowned upon, but not forbidden.
> >
> >> Makoto
> >
> >
> >   Groeten,
> >
> >   HPP
> >
> >
> >    _
> > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> > Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> >
> >> 2018-03-07 14:58 GMT+09:00 Henk P. Penning :
> >>>
> >>> On Wed, 7 Mar 2018, Yi JIN wrote:
> >>>
>  Date: Wed, 7 Mar 2018 03:56:54 +0100
>  From: Yi JIN 
>  To: general@incubator.apache.org
>  Subject: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
> >>>
> >>>
> >>>
>  The artifacts can be downloaded here:
> 
> 
>  https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.
> 0-incubating.RC2/
> >>>
> >>>
> >>>
> >>>   Recently the "release policy" [1] changed ; it (now) says :
> >>>
> >>> ...
> >>> * SHOULD NOT supply a MD5 checksum file
> >>> ...
> >>>
> >>>   [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
> >>>
>  Yi Jin (yjin)
> >>>
> >>>
> >>>
> >>>   Groeten,
> >>>
> >>>   Henk Penning -- apache.org infrastructure ; dist & mirrors
> >>>
> >>>    _
> >>> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> >>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> >>> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> >>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
> >>>
> >>> -
> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >>> For additional commands, e-mail: general-h...@incubator.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> Makoto YUI 
> >> Research Engineer, Treasure Data, Inc.
> >> http://myui.github.io/
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
>
> --
> Makoto YUI 
> Research Engineer, Treasure Data, Inc.
> http://myui.github.io/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Podling setup

[Julian Hyde]

I’m a mentor of a new podling, Druid. I would like to help them get set up, 
e.g. create mailing lists, create git repos. I tried to use 
https://selfserve.apache.org/  for these, but it 
only allows officers (i.e. PMC chairs).

How is this supposed to work? Is the podling supposed to log INFRA tickets for 
everything? Am I supposed to nag the IPMC chair for everything? Or should I 
reach out to friends who happen to be PMC chairs?

The red tape is getting me down.

Julian

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Yi JIN]

Hi IPMC members,

I dropped MD5 checksum files from this candidate following Groeten's
comment. I'm not sure if we can continue this vote or I have to move back
to PPMC to prepare another candidate. Thanks.

Best,
Yi Jin (yjin)


On Thu, Mar 8, 2018 at 9:41 AM, Yi JIN  wrote:

> Hi IPMC members,
>
> I dropped MD5 checksum files from this candidate following Groeten's
> comment. I'm now sure if we can continue this vote or I have to move back
> to PPMC to generate another candidate.
>
> Best,
> Yi Jin (yjin)
>
> On Wed, Mar 7, 2018 at 5:43 PM, Makoto Yui  wrote:
>
>> Groeten,
>>
>> Thanks for clarification.
>>
>> Makoto
>>
>> 2018-03-07 15:27 GMT+09:00 Henk P. Penning :
>> > On Wed, 7 Mar 2018, Makoto Yui wrote:
>> >
>> >> Date: Wed, 7 Mar 2018 07:15:15 +0100
>> >> From: Makoto Yui 
>> >> To: general@incubator.apache.org
>> >> Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>> >>
>> >>> Recently the "release policy" [1] changed ; it (now) says :
>> >>
>> >>
>> >> Good to know about it.
>> >>
>> >>> MUST supply at least one (SHA or MD5) checksum file,
>> >>> SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).
>> >
>> >
>> >> This sounds confusing. Could be "MUST supply SHA checksum file(s)," (?)
>> >
>> >
>> >   See RFC 2119 : https://www.ietf.org/rfc/rfc2119.txt
>> >
>> >   "MUST", "SHOULD", "SHOULD NOT" etc are technical terms.
>> >   RFC 2119 explains what they mean.
>> >
>> >   Hint :
>> >
>> > MUST   == obligation ; a strict requirement
>> > SHOULD == recommendation ;
>> >
>> >   Note : the policy can't say "MUST supply SHA checksum",
>> >   because many projects have older releases in /dist/
>> >   that are MD5-only ; under "new policy", that is
>> >   frowned upon, but not forbidden.
>> >
>> >> Makoto
>> >
>> >
>> >   Groeten,
>> >
>> >   HPP
>> >
>> >
>> >    _
>> > Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> > Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> > Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> > http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>> >
>> >> 2018-03-07 14:58 GMT+09:00 Henk P. Penning :
>> >>>
>> >>> On Wed, 7 Mar 2018, Yi JIN wrote:
>> >>>
>>  Date: Wed, 7 Mar 2018 03:56:54 +0100
>>  From: Yi JIN 
>>  To: general@incubator.apache.org
>>  Subject: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release
>> >>>
>> >>>
>> >>>
>>  The artifacts can be downloaded here:
>> 
>> 
>>  https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.
>> 0-incubating.RC2/
>> >>>
>> >>>
>> >>>
>> >>>   Recently the "release policy" [1] changed ; it (now) says :
>> >>>
>> >>> ...
>> >>> * SHOULD NOT supply a MD5 checksum file
>> >>> ...
>> >>>
>> >>>   [1] https://www.apache.org/dev/release-distribution#sigs-and-sums
>> >>>
>>  Yi Jin (yjin)
>> >>>
>> >>>
>> >>>
>> >>>   Groeten,
>> >>>
>> >>>   Henk Penning -- apache.org infrastructure ; dist & mirrors
>> >>>
>> >>>    _
>> >>> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
>> >>> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
>> >>> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
>> >>> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >>> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Makoto YUI 
>> >> Research Engineer, Treasure Data, Inc.
>> >> http://myui.github.io/
>> >>
>> >> -
>> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>
>> >>
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>>
>>
>> --
>> Makoto YUI 
>> Research Engineer, Treasure Data, Inc.
>> http://myui.github.io/
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>

Re: Wiki conflict for March report

[William Guo]

John,

Thanks for clearing the issue.

William
On behalf of Apache Griffin PPMC

On Wed, Mar 7, 2018 at 8:11 PM, John D. Ament  wrote:
> William,
>
> You may want to circle back on your dev list.  It seems that someone else
> posted the report [1].
>
> John
>
> [1]:
> https://lists.apache.org/thread.html/7f4f07379a98f2a51613a8704a8b0da9b359dfacd7a117b55d335cab@%3Ccvs.incubator.apache.org%3E
>
>
> On Wed, Mar 7, 2018 at 3:44 AM William Guo  wrote:
>
>> I am not sure why griffin report was updated to previous version, so I
>> just updated it manually for our report.
>>
>> I guess other incubator sections might impact as well, please check
>> your own section in case some conflicts were not detected.
>>
>>
>> Thanks,
>> William
>> On behalf of Apache Griffin PPMC
>>
>>
>> On Wed, Mar 7, 2018 at 4:03 PM, Mark Thomas  wrote:
>> > On 07/03/18 01:55, John D. Ament wrote:
>> >> Thanks Mark.  I went through the changes from when the conflict was
>> >> introduced to now, I don't see anything missing.  I also privately
>> pinged
>> >> the culprit.
>> >
>> > Thanks for the double check.
>> >
>> > Mark
>> >
>> >
>> >>
>> >> On Tue, Mar 6, 2018 at 7:34 PM Mark Thomas  wrote:
>> >>
>> >>> All,
>> >>>
>> >>> I have just spent rather longer than I would have liked cleaning up a
>> >>> conflicted edit in this month's report.
>> >>>
>> >>> I have two requests.
>> >>>
>> >>> 1. If you have submitted your report, please check I didn't
>> accidentally
>> >>> remove content. I tried hard not to but the report was a mess and
>> >>> something might have slipped through the net.
>> >>>
>> >>> 2. If you are editing the report please, please, please take care not
>> to
>> >>> create edit conflicts and if you do manage to create please clean up
>> >>> your own mess rather than leaving it for others to do it for you.
>> >>>
>> >>> Mark
>> >>>
>> >>> -
>> >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> >>> For additional commands, e-mail: general-h...@incubator.apache.org
>> >>>
>> >>>
>> >>
>> >
>> >
>> > -
>> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> > For additional commands, e-mail: general-h...@incubator.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

[Henk P. Penning]

On Thu, 8 Mar 2018, Yi JIN wrote:


Date: Thu, 8 Mar 2018 00:34:02 +0100
From: Yi JIN 
To: general@incubator.apache.org
Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release

Hi IPMC members,

I dropped MD5 checksum files from this candidate following Groeten's
comment. I'm not sure if we can continue this vote or I have to move back
to PPMC to prepare another candidate. Thanks.


  just continue the vote.


Yi Jin (yjin)


  Regards,

  Henk Penning


On Thu, Mar 8, 2018 at 9:41 AM, Yi JIN  wrote:


Hi IPMC members,

I dropped MD5 checksum files from this candidate following Groeten's
comment. I'm now sure if we can continue this vote or I have to move back
to PPMC to generate another candidate.

Best,
Yi Jin (yjin)

On Wed, Mar 7, 2018 at 5:43 PM, Makoto Yui  wrote:


Groeten,

Thanks for clarification.

Makoto

2018-03-07 15:27 GMT+09:00 Henk P. Penning :

On Wed, 7 Mar 2018, Makoto Yui wrote:


Date: Wed, 7 Mar 2018 07:15:15 +0100
From: Makoto Yui 
To: general@incubator.apache.org
Subject: Re: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release


Recently the "release policy" [1] changed ; it (now) says :



Good to know about it.


MUST supply at least one (SHA or MD5) checksum file,
SHOULD NOT supply a MD5 checksum file (because MD5 is too broken).




This sounds confusing. Could be "MUST supply SHA checksum file(s)," (?)



  See RFC 2119 : https://www.ietf.org/rfc/rfc2119.txt

  "MUST", "SHOULD", "SHOULD NOT" etc are technical terms.
  RFC 2119 explains what they mean.

  Hint :

MUST   == obligation ; a strict requirement
SHOULD == recommendation ;

  Note : the policy can't say "MUST supply SHA checksum",
  because many projects have older releases in /dist/
  that are MD5-only ; under "new policy", that is
  frowned upon, but not forbidden.


Makoto



  Groeten,

  HPP


   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/


2018-03-07 14:58 GMT+09:00 Henk P. Penning :


On Wed, 7 Mar 2018, Yi JIN wrote:


Date: Wed, 7 Mar 2018 03:56:54 +0100
From: Yi JIN 
To: general@incubator.apache.org
Subject: [VOTE]: Apache HAWQ 2.3.0.0-incubating Release





The artifacts can be downloaded here:


https://dist.apache.org/repos/dist/dev/incubator/hawq/2.3.0.

0-incubating.RC2/




  Recently the "release policy" [1] changed ; it (now) says :

...
* SHOULD NOT supply a MD5 checksum file
...

  [1] https://www.apache.org/dev/release-distribution#sigs-and-sums


Yi Jin (yjin)




  Groeten,

  Henk Penning -- apache.org infrastructure ; dist & mirrors

   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org





--
Makoto YUI 
Research Engineer, Treasure Data, Inc.
http://myui.github.io/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org





--
Makoto YUI 
Research Engineer, Treasure Data, Inc.
http://myui.github.io/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org








   _
Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Carl Steinbach]

Timothy Chen has volunteered to be a mentor. I have updated
the proposal on the wiki to reflect this.

Thanks Timothy!

- Carl

On Wed, Mar 7, 2018 at 12:47 PM, Carl Steinbach  wrote:

> I also wanted to add that we are looking for more mentors.
> Please email me if you are interested.
>
> Thanks.
>
> - Carl
>
> On Wed, Mar 7, 2018 at 12:46 PM, Carl Steinbach  wrote:
>
>> I will followup with LinkedIn's legal team regarding getting an SGA. I
>> don't
>> think this will be a problem since the same team has already reviewed Dr.
>> Elephant
>> and approved it for contribution to the Apache incubator.
>>
>> - Carl
>>
>> On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail 
>> wrote:
>>
>>> Sorry, I missed the copyright and checked only the LICENSE.  Agree
>>> completely with you and Craig an SGA is needed.
>>>
>>> --
>>> Kevin A. McGrail
>>> Asst. Treasurer & VP Fundraising, Apache Software Foundation
>>> Chair Emeritus Apache SpamAssassin Project
>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>
>>> On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament 
>>> wrote:
>>>
>>> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
>>> > wrote:
>>> >
>>> > > Fair enough but it would be procedural not legal.  Who would sign
>>> said
>>> > > SGA?  LI or representatives of the GH project?
>>> > >
>>> >
>>> > LinkedIn.  And it is a legal need.  Right now, the source files have
>>> > Copyright LinkedIn on them.  The SGA grants us the ability to remove
>>> that
>>> > copyright header.  The CCLA would allow the individual contributors to
>>> > submit the code to us with the appropriate header.  Hence why either
>>> works
>>> > in this case.
>>> >
>>> >
>>> > >
>>> > > --
>>> > > Kevin A. McGrail
>>> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>>> > > Chair Emeritus Apache SpamAssassin Project
>>> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>> <(703)%20798-0171>
>>> > >
>>> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
>>> > > wrote:
>>> > >
>>> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This
>>> is
>>> > part
>>> > > > of the incubation process, although as Bertrand notes, it's good to
>>> > know
>>> > > > ahead of time whether all of the current owners of the code are
>>> willing
>>> > > to
>>> > > > grant an explicit license to Apache.
>>> > > >
>>> > > > Please see http://www.apache.org/licenses/#provenance for details.
>>> > > >
>>> > > > If Dr. Elephant is only *used* as a dependency by an Apache
>>> project, no
>>> > > > SGA is needed.
>>> > > >
>>> > > > Craig
>>> > > >
>>> > > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail <
>>> kmcgr...@apache.org>
>>> > > > wrote:
>>> > > > >
>>> > > > > I do not believe an SGA is needed as Dr. Elephant is licensed
>>> under
>>> > > ASF.
>>> > > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
>>> > > > >
>>> > > > > Regards,
>>> > > > > KAM
>>> > > > >
>>> > > > > --
>>> > > > > Kevin A. McGrail
>>> > > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
>>> > > > > Chair Emeritus Apache SpamAssassin Project
>>> > > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>> > <(703)%20798-0171>
>>> > > > >
>>> > > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
>>> > > > > bdelacre...@codeconsult.ch> wrote:
>>> > > > >
>>> > > > >> Hi,
>>> > > > >>
>>> > > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach >> >
>>> > > wrote:
>>> > > > >>> = Source and Intellectual Property Submission Plan =
>>> > > > >>> ...The Dr. Elephant source code is already licensed under
>>> > > > >>> Apache License Version 2.0. Going forward, we will continue to
>>> have
>>> > > > >>> all the contributions licensed directly to the Apache Software
>>> > > > >>> Foundation through our signed Individual Contributor License
>>> > > > >>> Agreements for all of the committers on the project
>>> > > > >>
>>> > > > >> Note that whoever owns the code (LinkedIn IIUC) will have to
>>> submit
>>> > a
>>> > > > >> Software Grant to donate it to the ASF:
>>> > > > >>
>>> > > > >> https://www.apache.org/licenses/software-grant.txt
>>> > > > >>
>>> > > > >> I think it's prudent to verify that the owners of the code are
>>> ready
>>> > > > >> to sign and submit that document, and mention that in the above
>>> > > > >> section, before entering incubation.
>>> > > > >>
>>> > > > >> -Bertrand
>>> > > > >>
>>> > > > >> 
>>> > -
>>> > > > >> 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
>>> > > > c...@apache.org http://db.apache.org/jdo
>>> > > >
>>> > > >
>>> > > > 
>>> -
>>> > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> > > > For additional c

Re: 404 issues

[Hen]

Thanks John. I'll go ask some "I used to know this honest" questions on
HipChat tomorrow :)

On Wed, Mar 7, 2018 at 8:06 AM, John D. Ament 
wrote:

> Infra would be the best to get these questions asked.
>
> On Wed, Mar 7, 2018 at 9:52 AM Aaron Markham 
> wrote:
>
> > Ah ok thanks! We will try it out.
> > Regarding log access or reporting on logs, is that available? Would like
> > some more capability on spotting 404s, and doing reverse dns reporting so
> > we can track organization level traffic.
> >
> > Cheers,
> > Aaron
> >
> > On Mar 7, 2018 04:13, "John D. Ament"  wrote:
> >
> >> .htaccess support should still work.  I would recommend following up
> with
> >> infra if you're seeing something not quite right.
> >>
> >> John
> >>
> >> On Wed, Mar 7, 2018 at 1:54 AM Hen  wrote:
> >>
> >>> Apologies for my rustiness :(
> >>>
> >>> Are we still able to manage a mod_rewrite configuration per project, or
> >>> did
> >>> that go away?
> >>>
> >>> Thanks,
> >>>
> >>> Hen
> >>>
> >>> -- Forwarded message --
> >>> From: Aaron Markham 
> >>> Date: Mon, Mar 5, 2018 at 3:54 PM
> >>> Subject: 404 issues
> >>> To: d...@mxnet.incubator.apache.org
> >>>
> >>>
> >>> I've been notified by several parties about 404s for files that are
> >>> now longer available on the site.
> >>> https://github.com/apache/incubator-mxnet/issues/9917
> >>>
> >>> This page returns 404:
> >>> https://mxnet.incubator.apache.org/api/python/module.html
> >>>
> >>> It was moved here:
> >>> https://mxnet.incubator.apache.org/api/python/module/module.html
> >>>
> >>> There are many other examples of moved content. Some are temporarily
> >>> "fixed" via adding a meta-refresh tag in the html source for the old
> >>> pages. For example the meta tag is being used to redirect to faq, the
> >>> new location for the how_to docs.
> >>>
> >>> It would seem a better solution for us is to use htaccess files and
> >>> publish persistent redirects for the new location(s) of content.
> >>>
> >>> Do we have a way of pushing a config to the Apache infra to facilitate
> >>> this? I think we'd need config access if we're to put up some custom
> >>> 404 pages too (which would be nicer than what we have now.)
> >>>
> >>> Also, is there a good way to access the log files to get a better idea
> >>> of the 404 situation?
> >>>
> >>> Cheers,
> >>> Aaron
> >>>
> >>
>