Code import for Apache Accumulo

[Josh Elser <el...@apache.org>]

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

Re: RAccumulo's Home (was Code import for Apache Accumulo)

[David Medinets <da...@gmail.com>]

https://github.com/medined/RStudio_By_Vagrant makes it easy to get started
with RStudio.


On Wed, Oct 30, 2013 at 6:21 PM, Christopher <ct...@apache.org> wrote:

> If existing committers are willing to take on the project, and
> maintain it and really own it (so, more than just being a proxy for
> external committers), I'd be on board accepting it as a sub-project.
>
> However, if its just going to be an orphaned project, or we're just
> going to have to act as a proxy for external developers who've hosted
> their code in our project as a notional parent, but aren't committers
> themselves, I'm opposed to importing it and assuming ownership of it
> as a sub-project, and think it would be better served hosted where the
> originating developers can maintain it.
>
> In either case, I think it's a great related project to serve both the
> R and Accumulo communities, and we should link to it, provide
> feedback, and help make it better if we can. I'm just concerned about
> setting a precedent for accepting/hosting everything related to
> Accumulo, causing us to either be spread too thin or to cause projects
> to die because of lack of care.
>
> --
> Christopher L Tubbs II
> http://gravatar.com/ctubbsii
>
>
> On Wed, Oct 30, 2013 at 5:48 PM, Josh Elser <jo...@gmail.com> wrote:
> > On 10/29/13, 4:20 PM, Eric Whyne wrote:
> >>
> >> Some thoughts to re-ignite this thread:
> >>
> >> The raccumulo project has some of it's code written in the language R,
> but
> >> does not borrow any code from the R codebase and as such is not a
> >> derivative work.
> >>
> >> Unless anybody can think of a way in which R's own licensing could
> become
> >> a
> >> concern, potential license conflicts might be a dead issue?
> >
> >
> > Looking around at this some more, I can't find any similar case on LEGAL.
> > Given that there is only a GPL implementation of R (take openjdk,
> sun/oracle
> > jdk, IBM's java, etc as an example for Java projects), I wasn't sure if
> this
> > would present any sort of issue because raccumulo would be more or less
> > useless if someone did not want to use GPL software.
> >
> > <not-a-lawyer>Nothing is jumping out at me from a licensing standpoint
> that
> > would create concern to this code being hosted on ASF resources.
> > </not-a-lawyer>
> >
> >> The primary developer Phil Grim has signed an ICLA that I'm going to
> send
> >> off tomorrow pending our company's contracts department's approval. Same
> >> with company level CCLA, complete and pending final review. Phil, Aaron,
> >> and Myself as listed as representatives on it.
> >>
> >> Insofar as observations about lack of committership:
> >> Phil has been willing to share his code for a while and wants to keep
> >> contributing.
> >> https://issues.apache.org/jira/browse/SQOOP-767
> >> https://issues.apache.org/jira/browse/ACCUMULO-141
> >> discussion about this topic here:
> >>
> >>
> http://www.mail-archive.com/notifications@accumulo.apache.org/msg10665.html
> >>
> >> The other developer, Aaron is listed as a previous contributor to
> >> accumulo:
> >> http://accumulo.apache.org/people.html
> >>
> >> More about what's going on at the company:
> >> https://twitter.com/DataTactics
> >>
> >> More about DARPA XData (one of the programs of interest):
> >> http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx
> >> The customer project includes a charter to contribute to open source:
> >> "XDATA plans to release open-source software toolkits to enable
> >> collaboration among the applied mathematics, computer science and data
> >> visualization communities."
> >>
> >> As a company we'd be happy to just keep hosting the code on our Github
> >> page, but I think we'd rather see it be included closer to the accumulo
> >> project as mentioned previously. Given the momentum of R, the interest
> of
> >> DARPA and others, I think the benefits outweigh he risks. There's an
> >> extremely small chance of an orphaned project and even then as a 200+
> >> person company there's somebody you can blame if it does become a
> problem.
> >> We have a twitter account and github page people can go to with help
> >> requests or fixes.
> >
> >
> > (treating "you" as all of those who might be involved in raccumulo whom
> you
> > mentioned, Eric)
> >
> > Personally, I wouldn't mind seeing raccumulo as a sub-project of
> Accumulo.
> > If those who are going to maintain it want to step up and do things "The
> > Apache Way", I would be happy to help you all along the path so that you
> can
> > grow to maintain it yourself. This would give us a fairly low-risk,
> middle
> > ground which we could try to grow a community outside of your company
> that
> > is involved with raccumulo.
> >
> > The other Apache alternative would be for raccumulo to enter incubation
> > itself. I'm not sure if the current state of the project would merit the
> > effort of those involved at the moment. Regardless, this is also an
> option.
> >
> > And, as always, there is the Github (or other external hosting) option.
> I'm
> > sure we'd also be happy to make sure there's mention on accumulo.a.o to
> > point people to any other location.
> >
> > Thoughts everyone else?
>

Re: RAccumulo's Home (was Code import for Apache Accumulo)

[Joey Echeverria <jo...@cloudera.com>]

On Wed, Oct 30, 2013 at 6:21 PM, Christopher <ct...@apache.org> wrote:
>
> If existing committers are willing to take on the project, and
> maintain it and really own it (so, more than just being a proxy for
> external committers), I'd be on board accepting it as a sub-project.
>
> However, if its just going to be an orphaned project, or we're just
> going to have to act as a proxy for external developers who've hosted
> their code in our project as a notional parent, but aren't committers
> themselves, I'm opposed to importing it and assuming ownership of it
> as a sub-project, and think it would be better served hosted where the
> originating developers can maintain it.
>
> In either case, I think it's a great related project to serve both the
> R and Accumulo communities, and we should link to it, provide
> feedback, and help make it better if we can. I'm just concerned about
> setting a precedent for accepting/hosting everything related to
> Accumulo, causing us to either be spread too thin or to cause projects
> to die because of lack of care.

+1, orphaned code does no one any good.

Re: RAccumulo's Home (was Code import for Apache Accumulo)

[Christopher <ct...@apache.org>]

If existing committers are willing to take on the project, and
maintain it and really own it (so, more than just being a proxy for
external committers), I'd be on board accepting it as a sub-project.

However, if its just going to be an orphaned project, or we're just
going to have to act as a proxy for external developers who've hosted
their code in our project as a notional parent, but aren't committers
themselves, I'm opposed to importing it and assuming ownership of it
as a sub-project, and think it would be better served hosted where the
originating developers can maintain it.

In either case, I think it's a great related project to serve both the
R and Accumulo communities, and we should link to it, provide
feedback, and help make it better if we can. I'm just concerned about
setting a precedent for accepting/hosting everything related to
Accumulo, causing us to either be spread too thin or to cause projects
to die because of lack of care.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Wed, Oct 30, 2013 at 5:48 PM, Josh Elser <jo...@gmail.com> wrote:
> On 10/29/13, 4:20 PM, Eric Whyne wrote:
>>
>> Some thoughts to re-ignite this thread:
>>
>> The raccumulo project has some of it's code written in the language R, but
>> does not borrow any code from the R codebase and as such is not a
>> derivative work.
>>
>> Unless anybody can think of a way in which R's own licensing could become
>> a
>> concern, potential license conflicts might be a dead issue?
>
>
> Looking around at this some more, I can't find any similar case on LEGAL.
> Given that there is only a GPL implementation of R (take openjdk, sun/oracle
> jdk, IBM's java, etc as an example for Java projects), I wasn't sure if this
> would present any sort of issue because raccumulo would be more or less
> useless if someone did not want to use GPL software.
>
> <not-a-lawyer>Nothing is jumping out at me from a licensing standpoint that
> would create concern to this code being hosted on ASF resources.
> </not-a-lawyer>
>
>> The primary developer Phil Grim has signed an ICLA that I'm going to send
>> off tomorrow pending our company's contracts department's approval. Same
>> with company level CCLA, complete and pending final review. Phil, Aaron,
>> and Myself as listed as representatives on it.
>>
>> Insofar as observations about lack of committership:
>> Phil has been willing to share his code for a while and wants to keep
>> contributing.
>> https://issues.apache.org/jira/browse/SQOOP-767
>> https://issues.apache.org/jira/browse/ACCUMULO-141
>> discussion about this topic here:
>>
>> http://www.mail-archive.com/notifications@accumulo.apache.org/msg10665.html
>>
>> The other developer, Aaron is listed as a previous contributor to
>> accumulo:
>> http://accumulo.apache.org/people.html
>>
>> More about what's going on at the company:
>> https://twitter.com/DataTactics
>>
>> More about DARPA XData (one of the programs of interest):
>> http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx
>> The customer project includes a charter to contribute to open source:
>> "XDATA plans to release open-source software toolkits to enable
>> collaboration among the applied mathematics, computer science and data
>> visualization communities."
>>
>> As a company we'd be happy to just keep hosting the code on our Github
>> page, but I think we'd rather see it be included closer to the accumulo
>> project as mentioned previously. Given the momentum of R, the interest of
>> DARPA and others, I think the benefits outweigh he risks. There's an
>> extremely small chance of an orphaned project and even then as a 200+
>> person company there's somebody you can blame if it does become a problem.
>> We have a twitter account and github page people can go to with help
>> requests or fixes.
>
>
> (treating "you" as all of those who might be involved in raccumulo whom you
> mentioned, Eric)
>
> Personally, I wouldn't mind seeing raccumulo as a sub-project of Accumulo.
> If those who are going to maintain it want to step up and do things "The
> Apache Way", I would be happy to help you all along the path so that you can
> grow to maintain it yourself. This would give us a fairly low-risk, middle
> ground which we could try to grow a community outside of your company that
> is involved with raccumulo.
>
> The other Apache alternative would be for raccumulo to enter incubation
> itself. I'm not sure if the current state of the project would merit the
> effort of those involved at the moment. Regardless, this is also an option.
>
> And, as always, there is the Github (or other external hosting) option. I'm
> sure we'd also be happy to make sure there's mention on accumulo.a.o to
> point people to any other location.
>
> Thoughts everyone else?

RAccumulo's Home (was Code import for Apache Accumulo)

[Josh Elser <jo...@gmail.com>]

On 10/29/13, 4:20 PM, Eric Whyne wrote:
> Some thoughts to re-ignite this thread:
>
> The raccumulo project has some of it's code written in the language R, but
> does not borrow any code from the R codebase and as such is not a
> derivative work.
>
> Unless anybody can think of a way in which R's own licensing could become a
> concern, potential license conflicts might be a dead issue?

Looking around at this some more, I can't find any similar case on 
LEGAL. Given that there is only a GPL implementation of R (take openjdk, 
sun/oracle jdk, IBM's java, etc as an example for Java projects), I 
wasn't sure if this would present any sort of issue because raccumulo 
would be more or less useless if someone did not want to use GPL software.

<not-a-lawyer>Nothing is jumping out at me from a licensing standpoint 
that would create concern to this code being hosted on ASF resources. 
</not-a-lawyer>

> The primary developer Phil Grim has signed an ICLA that I'm going to send
> off tomorrow pending our company's contracts department's approval. Same
> with company level CCLA, complete and pending final review. Phil, Aaron,
> and Myself as listed as representatives on it.
>
> Insofar as observations about lack of committership:
> Phil has been willing to share his code for a while and wants to keep
> contributing.
> https://issues.apache.org/jira/browse/SQOOP-767
> https://issues.apache.org/jira/browse/ACCUMULO-141
> discussion about this topic here:
> http://www.mail-archive.com/notifications@accumulo.apache.org/msg10665.html
>
> The other developer, Aaron is listed as a previous contributor to accumulo:
> http://accumulo.apache.org/people.html
>
> More about what's going on at the company:
> https://twitter.com/DataTactics
>
> More about DARPA XData (one of the programs of interest):
> http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx
> The customer project includes a charter to contribute to open source:
> "XDATA plans to release open-source software toolkits to enable
> collaboration among the applied mathematics, computer science and data
> visualization communities."
>
> As a company we'd be happy to just keep hosting the code on our Github
> page, but I think we'd rather see it be included closer to the accumulo
> project as mentioned previously. Given the momentum of R, the interest of
> DARPA and others, I think the benefits outweigh he risks. There's an
> extremely small chance of an orphaned project and even then as a 200+
> person company there's somebody you can blame if it does become a problem.
> We have a twitter account and github page people can go to with help
> requests or fixes.

(treating "you" as all of those who might be involved in raccumulo whom 
you mentioned, Eric)

Personally, I wouldn't mind seeing raccumulo as a sub-project of 
Accumulo. If those who are going to maintain it want to step up and do 
things "The Apache Way", I would be happy to help you all along the path 
so that you can grow to maintain it yourself. This would give us a 
fairly low-risk, middle ground which we could try to grow a community 
outside of your company that is involved with raccumulo.

The other Apache alternative would be for raccumulo to enter incubation 
itself. I'm not sure if the current state of the project would merit the 
effort of those involved at the moment. Regardless, this is also an option.

And, as always, there is the Github (or other external hosting) option. 
I'm sure we'd also be happy to make sure there's mention on accumulo.a.o 
to point people to any other location.

Thoughts everyone else?

Re: Code import for Apache Accumulo

[Eric Whyne <er...@gmail.com>]

Some thoughts to re-ignite this thread:

The raccumulo project has some of it's code written in the language R, but
does not borrow any code from the R codebase and as such is not a
derivative work.

Unless anybody can think of a way in which R's own licensing could become a
concern, potential license conflicts might be a dead issue?

Some background:
R is a statistics domain specific language used mostly for statistics
research.
http://www.r-bloggers.com/r-usage-skyrocketing-rexer-poll/
"*R <http://www.revolutionanalytics.com/what-is-open-source-r/> is the most
popular data mining tool*, used at least occasionally by 70% of those
polled. This popularity holds amongst all of the subgroups in the survey as
well: R remains the most-used tool amongst corporate data miners (70%),
consulting data miners (73%), academic data miners (75%) and
nonprofit/NGO/government data miners (67%). And while the average data
miner reports using five software tools, R is also the most popular primary
tool in the survey, at 24% overall. "

The raccumulo code base was written for a defense customer, but has since
had investment from several DARPA programs and DHS because of the
importance of both accumulo and r. They practically go together like peanut
butter and jelly (I just made that up). Projects analagous to raccumulo
exist for HBase (rhbase).

The primary developer Phil Grim has signed an ICLA that I'm going to send
off tomorrow pending our company's contracts department's approval. Same
with company level CCLA, complete and pending final review. Phil, Aaron,
and Myself as listed as representatives on it.

Insofar as observations about lack of committership:
Phil has been willing to share his code for a while and wants to keep
contributing.
https://issues.apache.org/jira/browse/SQOOP-767
https://issues.apache.org/jira/browse/ACCUMULO-141
discussion about this topic here:
http://www.mail-archive.com/notifications@accumulo.apache.org/msg10665.html

The other developer, Aaron is listed as a previous contributor to accumulo:
http://accumulo.apache.org/people.html

More about what's going on at the company:
https://twitter.com/DataTactics

More about DARPA XData (one of the programs of interest):
http://www.darpa.mil/Our_Work/I2O/Programs/XDATA.aspx
The customer project includes a charter to contribute to open source:
"XDATA plans to release open-source software toolkits to enable
collaboration among the applied mathematics, computer science and data
visualization communities."

As a company we'd be happy to just keep hosting the code on our Github
page, but I think we'd rather see it be included closer to the accumulo
project as mentioned previously. Given the momentum of R, the interest of
DARPA and others, I think the benefits outweigh he risks. There's an
extremely small chance of an orphaned project and even then as a 200+
person company there's somebody you can blame if it does become a problem.
We have a twitter account and github page people can go to with help
requests or fixes.

We are interested in hearing more about how to best continue. I'll send a
note when CCLA and ICLAs are fully executed.



On Tue, Oct 29, 2013 at 5:52 AM, Steve Loughran <st...@hortonworks.com>wrote:

> On 29 October 2013 00:02, Christopher <ct...@apache.org> wrote:
>
> > +1 for it's own repo... but due to licensing concerns of the R
> > dependency, and lack of committership of the original developers, I'm
> > not sure it makes much sense for Accumulo to adopt it as a sub-project
> > by importing it, which would mean taking on the responsibility of
> > maintaining it.
> >
>
> That's the eternal problem with contributed code. Close to the project: you
> can keep an eye on it, but then people expect it to work and blame you if
> it can't. But at the same time, those contributions build up your project's
> functionality.
>
> One rule that I've found works is: never accept code that you can't test
> yourself.
>
> If it needs some non-standard filesystem, lots of pre-installed binaries or
> human intervention, its not something that you can hook up to a CI build,
> or test in a release process -so it will be broken almost from the outset.
>
> If you can test it yourself, even if if you have to pay a few cents of S3
> or openstack cluster time, then it is something you could consider
> releasing as "tested". Otherwise, it'll just become a maintenance and
> support nightmare in years to come.
>
> In Hadoop core some of the contribs/ -the schedulers - were pulled in, but
> other contrib stuff is now out -the general policy being "no orphaned works
> in the core codebase".
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

Re: Code import for Apache Accumulo

[Steve Loughran <st...@hortonworks.com>]

On 29 October 2013 00:02, Christopher <ct...@apache.org> wrote:

> +1 for it's own repo... but due to licensing concerns of the R
> dependency, and lack of committership of the original developers, I'm
> not sure it makes much sense for Accumulo to adopt it as a sub-project
> by importing it, which would mean taking on the responsibility of
> maintaining it.
>

That's the eternal problem with contributed code. Close to the project: you
can keep an eye on it, but then people expect it to work and blame you if
it can't. But at the same time, those contributions build up your project's
functionality.

One rule that I've found works is: never accept code that you can't test
yourself.

If it needs some non-standard filesystem, lots of pre-installed binaries or
human intervention, its not something that you can hook up to a CI build,
or test in a release process -so it will be broken almost from the outset.

If you can test it yourself, even if if you have to pay a few cents of S3
or openstack cluster time, then it is something you could consider
releasing as "tested". Otherwise, it'll just become a maintenance and
support nightmare in years to come.

In Hadoop core some of the contribs/ -the schedulers - were pulled in, but
other contrib stuff is now out -the general policy being "no orphaned works
in the core codebase".

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Re: Code import for Apache Accumulo

[Christopher <ct...@apache.org>]

+1 for it's own repo... but due to licensing concerns of the R
dependency, and lack of committership of the original developers, I'm
not sure it makes much sense for Accumulo to adopt it as a sub-project
by importing it, which would mean taking on the responsibility of
maintaining it.

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Mon, Oct 28, 2013 at 7:31 PM, Eric Whyne <er...@gmail.com> wrote:
> +1 The authors like the contrib project idea too.
> On Oct 28, 2013 7:28 PM, "David Medinets" <da...@gmail.com> wrote:
>
>> +1 for the RStudio integration to be in its own repository.
>>
>>
>> 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
>> >
>>

Re: Code import for Apache Accumulo

[Eric Whyne <er...@gmail.com>]

+1 The authors like the contrib project idea too.
On Oct 28, 2013 7:28 PM, "David Medinets" <da...@gmail.com> wrote:

> +1 for the RStudio integration to be in its own repository.
>
>
> 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
> >
>

Re: Code import for Apache Accumulo

[Eric Whyne <er...@gmail.com>]

+1 The authors like the contrib project idea too.
On Oct 28, 2013 7:28 PM, "David Medinets" <da...@gmail.com> wrote:

> +1 for the RStudio integration to be in its own repository.
>
>
> 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
> >
>

Re: Code import for Apache Accumulo

[David Medinets <da...@gmail.com>]

+1 for the RStudio integration to be in its own repository.


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
>

Re: Code import for Apache Accumulo

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

["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

["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
> 

Re: Code import for Apache Accumulo

[Jim Jagielski <ji...@jaguNET.com>]

+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

[Jim Jagielski <ji...@jaguNET.com>]

+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

[David Nalley <da...@gnsa.us>]

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
>

Re: Code import for Apache Accumulo

[David Medinets <da...@gmail.com>]

+1 for the RStudio integration to be in its own repository.


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
>

Re: Code import for Apache Accumulo

[David Nalley <da...@gnsa.us>]

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