Re: [IMPORTANT] Board proposal on podling releases

2019-06-12 Thread Hen
On Sun, Jun 9, 2019 at 4:11 PM Justin Mclean 
wrote:

> Hi,
>
> > I agree with other respondents that 'serious' seems bad here. To me the
> > serious ones are the only ones they can't release with.
>
> So we just continue as is then? You have any suggests to what we change?
>

I don't think we're using the same word meanings.

I think that serious = release blocker; but I equally think there are very
few items that are serious.


>
> > ReleaseBlocking:  Has a LICENSE.  Legally permitted to release and
> complies
> > with the license via some mechanism.
>
> We currently allow releases that are not strictly legal. This would be a
> step backwards.
>
>
I'd love to hear some examples. I suspect they are all legal.

Speculating hypothetically:

* We should never make a release that we know there is some content in that
we explicitly do not have permission to publish.
* We should never make a release that we know contains content that is
criminal (for whatever that would mean).

Other than that... I'm not sure what else would come under 'all legal'
label.


> > GraduationBlocking:  Everything else; including complying with the
> license
> > via our preferred mechanism (i.e. we might want the MIT license text in
> our
> > LICENSE file, but would accept it being in the source header of the files
> > themselves).
>
> We currently allow podlings to graduate with some issues as longs as the
> PPMC is dealing with them. This would be a step backwards.
>
>
Yeah. We need a third category for "MehNotBlockingPleaseFix".


> > I don't see a need to go to the board on this :)
>
> If we don’t want to change anything - sure there's no need to go to the
> board.
>

I'd definitely like to see change. My feeling is that there's a lot we can
make that falls comfortably within the scope of the Incubator PMC. IIRC the
release policies came out of the Incubator; I don't recall there being a
request for the board to ratify them, but I might be failing to remember
something a decade+ ago :)


>
> >> issues have been fixed. The IPMC will add additional information to the
> > incubator DISCLAIMER to cover that podling release may not abide by all
> >
> > The IPMC? That sounds like a people scaling problem. The podling
> committee
> > should handle it.
>
> I mean just changing this page [1] , podlings can update their own
> disclaimers.
>

Gotya :)


>
> > "This release still has the following issues that will need to be
> resolved
> > before the Foo Project can graduate to an Apache vetted Top Level
> Project”
>
> What about unknown issues?
>

By that are you suggesting that the text implies a guarantee that those are
the only issues? (Otherwise I'm off into philosophy of whether the unknown
can exist when the only test makes it known :) ).

"The Foo Project have currently identified the following issues that will
need to be resolved before the project can graduate to an Apache vetted Top
Level Project”

Any better?


> > Are the board lawyers? :) Until you have a well-defined list, I doubt
> > anything could be confirmed. I'd go with:  "Conceptually what you
> describe
> > could lead to a situation where a PPMC releases a project fully compliant
> > with the ASF's expectations. “
>
> I assume you mean “not fully compliant”?
>

Nope.

I was being defensive in my broad statements. For the given question; sure,
someone might manage a perfect release someday :)

Hen


Re: [IMPORTANT] Board proposal on podling releases

2019-06-12 Thread Justin Mclean
Hi,

Given we didn’t have consensus I’ve removed the proposal [1] and submitted the 
report to the board.[2] I’ve added further commentary about this thread. 
Feedback, as always welcome, I’ve tried to give an overview of the situation 
and actions going forward, but I may of missed something and it may not the the 
whole picture or how any individual IPMC member see it.

Thanks,
Justin

1. https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
2. https://whimsy.apache.org/board/agenda/2019-06-19/Incubator
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [DISCUSS] check LICENSE and NOTICE for Apache Tuweni

2019-06-12 Thread Justin Mclean
Hi,

Sorry there’s been a lot going on in the last week and I’ve not been able to 
double check it. I will have some time this weekend if someone else can’t look 
before then. I had a quick look and it seems fine. I not you mention cryto 
code, you may need to apply for an export license. [1]

Thanks,
Justin

1. http://www.apache.org/licenses/exports/
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



Re: [DISCUSS] check LICENSE and NOTICE for Apache Tuweni

2019-06-12 Thread Antoine Toulme
I’m not sure what to do at this point. Should I make a new release candidate 
and hope for the best?

> On Jun 8, 2019, at 7:22 PM, Antoine Toulme  wrote:
> 
> Is there anything else I need to get looked at?
> 
>> On Jun 6, 2019, at 8:45 AM, Antoine Toulme  wrote:
>> 
>> Thanks Justin.
>> 
>>> On Jun 3, 2019, at 14:30, Justin Mclean  wrote:
>>> 
>>> Hi,
>>> 
 If that’s no trouble, I’d rather have the text inlined and in the LICENSE 
 file. Please let me know if that’s a problem.
>>> 
>>> No issue it can be done either way. I won’t be able to do a full check 
>>> until later this week, so hopefully someone else can review it.
>>> 
>>> Thanks,
>>> Justin
>>> -
>>> 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



