You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Dor Ben Dov <do...@amdocs.com> on 2016/02/21 15:19:35 UTC
RE: [MARKETING] Re: License question
Thanks John,
But does it means that other company for example, can take my product and suggest support for it ?
Can that company take those sources and create their own product and sell it ?
Dor
-----Original Message-----
From: John D. Ament [mailto:johndament@apache.org]
Sent: יום א 21 פברואר 2016 16:17
To: general@incubator.apache.org
Subject: [MARKETING] Re: License question
The source code would have to be Apache V2 licensed.
There are a lot of instances of companies providing commercial versions, supported versions of ASF projects. Look at a few like DataStax, Pivotal.
John
On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov <do...@amdocs.com> wrote:
> Hi All,
>
> Let's say I (company) go the ASF way.
>
> To incubator and later on into TLP.
>
> Does it mean that the license would be in the end only Apache License 2 ?
> or can it still remain for example, lgpl ?
>
> By means, when It is Apache License 2, can one company take this open
> source and offer support for it for money ? or adopt it and sell it ?
>
> Regards,
> Dor Ben Dov
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
RE: [MARKETING] [Caution: Suspicious URL]: Re: [MARKETING] Re:
[MARKETING] Re: License question
Posted by Dor Ben Dov <do...@amdocs.com>.
Greg,
Thanks a lot.
Regards,
Dor
-----Original Message-----
From: Gregory Chase [mailto:gchase@pivotal.io]
Sent: יום א 21 פברואר 2016 20:18
To: general@incubator.apache.org
Subject: [MARKETING] [Caution: Suspicious URL]: Re: [MARKETING] Re: [MARKETING] Re: License question
Hi Dor,
I did a talk a few months ago about Apache Geode's journey to open source, you might find some of the information in selecting licenses useful:
https://lnkd.in/bqfB-p3 <https://t.co/KrNCFkjrmy>
When one selects an Apache V2 license and grants the code and related patents to Apache, they do so specifically to build a broad, developer-owned, multi vendor community around the technology. Compare this with the Spring Framework which is a single vendor community run by Pivotal, or Cloud Foundry or Docker, which are other foundations with their own specific membership and governance policies.
Now in terms of how to contribute back to a community, checking in code is one way, but I like this blog that explains them any other ways people can contribute to a technology community:
http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/
-Greg
On Sun, Feb 21, 2016 at 10:06 AM, Dor Ben Dov <do...@amdocs.com>
wrote:
> Ted,
>
> Thanks for the answer, this is the exactly what I know. Now I am calm.
> Regard the last part, of course, going to apache incubator is a
> commitment And building the community, being the community helping the
> community Being activate, answer questions solve if possible bugs is
> the goal. One of the benefits In the long run of course, is the
> self-growth by others.
>
> Dor
>
> -----Original Message-----
> From: Ted Dunning [mailto:ted.dunning@gmail.com]
> Sent: יום א 21 פברואר 2016 19:55
> To: general@incubator.apache.org
> Subject: [MARKETING] Re: [MARKETING] Re: License question
>
> Dor,
>
> The short answer is yes. By open sourcing your code, you are giving
> it to the world. If somebody wants to do something with that code, they can.
>
> That may be what you want. Or not. You have to decide that.
>
> Keep in mind as well that if you go the Apache route, you will be
> expected to help build a community to carry this code forward over
> time regardless of what any single contributor might do. That means
> you might drop out, but others could continue the project.
>
>
>
>
>
> On Sun, Feb 21, 2016 at 2:32 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > Hi Dor,
> >
> > Here's the relevant part of section 4 of the ALv2.
> >
> > You may add Your own copyright statement to Your modifications and
> > may provide additional or different license terms and conditions for
> > use, reproduction, or distribution of Your modifications, or for any
> > such Derivative Works as a whole, provided Your use, reproduction,
> > and distribution of the Work otherwise complies with the conditions
> > stated in this License.
> >
> > This explicitly allows you to make modifications to Apache licensed
> > code while applying your own license to those modifications.
> >
> > An apache project probably should not encourage supported versions
> > of the apache project, so your tlp.apache.org / podling.i.a.o site
> > shouldn't refer to it.
> >
> > This may be a better discussion for legal-discuss, but I think
> > anyone on there may be subscribed here to provide additional insight
> > on this discussion.
> >
> > John
> >
> > On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov <do...@amdocs.com>
> > wrote:
> >
> > > Thanks John,
> > >
> > > But does it means that other company for example, can take my
> > > product and suggest support for it ?
> > > Can that company take those sources and create their own product
> > > and sell it ?
> > >
> > > Dor
> > >
> > > -----Original Message-----
> > > From: John D. Ament [mailto:johndament@apache.org]
> > > Sent: יום א 21 פברואר 2016 16:17
> > > To: general@incubator.apache.org
> > > Subject: [MARKETING] Re: License question
> > >
> > > The source code would have to be Apache V2 licensed.
> > >
> > > There are a lot of instances of companies providing commercial
> > > versions, supported versions of ASF projects. Look at a few like
> > > DataStax,
> > Pivotal.
> > >
> > > John
> > >
> > > On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov
> > > <do...@amdocs.com>
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > Let's say I (company) go the ASF way.
> > > >
> > > > To incubator and later on into TLP.
> > > >
> > > > Does it mean that the license would be in the end only Apache
> > > > License
> > 2 ?
> > > > or can it still remain for example, lgpl ?
> > > >
> > > > By means, when It is Apache License 2, can one company take this
> > > > open source and offer support for it for money ? or adopt it and
> sell it ?
> > > >
> > > > Regards,
> > > > Dor Ben Dov
> > > >
> > > > This message and the information contained herein is proprietary
> > > > and confidential and subject to the Amdocs policy statement, you
> > > > may review at http://www.amdocs.com/email_disclaimer.asp
> > > >
> > >
> > > This message and the information contained herein is proprietary
> > > and confidential and subject to the Amdocs policy statement, you
> > > may review at http://www.amdocs.com/email_disclaimer.asp
> > >
> >
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement, you may
> review at http://www.amdocs.com/email_disclaimer.asp
>
--
Greg Chase
Global Head, Big Data Communities
http://www.pivotal.io/big-data
Pivotal Software
http://www.pivotal.io/
650-215-0477
@GregChase
Blog: http://geekmarketing.biz/
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
Re: [MARKETING] Re: [MARKETING] Re: License question
Posted by Gregory Chase <gc...@pivotal.io>.
Hi Dor,
I did a talk a few months ago about Apache Geode's journey to open source,
you might find some of the information in selecting licenses useful:
https://lnkd.in/bqfB-p3 <https://t.co/KrNCFkjrmy>
When one selects an Apache V2 license and grants the code and related
patents to Apache, they do so specifically to build a broad,
developer-owned, multi vendor community around the technology. Compare
this with the Spring Framework which is a single vendor community run by
Pivotal, or Cloud Foundry or Docker, which are other foundations with their
own specific membership and governance policies.
Now in terms of how to contribute back to a community, checking in code is
one way, but I like this blog that explains them any other ways people can
contribute to a technology community:
http://blog.smartbear.com/programming/14-ways-to-contribute-to-open-source-without-being-a-programming-genius-or-a-rock-star/
-Greg
On Sun, Feb 21, 2016 at 10:06 AM, Dor Ben Dov <do...@amdocs.com>
wrote:
> Ted,
>
> Thanks for the answer, this is the exactly what I know. Now I am calm.
> Regard the last part, of course, going to apache incubator is a commitment
> And building the community, being the community helping the community
> Being activate, answer questions solve if possible bugs is the goal. One
> of the benefits
> In the long run of course, is the self-growth by others.
>
> Dor
>
> -----Original Message-----
> From: Ted Dunning [mailto:ted.dunning@gmail.com]
> Sent: יום א 21 פברואר 2016 19:55
> To: general@incubator.apache.org
> Subject: [MARKETING] Re: [MARKETING] Re: License question
>
> Dor,
>
> The short answer is yes. By open sourcing your code, you are giving it to
> the world. If somebody wants to do something with that code, they can.
>
> That may be what you want. Or not. You have to decide that.
>
> Keep in mind as well that if you go the Apache route, you will be expected
> to help build a community to carry this code forward over time regardless
> of what any single contributor might do. That means you might drop out, but
> others could continue the project.
>
>
>
>
>
> On Sun, Feb 21, 2016 at 2:32 PM, John D. Ament <jo...@apache.org>
> wrote:
>
> > Hi Dor,
> >
> > Here's the relevant part of section 4 of the ALv2.
> >
> > You may add Your own copyright statement to Your modifications and may
> > provide additional or different license terms and conditions for use,
> > reproduction, or distribution of Your modifications, or for any such
> > Derivative Works as a whole, provided Your use, reproduction, and
> > distribution of the Work otherwise complies with the conditions stated
> > in this License.
> >
> > This explicitly allows you to make modifications to Apache licensed
> > code while applying your own license to those modifications.
> >
> > An apache project probably should not encourage supported versions of
> > the apache project, so your tlp.apache.org / podling.i.a.o site
> > shouldn't refer to it.
> >
> > This may be a better discussion for legal-discuss, but I think anyone
> > on there may be subscribed here to provide additional insight on this
> > discussion.
> >
> > John
> >
> > On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov <do...@amdocs.com>
> > wrote:
> >
> > > Thanks John,
> > >
> > > But does it means that other company for example, can take my
> > > product and suggest support for it ?
> > > Can that company take those sources and create their own product and
> > > sell it ?
> > >
> > > Dor
> > >
> > > -----Original Message-----
> > > From: John D. Ament [mailto:johndament@apache.org]
> > > Sent: יום א 21 פברואר 2016 16:17
> > > To: general@incubator.apache.org
> > > Subject: [MARKETING] Re: License question
> > >
> > > The source code would have to be Apache V2 licensed.
> > >
> > > There are a lot of instances of companies providing commercial
> > > versions, supported versions of ASF projects. Look at a few like
> > > DataStax,
> > Pivotal.
> > >
> > > John
> > >
> > > On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov <do...@amdocs.com>
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > Let's say I (company) go the ASF way.
> > > >
> > > > To incubator and later on into TLP.
> > > >
> > > > Does it mean that the license would be in the end only Apache
> > > > License
> > 2 ?
> > > > or can it still remain for example, lgpl ?
> > > >
> > > > By means, when It is Apache License 2, can one company take this
> > > > open source and offer support for it for money ? or adopt it and
> sell it ?
> > > >
> > > > Regards,
> > > > Dor Ben Dov
> > > >
> > > > This message and the information contained herein is proprietary
> > > > and confidential and subject to the Amdocs policy statement, you
> > > > may review at http://www.amdocs.com/email_disclaimer.asp
> > > >
> > >
> > > This message and the information contained herein is proprietary and
> > > confidential and subject to the Amdocs policy statement, you may
> > > review at http://www.amdocs.com/email_disclaimer.asp
> > >
> >
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>
--
Greg Chase
Global Head, Big Data Communities
http://www.pivotal.io/big-data
Pivotal Software
http://www.pivotal.io/
650-215-0477
@GregChase
Blog: http://geekmarketing.biz/
RE: [MARKETING] Re: [MARKETING] Re: License question
Posted by Dor Ben Dov <do...@amdocs.com>.
Ted,
Thanks for the answer, this is the exactly what I know. Now I am calm.
Regard the last part, of course, going to apache incubator is a commitment
And building the community, being the community helping the community
Being activate, answer questions solve if possible bugs is the goal. One of the benefits
In the long run of course, is the self-growth by others.
Dor
-----Original Message-----
From: Ted Dunning [mailto:ted.dunning@gmail.com]
Sent: יום א 21 פברואר 2016 19:55
To: general@incubator.apache.org
Subject: [MARKETING] Re: [MARKETING] Re: License question
Dor,
The short answer is yes. By open sourcing your code, you are giving it to the world. If somebody wants to do something with that code, they can.
That may be what you want. Or not. You have to decide that.
Keep in mind as well that if you go the Apache route, you will be expected to help build a community to carry this code forward over time regardless of what any single contributor might do. That means you might drop out, but others could continue the project.
On Sun, Feb 21, 2016 at 2:32 PM, John D. Ament <jo...@apache.org>
wrote:
> Hi Dor,
>
> Here's the relevant part of section 4 of the ALv2.
>
> You may add Your own copyright statement to Your modifications and may
> provide additional or different license terms and conditions for use,
> reproduction, or distribution of Your modifications, or for any such
> Derivative Works as a whole, provided Your use, reproduction, and
> distribution of the Work otherwise complies with the conditions stated
> in this License.
>
> This explicitly allows you to make modifications to Apache licensed
> code while applying your own license to those modifications.
>
> An apache project probably should not encourage supported versions of
> the apache project, so your tlp.apache.org / podling.i.a.o site
> shouldn't refer to it.
>
> This may be a better discussion for legal-discuss, but I think anyone
> on there may be subscribed here to provide additional insight on this
> discussion.
>
> John
>
> On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov <do...@amdocs.com>
> wrote:
>
> > Thanks John,
> >
> > But does it means that other company for example, can take my
> > product and suggest support for it ?
> > Can that company take those sources and create their own product and
> > sell it ?
> >
> > Dor
> >
> > -----Original Message-----
> > From: John D. Ament [mailto:johndament@apache.org]
> > Sent: יום א 21 פברואר 2016 16:17
> > To: general@incubator.apache.org
> > Subject: [MARKETING] Re: License question
> >
> > The source code would have to be Apache V2 licensed.
> >
> > There are a lot of instances of companies providing commercial
> > versions, supported versions of ASF projects. Look at a few like
> > DataStax,
> Pivotal.
> >
> > John
> >
> > On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov <do...@amdocs.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > Let's say I (company) go the ASF way.
> > >
> > > To incubator and later on into TLP.
> > >
> > > Does it mean that the license would be in the end only Apache
> > > License
> 2 ?
> > > or can it still remain for example, lgpl ?
> > >
> > > By means, when It is Apache License 2, can one company take this
> > > open source and offer support for it for money ? or adopt it and sell it ?
> > >
> > > Regards,
> > > Dor Ben Dov
> > >
> > > This message and the information contained herein is proprietary
> > > and confidential and subject to the Amdocs policy statement, you
> > > may review at http://www.amdocs.com/email_disclaimer.asp
> > >
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement, you may
> > review at http://www.amdocs.com/email_disclaimer.asp
> >
>
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
Re: [MARKETING] Re: License question
Posted by Ted Dunning <te...@gmail.com>.
Dor,
The short answer is yes. By open sourcing your code, you are giving it to
the world. If somebody wants to do something with that code, they can.
That may be what you want. Or not. You have to decide that.
Keep in mind as well that if you go the Apache route, you will be expected
to help build a community to carry this code forward over time regardless
of what any single contributor might do. That means you might drop out, but
others could continue the project.
On Sun, Feb 21, 2016 at 2:32 PM, John D. Ament <jo...@apache.org>
wrote:
> Hi Dor,
>
> Here's the relevant part of section 4 of the ALv2.
>
> You may add Your own copyright statement to Your modifications and may
> provide additional or different license terms and conditions for use,
> reproduction, or distribution of Your modifications, or for any such
> Derivative Works as a whole, provided Your use, reproduction, and
> distribution of the Work otherwise complies with the conditions stated in
> this License.
>
> This explicitly allows you to make modifications to Apache licensed code
> while applying your own license to those modifications.
>
> An apache project probably should not encourage supported versions of the
> apache project, so your tlp.apache.org / podling.i.a.o site shouldn't
> refer
> to it.
>
> This may be a better discussion for legal-discuss, but I think anyone on
> there may be subscribed here to provide additional insight on this
> discussion.
>
> John
>
> On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov <do...@amdocs.com>
> wrote:
>
> > Thanks John,
> >
> > But does it means that other company for example, can take my product and
> > suggest support for it ?
> > Can that company take those sources and create their own product and sell
> > it ?
> >
> > Dor
> >
> > -----Original Message-----
> > From: John D. Ament [mailto:johndament@apache.org]
> > Sent: יום א 21 פברואר 2016 16:17
> > To: general@incubator.apache.org
> > Subject: [MARKETING] Re: License question
> >
> > The source code would have to be Apache V2 licensed.
> >
> > There are a lot of instances of companies providing commercial versions,
> > supported versions of ASF projects. Look at a few like DataStax,
> Pivotal.
> >
> > John
> >
> > On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov <do...@amdocs.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > Let's say I (company) go the ASF way.
> > >
> > > To incubator and later on into TLP.
> > >
> > > Does it mean that the license would be in the end only Apache License
> 2 ?
> > > or can it still remain for example, lgpl ?
> > >
> > > By means, when It is Apache License 2, can one company take this open
> > > source and offer support for it for money ? or adopt it and sell it ?
> > >
> > > Regards,
> > > Dor Ben Dov
> > >
> > > This message and the information contained herein is proprietary and
> > > confidential and subject to the Amdocs policy statement, you may
> > > review at http://www.amdocs.com/email_disclaimer.asp
> > >
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement,
> > you may review at http://www.amdocs.com/email_disclaimer.asp
> >
>
Re: [MARKETING] Re: License question
Posted by "John D. Ament" <jo...@apache.org>.
Hi Dor,
Here's the relevant part of section 4 of the ALv2.
You may add Your own copyright statement to Your modifications and may
provide additional or different license terms and conditions for use,
reproduction, or distribution of Your modifications, or for any such
Derivative Works as a whole, provided Your use, reproduction, and
distribution of the Work otherwise complies with the conditions stated in
this License.
This explicitly allows you to make modifications to Apache licensed code
while applying your own license to those modifications.
An apache project probably should not encourage supported versions of the
apache project, so your tlp.apache.org / podling.i.a.o site shouldn't refer
to it.
This may be a better discussion for legal-discuss, but I think anyone on
there may be subscribed here to provide additional insight on this
discussion.
John
On Sun, Feb 21, 2016 at 9:19 AM Dor Ben Dov <do...@amdocs.com> wrote:
> Thanks John,
>
> But does it means that other company for example, can take my product and
> suggest support for it ?
> Can that company take those sources and create their own product and sell
> it ?
>
> Dor
>
> -----Original Message-----
> From: John D. Ament [mailto:johndament@apache.org]
> Sent: יום א 21 פברואר 2016 16:17
> To: general@incubator.apache.org
> Subject: [MARKETING] Re: License question
>
> The source code would have to be Apache V2 licensed.
>
> There are a lot of instances of companies providing commercial versions,
> supported versions of ASF projects. Look at a few like DataStax, Pivotal.
>
> John
>
> On Sun, Feb 21, 2016 at 8:25 AM Dor Ben Dov <do...@amdocs.com>
> wrote:
>
> > Hi All,
> >
> > Let's say I (company) go the ASF way.
> >
> > To incubator and later on into TLP.
> >
> > Does it mean that the license would be in the end only Apache License 2 ?
> > or can it still remain for example, lgpl ?
> >
> > By means, when It is Apache License 2, can one company take this open
> > source and offer support for it for money ? or adopt it and sell it ?
> >
> > Regards,
> > Dor Ben Dov
> >
> > This message and the information contained herein is proprietary and
> > confidential and subject to the Amdocs policy statement, you may
> > review at http://www.amdocs.com/email_disclaimer.asp
> >
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
>