You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by Roman Shaposhnik <ro...@shaposhnik.org> on 2016/03/07 02:46:46 UTC
Re: Making license adjustment tools publicly available
To close a loop on this: based on the consensus I created a public
version of the tools under:
http://svn.apache.org/viewvc/comdev/tools/licensing/
My attempts of preserving the history weren't successfully since
private and public are two different SVN repos (you can't just svn cp/mv).
I don't think this is that big of a deal, but please let me know if it is.
Finally, I'd like to remove content of:
https://svn.apache.org/repos/private/committers/relicense/
and replace it with a README.txt saying that the content has moved
to a new public location. Please let me know if that sounds ok.
My final step would be to update a few bits of publicly visible documentation
to point to a new public location.
Thanks,
Roman.
On Sat, Feb 6, 2016 at 8:33 AM, Shane Curcuru <as...@shanecurcuru.org> wrote:
> Christopher wrote on 2/4/16 7:25 PM:
>> It might be relevant that that both of those tools appear to be licensed
>> under ASL 2.0, which explicitly permits redistribution (presumably outside
>> the private area?). I would think it confusing to have an open source
>> license on software which is expected to remain private, or otherwise
>> restricted from redistribution. As such, it seems prudent to move them to a
>> more appropriate area. That's my opinion, anyway.
>
> Yes, the Apache license explicitly gives broad permissions. But the ASF
> organizationally is very conservative about actually redistributing
> software. That is, we *could* legally redistribute some random software
> we found under AL or MIT or the like, but if someone makes it clear they
> *didn't* intend to submit it to an Apache project, then we'll generally
> respect their wishes.
>
> In this case, it's all work done by ASF Committers for the purpose of
> doing work on Apache projects, so I can't see why it would be a problem.
> It's most likely that once Apache projects finished updating to 2.0
> license, no-one bothered to think of these tools again.
>
> In any case, I would definitely recommend either testing them, or
> putting in behavior so that it doesn't actually change files in the
> default command line (to prevent surprises, if it doesn't work as
> someone anticipated).
>
> - Shane
>
>>
>> On Thu, Feb 4, 2016 at 7:14 PM Roman Shaposhnik <rv...@apache.org> wrote:
>>
>>> Hi!
>>>
>>> a podling recently asked me why:
>>> https://svn.apache.org/repos/private/committers/relicense/
>>> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
>>> are only available to commiters. I see
>>> no reason why, but of course I'm appreciative
>>> of the warning here:
>>> https://svn.apache.org/repos/private/committers/README
>>>
>>> Two questions:
>>> 1. Is there any disagreement that making this tool publically
>>> available would be a 'good thing' ?
>>> 2. Who should bless the svn mv if we all agree?
>>>
>>> Thanks,
>>> Roman.
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Making license adjustment tools publicly available
Posted by Andreas Zechmeister <dj...@icloud.com>.
No Worry have Test , will longer Test To Found all Parameters And Sound , really Great Sequenzer better Sound we By Any Apps i am use for Ableton live this Sequenzer is The Best By live Play Ty Roman happy Weekend πΎπΎπΎπΎπ
Von meinem iPhone gesendet
> Am 13.03.2016 um 03:54 schrieb sebb <se...@gmail.com>:
>
>> On 13 March 2016 at 01:25, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>>> On Mon, Mar 7, 2016 at 3:11 AM, sebb <se...@gmail.com> wrote:
>>>> On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>>>> To close a loop on this: based on the consensus I created a public
>>>> version of the tools under:
>>>> http://svn.apache.org/viewvc/comdev/tools/licensing/
>>>>
>>>> My attempts of preserving the history weren't successfully since
>>>> private and public are two different SVN repos (you can't just svn cp/mv).
>>>> I don't think this is that big of a deal, but please let me know if it is.
>>>
>>> In such cases it would be helpful to document the original source in
>>> the commit log message.
>>
>> Great point sebb! Thanks! It also made me realize that if I remove the
>> source from the original location I'd have to reference the SVN rev,
>> rather than source location for anybody interested in tracking history.
>
> Good point; that is what SVN does for a copy/move.
> It includes the source rev and the source path; both are needed to
> retrieve the original source.
>
>> Will the work?
>
> The only problem I can see is that SVN does not keep a history of
> commit messages; once overwritten, they are gone forever.
> They should be in the relevant mail archive, but that's not
> guaranteed, and it's not particularly easy to find the info.
>
> This is not a problem for moves within a repo, because svn log will
> show the file details even if the commit message is changed.
>
> So for this case it would be sensible to also record the original
> source in a text file that is stored in SVN.
> For example, the README.txt that already exists.
> You've already indicated that you will update the old location to
> point to the new one; this is the inverse.
>
>> Thanks,
>> Roman.
Re: Making license adjustment tools publicly available
Posted by sebb <se...@gmail.com>.
On 13 March 2016 at 01:25, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> On Mon, Mar 7, 2016 at 3:11 AM, sebb <se...@gmail.com> wrote:
>> On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>>> To close a loop on this: based on the consensus I created a public
>>> version of the tools under:
>>> http://svn.apache.org/viewvc/comdev/tools/licensing/
>>>
>>> My attempts of preserving the history weren't successfully since
>>> private and public are two different SVN repos (you can't just svn cp/mv).
>>> I don't think this is that big of a deal, but please let me know if it is.
>>
>> In such cases it would be helpful to document the original source in
>> the commit log message.
>
> Great point sebb! Thanks! It also made me realize that if I remove the
> source from the original location I'd have to reference the SVN rev,
> rather than source location for anybody interested in tracking history.
Good point; that is what SVN does for a copy/move.
It includes the source rev and the source path; both are needed to
retrieve the original source.
> Will the work?
The only problem I can see is that SVN does not keep a history of
commit messages; once overwritten, they are gone forever.
They should be in the relevant mail archive, but that's not
guaranteed, and it's not particularly easy to find the info.
This is not a problem for moves within a repo, because svn log will
show the file details even if the commit message is changed.
So for this case it would be sensible to also record the original
source in a text file that is stored in SVN.
For example, the README.txt that already exists.
You've already indicated that you will update the old location to
point to the new one; this is the inverse.
> Thanks,
> Roman.
Re: Making license adjustment tools publicly available
Posted by sebb <se...@gmail.com>.
On 13 March 2016 at 01:25, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> On Mon, Mar 7, 2016 at 3:11 AM, sebb <se...@gmail.com> wrote:
>> On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>>> To close a loop on this: based on the consensus I created a public
>>> version of the tools under:
>>> http://svn.apache.org/viewvc/comdev/tools/licensing/
>>>
>>> My attempts of preserving the history weren't successfully since
>>> private and public are two different SVN repos (you can't just svn cp/mv).
>>> I don't think this is that big of a deal, but please let me know if it is.
>>
>> In such cases it would be helpful to document the original source in
>> the commit log message.
>
> Great point sebb! Thanks! It also made me realize that if I remove the
> source from the original location I'd have to reference the SVN rev,
> rather than source location for anybody interested in tracking history.
Good point; that is what SVN does for a copy/move.
It includes the source rev and the source path; both are needed to
retrieve the original source.
> Will the work?
The only problem I can see is that SVN does not keep a history of
commit messages; once overwritten, they are gone forever.
They should be in the relevant mail archive, but that's not
guaranteed, and it's not particularly easy to find the info.
This is not a problem for moves within a repo, because svn log will
show the file details even if the commit message is changed.
So for this case it would be sensible to also record the original
source in a text file that is stored in SVN.
For example, the README.txt that already exists.
You've already indicated that you will update the old location to
point to the new one; this is the inverse.
> Thanks,
> Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Making license adjustment tools publicly available
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Mar 7, 2016 at 3:11 AM, sebb <se...@gmail.com> wrote:
> On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>> To close a loop on this: based on the consensus I created a public
>> version of the tools under:
>> http://svn.apache.org/viewvc/comdev/tools/licensing/
>>
>> My attempts of preserving the history weren't successfully since
>> private and public are two different SVN repos (you can't just svn cp/mv).
>> I don't think this is that big of a deal, but please let me know if it is.
>
> In such cases it would be helpful to document the original source in
> the commit log message.
Great point sebb! Thanks! It also made me realize that if I remove the
source from the original location I'd have to reference the SVN rev,
rather than source location for anybody interested in tracking history.
Will the work?
Thanks,
Roman.
Re: Making license adjustment tools publicly available
Posted by Roman Shaposhnik <ro...@shaposhnik.org>.
On Mon, Mar 7, 2016 at 3:11 AM, sebb <se...@gmail.com> wrote:
> On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
>> To close a loop on this: based on the consensus I created a public
>> version of the tools under:
>> http://svn.apache.org/viewvc/comdev/tools/licensing/
>>
>> My attempts of preserving the history weren't successfully since
>> private and public are two different SVN repos (you can't just svn cp/mv).
>> I don't think this is that big of a deal, but please let me know if it is.
>
> In such cases it would be helpful to document the original source in
> the commit log message.
Great point sebb! Thanks! It also made me realize that if I remove the
source from the original location I'd have to reference the SVN rev,
rather than source location for anybody interested in tracking history.
Will the work?
Thanks,
Roman.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Making license adjustment tools publicly available
Posted by sebb <se...@gmail.com>.
On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> To close a loop on this: based on the consensus I created a public
> version of the tools under:
> http://svn.apache.org/viewvc/comdev/tools/licensing/
>
> My attempts of preserving the history weren't successfully since
> private and public are two different SVN repos (you can't just svn cp/mv).
> I don't think this is that big of a deal, but please let me know if it is.
In such cases it would be helpful to document the original source in
the commit log message.
> Finally, I'd like to remove content of:
> https://svn.apache.org/repos/private/committers/relicense/
> and replace it with a README.txt saying that the content has moved
> to a new public location. Please let me know if that sounds ok.
>
> My final step would be to update a few bits of publicly visible documentation
> to point to a new public location.
>
> Thanks,
> Roman.
>
> On Sat, Feb 6, 2016 at 8:33 AM, Shane Curcuru <as...@shanecurcuru.org> wrote:
>> Christopher wrote on 2/4/16 7:25 PM:
>>> It might be relevant that that both of those tools appear to be licensed
>>> under ASL 2.0, which explicitly permits redistribution (presumably outside
>>> the private area?). I would think it confusing to have an open source
>>> license on software which is expected to remain private, or otherwise
>>> restricted from redistribution. As such, it seems prudent to move them to a
>>> more appropriate area. That's my opinion, anyway.
>>
>> Yes, the Apache license explicitly gives broad permissions. But the ASF
>> organizationally is very conservative about actually redistributing
>> software. That is, we *could* legally redistribute some random software
>> we found under AL or MIT or the like, but if someone makes it clear they
>> *didn't* intend to submit it to an Apache project, then we'll generally
>> respect their wishes.
>>
>> In this case, it's all work done by ASF Committers for the purpose of
>> doing work on Apache projects, so I can't see why it would be a problem.
>> It's most likely that once Apache projects finished updating to 2.0
>> license, no-one bothered to think of these tools again.
>>
>> In any case, I would definitely recommend either testing them, or
>> putting in behavior so that it doesn't actually change files in the
>> default command line (to prevent surprises, if it doesn't work as
>> someone anticipated).
>>
>> - Shane
>>
>>>
>>> On Thu, Feb 4, 2016 at 7:14 PM Roman Shaposhnik <rv...@apache.org> wrote:
>>>
>>>> Hi!
>>>>
>>>> a podling recently asked me why:
>>>> https://svn.apache.org/repos/private/committers/relicense/
>>>> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
>>>> are only available to commiters. I see
>>>> no reason why, but of course I'm appreciative
>>>> of the warning here:
>>>> https://svn.apache.org/repos/private/committers/README
>>>>
>>>> Two questions:
>>>> 1. Is there any disagreement that making this tool publically
>>>> available would be a 'good thing' ?
>>>> 2. Who should bless the svn mv if we all agree?
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>
>>
Re: Making license adjustment tools publicly available
Posted by sebb <se...@gmail.com>.
On 7 March 2016 at 01:46, Roman Shaposhnik <ro...@shaposhnik.org> wrote:
> To close a loop on this: based on the consensus I created a public
> version of the tools under:
> http://svn.apache.org/viewvc/comdev/tools/licensing/
>
> My attempts of preserving the history weren't successfully since
> private and public are two different SVN repos (you can't just svn cp/mv).
> I don't think this is that big of a deal, but please let me know if it is.
In such cases it would be helpful to document the original source in
the commit log message.
> Finally, I'd like to remove content of:
> https://svn.apache.org/repos/private/committers/relicense/
> and replace it with a README.txt saying that the content has moved
> to a new public location. Please let me know if that sounds ok.
>
> My final step would be to update a few bits of publicly visible documentation
> to point to a new public location.
>
> Thanks,
> Roman.
>
> On Sat, Feb 6, 2016 at 8:33 AM, Shane Curcuru <as...@shanecurcuru.org> wrote:
>> Christopher wrote on 2/4/16 7:25 PM:
>>> It might be relevant that that both of those tools appear to be licensed
>>> under ASL 2.0, which explicitly permits redistribution (presumably outside
>>> the private area?). I would think it confusing to have an open source
>>> license on software which is expected to remain private, or otherwise
>>> restricted from redistribution. As such, it seems prudent to move them to a
>>> more appropriate area. That's my opinion, anyway.
>>
>> Yes, the Apache license explicitly gives broad permissions. But the ASF
>> organizationally is very conservative about actually redistributing
>> software. That is, we *could* legally redistribute some random software
>> we found under AL or MIT or the like, but if someone makes it clear they
>> *didn't* intend to submit it to an Apache project, then we'll generally
>> respect their wishes.
>>
>> In this case, it's all work done by ASF Committers for the purpose of
>> doing work on Apache projects, so I can't see why it would be a problem.
>> It's most likely that once Apache projects finished updating to 2.0
>> license, no-one bothered to think of these tools again.
>>
>> In any case, I would definitely recommend either testing them, or
>> putting in behavior so that it doesn't actually change files in the
>> default command line (to prevent surprises, if it doesn't work as
>> someone anticipated).
>>
>> - Shane
>>
>>>
>>> On Thu, Feb 4, 2016 at 7:14 PM Roman Shaposhnik <rv...@apache.org> wrote:
>>>
>>>> Hi!
>>>>
>>>> a podling recently asked me why:
>>>> https://svn.apache.org/repos/private/committers/relicense/
>>>> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
>>>> are only available to commiters. I see
>>>> no reason why, but of course I'm appreciative
>>>> of the warning here:
>>>> https://svn.apache.org/repos/private/committers/README
>>>>
>>>> Two questions:
>>>> 1. Is there any disagreement that making this tool publically
>>>> available would be a 'good thing' ?
>>>> 2. Who should bless the svn mv if we all agree?
>>>>
>>>> Thanks,
>>>> Roman.
>>>>
>>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org