Re: Do we need a disclaimer? (Storm)
On Fri, Nov 15, 2013 at 4:26 PM, Craig L Russell craig.russ...@oracle.com wrote: ...I think Storm could do the same. There is specific interest in the incubating Storm community but not general interest in the wider Apache community... +1 Another similar (but older) example is Wicket which made a number of non-Apache releases during incubation. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need a disclaimer? (Storm)
Also, if it's not an Apache release, it probaly should not be hosted and listed at Apache to avoid confusion. On Thursday, November 14, 2013, Ted Dunning wrote: First few words should read A disclaimer ... I blame a combo of jet lag and *really* slow net link. Not the guy who hit send without proofing, of course. On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning ted.dunn...@gmail.comjavascript:; wrote: I disclaimer to clarify that the 0.9.0 release is neither an Apache top-level project release nor an Apache incubator release is probably good. A file name like DISCLAIMER might be good. I would worry about it being clear rather than being totally crafted by a true legal mind. On Fri, Nov 15, 2013 at 4:48 AM, P. Taylor Goetz ptgo...@gmail.comjavascript:; wrote: The Strom project is just entering the incubator. We have promised our community that we will issue a stable 0.9.0 release prior to switching over to the Apache release process. We are currently in a release candidate process. Now that we are an Incubator project, but not yet releasing under the Apache process, should we be including a disclaimer with our pre-Apache releases stating so? It feels like we should have some sort legalese in place. - Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:; -- Sent from my Mobile device
Re: Do we need a disclaimer? (Storm)
Agreed. It will not be hosted or linked to from any Apache site. On another thread on the storm dev list, I have an open question as to whether or not it’s okay to announce it (with a disclaimer that it is not an Apache release) on the Apache mailing lists dev/u...@storm.incubator.apache.org, or if any announcements should only go to the google groups mailing list. - Taylor On Nov 15, 2013, at 10:02 AM, Luciano Resende luckbr1...@gmail.com wrote: Also, if it's not an Apache release, it probaly should not be hosted and listed at Apache to avoid confusion. On Thursday, November 14, 2013, Ted Dunning wrote: First few words should read A disclaimer ... I blame a combo of jet lag and *really* slow net link. Not the guy who hit send without proofing, of course. On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning ted.dunn...@gmail.comjavascript:; wrote: I disclaimer to clarify that the 0.9.0 release is neither an Apache top-level project release nor an Apache incubator release is probably good. A file name like DISCLAIMER might be good. I would worry about it being clear rather than being totally crafted by a true legal mind. On Fri, Nov 15, 2013 at 4:48 AM, P. Taylor Goetz ptgo...@gmail.comjavascript:; wrote: The Strom project is just entering the incubator. We have promised our community that we will issue a stable 0.9.0 release prior to switching over to the Apache release process. We are currently in a release candidate process. Now that we are an Incubator project, but not yet releasing under the Apache process, should we be including a disclaimer with our pre-Apache releases stating so? It feels like we should have some sort legalese in place. - Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:; -- Sent from my Mobile device - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need a disclaimer? (Storm)
IIRC, JSPWiki had exactly the same issue when it entered the incubator. There were a non-Apache release or two while it was incubating, using the non-Apache package names, hosted on non-Apache servers and announced on non-Apache mail lists. Since it wasn't an Apache release, it was not announced on announce at apache.org but was announced on the Apache incubating user and dev lists. I think Storm could do the same. There is specific interest in the incubating Storm community but not general interest in the wider Apache community. Craig On Nov 15, 2013, at 7:10 AM, P. Taylor Goetz wrote: Agreed. It will not be hosted or linked to from any Apache site. On another thread on the storm dev list, I have an open question as to whether or not it’s okay to announce it (with a disclaimer that it is not an Apache release) on the Apache mailing lists dev/u...@storm.incubator.apache.org, or if any announcements should only go to the google groups mailing list. - Taylor On Nov 15, 2013, at 10:02 AM, Luciano Resende luckbr1...@gmail.com wrote: Also, if it's not an Apache release, it probaly should not be hosted and listed at Apache to avoid confusion. On Thursday, November 14, 2013, Ted Dunning wrote: First few words should read A disclaimer ... I blame a combo of jet lag and *really* slow net link. Not the guy who hit send without proofing, of course. On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning ted.dunn...@gmail.comjavascript:; wrote: I disclaimer to clarify that the 0.9.0 release is neither an Apache top-level project release nor an Apache incubator release is probably good. A file name like DISCLAIMER might be good. I would worry about it being clear rather than being totally crafted by a true legal mind. On Fri, Nov 15, 2013 at 4:48 AM, P. Taylor Goetz ptgo...@gmail.comjavascript:; wrote: The Strom project is just entering the incubator. We have promised our community that we will issue a stable 0.9.0 release prior to switching over to the Apache release process. We are currently in a release candidate process. Now that we are an Incubator project, but not yet releasing under the Apache process, should we be including a disclaimer with our pre-Apache releases stating so? It feels like we should have some sort legalese in place. - Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.orgjavascript:; For additional commands, e-mail: general-h...@incubator.apache.orgjavascript:; -- Sent from my Mobile device - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need a disclaimer? (Storm)
If you release as an Apache Incubator project, the disclaimer is required. If you release as your prior project, with prior infra and procedures, then no. Note: you cannot release as an Incubator project unless you use Apache procedures. Cheers, -g On Nov 14, 2013 11:49 PM, P. Taylor Goetz ptgo...@gmail.com wrote: The Strom project is just entering the incubator. We have promised our community that we will issue a stable 0.9.0 release prior to switching over to the Apache release process. We are currently in a release candidate process. Now that we are an Incubator project, but not yet releasing under the Apache process, should we be including a disclaimer with our pre-Apache releases stating so? It feels like we should have some sort legalese in place. - Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Do we need a disclaimer? (Storm)
First few words should read A disclaimer ... I blame a combo of jet lag and *really* slow net link. Not the guy who hit send without proofing, of course. On Fri, Nov 15, 2013 at 7:41 AM, Ted Dunning ted.dunn...@gmail.com wrote: I disclaimer to clarify that the 0.9.0 release is neither an Apache top-level project release nor an Apache incubator release is probably good. A file name like DISCLAIMER might be good. I would worry about it being clear rather than being totally crafted by a true legal mind. On Fri, Nov 15, 2013 at 4:48 AM, P. Taylor Goetz ptgo...@gmail.comwrote: The Strom project is just entering the incubator. We have promised our community that we will issue a stable 0.9.0 release prior to switching over to the Apache release process. We are currently in a release candidate process. Now that we are an Incubator project, but not yet releasing under the Apache process, should we be including a disclaimer with our pre-Apache releases stating so? It feels like we should have some sort legalese in place. - Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
