You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@blueyonder.co.uk> on 2005/12/08 04:02:03 UTC
Checking Release Candidates - Wiki Page
I started a page on the wiki with notes for checking a release candidate:
http://wiki.apache.org/jakarta-commons/ReleaseChecking
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Checking Release Candidates - Wiki Page
Posted by Henri Yandell <fl...@gmail.com>.
On 12/8/05, Martin Cooper <ma...@apache.org> wrote:
> On 12/7/05, Martin Cooper <ma...@apache.org> wrote:
> >
> > I've requested clarification from Simian. I'll post or paraphrase the
> > response here.
>
>
> Well that was fast! Herewith the response from Simon Harris at RedHill
> Consulting, makers of Simian:
>
> ----------
> Martin,
> I might change the wording. The intent is that open-source projects have an
> implicit license to use Simian--unlike IntelliJ for example which require
> that you apply for one. The license isn't transferable.
>
> I hope that clears things up. If not, just ping me again and I'll see what I
> can do to help :)
>
> Cheers,
>
> Simon
> ----------
>
> So I don't believe there's any issue in including Simian reports in Commons
> docs or sites (or any other ASF docs or sites, for that matter).
Cool, so not a problem for this release right?
While someone could use our distribution to build our site and then
have legal problems, that's a pretty weak point; however it does seem
a bit more of a problem for Maven who are redistributing it.
Something to mention at ApacheCon :)
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Checking Release Candidates - Wiki Page
Posted by Martin Cooper <ma...@apache.org>.
On 12/7/05, Martin Cooper <ma...@apache.org> wrote:
>
> I've requested clarification from Simian. I'll post or paraphrase the
> response here.
Well that was fast! Herewith the response from Simon Harris at RedHill
Consulting, makers of Simian:
----------
Martin,
I might change the wording. The intent is that open-source projects have an
implicit license to use Simian--unlike IntelliJ for example which require
that you apply for one. The license isn't transferable.
I hope that clears things up. If not, just ping me again and I'll see what I
can do to help :)
Cheers,
Simon
----------
So I don't believe there's any issue in including Simian reports in Commons
docs or sites (or any other ASF docs or sites, for that matter).
--
Martin Cooper
--
> Martin Cooper
>
>
> On 12/7/05, Henri Yandell <fl...@gmail.com> wrote:
> >
> > It's definitely arguable that we shouldn't have Simian turned on in
> > our source releases, or even in SVN. While we are able to use it, our
> > users may not be able to.
> >
> > Assuming that Redhill's licensing for open source is just a free
> > version of their commercial license
> > (http://www.redhillconsulting.com.au/products/simian/get_it_now.html),
> > then the Maven plugin would seem to be in breach of it too. The
> > license is non-sublicenseable/non-transferrable.
> >
> > This makes it much like Jira, which while we can use it as much as we
> > want on our own servers, and publish the output, we can't distribute
> > it under the ASL licence.
> >
> > So I'd recommend that we don't have it listed as a report in Commons
> > components.
> >
> > Hen
> >
> > On 12/7/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk > wrote:
> > > I included that because Robert indicated it was required and Stephen
> > > voted -1 in the recent Configuration release vote because of it:
> > >
> > >
> > http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html
> > > http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html
> >
> > >
> > > Personally I found the site unclear whether we were required to
> > actually
> > > "apply" for one of the free licenses or not, but if people are going
> > to -1 a
> > > release on that basis, seemed like a good idea to put it in the check
> > list.
> > > Hopefully they'll jump in and answer you properly :-)
> > >
> > > I think the same was the case for Validator - the recent 1.2.0 release
> > went
> > > out with it in, but I hadn't seen it raised as an issue at that point.
> >
> > >
> > > Niall
> > >
> > > ----- Original Message -----
> > > From: "Martin Cooper" <ma...@apache.org>
> > > Sent: Thursday, December 08, 2005 3:26 AM
> > >
> > >
> > > On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> > > >
> > > > I started a page on the wiki with notes for checking a release
> > candidate:
> > > >
> > > > http://wiki.apache.org/jakarta-commons/ReleaseChecking
> > >
> > >
> > > Excellent!
> > >
> > > One question, though: I don't understand the part about ensuring that
> > the
> > > component has a license for Simian. The referenced page on the Simian
> > site
> > > says it's free for open source use. Is there something else we're
> > expected
> > > to do?
> > >
> > > Frankly, what it produces doesn't seem too useful, but I have it in
> > > FileUpload because I picked up the line from some other project.xml.
> > If
> > > there's more work involved, then I'm probably more likely to simply
> > remove
> > > it.
> > >
> > > --
> > > Martin Cooper
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
Re: Checking Release Candidates - Wiki Page
Posted by Martin Cooper <ma...@apache.org>.
I've requested clarification from Simian. I'll post or paraphrase the
response here.
--
Martin Cooper
On 12/7/05, Henri Yandell <fl...@gmail.com> wrote:
>
> It's definitely arguable that we shouldn't have Simian turned on in
> our source releases, or even in SVN. While we are able to use it, our
> users may not be able to.
>
> Assuming that Redhill's licensing for open source is just a free
> version of their commercial license
> (http://www.redhillconsulting.com.au/products/simian/get_it_now.html),
> then the Maven plugin would seem to be in breach of it too. The
> license is non-sublicenseable/non-transferrable.
>
> This makes it much like Jira, which while we can use it as much as we
> want on our own servers, and publish the output, we can't distribute
> it under the ASL licence.
>
> So I'd recommend that we don't have it listed as a report in Commons
> components.
>
> Hen
>
> On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> > I included that because Robert indicated it was required and Stephen
> > voted -1 in the recent Configuration release vote because of it:
> >
> >
> http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html
> >
> http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html
> >
> > Personally I found the site unclear whether we were required to actually
> > "apply" for one of the free licenses or not, but if people are going to
> -1 a
> > release on that basis, seemed like a good idea to put it in the check
> list.
> > Hopefully they'll jump in and answer you properly :-)
> >
> > I think the same was the case for Validator - the recent 1.2.0 release
> went
> > out with it in, but I hadn't seen it raised as an issue at that point.
> >
> > Niall
> >
> > ----- Original Message -----
> > From: "Martin Cooper" <ma...@apache.org>
> > Sent: Thursday, December 08, 2005 3:26 AM
> >
> >
> > On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> > >
> > > I started a page on the wiki with notes for checking a release
> candidate:
> > >
> > > http://wiki.apache.org/jakarta-commons/ReleaseChecking
> >
> >
> > Excellent!
> >
> > One question, though: I don't understand the part about ensuring that
> the
> > component has a license for Simian. The referenced page on the Simian
> site
> > says it's free for open source use. Is there something else we're
> expected
> > to do?
> >
> > Frankly, what it produces doesn't seem too useful, but I have it in
> > FileUpload because I picked up the line from some other project.xml. If
> > there's more work involved, then I'm probably more likely to simply
> remove
> > it.
> >
> > --
> > Martin Cooper
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: Checking Release Candidates - Wiki Page
Posted by Henri Yandell <fl...@gmail.com>.
It's definitely arguable that we shouldn't have Simian turned on in
our source releases, or even in SVN. While we are able to use it, our
users may not be able to.
Assuming that Redhill's licensing for open source is just a free
version of their commercial license
(http://www.redhillconsulting.com.au/products/simian/get_it_now.html),
then the Maven plugin would seem to be in breach of it too. The
license is non-sublicenseable/non-transferrable.
This makes it much like Jira, which while we can use it as much as we
want on our own servers, and publish the output, we can't distribute
it under the ASL licence.
So I'd recommend that we don't have it listed as a report in Commons components.
Hen
On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> I included that because Robert indicated it was required and Stephen
> voted -1 in the recent Configuration release vote because of it:
>
> http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html
> http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html
>
> Personally I found the site unclear whether we were required to actually
> "apply" for one of the free licenses or not, but if people are going to -1 a
> release on that basis, seemed like a good idea to put it in the check list.
> Hopefully they'll jump in and answer you properly :-)
>
> I think the same was the case for Validator - the recent 1.2.0 release went
> out with it in, but I hadn't seen it raised as an issue at that point.
>
> Niall
>
> ----- Original Message -----
> From: "Martin Cooper" <ma...@apache.org>
> Sent: Thursday, December 08, 2005 3:26 AM
>
>
> On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> >
> > I started a page on the wiki with notes for checking a release candidate:
> >
> > http://wiki.apache.org/jakarta-commons/ReleaseChecking
>
>
> Excellent!
>
> One question, though: I don't understand the part about ensuring that the
> component has a license for Simian. The referenced page on the Simian site
> says it's free for open source use. Is there something else we're expected
> to do?
>
> Frankly, what it produces doesn't seem too useful, but I have it in
> FileUpload because I picked up the line from some other project.xml. If
> there's more work involved, then I'm probably more likely to simply remove
> it.
>
> --
> Martin Cooper
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Checking Release Candidates - Wiki Page
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
I included that because Robert indicated it was required and Stephen
voted -1 in the recent Configuration release vote because of it:
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70746.html
http://www.mail-archive.com/commons-dev%40jakarta.apache.org/msg70942.html
Personally I found the site unclear whether we were required to actually
"apply" for one of the free licenses or not, but if people are going to -1 a
release on that basis, seemed like a good idea to put it in the check list.
Hopefully they'll jump in and answer you properly :-)
I think the same was the case for Validator - the recent 1.2.0 release went
out with it in, but I hadn't seen it raised as an issue at that point.
Niall
----- Original Message -----
From: "Martin Cooper" <ma...@apache.org>
Sent: Thursday, December 08, 2005 3:26 AM
On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
>
> I started a page on the wiki with notes for checking a release candidate:
>
> http://wiki.apache.org/jakarta-commons/ReleaseChecking
Excellent!
One question, though: I don't understand the part about ensuring that the
component has a license for Simian. The referenced page on the Simian site
says it's free for open source use. Is there something else we're expected
to do?
Frankly, what it produces doesn't seem too useful, but I have it in
FileUpload because I picked up the line from some other project.xml. If
there's more work involved, then I'm probably more likely to simply remove
it.
--
Martin Cooper
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: Checking Release Candidates - Wiki Page
Posted by Martin Cooper <ma...@apache.org>.
On 12/7/05, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
>
> I started a page on the wiki with notes for checking a release candidate:
>
> http://wiki.apache.org/jakarta-commons/ReleaseChecking
Excellent!
One question, though: I don't understand the part about ensuring that the
component has a license for Simian. The referenced page on the Simian site
says it's free for open source use. Is there something else we're expected
to do?
Frankly, what it produces doesn't seem too useful, but I have it in
FileUpload because I picked up the line from some other project.xml. If
there's more work involved, then I'm probably more likely to simply remove
it.
--
Martin Cooper
Niall
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>