You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Noah Slater <ns...@tumbolia.org> on 2012/09/30 23:41:53 UTC
How to handle non-OS jars in repository
Hey,
It came up on the CloudStack list that we have non-OS (I don't know the
specific license, but I can find out if it's important) jars in the
repository, and some people (at least one) is downloading them from that
location for convenience.
Obviously, we're not going to ship them, and we can certainly delete them.
(This may've happened already.) But what I wanted to know was: do we have
to do anything about the fact that they exist in the repository history?
Thanks,
--
NS
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
David Nalley just added:
They have all (to my knowledge) been removed.
> Some were under VMwares SDK license, which does permit some redistribution
> in certain cases, others were under the NetApp SDK license for which I am
> unaware of the terms but it was posted to the list some time back.
Those are the only two that jump to mind that weren't under some sort of an
> open source license, but my memory might be fallible.
On Sun, Sep 30, 2012 at 10:50 PM, Noah Slater <ns...@tumbolia.org> wrote:
> In relation to the non-OS jars, Chiradeep Vittal wrote:
>
> I am currently downloading them from the repository history.
>
>
> Presumably he is doing this because he knew of their existence before they
> were removed (they were part of the original import from Citrix), and finds
> it convenient to snag them each time he's preparing a build.
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
>
> On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>
>> To clarify, are you saying that people download jars directly from
>> version control history? Where do they find the references to their
>> existence there?
>>
>> Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
>> > Hey,
>> >
>> > It came up on the CloudStack list that we have non-OS (I don't know the
>> > specific license, but I can find out if it's important) jars in the
>> > repository, and some people (at least one) is downloading them from that
>> > location for convenience.
>> >
>> > Obviously, we're not going to ship them, and we can certainly delete
>> them.
>> > (This may've happened already.) But what I wanted to know was: do we
>> have
>> > to do anything about the fact that they exist in the repository history?
>> >
>> > Thanks,
>> >
>> > --
>> > NS
>>
>
>
>
> --
> NS
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
Thanks. :)
On Sun, Sep 30, 2012 at 11:14 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> If you've not released it and you've deleted it from HEAD of all
> branches, I think you're fine.
>
> Noah Slater wrote on Sun, Sep 30, 2012 at 23:09:45 +0100:
> > Okay cool.
> >
> > My root concern was that we have non-OS data in our repository. But if
> you
> > think that's an academic concern (i.e. we've not released it, so it
> doesn't
> > matter) then okay.
> >
> > On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d.s@daniel.shahaf.name
> >wrote:
> >
> > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> > > > In relation to the non-OS jars, Chiradeep Vittal wrote:
> > > >
> > > > I am currently downloading them from the repository history.
> > > >
> > >
> > > If it's just one developer who does it in his own personal builds of
> > > HEAD, builds which don't leave his personal dev environment, I don't
> see
> > > the problem.
> > >
> > > >
> > > > Presumably he is doing this because he knew of their existence before
> > > they
> > > > were removed (they were part of the original import from Citrix), and
> > > finds
> > > > it convenient to snag them each time he's preparing a build.
> > > >
> > > >
> > >
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
> > > >
> > > > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <
> d.s@daniel.shahaf.name
> > > >wrote:
> > > >
> > > > > To clarify, are you saying that people download jars directly from
> > > > > version control history? Where do they find the references to
> their
> > > > > existence there?
> > > > >
> > > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > > > > Hey,
> > > > > >
> > > > > > It came up on the CloudStack list that we have non-OS (I don't
> know
> > > the
> > > > > > specific license, but I can find out if it's important) jars in
> the
> > > > > > repository, and some people (at least one) is downloading them
> from
> > > that
> > > > > > location for convenience.
> > > > > >
> > > > > > Obviously, we're not going to ship them, and we can certainly
> delete
> > > > > them.
> > > > > > (This may've happened already.) But what I wanted to know was:
> do we
> > > have
> > > > > > to do anything about the fact that they exist in the repository
> > > history?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --
> > > > > > NS
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > NS
> > >
> >
> >
> >
> > --
> > NS
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Fabian Christ <ch...@googlemail.com>.
Hi,
just wanted to add what I have learned during Stanbol incubation:
The ASF releases source code, only. The repo should contain only the
sources - and no binary code (JARs) at all. This is fundamental to the
idea of open source. Once you start hosting binaries the users can not
be sure what they get.
If your build needs additional JARs that are not available at places
like Maven Central, then you should create a "-deps" package that
contains the needed JARs. You can put this -deps package for download
in your dist section and mark it as a download for convenience (i.e.
be clear that it is not an officially released artifact). Do not host
such JARs in your repo. And the JARs need to have a license that is
compatible with the AL20 license.
Best,
- Fabian
2012/10/1 Upayavira <uv...@odoko.co.uk>:
> Here's my take:
>
> As I see it, anything that goes into SVN we need to be sure we have the
> _legal_ right to redistribute, regardless of any compatibility or
> otherwise with the Apache License (e.g. GPL in our repo is not a
> disaster).
>
> It is a _policy_ decision of the ASF that anything that goes into ASF
> releases is compatible with, and sublicensable under the Apache License.
>
> So long as it is legal to redistribute them, it is okay to have them in
> SVN. If it is not legal to redistribute, we should certainly delete
> immediately from HEAD, and whether we do more than that would, I guess,
> be up to the copyright holder (assuming they knew it was there at all).
>
> Upayavira
>
> On Sun, Sep 30, 2012, at 11:14 PM, Daniel Shahaf wrote:
>> If you've not released it and you've deleted it from HEAD of all
>> branches, I think you're fine.
>>
>> Noah Slater wrote on Sun, Sep 30, 2012 at 23:09:45 +0100:
>> > Okay cool.
>> >
>> > My root concern was that we have non-OS data in our repository. But if you
>> > think that's an academic concern (i.e. we've not released it, so it doesn't
>> > matter) then okay.
>> >
>> > On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>> >
>> > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
>> > > > In relation to the non-OS jars, Chiradeep Vittal wrote:
>> > > >
>> > > > I am currently downloading them from the repository history.
>> > > >
>> > >
>> > > If it's just one developer who does it in his own personal builds of
>> > > HEAD, builds which don't leave his personal dev environment, I don't see
>> > > the problem.
>> > >
>> > > >
>> > > > Presumably he is doing this because he knew of their existence before
>> > > they
>> > > > were removed (they were part of the original import from Citrix), and
>> > > finds
>> > > > it convenient to snag them each time he's preparing a build.
>> > > >
>> > > >
>> > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
>> > > >
>> > > > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d.s@daniel.shahaf.name
>> > > >wrote:
>> > > >
>> > > > > To clarify, are you saying that people download jars directly from
>> > > > > version control history? Where do they find the references to their
>> > > > > existence there?
>> > > > >
>> > > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
>> > > > > > Hey,
>> > > > > >
>> > > > > > It came up on the CloudStack list that we have non-OS (I don't know
>> > > the
>> > > > > > specific license, but I can find out if it's important) jars in the
>> > > > > > repository, and some people (at least one) is downloading them from
>> > > that
>> > > > > > location for convenience.
>> > > > > >
>> > > > > > Obviously, we're not going to ship them, and we can certainly delete
>> > > > > them.
>> > > > > > (This may've happened already.) But what I wanted to know was: do we
>> > > have
>> > > > > > to do anything about the fact that they exist in the repository
>> > > history?
>> > > > > >
>> > > > > > Thanks,
>> > > > > >
>> > > > > > --
>> > > > > > NS
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > NS
>> > >
>> >
>> >
>> >
>> > --
>> > NS
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
--
Fabian
http://twitter.com/fctwitt
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Upayavira wrote on Mon, Oct 01, 2012 at 13:42:04 +0100:
> This is something I recall from clarifications by Roy some while back -
> made a lot of sense to me. I'm not aware of it being documented
> anywhere, nor am I aware of it having been collectively agreed. If we
> can work out where,
www.apache.org/legal/resolved , after legal@ consensus?
> I'd be happy to write it up.
>
Cheers
Daniel
> Upayavira
>
> On Mon, Oct 1, 2012, at 01:35 PM, Daniel Shahaf wrote:
> > Upayavira wrote on Mon, Oct 01, 2012 at 13:26:00 +0100:
> > > Note, podlings are free to check in IP that is dubious from a *policy*
> > > perspective (i.e. incompatible with Apache License), but should not, as
> > > I see it, check in anything that is dubious from a *legal* one (i.e. it
> > > is not and should not be public, or we don't have *any* rights to
> > > distribute). While we may not consider putting stuff into SVN as
> > > publishing or distributing, others might not agree with that.
> > >
> >
> > Is this info on www.a.o/legal/ somewhere? If not, should it?
> >
> > > I've not heard of anyone demanding us to remove something from SVN
> > > entirely, and I believe that would be a very painful exercise. Best is
> > > to make sure it is only license compatibility issues that exist before
> > > code is checked in.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Upayavira <uv...@odoko.co.uk>.
This is something I recall from clarifications by Roy some while back -
made a lot of sense to me. I'm not aware of it being documented
anywhere, nor am I aware of it having been collectively agreed. If we
can work out where, I'd be happy to write it up.
Upayavira
On Mon, Oct 1, 2012, at 01:35 PM, Daniel Shahaf wrote:
> Upayavira wrote on Mon, Oct 01, 2012 at 13:26:00 +0100:
> > Note, podlings are free to check in IP that is dubious from a *policy*
> > perspective (i.e. incompatible with Apache License), but should not, as
> > I see it, check in anything that is dubious from a *legal* one (i.e. it
> > is not and should not be public, or we don't have *any* rights to
> > distribute). While we may not consider putting stuff into SVN as
> > publishing or distributing, others might not agree with that.
> >
>
> Is this info on www.a.o/legal/ somewhere? If not, should it?
>
> > I've not heard of anyone demanding us to remove something from SVN
> > entirely, and I believe that would be a very painful exercise. Best is
> > to make sure it is only license compatibility issues that exist before
> > code is checked in.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Upayavira wrote on Mon, Oct 01, 2012 at 13:26:00 +0100:
> Note, podlings are free to check in IP that is dubious from a *policy*
> perspective (i.e. incompatible with Apache License), but should not, as
> I see it, check in anything that is dubious from a *legal* one (i.e. it
> is not and should not be public, or we don't have *any* rights to
> distribute). While we may not consider putting stuff into SVN as
> publishing or distributing, others might not agree with that.
>
Is this info on www.a.o/legal/ somewhere? If not, should it?
> I've not heard of anyone demanding us to remove something from SVN
> entirely, and I believe that would be a very painful exercise. Best is
> to make sure it is only license compatibility issues that exist before
> code is checked in.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Upayavira <uv...@odoko.co.uk>.
good question, and probably one for legal-discuss.
It seems that most of the time deleting from svn is enough, although
that's not a definitive statement!
Upayavira
On Wed, Oct 3, 2012, at 11:16 PM, Noah Slater wrote:
> We have a situation with CloudStack where we have some jars that we do
> not
> know our distribution rights. If it turns out that we do not have the
> right
> to distribute them (Apache compatibility aside) what course of action
> should we take?
>
> On Mon, Oct 1, 2012 at 1:26 PM, Upayavira <uv...@odoko.co.uk> wrote:
>
> > Note, podlings are free to check in IP that is dubious from a *policy*
> > perspective (i.e. incompatible with Apache License), but should not, as
> > I see it, check in anything that is dubious from a *legal* one (i.e. it
> > is not and should not be public, or we don't have *any* rights to
> > distribute). While we may not consider putting stuff into SVN as
> > publishing or distributing, others might not agree with that.
> >
> > I've not heard of anyone demanding us to remove something from SVN
> > entirely, and I believe that would be a very painful exercise. Best is
> > to make sure it is only license compatibility issues that exist before
> > code is checked in.
> >
> > Upayavira
> >
> > On Mon, Oct 1, 2012, at 01:14 PM, Benson Margulies wrote:
> > > Podling frequently check in dubious IP as part of initial imports, and
> > > then clean up HEAD later. I've never seen any evidence of a more
> > > thorough extirpation.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: general-help@incubator.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
>
>
> --
> NS
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
We have a situation with CloudStack where we have some jars that we do not
know our distribution rights. If it turns out that we do not have the right
to distribute them (Apache compatibility aside) what course of action
should we take?
On Mon, Oct 1, 2012 at 1:26 PM, Upayavira <uv...@odoko.co.uk> wrote:
> Note, podlings are free to check in IP that is dubious from a *policy*
> perspective (i.e. incompatible with Apache License), but should not, as
> I see it, check in anything that is dubious from a *legal* one (i.e. it
> is not and should not be public, or we don't have *any* rights to
> distribute). While we may not consider putting stuff into SVN as
> publishing or distributing, others might not agree with that.
>
> I've not heard of anyone demanding us to remove something from SVN
> entirely, and I believe that would be a very painful exercise. Best is
> to make sure it is only license compatibility issues that exist before
> code is checked in.
>
> Upayavira
>
> On Mon, Oct 1, 2012, at 01:14 PM, Benson Margulies wrote:
> > Podling frequently check in dubious IP as part of initial imports, and
> > then clean up HEAD later. I've never seen any evidence of a more
> > thorough extirpation.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Upayavira <uv...@odoko.co.uk>.
Note, podlings are free to check in IP that is dubious from a *policy*
perspective (i.e. incompatible with Apache License), but should not, as
I see it, check in anything that is dubious from a *legal* one (i.e. it
is not and should not be public, or we don't have *any* rights to
distribute). While we may not consider putting stuff into SVN as
publishing or distributing, others might not agree with that.
I've not heard of anyone demanding us to remove something from SVN
entirely, and I believe that would be a very painful exercise. Best is
to make sure it is only license compatibility issues that exist before
code is checked in.
Upayavira
On Mon, Oct 1, 2012, at 01:14 PM, Benson Margulies wrote:
> Podling frequently check in dubious IP as part of initial imports, and
> then clean up HEAD later. I've never seen any evidence of a more
> thorough extirpation.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
Okay, thanks. :)
On Mon, Oct 1, 2012 at 1:14 PM, Benson Margulies <bi...@gmail.com>wrote:
> Podling frequently check in dubious IP as part of initial imports, and
> then clean up HEAD later. I've never seen any evidence of a more
> thorough extirpation.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Benson Margulies <bi...@gmail.com>.
Podling frequently check in dubious IP as part of initial imports, and
then clean up HEAD later. I've never seen any evidence of a more
thorough extirpation.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Makes sense, thanks for clarifying!
Upayavira wrote on Mon, Oct 01, 2012 at 08:30:56 +0100:
> Here's my take:
>
> As I see it, anything that goes into SVN we need to be sure we have the
> _legal_ right to redistribute, regardless of any compatibility or
> otherwise with the Apache License (e.g. GPL in our repo is not a
> disaster).
>
> It is a _policy_ decision of the ASF that anything that goes into ASF
> releases is compatible with, and sublicensable under the Apache License.
>
> So long as it is legal to redistribute them, it is okay to have them in
> SVN. If it is not legal to redistribute, we should certainly delete
> immediately from HEAD, and whether we do more than that would, I guess,
> be up to the copyright holder (assuming they knew it was there at all).
>
> Upayavira
>
> On Sun, Sep 30, 2012, at 11:14 PM, Daniel Shahaf wrote:
> > If you've not released it and you've deleted it from HEAD of all
> > branches, I think you're fine.
> >
> > Noah Slater wrote on Sun, Sep 30, 2012 at 23:09:45 +0100:
> > > Okay cool.
> > >
> > > My root concern was that we have non-OS data in our repository. But if you
> > > think that's an academic concern (i.e. we've not released it, so it doesn't
> > > matter) then okay.
> > >
> > > On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> > >
> > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> > > > > In relation to the non-OS jars, Chiradeep Vittal wrote:
> > > > >
> > > > > I am currently downloading them from the repository history.
> > > > >
> > > >
> > > > If it's just one developer who does it in his own personal builds of
> > > > HEAD, builds which don't leave his personal dev environment, I don't see
> > > > the problem.
> > > >
> > > > >
> > > > > Presumably he is doing this because he knew of their existence before
> > > > they
> > > > > were removed (they were part of the original import from Citrix), and
> > > > finds
> > > > > it convenient to snag them each time he's preparing a build.
> > > > >
> > > > >
> > > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
> > > > >
> > > > > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d.s@daniel.shahaf.name
> > > > >wrote:
> > > > >
> > > > > > To clarify, are you saying that people download jars directly from
> > > > > > version control history? Where do they find the references to their
> > > > > > existence there?
> > > > > >
> > > > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > > > > > Hey,
> > > > > > >
> > > > > > > It came up on the CloudStack list that we have non-OS (I don't know
> > > > the
> > > > > > > specific license, but I can find out if it's important) jars in the
> > > > > > > repository, and some people (at least one) is downloading them from
> > > > that
> > > > > > > location for convenience.
> > > > > > >
> > > > > > > Obviously, we're not going to ship them, and we can certainly delete
> > > > > > them.
> > > > > > > (This may've happened already.) But what I wanted to know was: do we
> > > > have
> > > > > > > to do anything about the fact that they exist in the repository
> > > > history?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > --
> > > > > > > NS
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > NS
> > > >
> > >
> > >
> > >
> > > --
> > > NS
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Upayavira <uv...@odoko.co.uk>.
Here's my take:
As I see it, anything that goes into SVN we need to be sure we have the
_legal_ right to redistribute, regardless of any compatibility or
otherwise with the Apache License (e.g. GPL in our repo is not a
disaster).
It is a _policy_ decision of the ASF that anything that goes into ASF
releases is compatible with, and sublicensable under the Apache License.
So long as it is legal to redistribute them, it is okay to have them in
SVN. If it is not legal to redistribute, we should certainly delete
immediately from HEAD, and whether we do more than that would, I guess,
be up to the copyright holder (assuming they knew it was there at all).
Upayavira
On Sun, Sep 30, 2012, at 11:14 PM, Daniel Shahaf wrote:
> If you've not released it and you've deleted it from HEAD of all
> branches, I think you're fine.
>
> Noah Slater wrote on Sun, Sep 30, 2012 at 23:09:45 +0100:
> > Okay cool.
> >
> > My root concern was that we have non-OS data in our repository. But if you
> > think that's an academic concern (i.e. we've not released it, so it doesn't
> > matter) then okay.
> >
> > On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> >
> > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> > > > In relation to the non-OS jars, Chiradeep Vittal wrote:
> > > >
> > > > I am currently downloading them from the repository history.
> > > >
> > >
> > > If it's just one developer who does it in his own personal builds of
> > > HEAD, builds which don't leave his personal dev environment, I don't see
> > > the problem.
> > >
> > > >
> > > > Presumably he is doing this because he knew of their existence before
> > > they
> > > > were removed (they were part of the original import from Citrix), and
> > > finds
> > > > it convenient to snag them each time he's preparing a build.
> > > >
> > > >
> > > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
> > > >
> > > > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d.s@daniel.shahaf.name
> > > >wrote:
> > > >
> > > > > To clarify, are you saying that people download jars directly from
> > > > > version control history? Where do they find the references to their
> > > > > existence there?
> > > > >
> > > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > > > > Hey,
> > > > > >
> > > > > > It came up on the CloudStack list that we have non-OS (I don't know
> > > the
> > > > > > specific license, but I can find out if it's important) jars in the
> > > > > > repository, and some people (at least one) is downloading them from
> > > that
> > > > > > location for convenience.
> > > > > >
> > > > > > Obviously, we're not going to ship them, and we can certainly delete
> > > > > them.
> > > > > > (This may've happened already.) But what I wanted to know was: do we
> > > have
> > > > > > to do anything about the fact that they exist in the repository
> > > history?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > --
> > > > > > NS
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > NS
> > >
> >
> >
> >
> > --
> > NS
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
If you've not released it and you've deleted it from HEAD of all
branches, I think you're fine.
Noah Slater wrote on Sun, Sep 30, 2012 at 23:09:45 +0100:
> Okay cool.
>
> My root concern was that we have non-OS data in our repository. But if you
> think that's an academic concern (i.e. we've not released it, so it doesn't
> matter) then okay.
>
> On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>
> > Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> > > In relation to the non-OS jars, Chiradeep Vittal wrote:
> > >
> > > I am currently downloading them from the repository history.
> > >
> >
> > If it's just one developer who does it in his own personal builds of
> > HEAD, builds which don't leave his personal dev environment, I don't see
> > the problem.
> >
> > >
> > > Presumably he is doing this because he knew of their existence before
> > they
> > > were removed (they were part of the original import from Citrix), and
> > finds
> > > it convenient to snag them each time he's preparing a build.
> > >
> > >
> > http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
> > >
> > > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d.s@daniel.shahaf.name
> > >wrote:
> > >
> > > > To clarify, are you saying that people download jars directly from
> > > > version control history? Where do they find the references to their
> > > > existence there?
> > > >
> > > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > > > Hey,
> > > > >
> > > > > It came up on the CloudStack list that we have non-OS (I don't know
> > the
> > > > > specific license, but I can find out if it's important) jars in the
> > > > > repository, and some people (at least one) is downloading them from
> > that
> > > > > location for convenience.
> > > > >
> > > > > Obviously, we're not going to ship them, and we can certainly delete
> > > > them.
> > > > > (This may've happened already.) But what I wanted to know was: do we
> > have
> > > > > to do anything about the fact that they exist in the repository
> > history?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > --
> > > > > NS
> > > >
> > >
> > >
> > >
> > > --
> > > NS
> >
>
>
>
> --
> NS
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
Okay cool.
My root concern was that we have non-OS data in our repository. But if you
think that's an academic concern (i.e. we've not released it, so it doesn't
matter) then okay.
On Sun, Sep 30, 2012 at 11:02 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> > In relation to the non-OS jars, Chiradeep Vittal wrote:
> >
> > I am currently downloading them from the repository history.
> >
>
> If it's just one developer who does it in his own personal builds of
> HEAD, builds which don't leave his personal dev environment, I don't see
> the problem.
>
> >
> > Presumably he is doing this because he knew of their existence before
> they
> > were removed (they were part of the original import from Citrix), and
> finds
> > it convenient to snag them each time he's preparing a build.
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
> >
> > On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d.s@daniel.shahaf.name
> >wrote:
> >
> > > To clarify, are you saying that people download jars directly from
> > > version control history? Where do they find the references to their
> > > existence there?
> > >
> > > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > > Hey,
> > > >
> > > > It came up on the CloudStack list that we have non-OS (I don't know
> the
> > > > specific license, but I can find out if it's important) jars in the
> > > > repository, and some people (at least one) is downloading them from
> that
> > > > location for convenience.
> > > >
> > > > Obviously, we're not going to ship them, and we can certainly delete
> > > them.
> > > > (This may've happened already.) But what I wanted to know was: do we
> have
> > > > to do anything about the fact that they exist in the repository
> history?
> > > >
> > > > Thanks,
> > > >
> > > > --
> > > > NS
> > >
> >
> >
> >
> > --
> > NS
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Noah Slater wrote on Sun, Sep 30, 2012 at 22:50:48 +0100:
> In relation to the non-OS jars, Chiradeep Vittal wrote:
>
> I am currently downloading them from the repository history.
>
If it's just one developer who does it in his own personal builds of
HEAD, builds which don't leave his personal dev environment, I don't see
the problem.
>
> Presumably he is doing this because he knew of their existence before they
> were removed (they were part of the original import from Citrix), and finds
> it convenient to snag them each time he's preparing a build.
>
> http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
>
> On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>
> > To clarify, are you saying that people download jars directly from
> > version control history? Where do they find the references to their
> > existence there?
> >
> > Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > > Hey,
> > >
> > > It came up on the CloudStack list that we have non-OS (I don't know the
> > > specific license, but I can find out if it's important) jars in the
> > > repository, and some people (at least one) is downloading them from that
> > > location for convenience.
> > >
> > > Obviously, we're not going to ship them, and we can certainly delete
> > them.
> > > (This may've happened already.) But what I wanted to know was: do we have
> > > to do anything about the fact that they exist in the repository history?
> > >
> > > Thanks,
> > >
> > > --
> > > NS
> >
>
>
>
> --
> NS
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: How to handle non-OS jars in repository
Posted by Noah Slater <ns...@tumbolia.org>.
In relation to the non-OS jars, Chiradeep Vittal wrote:
I am currently downloading them from the repository history.
Presumably he is doing this because he knew of their existence before they
were removed (they were part of the original import from Citrix), and finds
it convenient to snag them each time he's preparing a build.
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201209.mbox/%3CCC78B251.2EA43%25chiradeep.vittal@citrix.com%3E
On Sun, Sep 30, 2012 at 10:46 PM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> To clarify, are you saying that people download jars directly from
> version control history? Where do they find the references to their
> existence there?
>
> Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> > Hey,
> >
> > It came up on the CloudStack list that we have non-OS (I don't know the
> > specific license, but I can find out if it's important) jars in the
> > repository, and some people (at least one) is downloading them from that
> > location for convenience.
> >
> > Obviously, we're not going to ship them, and we can certainly delete
> them.
> > (This may've happened already.) But what I wanted to know was: do we have
> > to do anything about the fact that they exist in the repository history?
> >
> > Thanks,
> >
> > --
> > NS
>
--
NS
Re: How to handle non-OS jars in repository
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
To clarify, are you saying that people download jars directly from
version control history? Where do they find the references to their
existence there?
Noah Slater wrote on Sun, Sep 30, 2012 at 22:41:53 +0100:
> Hey,
>
> It came up on the CloudStack list that we have non-OS (I don't know the
> specific license, but I can find out if it's important) jars in the
> repository, and some people (at least one) is downloading them from that
> location for convenience.
>
> Obviously, we're not going to ship them, and we can certainly delete them.
> (This may've happened already.) But what I wanted to know was: do we have
> to do anything about the fact that they exist in the repository history?
>
> Thanks,
>
> --
> NS
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org