Re: New disclaimer text

Hi, > I think that the free-form section should also be generic, and refer to the > JIRA or github issues for the podling. Something like > > https://github.com/apache//issues or > https://issues.apache.org/jira/projects//issues There’s an issue with that is you pointing to something that

Re: New disclaimer text

I agree that the DISCLAIMER-WIP should refer to the status page, but the current disclaimer https://cwiki.apache.org/confluence/display/INCUBATOR/New+Incubator+Disclaimer also has a free-form section for a list of known issues. "What follows is a list of known issues the project is currently

Re: New disclaimer text

Hi, Seems a few people like DISCLAIMER-WIP and there no strong objection or opinions to other names, so let's go with that. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional

Re: New disclaimer text

+1 for: DISCLAIMER-PERMISSIVE or DISCLAIMER-WIP Virus-free. www.avast.com

Re: New disclaimer text

> 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 releases may not

Re: New disclaimer text

Hi, On Wed, Jul 17, 2019 at 8:06 AM Justin Mclean wrote: > - Keep the existing one called as it is... And have it mention the possible additional disclaimers, as DISCLAIMER-* maybe. >... Name the new one something like DISCLAIMER-PERMISSIVE, DISCLAIMER-ISSUES, > DISCLAIMER-INITIAL, or

Re: New disclaimer text

Hi, I don’t rally care what they are called but I would suggest that we use - Keep the existing one called as it is - Name the new one something like DISCLAIMER-PERMISSIVE, DISCLAIMER-ISSUES, DISCLAIMER-INITIAL, or DISCLAIMER-PROGRESS The name may be a bit long but I think it needs to clearly

Re: New disclaimer text

Very good point... I'm personally fine w/ anything. Let's avoid bike shedding :) > On Jul 15, 2019, at 11:07 AM, David Jencks wrote: > > To me, v2 implies an improvement over its predecessor and an expectation that > eventually it will universally replace said predecessor. > > Perhaps >

Re: New disclaimer text

To me, v2 implies an improvement over its predecessor and an expectation that eventually it will universally replace said predecessor. Perhaps DISCLAIMER-b.txt DISCLAIMER-x.txt might avoid this implication? David Jencks Sent from my iPhone > On Jul 15, 2019, at 7:40 AM, Jim Jagielski

Re: New disclaimer text

> On Jul 13, 2019, at 9:49 PM, Craig Russell wrote: > > DISCLAIMER.txt for the current standard disclaimer and some other name for > the new disclaimer. > This seems less confusing, I think. DISCLAIMERv2.txt for the other?

Re: New disclaimer text

+1 On Sat, Jul 13, 2019 at 10:44 AM Sheng Wu wrote: > +1 from me to have two disclaimers, chosen by podings. > > Also, +1 from me, the one they chosen should stay in website and > announcement. > > Sheng > > Justin Mclean 于2019年7月13日 周六上午9:37写道： > > > Hi, > > > > +1 Works for me. > > > > It

Re: New disclaimer text

Not good at naming stuff :) But I support to use different names. Sheng Wu Apache Skywalking, ShardingSphere, Zipkin > 在 2019年7月14日，上午9:49，Craig Russell 写道： > > It looks like we are closing on agreement to have (at least) two disclaimers. > Now we need to discuss naming. [1] > > Two big

Re: New disclaimer text

It looks like we are closing on agreement to have (at least) two disclaimers. Now we need to discuss naming. [1] Two big choices here: DISCLAIMER.txt for both versions of disclaimer; or DISCLAIMER.txt for the current standard disclaimer and some other name for the new disclaimer. If we

Re: New disclaimer text

Hi, > The language would be: > > “For the current status of this project through the Apache Incubator visit > http://incubator.apache.org/project/${podling}.html Understand you now I’ve added that to the wiki page. Thanks, Justin

Re: New disclaimer text

Sent from my iPhone > On Jul 12, 2019, at 7:32 PM, Justin Mclean wrote: > > HI, > >> +1 if as discussed earlier we enhance both disclaimers to include a link to >> the podling status page where the podling will provide the most up to date >> details. > > I think the text needs to refer

Re: New disclaimer text

HI, > +1 if as discussed earlier we enhance both disclaimers to include a link to > the podling status page where the podling will provide the most up to date > details. I think the text needs to refer to that release, while the latest is also useful, it if doesn’t include things that were in

Re: New disclaimer text

+1 if as discussed earlier we enhance both disclaimers to include a link to the podling status page where the podling will provide the most up to date details. We can discuss a new Git based status page in a separate thread. I’d like to change from the xml/secret yaml files in svn to a straight

Re: New disclaimer text

+1 from me to have two disclaimers, chosen by podings. Also, +1 from me, the one they chosen should stay in website and announcement. Sheng Justin Mclean 于2019年7月13日 周六上午9:37写道： > Hi, > > +1 Works for me. > > It will need to be made very clear to podlings that different rules apply > depending

