All,
Just a reminder that podling reports are due today. the following podlings
have not reported yet:
BatchEE (2nd month)
Ignite
Kalumet
Kylin
Ranger
Sentry
Streams
Thanks,
John
On Mon, Feb 23, 2015 at 5:54 PM John D. Ament wrote:
> Howdy ya'll
>
>
> Trying to get an early start on the nex
+1 (binding)
Thanks everybody for your contributions to this proposal. Particularly
Lewis John Mcgibbney for taking care of the VOTE. I still need to
catch-up my mail of the last two vacations weeks to get an overview of
the latest discussions.
On 27/02/15 20:19, Lewis John Mcgibbney wrote
Question: I know I've seen this discussed here before, and in any case, you
guys are the best source for an answer:
Can we have GPL code in a repository as long as that is not distributed with
the product in a 'official' release?
Thanks a lot,
Julian
This message and any attachment are int
Hi Julian,
the code is not included in the project (just a reference) ?
Regards
JB
On 03/04/2015 02:44 PM, Julian Tenney wrote:
Question: I know I've seen this discussed here before, and in any case, you
guys are the best source for an answer:
Can we have GPL code in a repository as long as
On Wed, Mar 4, 2015 at 8:45 AM Julian Tenney
wrote:
> Question: I know I've seen this discussed here before, and in any case,
> you guys are the best source for an answer:
>
> Can we have GPL code in a repository as long as that is not distributed
> with the product in a 'official' release?
>
Th
It depends how you integrate it - you can't put LGPL or GPL stuff into
distributions from Apache - and you can't really do a release that is
incomplete without it (e.g. "To make X work, download the GPL library
Y and put it into lib")
Optional dependencies (e.g. plugins) should however be fine to
An Apache project may not manage a codebase outside of Apache. Some people
who happen to be members of an Apache community can maintain code outside
of Apache, if they are very clear in distinguishing; it must not be a
product of the project. See 'Apache Extras'.
On Wed, Mar 4, 2015 at 8:46 AM, Je
Thanks.
-Original Message-
From: Stian Soiland-Reyes [mailto:st...@apache.org]
Sent: 04 March 2015 15:14
To: general@incubator.apache.org
Subject: Re: GPL Code in GitHub
It depends how you integrate it - you can't put LGPL or GPL stuff into
distributions from Apache - and you can't real
Exactly, that's why I asked ;)
Just to be sure, else it's an issue IMHO.
Regards
JB
On 03/04/2015 04:14 PM, Benson Margulies wrote:
An Apache project may not manage a codebase outside of Apache. Some people
who happen to be members of an Apache community can maintain code outside
of Apache, if
We have two things that are GPL: one is optional, I don't have any problem with
that. I'm trying to get a bit more understanding of the other one!
But the point is taken: if that component is needed to make a certain function
work, and that function is considered a central part of the software (
On Wed, Mar 4, 2015 at 10:23 AM Julian Tenney <
julian.ten...@nottingham.ac.uk> wrote:
> We have two things that are GPL: one is optional, I don't have any problem
> with that. I'm trying to get a bit more understanding of the other one!
>
> But the point is taken: if that component is needed to m
> The following should help the developer understand why we can't accept GPL
> code in Apache projects:
The question is more about when does 'distribution' happen? When you put
something in your github? Or when you make a release and the files associated
with that release?
-Original Messag
I notice that apache-extras is now forwarding to Any23. Is that on purpose?
On Wed, Mar 4, 2015 at 10:15 AM Benson Margulies
wrote:
> An Apache project may not manage a codebase outside of Apache. Some people
> who happen to be members of an Apache community can maintain code outside
> of Apach
That must be a configuration error for http://www.apache-extras.org/
http://apache-extras.org/ redirect correctly to
https://code.google.com/a/apache-extras.org/hosting/
I've raised it as https://issues.apache.org/jira/browse/INFRA-9229
On 4 March 2015 at 15:26, John D. Ament wrote:
> I notice
I have a feeling it is some alternative authentication thing. It's optional, to
make the project work under certain circumstances.
-Original Message-
From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net]
Sent: 04 March 2015 13:47
To: general@incubator.apache.org
Subject: Re: GPL Code in
Releases explained here:
https://www.apache.org/dev/release.html
Basically putting into git/svn is not a release - but as anyone
(practically any committer) can propose a release candidate for voting
based on the code in the source code repository, it should still be
code that is distributable un
There's not strictly a legal problem with the GPL-using code to be in
Apache's source code repository (and itself be under the Apache
license) - but due to the 'viral' nature of GPL, any compiled products
become GPL as well.
For LGPL dependencies this is less of a worry - but still LGPL comes
with
It provides some alternative authentication I think. It's not mine: I found it
there and needed to check out licensing issues etc. Most of it, in fact can be
deleted.
But the point " There cannot be any GPL code in an Apache repository or in an
Apache release" is the stance we will take. It's s
Thanks to everyone for their contributions. The key uncertainty is whether GPL
code in the github is problematic, and the answer is 'yes'.
I wrote the following back to our own lists:
"The whole reason to do Apache license is to make it super-crystal clear that
this code is absolutely fine fo
In *github* you should not be worried about GPL code. In git.apache.org you
should. (Apache's git repos are mirrored back again to github.com/apache
but that is another matter)
Apologies for not knowing your context..
If you are staging the github repos to move them into Apache, then I would
remo
OK, we are Xerte Project, we make multimedia authoring tools for educators -
it's a successful project. Last year we decided we wanted to transition
stewardship of the software from University of Nottingham, where I work, to a
foundation. We are working through the incubation process at the Aper
On Mon, Mar 2, 2015 at 5:31 PM, Roman Shaposhnik wrote:
> At this point, I would like to open this document for soliciting as
> wide a feedback as possible. I would like to especially request
> attention of the ASF board members who asked for this type of
> a document to be available.
As a direct
On Wed, Mar 4, 2015 at 1:12 PM, Doug Cutting wrote:
> On Mon, Mar 2, 2015 at 5:31 PM, Roman Shaposhnik wrote:
> > At this point, I would like to open this document for soliciting as
> > wide a feedback as possible. I would like to especially request
> > attention of the ASF board members who ask
On 03/04/2015 01:41 PM, Benson Margulies wrote:
On Wed, Mar 4, 2015 at 1:12 PM, Doug Cutting mailto:cutt...@apache.org>> wrote:
On Mon, Mar 2, 2015 at 5:31 PM, Roman Shaposhnik mailto:r...@apache.org>> wrote:
> At this point, I would like to open this document for soliciting as
>
The bylaws don't grok the idea of a "provisional" PMC; it either
is one, or it isn't. So whether we call it provisional or not,
legally we need to understand whether we actually want it
as a real, official PMC or not.
And if we do, what, again, does the "provisional" qualifier really
mean?
> On M
And with a major assist from Humbledooh, Marvin is back up
and running!
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
On Wed, Mar 4, 2015 at 12:30 PM, Jim Jagielski wrote:
> And with a major assist from Humbledooh, Marvin is back up
> and running!
Go go go the-other-marvin!
Thanks Jim and Daniel!
-- the other-other-Marvin
-
To unsubscribe, e-
On Wed, Mar 4, 2015 at 3:34 PM Marvin Humphrey
wrote:
> On Wed, Mar 4, 2015 at 12:30 PM, Jim Jagielski wrote:
> > And with a major assist from Humbledooh, Marvin is back up
> > and running!
>
> Go go go the-other-marvin!
>
> Thanks Jim and Daniel!
>
> -- the other-other-Marvin
>
Great news, we
Hi general@,
I am bringing this VOTE a a close. We have the following RESULT to report.
[13] +1 I am happy with Commons RDF entering incubation
Alan D. Cabrera
Chris Mattmann*
Benedikt Ritter
Lewis J. McGibbney*
John D. Ament (Gary is now on board as mentor)
Rob Vesse
Hadrian Zbarcea
Sergio Ferná
Hi all,
The Apache Lens team is proud to announce the release of Apache Lens
2.0.1-beta-incutaing. This is the first release of Apache Lens.
Apache Lens provides an Unified Analytics interface. Lens aims to cut the
Data Analytics silos by providing a single view of data across multiple
tiered dat
On Thursday, March 5, 2015, Lewis John Mcgibbney
wrote:
> Hi general@,
>
> I am bringing this VOTE a a close. We have the following RESULT to report.
>
> [13] +1 I am happy with Commons RDF entering incubation
> Alan D. Cabrera
> Chris Mattmann*
> Benedikt Ritter
> Lewis J. McGibbney*
> John D. A
31 matches
Mail list logo