ApacheCon North America 2019 Schedule Now Live!

2019-06-12 Thread Rich Bowen

Dear Apache Enthusiast,

We’re thrilled to announce the schedule for our upcoming conference, 
ApacheCon North America 2019, in Las Vegas, Nevada. See it now at 
https://www.apachecon.com/acna19/schedule.html  The event will be held 
September 9th through 12th at the Flamingo Hotel.  Register today at 
https://www.apachecon.com/acna19/register.html


Our schedule features keynotes by James Gosling, the father of Java; 
Samaira Mehta, founder and CEO of the Billion Kids Can Code project; and 
David Brin, noted science fiction author and futurist. And we’ll have a 
discussion panel featuring some of the founders of The Apache Software 
Foundation, talking about the past as well as their vision for the future.


ApacheCon is the flagship convention of the ASF, and features tracks 
curated by many of our project communities: Apache Drill, Apache Karaf, 
Big Data, TomcatCon, Apache Cloudstack, Integration, Apache Cassandra, 
Streaming, Geospatial software, Graph processing, Internet of Things, 
Community, Machine Learning, Apache Traffic Control, Apache Beam, 
Observability, OFBiz, and Mobile app development.


The Hackathon, which will run all day, every day, is the place to meet 
your project community, and get some serious work knocked out in a short 
focused time. The BarCamp is the place to discuss the topics that are 
important to you, with your colleagues, in an unconference format.


We offer financial assistance for travel and lodging for those who want 
to come to ApacheCon but are unable to afford it. Apply at 
http://apache.org/travel/ by June 21st to be considered for this.


If you’re unable to make it to North America, we’ll also be running 
ApacheCon Europe in Berlin in October. Details of that event are at 
https://aceu19.apachecon.com/


Follow us on Twitter - @ApacheCon - for all the latest updates. See you 
in Las Vegas!


Rich Bowen, VP Conferences, The ASF
rbo...@apache.org
http://apachecon.com/

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



[IP CLEARANCE] ServiceComb Toolkit project contribution

2019-06-12 Thread Willem Jiang
Hi Incubator PMC,

The TLP Apache ServiceComb has been donated code for a toolkit, being
referred to as `servicecomb-toolkit`[1], old hostsd at MaBin's
personal repo[2].

This is the formal request for IP clearance to be checked as per [3].
The donated code can be found at [4] .

Please check the ip-clearance filed here[5] for more information.
The PMC has voted and passed to accept this donation.
The ICLA of major contributors, Bin Ma and Lisen Sun have been filed
before.
The SGA from Huawei has been filed.

Please vote to approve this contribution.

This majority vote is open for at least 72 hours and as usual lazy
consensus applies.

[1]https://github.com/apache/servicecomb-toolkit
[2]https://github.com/MabinGo/toolkit
[3]https://incubator.apache.org/ip-clearance/ip-clearance-template.html#form-filling
[4]https://issues.apache.org/jira/browse/INCUBATOR-239
[5]https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html

Willem Jiang

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



[jira] [Updated] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-12 Thread Willem Jiang (JIRA)


 [ 
https://issues.apache.org/jira/browse/INCUBATOR-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Willem Jiang updated INCUBATOR-239:
---
Attachment: servicecomb-toolkit.zip

> IP clearance for ServiceComb Toolkit
> 
>
> Key: INCUBATOR-239
> URL: https://issues.apache.org/jira/browse/INCUBATOR-239
> Project: Incubator
>  Issue Type: Task
>Reporter: Willem Jiang
>Priority: Major
> Attachments: servicecomb-toolkit.zip
>
>
> Mabin is contributing the Toolkit to Apache ServiceComb.
> The clearance tasks are in progress and recorded at: 
> https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html
> This issue is partly to track that and primarily to provide an official 
> record of the code drop contribution. The contributed code is attached to 
> this issue as toolkit-master.zip
> md5sum toolkit-master.zip
> MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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



[jira] [Created] (INCUBATOR-239) IP clearance for ServiceComb Toolkit

2019-06-12 Thread Willem Jiang (JIRA)
Willem Jiang created INCUBATOR-239:
--

 Summary: IP clearance for ServiceComb Toolkit
 Key: INCUBATOR-239
 URL: https://issues.apache.org/jira/browse/INCUBATOR-239
 Project: Incubator
  Issue Type: Task
Reporter: Willem Jiang


Mabin is contributing the Toolkit to Apache ServiceComb.

The clearance tasks are in progress and recorded at: 
https://incubator.apache.org/ip-clearance/servicecomb-toolkit.html

This issue is partly to track that and primarily to provide an official record 
of the code drop contribution. The contributed code is attached to this issue 
as toolkit-master.zip

md5sum toolkit-master.zip

MD5 (toolkit-master.zip) = 8bbf00a59e0476192d3dced20e2565ef





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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