Re: New disclaimer text

Hi, +1 Works for me. It will need to be made very clear to podlings that different rules apply depending on what disclaimer they have. Would this also please to the disclaimer on their web site and in announcement emails? Thanks, Justin

Re: New disclaimer text

Big +1! On Fri, Jul 12, 2019 at 4:08 PM Matt Sicker wrote: > > Agreed, this sounds like a great way to do this. As IPMC members reviewing > releases, you now have better guidelines on how to go about reviewing a > podling release. > > On Fri, Jul 12, 2019 at 17:59, Jim Jagielski wrote: > > >

Re: New disclaimer text

Agreed, this sounds like a great way to do this. As IPMC members reviewing releases, you now have better guidelines on how to go about reviewing a podling release. On Fri, Jul 12, 2019 at 17:59, Jim Jagielski wrote: > This is a great idea... +1 > > > On Jul 12, 2019, at 6:31 PM, Craig Russell

Re: New disclaimer text

This is a great idea... +1 > On Jul 12, 2019, at 6:31 PM, Craig Russell wrote: > > Hi, > > I understand I'm a bit late to this particular discussion, but perhaps we can > consider two different disclaimers that podlings can choose: > > The standard disclaimer that does not disclaim licensing

Re: New disclaimer text

Hi, I understand I'm a bit late to this particular discussion, but perhaps we can consider two different disclaimers that podlings can choose: The standard disclaimer that does not disclaim licensing issues; or, The proposed new disclaimer to be used by podlings' first releases until they

Re: New disclaimer text

Replies inline: > On Jul 12, 2019, at 3:49 AM, Justin Mclean wrote: > > Hi, > >> Adding an additional disclaimer that we may have known issues adds >> additional barriers to adoption and community growth. > > I think the question to be asked is does that add barries more than having to >

Re: New disclaimer text

> I think the question to be asked is does that add barries more than having to > have 100% compliant releases? Is this a current requirement that is written down somewhere and generally practiced? Am Fr., 12. Juli 2019 um 09:49 Uhr schrieb Justin Mclean : > > Hi, > > > Adding an additional

Re: New disclaimer text

Hi, > Adding an additional disclaimer that we may have known issues adds additional > barriers to adoption and community growth. I think the question to be asked is does that add barries more than having to have 100% compliant releases? I think the answer may depend on the podling. Have does

Re: New disclaimer text

Hi, I’m also a PPMC member (Apache Flagon). It seems the Incubator is at an inflection point—been tracking how different threads on general@ are capitulating on issues of identity and process. Gian’s points are SPOT on, but so are Justin’s. I have some reconciliatory thoughts and suggestions,

Re: New disclaimer text

Hi, > Speaking as a member of a currently-incubating project (Apache Druid) where > we have always strived to do releases with no known licensing issues, the > text sounds needlessly scary to downstream consumers. And that may be the problem with a one solution fits all process. It has been

Re: New disclaimer text

Hi, > What is the requirement for this disclaimer text change? > Is this coming from Legal? Or is this Incubator policy? The incubator wold like to make it easies for podlings to make releases, allowing realises with issues in them is a way of doing this. The legal committee has been involved

Re: New disclaimer text

My thought is that having a scary incubator warning text is the price to be paid for having an incubator release process that could allow releases with problems. The best solution to that is to graduate and get rid of the warning entirely. On Wed, Jul 10, 2019 at 9:50 AM Gian Merlino wrote:

Re: New disclaimer text

Speaking as a member of a currently-incubating project (Apache Druid) where we have always strived to do releases with no known licensing issues, the text sounds needlessly scary to downstream consumers. Especially this part: > If you are planning to incorporate this work into your >

Re: New disclaimer text

What is the requirement for this disclaimer text change? Is this coming from Legal? Or is this Incubator policy? Has this been decided on already or is this text suggestion to be used for a decision? J Am Mi., 10. Juli 2019 um 15:50 Uhr schrieb Matt Sicker : > > Since this is sort of a

Re: New disclaimer text

Since this is sort of a post-release set of info, I think it’d make sense to have either a page specific to each version, or at least a section per version all on a single page (similar to a security issues page might be or a change log in general). On Tue, Jul 9, 2019 at 21:24, Justin Mclean

Re: New disclaimer text

Hi, The issue with having a detached disclaimer is that it can change and get out of sync with what was actually in a released version. However one possible compromise would be to list known issues in the disclaimer and list any other issues found by the IPMC in the release announcements and

Re: New disclaimer text

Dave Fisher wrote on Wed, 03 Jul 2019 16:06 -0700: > > On Jul 3, 2019, at 3:59 PM, Daniel Shahaf wrote: > > Alex Harui wrote on Wed, 03 Jul 2019 21:35 +: > It really is up to the PPMC Members coming around to how a full PMC and > RM would act in the Apache Way! No, it isn't. Getting the

