Re: LGPL dependency

Hey Jim, Thank you for asking. : o) Weex is still cutting the release. It's precisely because this can be time-consuming that they asked before they started. They'll bring it for a vote once they have it. Best, Myrle On Mon, Jul 1, 2019 at 6:19 PM Jim Jagielski wrote: > Myrle, did you get

Re: LGPL dependency

Thanks for your supporting. I will bring it to general@incubator when vote passed in weex@dev Best Regards, York Shen 申远 > 在 2019年7月2日，15:20，Myrle Krantz 写道： > > Hey Jim, > > Thank you for asking. : o) Weex is still cutting the release. It's > precisely because this can be time-consuming

Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

Hi, There were a couple of minor issue around branding. communication and releases brought up in the discussion on graduation, I believe most (if not all) of these have been sorted or in progress of being sorted. Would you mind posting a short summary of what the PPMC is going about these issue

Re: Podlings, the Incubator, relationships and Apache

Hey Alex, The Incubator plays a special role. We should be willing to take on some risks in the process of helping newer, or older projects adjust to us. But once those adjustments are complete, we should be able to expect TLP's to "color in the lines". If you believe that is impossible for you

Re: Podlings, the Incubator, relationships and Apache

> On Jul 1, 2019, at 1:45 AM, Alex Harui wrote: > > FWIW, I reconcile it as: > > Incubator is a PMC and must record a business decision to call something an > ASF release in order to place that release under the legal protection of the > ASF. ASF releases may have policy non-compliance iss

Re: Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

Justin Mclean wrote on 07/02/2019 05:53:06 AM: > > There were a couple of minor issue around branding. communication > and releases brought up in the discussion on graduation, I believe > most (if not all) of these have been sorted or in progress of being > sorted. Would you mind posting a short s

Re: Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

Hi - LGTM! Some comments inline: > On Jul 2, 2019, at 8:42 AM, David P Grove wrote: > > Justin Mclean wrote on 07/02/2019 05:53:06 AM: >> >> There were a couple of minor issue around branding. communication >> and releases brought up in the discussion on graduation, I believe >> most (if not

Re: New disclaimer text

Hi - > On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz > wrote: > > Hi, > > On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean > wrote: >> ...I put up suggested text changes for an incubator disclaimer here [1]... > > Basically just adding this, right? > >> Some of the project releas

Re: [Discuss] Graduate Apache OpenWhisk (incubating) as a TLP

I have been following some of the OpenWhisk traffic on the mailing list but mostly at arms length, so I thought I would have my first play writing a Groovy action this evening to see if the process would shed any light on the project's graduation readiness. The result (with kudos to Markus Thömmes

Re: New disclaimer text

Dave Fisher wrote on Tue, 02 Jul 2019 10:28 -0700: > > On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz > > wrote: > > > > Hi, > > > > On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean > > wrote: > >> ...I put up suggested text changes for an incubator disclaimer here [1]... > > > > Basically jus

New Project?

Hey Folks, I'm interested in submitting a project as a seedling and am looking exactly where to start. The project is already off the ground, being used by many, is stable, reasonably mature (it's in alpha release), open source, and already Apache licensed. I've been looking at a lot of resources

Re: New Project?

I'm a little unclear about the scope of the project here. This project looks more like a service, and I don't know of any ASF projects that exist to provide services outside the ASF. On Tue, 2 Jul 2019 at 14:28, Alejandro Caceres wrote: > > Hey Folks, > > I'm interested in submitting a project as

Re: New disclaimer text

On Tue, Jul 2, 2019 at 1:55 PM Daniel Shahaf wrote: > Dave Fisher wrote on Tue, 02 Jul 2019 10:28 -0700: > > > On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz < > bdelacre...@codeconsult.ch> wrote: > > > > > > Hi, > > > > > > On Sun, Jun 30, 2019 at 1:39 AM Justin Mclean < > jus...@classsoftware.

Re: New Project?

Hi Matt, Thanks for the response. You are sort of correct, I would say the end goal is a service - an open source engine that is able to grab and ingest this highly unstructured security information and turn it into something useful - then provide that back to the user in a few different forms. On

Re: New Project?

Hi, > Thanks for the response. You are sort of correct, I would say the end goal > is a service We do have a couple of project along those lines eg. pony mail and kibble,, so that may not be an issue. Is there an existing code base and a community using it? Thanks, Justin

Re: New Project?

Hi - To me you have two parts. One fits Apache and the other would need to be outside. (1) Open Source Software which is the library, service and CLI tools. This is something that an Apache Community could grow around and be governed in the Apache Way. This part can be incubated. (2) Open Dat

Re: Podlings, the Incubator, relationships and Apache

Jim said "Let's also recall that the origin genesis of the Incubator was NOT to provide legal oversight, but rather education and guidance into The Apache Way" I say... HEAR! HEAR! Get Outlook for Android From: Jim Jagielski Sent: Tuesday

Re: Podlings, the Incubator, relationships and Apache

All we need is a simple pivot back. This is the closest, easiest path. Prioritize and ease the acceptance of the Apache Way. Our current Disclaimer is enough. If governing in the way then the path to a PMC is eased. We need to assure that the lessons from all versions of the Incubator are cons

Re: Podlings, the Incubator, relationships and Apache

Hi, > Jim said "Let's also recall that the origin genesis of the Incubator was NOT > to provide legal oversight, but rather education and guidance into The Apache > Way” If you look at the history threads I posted the other day one was about “legal oversight” way back in 2004. Thanks, Justin

Re: Podlings, the Incubator, relationships and Apache

Hi, > Although not a "real" PMC, we do need to provide legal protection for each > PPMC and distributing releases is the time that most legal considerations > "kick in" as it were. So we need a clear "paper trail" of approvals for that > PPMC to enjoy the legal protection the foundation exists

Re: Podlings, the Incubator, relationships and Apache

On Wed, Jul 3, 2019 at 12:10 AM Justin Mclean wrote: >... > Hi, > > > Although not a "real" PMC, we do need to provide legal protection for > each PPMC and distributing releases is the time that most legal > considerations "kick in" as it were. So we need a Or we *don't* provide legal protectio

Re: Podlings, the Incubator, relationships and Apache

Hi, > Or we *don't* provide legal protections. That *is* what the disclaimer is > there for. For that to happen I think the disclaimer text would need to change, I’m assuming you don’t think that. Even so a DISCLAIMER doesn’t remove legal obligations. > I don't recall that advice. In fact, Rom

Re: Podlings, the Incubator, relationships and Apache

Hi, Of historical interest - “legal oversight” goes back to some to some the very first email about the incubator in 2003. Here's one [1] slightly later from Jim in 2005 who seemed to think back then legal aspects were important. Perhaps that's out of context, and you had to be there, it’s real