You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Jim Jagielski <ji...@jaguNET.com> on 2013/11/04 21:25:22 UTC
Re: Code import for Apache Accumulo
+1
On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
> Hi Josh:
>
> Separate repo (or not), release cycles, etc are project decisions.
>
> As far as importation of the code; it almost certainly needs to go
> through IP Clearance.
> http://incubator.apache.org/ip-clearance/
>
> If you have questions or need help with that process, don't hesitate to ask.
>
> --David
>
> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org> wrote:
>> Hi,
>>
>> Over at Apache Accumulo, we just got a nice bit of code that
>> integrates the R programming language (via RStudio) with Accumulo.
>> This was done completely by the community (non-committers) and we're
>> trying to figure out what's best for it and where it can live.
>>
>> The general consensus for us is that we would want to import it into
>> it's own repository (treat it as a contrib-project) since Accumulo has
>> no need to depend on it and thus it can be versioned at its own pace.
>>
>> The contributors are currently working on ICLA/CCLA forms, but I
>> wanted to see what else we (the Accumulo PMC) would need to do to
>> import this code.
>>
>> Thanks!
>>
>> - Josh
>>
>> ---------------------------------------------------------------------
>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
Although good to know historical context, there isn't any ambition to do a
split/incubation now or in the future unless it's necessary. No diploid
present yet.
On Sat, Nov 9, 2013 at 10:00 AM, Benson Margulies <bi...@gmail.com>wrote:
> On Sat, Nov 9, 2013 at 9:15 AM, Eric Whyne <er...@gmail.com> wrote:
> > Josh,
> > That looks like a great plan. I agree with your thoughts on incubation
> and
> > governance and have no concerns with your suggested path.
>
> One footnote. The board has, in the past, approved 'meiosis' of TLP's.
> Imagine that you accept the code as a contribution, and some of the
> people involved are eventually voted onto the PMC here. If there is a
> large enough, experienced enough, group that wishes to split off down
> the line, they might not have to go through the incubator. I really
> don't recommend _planning on that_, I suspect that such a plan would
> receive unfavorable reviews. I think it's fine to accept their
> contribution, let them come up to speed as committers and PMC members,
> and just know that there are various options down the line.
>
> >
> > R/
> > Eric
> >
> >
> > On Fri, Nov 8, 2013 at 10:34 PM, Josh Elser <jo...@gmail.com>
> wrote:
> >
> >> (removing general@incubator because we don't need to keep spamming them
> >> right now)
> >>
> >> First, I talked to Benson who cleared up some confusion that I had.
> >>
> >> "The question is the governance. If you're willing to adopt these people
> >> as part of your community, you can do that. If your community chooses to
> >> organize its code in two git repos, you can do that. What you can't do
> is
> >> create an umbrella in which they are a separate self-governing thing
> inside
> >> your community. The accumulo PMC can even grant them commit to a new
> repo,
> >> I think, in the same way that various communities grant commit access to
> >> svn branches as part of their process of joining up with you."
> >>
> >> In short, we can bring in raccumulo to Accumulo under our "governance".
> If
> >> at some point raccumulo grows into its own community and wants to have
> its
> >> own governance, it would have to go through incubator.
> >>
> >> To me, it seems like incubator at this point would be premature (as
> >> raccumulo is very tied to Accumulo and all interested parties so far are
> >> from one company); however, I'm not one to tell you that you can't go
> >> through incubation on your own.
> >>
> >> As such, the best thing seems to me to bring in raccumulo under Accumulo
> >> governance. To make this actually happen, the Accumulo PMC need to have
> a
> >> vote as to whether or not we should do this.
> >>
> >> PMC -- is there more discussion that wants to be had before moving to a
> >> vote on the matter?
> >>
> >> Eric + others -- any concerns with the path I've suggested?
> >>
> >>
> >> On 11/4/13, 9:37 PM, Eric Whyne wrote:
> >>
> >>> If we eventually get the code hosted on
> >>> https://git-wip-us.apache.org/repos/asf it should be no problem to
> >>> propagate updates to or from the github page, depending on how things
> >>> worked out. This model seemed to make sense at the time. I had noticed
> >>> that
> >>> the accumulo core was doing the same thing. This also had the added
> >>> benefit
> >>> of having a place where the code could be subject to public scrutiny
> and
> >>> version controlled as we got it to an acceptable state. I noticed some
> >>> notes in the apache documents about coding standards and there was the
> >>> whole licensing concern etc... There has already been some
> modification of
> >>> the code since Aaron uploaded the .tgz here
> >>> https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
> >>> adding documentation.
> >>>
> >>> Sub-project is identified as an incubation graduation status. I think
> in
> >>> accumulo project vocabulary sub-projects are contrib projects? Am I
> right
> >>> to think this?
> >>>
> >>> I think you had offered to help kick off incubation. Is that the right
> >>> path
> >>> to a contrib project or is there a different way to get there from
> here?
> >>>
> >>> R/
> >>> Eric
> >>>
> >>>
> >>>
> >>> On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com>
> wrote:
> >>>
> >>>
> >>>>
> >>>> On 11/4/13, 8:45 PM, Eric Whyne wrote:
> >>>>
> >>>> I just scanned through the ip-clearance page and came away a bit
> >>>>> confused
> >>>>> after reading this sentence.
> >>>>> "*This form is not for new projects.* This is for projects and PMCs
> that
> >>>>>
> >>>>> have already been created and are receiving a code donation into an
> >>>>> existing codebase."
> >>>>>
> >>>>> We've brought raccumulo out of our internal repos and are now
> hosting it
> >>>>> publicly here. The plan is for this to be it's new home.
> >>>>> https://github.com/DataTacticsCorp/raccumulo
> >>>>>
> >>>>>
> >>>> Uhh... what? I thought this entire discussion was that you wanted
> >>>> raccumulo to be a part of Apache Accumulo. If you're planning to host
> it
> >>>> on
> >>>> your company's Github page, why are we having this discussion?
> >>>>
> >>>>
> >>>> Developer ICLAs are complete and filed with secretary@apache
> >>>>
> >>>>> Data Tactics CCLA is complete and filed with secretary@apache
> >>>>>
> >>>>> A good goal seems to be having the project included as a contrib
> project
> >>>>> here:
> >>>>> http://accumulo.apache.org/contrib.html
> >>>>>
> >>>>>
> >>>> Again, I'm confused about your Github comment *and* having it be a
> >>>> contrib
> >>>> (sub project) to Accumulo.
> >>>>
> >>>>
> >>>>
> >>>> Some of my most recent questions:
> >>>>> Of course, the big question, what is the "apache way" to do that? We
> >>>>> want
> >>>>> to do that, we're learning the process and we have more code we want
> to
> >>>>> donate to the community.
> >>>>>
> >>>>>
> >>>> "The Apache Way" can be summed up by (taken from
> http://www.apache.org/
> >>>> foundation/how-it-works.html):
> >>>>
> >>>> - collaborative software development
> >>>> - commercial-friendly standard license
> >>>> - consistently high quality software
> >>>> - respectful, honest, technical-based interaction
> >>>> - faithful implementation of standards
> >>>> - security as a mandatory feature
> >>>>
> >>>> You can think of it as guidelines and best practices designed to help
> you
> >>>> grow communities around software projects.
> >>>>
> >>>>
> >>>> Is it ip-clearance, since it's a large code donation to an apache
> >>>> project?
> >>>>
> >>>>>
> >>>>>
> >>>> This is a prerequisite to inclusion into the ASF.
> >>>>
> >>>>
> >>>> Is it incubation as a sub-project? If incubation is the right way,
> >>>> would
> >>>>
> >>>>> it
> >>>>> preclude initiating the ip-clearance now?
> >>>>>
> >>>>>
> >>>> Incubation would also require IP clearance (as the ASF would still
> hold
> >>>> the copyright). Incubation != sub-project, however sub-project
> sometimes
> >>>> leads into incubation as their own project (e.g. HBase, Hive, Pig,
> >>>> ZooKeeper to name a few). This typically depends on how the top-level
> >>>> project wants to "do business".
> >>>>
> >>>>
> >>>>
> >>>> R/
> >>>>> Eric
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
> >>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
> >>>>>
> >>>>> +1
> >>>>>
> >>>>>>
> >>>>>> Sent from my iPhone
> >>>>>>
> >>>>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
> >>>>>>>>
> >>>>>>>> Hi Josh:
> >>>>>>>>
> >>>>>>>> Separate repo (or not), release cycles, etc are project decisions.
> >>>>>>>>
> >>>>>>>> As far as importation of the code; it almost certainly needs to go
> >>>>>>>> through IP Clearance.
> >>>>>>>> http://incubator.apache.org/ip-clearance/
> >>>>>>>>
> >>>>>>>> If you have questions or need help with that process, don't
> hesitate
> >>>>>>>> to
> >>>>>>>>
> >>>>>>>> ask.
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>> --David
> >>>>>>>>
> >>>>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <elserj@apache.org
> >
> >>>>>>>>
> >>>>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>
> >>>>>> Hi,
> >>>>>>>
> >>>>>>>>
> >>>>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
> >>>>>>>>> integrates the R programming language (via RStudio) with
> Accumulo.
> >>>>>>>>> This was done completely by the community (non-committers) and
> we're
> >>>>>>>>> trying to figure out what's best for it and where it can live.
> >>>>>>>>>
> >>>>>>>>> The general consensus for us is that we would want to import it
> into
> >>>>>>>>> it's own repository (treat it as a contrib-project) since
> Accumulo
> >>>>>>>>> has
> >>>>>>>>> no need to depend on it and thus it can be versioned at its own
> >>>>>>>>> pace.
> >>>>>>>>>
> >>>>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
> >>>>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
> >>>>>>>>> import this code.
> >>>>>>>>>
> >>>>>>>>> Thanks!
> >>>>>>>>>
> >>>>>>>>> - Josh
> >>>>>>>>>
> >>>>>>>>> ------------------------------------------------------------
> >>>>>>>>> ---------
> >>>>>>>>> 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: Code import for Apache Accumulo
Posted by Benson Margulies <bi...@gmail.com>.
On Sat, Nov 9, 2013 at 9:15 AM, Eric Whyne <er...@gmail.com> wrote:
> Josh,
> That looks like a great plan. I agree with your thoughts on incubation and
> governance and have no concerns with your suggested path.
One footnote. The board has, in the past, approved 'meiosis' of TLP's.
Imagine that you accept the code as a contribution, and some of the
people involved are eventually voted onto the PMC here. If there is a
large enough, experienced enough, group that wishes to split off down
the line, they might not have to go through the incubator. I really
don't recommend _planning on that_, I suspect that such a plan would
receive unfavorable reviews. I think it's fine to accept their
contribution, let them come up to speed as committers and PMC members,
and just know that there are various options down the line.
>
> R/
> Eric
>
>
> On Fri, Nov 8, 2013 at 10:34 PM, Josh Elser <jo...@gmail.com> wrote:
>
>> (removing general@incubator because we don't need to keep spamming them
>> right now)
>>
>> First, I talked to Benson who cleared up some confusion that I had.
>>
>> "The question is the governance. If you're willing to adopt these people
>> as part of your community, you can do that. If your community chooses to
>> organize its code in two git repos, you can do that. What you can't do is
>> create an umbrella in which they are a separate self-governing thing inside
>> your community. The accumulo PMC can even grant them commit to a new repo,
>> I think, in the same way that various communities grant commit access to
>> svn branches as part of their process of joining up with you."
>>
>> In short, we can bring in raccumulo to Accumulo under our "governance". If
>> at some point raccumulo grows into its own community and wants to have its
>> own governance, it would have to go through incubator.
>>
>> To me, it seems like incubator at this point would be premature (as
>> raccumulo is very tied to Accumulo and all interested parties so far are
>> from one company); however, I'm not one to tell you that you can't go
>> through incubation on your own.
>>
>> As such, the best thing seems to me to bring in raccumulo under Accumulo
>> governance. To make this actually happen, the Accumulo PMC need to have a
>> vote as to whether or not we should do this.
>>
>> PMC -- is there more discussion that wants to be had before moving to a
>> vote on the matter?
>>
>> Eric + others -- any concerns with the path I've suggested?
>>
>>
>> On 11/4/13, 9:37 PM, Eric Whyne wrote:
>>
>>> If we eventually get the code hosted on
>>> https://git-wip-us.apache.org/repos/asf it should be no problem to
>>> propagate updates to or from the github page, depending on how things
>>> worked out. This model seemed to make sense at the time. I had noticed
>>> that
>>> the accumulo core was doing the same thing. This also had the added
>>> benefit
>>> of having a place where the code could be subject to public scrutiny and
>>> version controlled as we got it to an acceptable state. I noticed some
>>> notes in the apache documents about coding standards and there was the
>>> whole licensing concern etc... There has already been some modification of
>>> the code since Aaron uploaded the .tgz here
>>> https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
>>> adding documentation.
>>>
>>> Sub-project is identified as an incubation graduation status. I think in
>>> accumulo project vocabulary sub-projects are contrib projects? Am I right
>>> to think this?
>>>
>>> I think you had offered to help kick off incubation. Is that the right
>>> path
>>> to a contrib project or is there a different way to get there from here?
>>>
>>> R/
>>> Eric
>>>
>>>
>>>
>>> On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com> wrote:
>>>
>>>
>>>>
>>>> On 11/4/13, 8:45 PM, Eric Whyne wrote:
>>>>
>>>> I just scanned through the ip-clearance page and came away a bit
>>>>> confused
>>>>> after reading this sentence.
>>>>> "*This form is not for new projects.* This is for projects and PMCs that
>>>>>
>>>>> have already been created and are receiving a code donation into an
>>>>> existing codebase."
>>>>>
>>>>> We've brought raccumulo out of our internal repos and are now hosting it
>>>>> publicly here. The plan is for this to be it's new home.
>>>>> https://github.com/DataTacticsCorp/raccumulo
>>>>>
>>>>>
>>>> Uhh... what? I thought this entire discussion was that you wanted
>>>> raccumulo to be a part of Apache Accumulo. If you're planning to host it
>>>> on
>>>> your company's Github page, why are we having this discussion?
>>>>
>>>>
>>>> Developer ICLAs are complete and filed with secretary@apache
>>>>
>>>>> Data Tactics CCLA is complete and filed with secretary@apache
>>>>>
>>>>> A good goal seems to be having the project included as a contrib project
>>>>> here:
>>>>> http://accumulo.apache.org/contrib.html
>>>>>
>>>>>
>>>> Again, I'm confused about your Github comment *and* having it be a
>>>> contrib
>>>> (sub project) to Accumulo.
>>>>
>>>>
>>>>
>>>> Some of my most recent questions:
>>>>> Of course, the big question, what is the "apache way" to do that? We
>>>>> want
>>>>> to do that, we're learning the process and we have more code we want to
>>>>> donate to the community.
>>>>>
>>>>>
>>>> "The Apache Way" can be summed up by (taken from http://www.apache.org/
>>>> foundation/how-it-works.html):
>>>>
>>>> - collaborative software development
>>>> - commercial-friendly standard license
>>>> - consistently high quality software
>>>> - respectful, honest, technical-based interaction
>>>> - faithful implementation of standards
>>>> - security as a mandatory feature
>>>>
>>>> You can think of it as guidelines and best practices designed to help you
>>>> grow communities around software projects.
>>>>
>>>>
>>>> Is it ip-clearance, since it's a large code donation to an apache
>>>> project?
>>>>
>>>>>
>>>>>
>>>> This is a prerequisite to inclusion into the ASF.
>>>>
>>>>
>>>> Is it incubation as a sub-project? If incubation is the right way,
>>>> would
>>>>
>>>>> it
>>>>> preclude initiating the ip-clearance now?
>>>>>
>>>>>
>>>> Incubation would also require IP clearance (as the ASF would still hold
>>>> the copyright). Incubation != sub-project, however sub-project sometimes
>>>> leads into incubation as their own project (e.g. HBase, Hive, Pig,
>>>> ZooKeeper to name a few). This typically depends on how the top-level
>>>> project wants to "do business".
>>>>
>>>>
>>>>
>>>> R/
>>>>> Eric
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
>>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>>
>>>>> +1
>>>>>
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com>
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>>>>>
>>>>>>>> Hi Josh:
>>>>>>>>
>>>>>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>>>>>
>>>>>>>> As far as importation of the code; it almost certainly needs to go
>>>>>>>> through IP Clearance.
>>>>>>>> http://incubator.apache.org/ip-clearance/
>>>>>>>>
>>>>>>>> If you have questions or need help with that process, don't hesitate
>>>>>>>> to
>>>>>>>>
>>>>>>>> ask.
>>>>>>>
>>>>>>
>>>>>>
>>>>>>> --David
>>>>>>>>
>>>>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>
>>>>>> Hi,
>>>>>>>
>>>>>>>>
>>>>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>>>>>> This was done completely by the community (non-committers) and we're
>>>>>>>>> trying to figure out what's best for it and where it can live.
>>>>>>>>>
>>>>>>>>> The general consensus for us is that we would want to import it into
>>>>>>>>> it's own repository (treat it as a contrib-project) since Accumulo
>>>>>>>>> has
>>>>>>>>> no need to depend on it and thus it can be versioned at its own
>>>>>>>>> pace.
>>>>>>>>>
>>>>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>>>>>> import this code.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> - Josh
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------
>>>>>>>>> ---------
>>>>>>>>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
Josh,
That looks like a great plan. I agree with your thoughts on incubation and
governance and have no concerns with your suggested path.
R/
Eric
On Fri, Nov 8, 2013 at 10:34 PM, Josh Elser <jo...@gmail.com> wrote:
> (removing general@incubator because we don't need to keep spamming them
> right now)
>
> First, I talked to Benson who cleared up some confusion that I had.
>
> "The question is the governance. If you're willing to adopt these people
> as part of your community, you can do that. If your community chooses to
> organize its code in two git repos, you can do that. What you can't do is
> create an umbrella in which they are a separate self-governing thing inside
> your community. The accumulo PMC can even grant them commit to a new repo,
> I think, in the same way that various communities grant commit access to
> svn branches as part of their process of joining up with you."
>
> In short, we can bring in raccumulo to Accumulo under our "governance". If
> at some point raccumulo grows into its own community and wants to have its
> own governance, it would have to go through incubator.
>
> To me, it seems like incubator at this point would be premature (as
> raccumulo is very tied to Accumulo and all interested parties so far are
> from one company); however, I'm not one to tell you that you can't go
> through incubation on your own.
>
> As such, the best thing seems to me to bring in raccumulo under Accumulo
> governance. To make this actually happen, the Accumulo PMC need to have a
> vote as to whether or not we should do this.
>
> PMC -- is there more discussion that wants to be had before moving to a
> vote on the matter?
>
> Eric + others -- any concerns with the path I've suggested?
>
>
> On 11/4/13, 9:37 PM, Eric Whyne wrote:
>
>> If we eventually get the code hosted on
>> https://git-wip-us.apache.org/repos/asf it should be no problem to
>> propagate updates to or from the github page, depending on how things
>> worked out. This model seemed to make sense at the time. I had noticed
>> that
>> the accumulo core was doing the same thing. This also had the added
>> benefit
>> of having a place where the code could be subject to public scrutiny and
>> version controlled as we got it to an acceptable state. I noticed some
>> notes in the apache documents about coding standards and there was the
>> whole licensing concern etc... There has already been some modification of
>> the code since Aaron uploaded the .tgz here
>> https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
>> adding documentation.
>>
>> Sub-project is identified as an incubation graduation status. I think in
>> accumulo project vocabulary sub-projects are contrib projects? Am I right
>> to think this?
>>
>> I think you had offered to help kick off incubation. Is that the right
>> path
>> to a contrib project or is there a different way to get there from here?
>>
>> R/
>> Eric
>>
>>
>>
>> On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com> wrote:
>>
>>
>>>
>>> On 11/4/13, 8:45 PM, Eric Whyne wrote:
>>>
>>> I just scanned through the ip-clearance page and came away a bit
>>>> confused
>>>> after reading this sentence.
>>>> "*This form is not for new projects.* This is for projects and PMCs that
>>>>
>>>> have already been created and are receiving a code donation into an
>>>> existing codebase."
>>>>
>>>> We've brought raccumulo out of our internal repos and are now hosting it
>>>> publicly here. The plan is for this to be it's new home.
>>>> https://github.com/DataTacticsCorp/raccumulo
>>>>
>>>>
>>> Uhh... what? I thought this entire discussion was that you wanted
>>> raccumulo to be a part of Apache Accumulo. If you're planning to host it
>>> on
>>> your company's Github page, why are we having this discussion?
>>>
>>>
>>> Developer ICLAs are complete and filed with secretary@apache
>>>
>>>> Data Tactics CCLA is complete and filed with secretary@apache
>>>>
>>>> A good goal seems to be having the project included as a contrib project
>>>> here:
>>>> http://accumulo.apache.org/contrib.html
>>>>
>>>>
>>> Again, I'm confused about your Github comment *and* having it be a
>>> contrib
>>> (sub project) to Accumulo.
>>>
>>>
>>>
>>> Some of my most recent questions:
>>>> Of course, the big question, what is the "apache way" to do that? We
>>>> want
>>>> to do that, we're learning the process and we have more code we want to
>>>> donate to the community.
>>>>
>>>>
>>> "The Apache Way" can be summed up by (taken from http://www.apache.org/
>>> foundation/how-it-works.html):
>>>
>>> - collaborative software development
>>> - commercial-friendly standard license
>>> - consistently high quality software
>>> - respectful, honest, technical-based interaction
>>> - faithful implementation of standards
>>> - security as a mandatory feature
>>>
>>> You can think of it as guidelines and best practices designed to help you
>>> grow communities around software projects.
>>>
>>>
>>> Is it ip-clearance, since it's a large code donation to an apache
>>> project?
>>>
>>>>
>>>>
>>> This is a prerequisite to inclusion into the ASF.
>>>
>>>
>>> Is it incubation as a sub-project? If incubation is the right way,
>>> would
>>>
>>>> it
>>>> preclude initiating the ip-clearance now?
>>>>
>>>>
>>> Incubation would also require IP clearance (as the ASF would still hold
>>> the copyright). Incubation != sub-project, however sub-project sometimes
>>> leads into incubation as their own project (e.g. HBase, Hive, Pig,
>>> ZooKeeper to name a few). This typically depends on how the top-level
>>> project wants to "do business".
>>>
>>>
>>>
>>> R/
>>>> Eric
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
>>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>>
>>>> +1
>>>>
>>>>>
>>>>> Sent from my iPhone
>>>>>
>>>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> +1
>>>>>>
>>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>>>>
>>>>>>> Hi Josh:
>>>>>>>
>>>>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>>>>
>>>>>>> As far as importation of the code; it almost certainly needs to go
>>>>>>> through IP Clearance.
>>>>>>> http://incubator.apache.org/ip-clearance/
>>>>>>>
>>>>>>> If you have questions or need help with that process, don't hesitate
>>>>>>> to
>>>>>>>
>>>>>>> ask.
>>>>>>
>>>>>
>>>>>
>>>>>> --David
>>>>>>>
>>>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>>>>>>>
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>
>>>>>>
>>>>> Hi,
>>>>>>
>>>>>>>
>>>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>>>>> This was done completely by the community (non-committers) and we're
>>>>>>>> trying to figure out what's best for it and where it can live.
>>>>>>>>
>>>>>>>> The general consensus for us is that we would want to import it into
>>>>>>>> it's own repository (treat it as a contrib-project) since Accumulo
>>>>>>>> has
>>>>>>>> no need to depend on it and thus it can be versioned at its own
>>>>>>>> pace.
>>>>>>>>
>>>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>>>>> import this code.
>>>>>>>>
>>>>>>>> Thanks!
>>>>>>>>
>>>>>>>> - Josh
>>>>>>>>
>>>>>>>> ------------------------------------------------------------
>>>>>>>> ---------
>>>>>>>> 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: Code import for Apache Accumulo
Posted by Josh Elser <jo...@gmail.com>.
(removing general@incubator because we don't need to keep spamming them
right now)
First, I talked to Benson who cleared up some confusion that I had.
"The question is the governance. If you're willing to adopt these people
as part of your community, you can do that. If your community chooses to
organize its code in two git repos, you can do that. What you can't do
is create an umbrella in which they are a separate self-governing thing
inside your community. The accumulo PMC can even grant them commit to a
new repo, I think, in the same way that various communities grant commit
access to svn branches as part of their process of joining up with you."
In short, we can bring in raccumulo to Accumulo under our "governance".
If at some point raccumulo grows into its own community and wants to
have its own governance, it would have to go through incubator.
To me, it seems like incubator at this point would be premature (as
raccumulo is very tied to Accumulo and all interested parties so far are
from one company); however, I'm not one to tell you that you can't go
through incubation on your own.
As such, the best thing seems to me to bring in raccumulo under Accumulo
governance. To make this actually happen, the Accumulo PMC need to have
a vote as to whether or not we should do this.
PMC -- is there more discussion that wants to be had before moving to a
vote on the matter?
Eric + others -- any concerns with the path I've suggested?
On 11/4/13, 9:37 PM, Eric Whyne wrote:
> If we eventually get the code hosted on
> https://git-wip-us.apache.org/repos/asf it should be no problem to
> propagate updates to or from the github page, depending on how things
> worked out. This model seemed to make sense at the time. I had noticed that
> the accumulo core was doing the same thing. This also had the added benefit
> of having a place where the code could be subject to public scrutiny and
> version controlled as we got it to an acceptable state. I noticed some
> notes in the apache documents about coding standards and there was the
> whole licensing concern etc... There has already been some modification of
> the code since Aaron uploaded the .tgz here
> https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
> adding documentation.
>
> Sub-project is identified as an incubation graduation status. I think in
> accumulo project vocabulary sub-projects are contrib projects? Am I right
> to think this?
>
> I think you had offered to help kick off incubation. Is that the right path
> to a contrib project or is there a different way to get there from here?
>
> R/
> Eric
>
>
>
> On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com> wrote:
>
>>
>>
>> On 11/4/13, 8:45 PM, Eric Whyne wrote:
>>
>>> I just scanned through the ip-clearance page and came away a bit confused
>>> after reading this sentence.
>>> "*This form is not for new projects.* This is for projects and PMCs that
>>>
>>> have already been created and are receiving a code donation into an
>>> existing codebase."
>>>
>>> We've brought raccumulo out of our internal repos and are now hosting it
>>> publicly here. The plan is for this to be it's new home.
>>> https://github.com/DataTacticsCorp/raccumulo
>>>
>>
>> Uhh... what? I thought this entire discussion was that you wanted
>> raccumulo to be a part of Apache Accumulo. If you're planning to host it on
>> your company's Github page, why are we having this discussion?
>>
>>
>> Developer ICLAs are complete and filed with secretary@apache
>>> Data Tactics CCLA is complete and filed with secretary@apache
>>>
>>> A good goal seems to be having the project included as a contrib project
>>> here:
>>> http://accumulo.apache.org/contrib.html
>>>
>>
>> Again, I'm confused about your Github comment *and* having it be a contrib
>> (sub project) to Accumulo.
>>
>>
>>
>>> Some of my most recent questions:
>>> Of course, the big question, what is the "apache way" to do that? We want
>>> to do that, we're learning the process and we have more code we want to
>>> donate to the community.
>>>
>>
>> "The Apache Way" can be summed up by (taken from http://www.apache.org/
>> foundation/how-it-works.html):
>>
>> - collaborative software development
>> - commercial-friendly standard license
>> - consistently high quality software
>> - respectful, honest, technical-based interaction
>> - faithful implementation of standards
>> - security as a mandatory feature
>>
>> You can think of it as guidelines and best practices designed to help you
>> grow communities around software projects.
>>
>>
>> Is it ip-clearance, since it's a large code donation to an apache project?
>>>
>>
>> This is a prerequisite to inclusion into the ASF.
>>
>>
>> Is it incubation as a sub-project? If incubation is the right way, would
>>> it
>>> preclude initiating the ip-clearance now?
>>>
>>
>> Incubation would also require IP clearance (as the ASF would still hold
>> the copyright). Incubation != sub-project, however sub-project sometimes
>> leads into incubation as their own project (e.g. HBase, Hive, Pig,
>> ZooKeeper to name a few). This typically depends on how the top-level
>> project wants to "do business".
>>
>>
>>
>>> R/
>>> Eric
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
>>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>>
>>> +1
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>>>>>
>>>>> +1
>>>>>
>>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>>>
>>>>>> Hi Josh:
>>>>>>
>>>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>>>
>>>>>> As far as importation of the code; it almost certainly needs to go
>>>>>> through IP Clearance.
>>>>>> http://incubator.apache.org/ip-clearance/
>>>>>>
>>>>>> If you have questions or need help with that process, don't hesitate to
>>>>>>
>>>>> ask.
>>>>
>>>>>
>>>>>> --David
>>>>>>
>>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>>>>>>>
>>>>>> wrote:
>>>>
>>>>> Hi,
>>>>>>>
>>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>>>> This was done completely by the community (non-committers) and we're
>>>>>>> trying to figure out what's best for it and where it can live.
>>>>>>>
>>>>>>> The general consensus for us is that we would want to import it into
>>>>>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>>>>>> no need to depend on it and thus it can be versioned at its own pace.
>>>>>>>
>>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>>>> import this code.
>>>>>>>
>>>>>>> Thanks!
>>>>>>>
>>>>>>> - Josh
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
If we eventually get the code hosted on
https://git-wip-us.apache.org/repos/asf it should be no problem to
propagate updates to or from the github page, depending on how things
worked out. This model seemed to make sense at the time. I had noticed that
the accumulo core was doing the same thing. This also had the added benefit
of having a place where the code could be subject to public scrutiny and
version controlled as we got it to an acceptable state. I noticed some
notes in the apache documents about coding standards and there was the
whole licensing concern etc... There has already been some modification of
the code since Aaron uploaded the .tgz here
https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
adding documentation.
Sub-project is identified as an incubation graduation status. I think in
accumulo project vocabulary sub-projects are contrib projects? Am I right
to think this?
I think you had offered to help kick off incubation. Is that the right path
to a contrib project or is there a different way to get there from here?
R/
Eric
On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com> wrote:
>
>
> On 11/4/13, 8:45 PM, Eric Whyne wrote:
>
>> I just scanned through the ip-clearance page and came away a bit confused
>> after reading this sentence.
>> "*This form is not for new projects.* This is for projects and PMCs that
>>
>> have already been created and are receiving a code donation into an
>> existing codebase."
>>
>> We've brought raccumulo out of our internal repos and are now hosting it
>> publicly here. The plan is for this to be it's new home.
>> https://github.com/DataTacticsCorp/raccumulo
>>
>
> Uhh... what? I thought this entire discussion was that you wanted
> raccumulo to be a part of Apache Accumulo. If you're planning to host it on
> your company's Github page, why are we having this discussion?
>
>
> Developer ICLAs are complete and filed with secretary@apache
>> Data Tactics CCLA is complete and filed with secretary@apache
>>
>> A good goal seems to be having the project included as a contrib project
>> here:
>> http://accumulo.apache.org/contrib.html
>>
>
> Again, I'm confused about your Github comment *and* having it be a contrib
> (sub project) to Accumulo.
>
>
>
>> Some of my most recent questions:
>> Of course, the big question, what is the "apache way" to do that? We want
>> to do that, we're learning the process and we have more code we want to
>> donate to the community.
>>
>
> "The Apache Way" can be summed up by (taken from http://www.apache.org/
> foundation/how-it-works.html):
>
> - collaborative software development
> - commercial-friendly standard license
> - consistently high quality software
> - respectful, honest, technical-based interaction
> - faithful implementation of standards
> - security as a mandatory feature
>
> You can think of it as guidelines and best practices designed to help you
> grow communities around software projects.
>
>
> Is it ip-clearance, since it's a large code donation to an apache project?
>>
>
> This is a prerequisite to inclusion into the ASF.
>
>
> Is it incubation as a sub-project? If incubation is the right way, would
>> it
>> preclude initiating the ip-clearance now?
>>
>
> Incubation would also require IP clearance (as the ASF would still hold
> the copyright). Incubation != sub-project, however sub-project sometimes
> leads into incubation as their own project (e.g. HBase, Hive, Pig,
> ZooKeeper to name a few). This typically depends on how the top-level
> project wants to "do business".
>
>
>
>> R/
>> Eric
>>
>>
>>
>>
>>
>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> +1
>>>
>>> Sent from my iPhone
>>>
>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>>>>
>>>> +1
>>>>
>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>>
>>>>> Hi Josh:
>>>>>
>>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>>
>>>>> As far as importation of the code; it almost certainly needs to go
>>>>> through IP Clearance.
>>>>> http://incubator.apache.org/ip-clearance/
>>>>>
>>>>> If you have questions or need help with that process, don't hesitate to
>>>>>
>>>> ask.
>>>
>>>>
>>>>> --David
>>>>>
>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>>>>>>
>>>>> wrote:
>>>
>>>> Hi,
>>>>>>
>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>>> This was done completely by the community (non-committers) and we're
>>>>>> trying to figure out what's best for it and where it can live.
>>>>>>
>>>>>> The general consensus for us is that we would want to import it into
>>>>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>>>>> no need to depend on it and thus it can be versioned at its own pace.
>>>>>>
>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>>> import this code.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> - Josh
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
If we eventually get the code hosted on
https://git-wip-us.apache.org/repos/asf it should be no problem to
propagate updates to or from the github page, depending on how things
worked out. This model seemed to make sense at the time. I had noticed that
the accumulo core was doing the same thing. This also had the added benefit
of having a place where the code could be subject to public scrutiny and
version controlled as we got it to an acceptable state. I noticed some
notes in the apache documents about coding standards and there was the
whole licensing concern etc... There has already been some modification of
the code since Aaron uploaded the .tgz here
https://issues.apache.org/jira/browse/ACCUMULO-1804 Restructuring and
adding documentation.
Sub-project is identified as an incubation graduation status. I think in
accumulo project vocabulary sub-projects are contrib projects? Am I right
to think this?
I think you had offered to help kick off incubation. Is that the right path
to a contrib project or is there a different way to get there from here?
R/
Eric
On Mon, Nov 4, 2013 at 9:14 PM, Josh Elser <jo...@gmail.com> wrote:
>
>
> On 11/4/13, 8:45 PM, Eric Whyne wrote:
>
>> I just scanned through the ip-clearance page and came away a bit confused
>> after reading this sentence.
>> "*This form is not for new projects.* This is for projects and PMCs that
>>
>> have already been created and are receiving a code donation into an
>> existing codebase."
>>
>> We've brought raccumulo out of our internal repos and are now hosting it
>> publicly here. The plan is for this to be it's new home.
>> https://github.com/DataTacticsCorp/raccumulo
>>
>
> Uhh... what? I thought this entire discussion was that you wanted
> raccumulo to be a part of Apache Accumulo. If you're planning to host it on
> your company's Github page, why are we having this discussion?
>
>
> Developer ICLAs are complete and filed with secretary@apache
>> Data Tactics CCLA is complete and filed with secretary@apache
>>
>> A good goal seems to be having the project included as a contrib project
>> here:
>> http://accumulo.apache.org/contrib.html
>>
>
> Again, I'm confused about your Github comment *and* having it be a contrib
> (sub project) to Accumulo.
>
>
>
>> Some of my most recent questions:
>> Of course, the big question, what is the "apache way" to do that? We want
>> to do that, we're learning the process and we have more code we want to
>> donate to the community.
>>
>
> "The Apache Way" can be summed up by (taken from http://www.apache.org/
> foundation/how-it-works.html):
>
> - collaborative software development
> - commercial-friendly standard license
> - consistently high quality software
> - respectful, honest, technical-based interaction
> - faithful implementation of standards
> - security as a mandatory feature
>
> You can think of it as guidelines and best practices designed to help you
> grow communities around software projects.
>
>
> Is it ip-clearance, since it's a large code donation to an apache project?
>>
>
> This is a prerequisite to inclusion into the ASF.
>
>
> Is it incubation as a sub-project? If incubation is the right way, would
>> it
>> preclude initiating the ip-clearance now?
>>
>
> Incubation would also require IP clearance (as the ASF would still hold
> the copyright). Incubation != sub-project, however sub-project sometimes
> leads into incubation as their own project (e.g. HBase, Hive, Pig,
> ZooKeeper to name a few). This typically depends on how the top-level
> project wants to "do business".
>
>
>
>> R/
>> Eric
>>
>>
>>
>>
>>
>> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>>
>> +1
>>>
>>> Sent from my iPhone
>>>
>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>>>>
>>>> +1
>>>>
>>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>>
>>>>> Hi Josh:
>>>>>
>>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>>
>>>>> As far as importation of the code; it almost certainly needs to go
>>>>> through IP Clearance.
>>>>> http://incubator.apache.org/ip-clearance/
>>>>>
>>>>> If you have questions or need help with that process, don't hesitate to
>>>>>
>>>> ask.
>>>
>>>>
>>>>> --David
>>>>>
>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>>>>>>
>>>>> wrote:
>>>
>>>> Hi,
>>>>>>
>>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>>> This was done completely by the community (non-committers) and we're
>>>>>> trying to figure out what's best for it and where it can live.
>>>>>>
>>>>>> The general consensus for us is that we would want to import it into
>>>>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>>>>> no need to depend on it and thus it can be versioned at its own pace.
>>>>>>
>>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>>> import this code.
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> - Josh
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> 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: Code import for Apache Accumulo
Posted by Josh Elser <jo...@gmail.com>.
On 11/4/13, 8:45 PM, Eric Whyne wrote:
> I just scanned through the ip-clearance page and came away a bit confused
> after reading this sentence.
> "*This form is not for new projects.* This is for projects and PMCs that
> have already been created and are receiving a code donation into an
> existing codebase."
>
> We've brought raccumulo out of our internal repos and are now hosting it
> publicly here. The plan is for this to be it's new home.
> https://github.com/DataTacticsCorp/raccumulo
Uhh... what? I thought this entire discussion was that you wanted
raccumulo to be a part of Apache Accumulo. If you're planning to host it
on your company's Github page, why are we having this discussion?
> Developer ICLAs are complete and filed with secretary@apache
> Data Tactics CCLA is complete and filed with secretary@apache
>
> A good goal seems to be having the project included as a contrib project
> here:
> http://accumulo.apache.org/contrib.html
Again, I'm confused about your Github comment *and* having it be a
contrib (sub project) to Accumulo.
>
> Some of my most recent questions:
> Of course, the big question, what is the "apache way" to do that? We want
> to do that, we're learning the process and we have more code we want to
> donate to the community.
"The Apache Way" can be summed up by (taken from
http://www.apache.org/foundation/how-it-works.html):
- collaborative software development
- commercial-friendly standard license
- consistently high quality software
- respectful, honest, technical-based interaction
- faithful implementation of standards
- security as a mandatory feature
You can think of it as guidelines and best practices designed to help
you grow communities around software projects.
> Is it ip-clearance, since it's a large code donation to an apache project?
This is a prerequisite to inclusion into the ASF.
> Is it incubation as a sub-project? If incubation is the right way, would it
> preclude initiating the ip-clearance now?
Incubation would also require IP clearance (as the ASF would still hold
the copyright). Incubation != sub-project, however sub-project sometimes
leads into incubation as their own project (e.g. HBase, Hive, Pig,
ZooKeeper to name a few). This typically depends on how the top-level
project wants to "do business".
>
> R/
> Eric
>
>
>
>
>
> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> +1
>>
>> Sent from my iPhone
>>
>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>>>
>>> +1
>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>
>>>> Hi Josh:
>>>>
>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>
>>>> As far as importation of the code; it almost certainly needs to go
>>>> through IP Clearance.
>>>> http://incubator.apache.org/ip-clearance/
>>>>
>>>> If you have questions or need help with that process, don't hesitate to
>> ask.
>>>>
>>>> --David
>>>>
>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>> wrote:
>>>>> Hi,
>>>>>
>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>> This was done completely by the community (non-committers) and we're
>>>>> trying to figure out what's best for it and where it can live.
>>>>>
>>>>> The general consensus for us is that we would want to import it into
>>>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>>>> no need to depend on it and thus it can be versioned at its own pace.
>>>>>
>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>> import this code.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> - Josh
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Code import for Apache Accumulo
Posted by Josh Elser <jo...@gmail.com>.
On 11/4/13, 8:45 PM, Eric Whyne wrote:
> I just scanned through the ip-clearance page and came away a bit confused
> after reading this sentence.
> "*This form is not for new projects.* This is for projects and PMCs that
> have already been created and are receiving a code donation into an
> existing codebase."
>
> We've brought raccumulo out of our internal repos and are now hosting it
> publicly here. The plan is for this to be it's new home.
> https://github.com/DataTacticsCorp/raccumulo
Uhh... what? I thought this entire discussion was that you wanted
raccumulo to be a part of Apache Accumulo. If you're planning to host it
on your company's Github page, why are we having this discussion?
> Developer ICLAs are complete and filed with secretary@apache
> Data Tactics CCLA is complete and filed with secretary@apache
>
> A good goal seems to be having the project included as a contrib project
> here:
> http://accumulo.apache.org/contrib.html
Again, I'm confused about your Github comment *and* having it be a
contrib (sub project) to Accumulo.
>
> Some of my most recent questions:
> Of course, the big question, what is the "apache way" to do that? We want
> to do that, we're learning the process and we have more code we want to
> donate to the community.
"The Apache Way" can be summed up by (taken from
http://www.apache.org/foundation/how-it-works.html):
- collaborative software development
- commercial-friendly standard license
- consistently high quality software
- respectful, honest, technical-based interaction
- faithful implementation of standards
- security as a mandatory feature
You can think of it as guidelines and best practices designed to help
you grow communities around software projects.
> Is it ip-clearance, since it's a large code donation to an apache project?
This is a prerequisite to inclusion into the ASF.
> Is it incubation as a sub-project? If incubation is the right way, would it
> preclude initiating the ip-clearance now?
Incubation would also require IP clearance (as the ASF would still hold
the copyright). Incubation != sub-project, however sub-project sometimes
leads into incubation as their own project (e.g. HBase, Hive, Pig,
ZooKeeper to name a few). This typically depends on how the top-level
project wants to "do business".
>
> R/
> Eric
>
>
>
>
>
> On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> +1
>>
>> Sent from my iPhone
>>
>>> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>>>
>>> +1
>>>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>>>
>>>> Hi Josh:
>>>>
>>>> Separate repo (or not), release cycles, etc are project decisions.
>>>>
>>>> As far as importation of the code; it almost certainly needs to go
>>>> through IP Clearance.
>>>> http://incubator.apache.org/ip-clearance/
>>>>
>>>> If you have questions or need help with that process, don't hesitate to
>> ask.
>>>>
>>>> --David
>>>>
>>>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
>> wrote:
>>>>> Hi,
>>>>>
>>>>> Over at Apache Accumulo, we just got a nice bit of code that
>>>>> integrates the R programming language (via RStudio) with Accumulo.
>>>>> This was done completely by the community (non-committers) and we're
>>>>> trying to figure out what's best for it and where it can live.
>>>>>
>>>>> The general consensus for us is that we would want to import it into
>>>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>>>> no need to depend on it and thus it can be versioned at its own pace.
>>>>>
>>>>> The contributors are currently working on ICLA/CCLA forms, but I
>>>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>>>> import this code.
>>>>>
>>>>> Thanks!
>>>>>
>>>>> - Josh
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
I just scanned through the ip-clearance page and came away a bit confused
after reading this sentence.
"*This form is not for new projects.* This is for projects and PMCs that
have already been created and are receiving a code donation into an
existing codebase."
We've brought raccumulo out of our internal repos and are now hosting it
publicly here. The plan is for this to be it's new home.
https://github.com/DataTacticsCorp/raccumulo
Developer ICLAs are complete and filed with secretary@apache
Data Tactics CCLA is complete and filed with secretary@apache
A good goal seems to be having the project included as a contrib project
here:
http://accumulo.apache.org/contrib.html
Some of my most recent questions:
Of course, the big question, what is the "apache way" to do that? We want
to do that, we're learning the process and we have more code we want to
donate to the community.
Is it ip-clearance, since it's a large code donation to an apache project?
Is it incubation as a sub-project? If incubation is the right way, would it
preclude initiating the ip-clearance now?
R/
Eric
On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> +1
>
> Sent from my iPhone
>
> > On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
> >
> > +1
> >> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
> >>
> >> Hi Josh:
> >>
> >> Separate repo (or not), release cycles, etc are project decisions.
> >>
> >> As far as importation of the code; it almost certainly needs to go
> >> through IP Clearance.
> >> http://incubator.apache.org/ip-clearance/
> >>
> >> If you have questions or need help with that process, don't hesitate to
> ask.
> >>
> >> --David
> >>
> >>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
> wrote:
> >>> Hi,
> >>>
> >>> Over at Apache Accumulo, we just got a nice bit of code that
> >>> integrates the R programming language (via RStudio) with Accumulo.
> >>> This was done completely by the community (non-committers) and we're
> >>> trying to figure out what's best for it and where it can live.
> >>>
> >>> The general consensus for us is that we would want to import it into
> >>> it's own repository (treat it as a contrib-project) since Accumulo has
> >>> no need to depend on it and thus it can be versioned at its own pace.
> >>>
> >>> The contributors are currently working on ICLA/CCLA forms, but I
> >>> wanted to see what else we (the Accumulo PMC) would need to do to
> >>> import this code.
> >>>
> >>> Thanks!
> >>>
> >>> - Josh
> >>>
> >>> ---------------------------------------------------------------------
> >>> 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: Code import for Apache Accumulo
Posted by Eric Whyne <er...@gmail.com>.
I just scanned through the ip-clearance page and came away a bit confused
after reading this sentence.
"*This form is not for new projects.* This is for projects and PMCs that
have already been created and are receiving a code donation into an
existing codebase."
We've brought raccumulo out of our internal repos and are now hosting it
publicly here. The plan is for this to be it's new home.
https://github.com/DataTacticsCorp/raccumulo
Developer ICLAs are complete and filed with secretary@apache
Data Tactics CCLA is complete and filed with secretary@apache
A good goal seems to be having the project included as a contrib project
here:
http://accumulo.apache.org/contrib.html
Some of my most recent questions:
Of course, the big question, what is the "apache way" to do that? We want
to do that, we're learning the process and we have more code we want to
donate to the community.
Is it ip-clearance, since it's a large code donation to an apache project?
Is it incubation as a sub-project? If incubation is the right way, would it
preclude initiating the ip-clearance now?
R/
Eric
On Mon, Nov 4, 2013 at 3:26 PM, Mattmann, Chris A (398J) <
chris.a.mattmann@jpl.nasa.gov> wrote:
> +1
>
> Sent from my iPhone
>
> > On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
> >
> > +1
> >> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
> >>
> >> Hi Josh:
> >>
> >> Separate repo (or not), release cycles, etc are project decisions.
> >>
> >> As far as importation of the code; it almost certainly needs to go
> >> through IP Clearance.
> >> http://incubator.apache.org/ip-clearance/
> >>
> >> If you have questions or need help with that process, don't hesitate to
> ask.
> >>
> >> --David
> >>
> >>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org>
> wrote:
> >>> Hi,
> >>>
> >>> Over at Apache Accumulo, we just got a nice bit of code that
> >>> integrates the R programming language (via RStudio) with Accumulo.
> >>> This was done completely by the community (non-committers) and we're
> >>> trying to figure out what's best for it and where it can live.
> >>>
> >>> The general consensus for us is that we would want to import it into
> >>> it's own repository (treat it as a contrib-project) since Accumulo has
> >>> no need to depend on it and thus it can be versioned at its own pace.
> >>>
> >>> The contributors are currently working on ICLA/CCLA forms, but I
> >>> wanted to see what else we (the Accumulo PMC) would need to do to
> >>> import this code.
> >>>
> >>> Thanks!
> >>>
> >>> - Josh
> >>>
> >>> ---------------------------------------------------------------------
> >>> 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: Code import for Apache Accumulo
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
+1
Sent from my iPhone
> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>
> +1
>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>
>> Hi Josh:
>>
>> Separate repo (or not), release cycles, etc are project decisions.
>>
>> As far as importation of the code; it almost certainly needs to go
>> through IP Clearance.
>> http://incubator.apache.org/ip-clearance/
>>
>> If you have questions or need help with that process, don't hesitate to ask.
>>
>> --David
>>
>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org> wrote:
>>> Hi,
>>>
>>> Over at Apache Accumulo, we just got a nice bit of code that
>>> integrates the R programming language (via RStudio) with Accumulo.
>>> This was done completely by the community (non-committers) and we're
>>> trying to figure out what's best for it and where it can live.
>>>
>>> The general consensus for us is that we would want to import it into
>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>> no need to depend on it and thus it can be versioned at its own pace.
>>>
>>> The contributors are currently working on ICLA/CCLA forms, but I
>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>> import this code.
>>>
>>> Thanks!
>>>
>>> - Josh
>>>
>>> ---------------------------------------------------------------------
>>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: Code import for Apache Accumulo
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
+1
Sent from my iPhone
> On Nov 4, 2013, at 12:25 PM, "Jim Jagielski" <ji...@jaguNET.com> wrote:
>
> +1
>> On Oct 30, 2013, at 8:22 AM, David Nalley <da...@gnsa.us> wrote:
>>
>> Hi Josh:
>>
>> Separate repo (or not), release cycles, etc are project decisions.
>>
>> As far as importation of the code; it almost certainly needs to go
>> through IP Clearance.
>> http://incubator.apache.org/ip-clearance/
>>
>> If you have questions or need help with that process, don't hesitate to ask.
>>
>> --David
>>
>>> On Mon, Oct 28, 2013 at 11:19 AM, Josh Elser <el...@apache.org> wrote:
>>> Hi,
>>>
>>> Over at Apache Accumulo, we just got a nice bit of code that
>>> integrates the R programming language (via RStudio) with Accumulo.
>>> This was done completely by the community (non-committers) and we're
>>> trying to figure out what's best for it and where it can live.
>>>
>>> The general consensus for us is that we would want to import it into
>>> it's own repository (treat it as a contrib-project) since Accumulo has
>>> no need to depend on it and thus it can be versioned at its own pace.
>>>
>>> The contributors are currently working on ICLA/CCLA forms, but I
>>> wanted to see what else we (the Accumulo PMC) would need to do to
>>> import this code.
>>>
>>> Thanks!
>>>
>>> - Josh
>>>
>>> ---------------------------------------------------------------------
>>> 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
>