Re: New disclaimer text

Sent from my iPhone > On Jul 3, 2019, at 3:59 PM, Daniel Shahaf wrote: > > Alex Harui wrote on Wed, 03 Jul 2019 21:35 +: >> Re-rolling required re-GPG-signing, new hashes, etc. > > Yes, I know how re-rolling works. I've RM'd things before. I still think > in-band is better. It

Re: New disclaimer text

On Wed, Jul 3, 2019 at 2:52 PM Greg Stein wrote: > > On Wed, Jul 3, 2019 at 4:35 PM Alex Harui wrote: > > > Suggestion: The DISCLAIMER references a detached copy of the DISCLAIMER > > at dist.a.o/releases/incubator/project and that detached copy is the one > > that gets updated with late

Re: New disclaimer text

Alex Harui wrote on Wed, 03 Jul 2019 21:35 +: > Re-rolling required re-GPG-signing, new hashes, etc. Yes, I know how re-rolling works. I've RM'd things before. I still think in-band is better. - To unsubscribe, e-mail:

Re: New disclaimer text

On Wed, Jul 3, 2019 at 4:35 PM Alex Harui wrote: > Suggestion: The DISCLAIMER references a detached copy of the DISCLAIMER > at dist.a.o/releases/incubator/project and that detached copy is the one > that gets updated with late breaking stuff. > > Re-rolling required re-GPG-signing, new hashes,

Re: New disclaimer text

Suggestion: The DISCLAIMER references a detached copy of the DISCLAIMER at dist.a.o/releases/incubator/project and that detached copy is the one that gets updated with late breaking stuff. Re-rolling required re-GPG-signing, new hashes, etc. -Alex On 7/3/19, 2:08 PM, "Daniel Shahaf" wrote:

Re: New disclaimer text

Dave Fisher wrote on Wed, 03 Jul 2019 12:16 -0700: > This only works for issues known before a release is cut. It does NOT > WORK if the issue is discovered during the release vote. Why? Because we > are trying to allow the release to go through without redoing it and > this would require

Re: New disclaimer text

> On Jul 3, 2019, at 12:32 PM, Roman Shaposhnik wrote: > > On Wed, Jul 3, 2019 at 12:29 PM Dave Fisher wrote: >> >> >> >>> On Jul 3, 2019, at 12:24 PM, Roman Shaposhnik wrote: >>> >>> On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrote: > On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik

Re: New disclaimer text

On Wed, Jul 3, 2019 at 12:29 PM Dave Fisher wrote: > > > > > On Jul 3, 2019, at 12:24 PM, Roman Shaposhnik wrote: > > > > On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrote: > >>> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik > >>> wrote: > >>> > >>> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher

Re: New disclaimer text

> On Jul 3, 2019, at 12:24 PM, Roman Shaposhnik wrote: > > On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrote: >>> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote: >>> >>> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote: Hi - > On Jul 1, 2019, at 1:30 AM,

Re: New disclaimer text

On Wed, Jul 3, 2019 at 12:17 PM Dave Fisher wrote: > > On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote: > > > > On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote: > >> > >> Hi - > >> > >>> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz > >>> wrote: > >>> > >>> Hi, > >>> > >>> On Sun, Jun

Re: New disclaimer text

> On Jul 3, 2019, at 12:16 PM, Dave Fisher wrote: > > > >> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote: >> >> On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote: >>> >>> Hi - >>> On Jul 1, 2019, at 1:30 AM, Bertrand Delacretaz wrote: Hi, On Sun,

Re: New disclaimer text

> On Jul 3, 2019, at 11:50 AM, Roman Shaposhnik wrote: > > On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote: >> >> 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

Re: New disclaimer text

On Tue, Jul 2, 2019 at 10:28 AM Dave Fisher wrote: > > 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]... > > > >

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 < >

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

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

Re: New disclaimer text

Hi, >> Some of the project releases may not follow ASF policy or have >> incomplete or unknown licensing conditions…. Yes just that line added, I put it own the wiki and highlighted any changes. > It works for me but I'd say "incubating project" to be clearer. Will change. > I don't think

Re: New disclaimer text

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 releases may not follow ASF policy or have > incomplete or unknown licensing conditions It works

Re: New disclaimer text

Justin Mclean wrote on Sun, Jun 30, 2019 at 09:39:22 +1000: > I put up suggested text changes for an incubator disclaimer here [1]. Fullquote of the link: > Apache Podling-Name is an effort undergoing incubation at The Apache Software > Foundation (ASF), sponsored by the name of Apache TLP

New disclaimer text

Hi, I put up suggested text changes for an incubator disclaimer here [1]. Comments and feedback welcome. Text changes have been highlighted in yellow. Note that a disclaimer can’t remove any licence or other rights a user may have, the intent here it to just inform them that some podling