Apache Gora March board report (draft)

[Lewis John Mcgibbney <le...@gmail.com>]

Hi All,

Time of month again, we have monthly reporting for the first three months
after graduation so please review and comment accordingly.
I'll get it committed as of

Apache Gora

The Apache Gora open source framework provides an in-memory data model and
persistence for big data. Gora supports persisting to column stores, key
value stores, document stores and RDBMSs, and analyzing the data with
extensive Apache Hadoop MapReduce support.

Project Releases

The last official project release was made on 24/09/2011 which was the
0.1.1-incubating release (2nd whilst in the Incubator).
Although there have been some commits to three Gora modules, some remaining
issues still need to be addressed before we are ready to roll out a 0.2
release.
This is rather frustrating, as the main issue which blocks a 0.2 release is
a licensing issue on the gora-sql store. It is widely acknowledged that
although
gora-sql is the least used module, it is the one which requires attention
to rectify this
licensing issue.

Overall Project Activity since last report

Since graduation all documentation, and infrastructure has been successfully
migrated over to TLP status. We've witnessed development and committs to
three
datastores and a number of issues addressed as a result. It is safe to say
that the gora-hbase
store seems to be attracting the most development, however there are also
a number of issues which have recently been opened for the gora-cassandra
module.
In the last report we stated that there were two new modules in the process
of being
integrated into the project (namely gora-accumulo and gora-solr), however
due to blocking issues
with releases for Solr and Accumulo, we are not able to release the gora
modules.

How has the community developed since the last report?

The Gora mailing lists have seen some activity with regards to
gora-accumulo,
however generally speaking traffic was quite low for the month until this
report.
We do however have some excellent news that we are submitting an
application
to Google Summer of Code. The project comprises a gora-dynamodb (Amazon
Dynamo
DB) module again making best efforts to open up Gora to a wider audience.

Changes to PMC & Committers

Since VOTE'ing Keither Turner on to the team no new members have been
accepted
into the Gora development team. Additionally, no new VOTE'ing has taken
place.

PMC and Committer diversity

We currently have committers from a wide variety of projects including,
Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an
exhaustive list). There is work to be
done with the Avro implementations, so once we are 100% ready to work on
these issues,
we will be looking to interest members of the Avro community in Gora.

Project Branding or Naming issues

We recently sorted out all branding and trademark issues through trademarks@
.
As this has been addressed there is no more to add at this stage.

Legal issues

We currently have an issue with one particular library being used within the
gora-sql store. It is the communities intention to remove this LGPL
licensed library
from the codebase replacing it with implementations from JOOQ an ASL 2.0
licensed library.
The re-write of the gora-sql module building from the JOOQ library has been
delayed
until after our 0.2 release.

-- 
*Lewis*

Re: Apache Gora March board report (draft)

["Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>]

+1 from me. I'd be happy to RM the release too!

Cheers,
Chris

On Mar 7, 2012, at 7:05 AM, Lewis John Mcgibbney wrote:

> OK so Board report is submitted and Committed @ revision 33866.
> 
> I think we should progress with replacing offending method's/code in
> SqlStore with TODO's. This will mean that we can spin a 0.2 RC and put it
> to bed.
> 
> Development can continue towards 0.3 with a gora-sql re-write, then
> addition of the gora-accumulo, gora-dynamodb, and possibly (hopefully) the
> gora-solr modules. This would make good logical sense and also shows the
> incremental strategy we are moving towards to make the Gora framework a
> better piece of software.
> 
> What do you guys feel about addressing GORA-78 as per above, then knocking
> back the remaining issues which can be addressed under 0.3?
> 
> Thanks
> 
> On Tue, Mar 6, 2012 at 5:59 PM, Lewis John Mcgibbney <
> lewis.mcgibbney@gmail.com> wrote:
> 
>> OK then.
>> 
>> On Tue, Mar 6, 2012 at 3:55 PM, Mattmann, Chris A (388J) <
>> chris.a.mattmann@jpl.nasa.gov> wrote:
>> 
>>> One option is simply to remove the sqlbuilder library
>>> and to replace SqlStore with stubbed out methods that throw Exceptions
>>> and that simply don't work. Then we ship Gora 0.2, with a note saying
>>> don't use SqlStore.
>> 
>> +1 I will get this sorted out shortly subject to other comments that come
>> through in the interim.
>> 
>> 
>>> Then if folks complain and want to use it, we ask that
>>> they help to write the method implementations using an ALv2 compatible
>>> library.
>> 
>> yep
>> 
>> 
>>> Would Derby be useful here, or Hypersonic SQL? Both of those
>>> are ALv2 compatible I think.
>>> 
>> 
>> Well the benefit of rewriting the gora-sql module to utilise JOOQ was that
>> it would provide a common interface which supported many underlying sql
>> store implementations. The reason that the specific DDL statements which we
>> require are not currently implemented in JOOQ is that Lukas has not been
>> able to identify a common way of doing this in the framework yet. I think
>> it is beneficial for us to aspire to have a great gora-sql module, but it
>> is not good for this to block a release, especially as most of us are not
>> using this module, and of course the fact that we have witnessed some
>> excellent work going into the Gora framework elsewhere.
>> 
>> Implementing your suggestion as above would leave us with no blockers (in
>> my opinion) to getting an RC rolled out.The quicker we can get more people
>> using Gora the better.
>> 
>> 
>> 
> 
> 
> -- 
> *Lewis*


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Apache Gora March board report (draft)

[Lewis John Mcgibbney <le...@gmail.com>]

OK so Board report is submitted and Committed @ revision 33866.

I think we should progress with replacing offending method's/code in
SqlStore with TODO's. This will mean that we can spin a 0.2 RC and put it
to bed.

Development can continue towards 0.3 with a gora-sql re-write, then
addition of the gora-accumulo, gora-dynamodb, and possibly (hopefully) the
gora-solr modules. This would make good logical sense and also shows the
incremental strategy we are moving towards to make the Gora framework a
better piece of software.

What do you guys feel about addressing GORA-78 as per above, then knocking
back the remaining issues which can be addressed under 0.3?

Thanks

On Tue, Mar 6, 2012 at 5:59 PM, Lewis John Mcgibbney <
lewis.mcgibbney@gmail.com> wrote:

> OK then.
>
> On Tue, Mar 6, 2012 at 3:55 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
>
>> One option is simply to remove the sqlbuilder library
>> and to replace SqlStore with stubbed out methods that throw Exceptions
>> and that simply don't work. Then we ship Gora 0.2, with a note saying
>> don't use SqlStore.
>
> +1 I will get this sorted out shortly subject to other comments that come
> through in the interim.
>
>
>> Then if folks complain and want to use it, we ask that
>> they help to write the method implementations using an ALv2 compatible
>> library.
>
> yep
>
>
>> Would Derby be useful here, or Hypersonic SQL? Both of those
>> are ALv2 compatible I think.
>>
>
> Well the benefit of rewriting the gora-sql module to utilise JOOQ was that
> it would provide a common interface which supported many underlying sql
> store implementations. The reason that the specific DDL statements which we
> require are not currently implemented in JOOQ is that Lukas has not been
> able to identify a common way of doing this in the framework yet. I think
> it is beneficial for us to aspire to have a great gora-sql module, but it
> is not good for this to block a release, especially as most of us are not
> using this module, and of course the fact that we have witnessed some
> excellent work going into the Gora framework elsewhere.
>
> Implementing your suggestion as above would leave us with no blockers (in
> my opinion) to getting an RC rolled out.The quicker we can get more people
> using Gora the better.
>
>
>


-- 
*Lewis*

Re: Apache Gora March board report (draft)

[Lewis John Mcgibbney <le...@gmail.com>]

OK then.

On Tue, Mar 6, 2012 at 3:55 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> One option is simply to remove the sqlbuilder library
> and to replace SqlStore with stubbed out methods that throw Exceptions
> and that simply don't work. Then we ship Gora 0.2, with a note saying
> don't use SqlStore.

+1 I will get this sorted out shortly subject to other comments that come
through in the interim.


> Then if folks complain and want to use it, we ask that
> they help to write the method implementations using an ALv2 compatible
> library.

yep


> Would Derby be useful here, or Hypersonic SQL? Both of those
> are ALv2 compatible I think.
>

Well the benefit of rewriting the gora-sql module to utilise JOOQ was that
it would provide a common interface which supported many underlying sql
store implementations. The reason that the specific DDL statements which we
require are not currently implemented in JOOQ is that Lukas has not been
able to identify a common way of doing this in the framework yet. I think
it is beneficial for us to aspire to have a great gora-sql module, but it
is not good for this to block a release, especially as most of us are not
using this module, and of course the fact that we have witnessed some
excellent work going into the Gora framework elsewhere.

Implementing your suggestion as above would leave us with no blockers (in
my opinion) to getting an RC rolled out.The quicker we can get more people
using Gora the better.

Re: Apache Gora March board report (draft)

["Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>]

Hey Lewis,

Gotcha, no problem. One option is simply to remove the sqlbuilder library
and to replace SqlStore with stubbed out methods that throw Exceptions
and that simply don't work. Then we ship Gora 0.2, with a note saying
don't use SqlStore. Then if folks complain and want to use it, we ask that
they help to write the method implementations using an ALv2 compatible
library. Would Derby be useful here, or Hypersonic SQL? Both of those
are ALv2 compatible I think.

Cheers,
Chris

On Mar 6, 2012, at 7:40 AM, Lewis John Mcgibbney wrote:

> Hi Chris,
> 
> We'll in all honesty, I think it's best for me to  provide a brief summary.
> 
> We need to remove our dependency upon and use of the healthmarketscience
> sqlbuilder libary. Used very little in SqlStore class [0]. The problem I
> ran into when looking into this was that unfortunately JOOQ doesn't support
> data definition language constructs which is exactly what we require.
> Although this is in the pipeline (for JOOQ), I have a feeling that it may
> be some way off. I did however run into a couple of examples of
> implementing similar functionality to what we require, unfortunately I got
> distracted and haven't had time to go back to it. I have included all of my
> resources on the offending issue on our Jira so anyone trying to pick it up
> would really be starting off from where I got to. This is the blocking
> issue here and unfortunately it doesn't look like something legal guys can
> help out with, it simply a case of understanding exactly what functionality
> we require then finding a replacement and someone that can code it in using
> a more suitably licensed library.
> 
> If it is for the sake of pushing out with a Gora 0.2 release as per your
> requirement's E.g. archive gora-sql then I would probably back this for the
> time being... I am not using the gora-sql module, and in all honesty I
> don't think that many others are hence the level of interest to get this
> module up to scratch!
> 
> I began a thread a week or so ago, and to be honest the gora-sql issue was
> the only blocked in my opinion.
> 
> Thanks for chiming in on this one.
> 
> Lewis
> 
> 
> [0]
> http://svn.apache.org/viewvc/gora/trunk/gora-sql/src/main/java/org/apache/gora/sql/store/SqlStore.java?view=markup
> 
> On Tue, Mar 6, 2012 at 3:29 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> 
>> +1 from me, Lewis, Looks awesome. RE: gora-sql: what are the next steps
>> there?
>> Is it something the legal committee can help out with? At worst, I'd
>> imagine, we
>> could move gora-sql to a non-released area of SVN and then push forward
>> with
>> an 0.2 that doesn't include it?
>> 
>> Cheers,
>> Chris
>> 
>> On Mar 6, 2012, at 7:26 AM, Lewis John Mcgibbney wrote:
>> 
>>> Hi All,
>>> 
>>> Time of month again, we have monthly reporting for the first three months
>>> after graduation so please review and comment accordingly.
>>> I'll get it committed as of
>>> 
>>> Apache Gora
>>> 
>>> The Apache Gora open source framework provides an in-memory data model
>> and
>>> persistence for big data. Gora supports persisting to column stores, key
>>> value stores, document stores and RDBMSs, and analyzing the data with
>>> extensive Apache Hadoop MapReduce support.
>>> 
>>> Project Releases
>>> 
>>> The last official project release was made on 24/09/2011 which was the
>>> 0.1.1-incubating release (2nd whilst in the Incubator).
>>> Although there have been some commits to three Gora modules, some
>> remaining
>>> issues still need to be addressed before we are ready to roll out a 0.2
>>> release.
>>> This is rather frustrating, as the main issue which blocks a 0.2 release
>> is
>>> a licensing issue on the gora-sql store. It is widely acknowledged that
>>> although
>>> gora-sql is the least used module, it is the one which requires attention
>>> to rectify this
>>> licensing issue.
>>> 
>>> Overall Project Activity since last report
>>> 
>>> Since graduation all documentation, and infrastructure has been
>> successfully
>>> migrated over to TLP status. We've witnessed development and committs to
>>> three
>>> datastores and a number of issues addressed as a result. It is safe to
>> say
>>> that the gora-hbase
>>> store seems to be attracting the most development, however there are also
>>> a number of issues which have recently been opened for the gora-cassandra
>>> module.
>>> In the last report we stated that there were two new modules in the
>> process
>>> of being
>>> integrated into the project (namely gora-accumulo and gora-solr), however
>>> due to blocking issues
>>> with releases for Solr and Accumulo, we are not able to release the gora
>>> modules.
>>> 
>>> How has the community developed since the last report?
>>> 
>>> The Gora mailing lists have seen some activity with regards to
>>> gora-accumulo,
>>> however generally speaking traffic was quite low for the month until this
>>> report.
>>> We do however have some excellent news that we are submitting an
>>> application
>>> to Google Summer of Code. The project comprises a gora-dynamodb (Amazon
>>> Dynamo
>>> DB) module again making best efforts to open up Gora to a wider audience.
>>> 
>>> Changes to PMC & Committers
>>> 
>>> Since VOTE'ing Keither Turner on to the team no new members have been
>>> accepted
>>> into the Gora development team. Additionally, no new VOTE'ing has taken
>>> place.
>>> 
>>> PMC and Committer diversity
>>> 
>>> We currently have committers from a wide variety of projects including,
>>> Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an
>>> exhaustive list). There is work to be
>>> done with the Avro implementations, so once we are 100% ready to work on
>>> these issues,
>>> we will be looking to interest members of the Avro community in Gora.
>>> 
>>> Project Branding or Naming issues
>>> 
>>> We recently sorted out all branding and trademark issues through
>> trademarks@
>>> .
>>> As this has been addressed there is no more to add at this stage.
>>> 
>>> Legal issues
>>> 
>>> We currently have an issue with one particular library being used within
>> the
>>> gora-sql store. It is the communities intention to remove this LGPL
>>> licensed library
>>> from the codebase replacing it with implementations from JOOQ an ASL 2.0
>>> licensed library.
>>> The re-write of the gora-sql module building from the JOOQ library has
>> been
>>> delayed
>>> until after our 0.2 release.
>>> 
>>> --
>>> *Lewis*
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Chris Mattmann, Ph.D.
>> Senior Computer Scientist
>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>> Office: 171-266B, Mailstop: 171-246
>> Email: chris.a.mattmann@nasa.gov
>> WWW:   http://sunset.usc.edu/~mattmann/
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> Adjunct Assistant Professor, Computer Science Department
>> University of Southern California, Los Angeles, CA 90089 USA
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
>> 
> 
> 
> -- 
> *Lewis*


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Apache Gora March board report (draft)

[Lewis John Mcgibbney <le...@gmail.com>]

Hi Chris,

We'll in all honesty, I think it's best for me to  provide a brief summary.

We need to remove our dependency upon and use of the healthmarketscience
sqlbuilder libary. Used very little in SqlStore class [0]. The problem I
ran into when looking into this was that unfortunately JOOQ doesn't support
data definition language constructs which is exactly what we require.
Although this is in the pipeline (for JOOQ), I have a feeling that it may
be some way off. I did however run into a couple of examples of
implementing similar functionality to what we require, unfortunately I got
distracted and haven't had time to go back to it. I have included all of my
resources on the offending issue on our Jira so anyone trying to pick it up
would really be starting off from where I got to. This is the blocking
issue here and unfortunately it doesn't look like something legal guys can
help out with, it simply a case of understanding exactly what functionality
we require then finding a replacement and someone that can code it in using
a more suitably licensed library.

If it is for the sake of pushing out with a Gora 0.2 release as per your
requirement's E.g. archive gora-sql then I would probably back this for the
time being... I am not using the gora-sql module, and in all honesty I
don't think that many others are hence the level of interest to get this
module up to scratch!

I began a thread a week or so ago, and to be honest the gora-sql issue was
the only blocked in my opinion.

Thanks for chiming in on this one.

Lewis


[0]
http://svn.apache.org/viewvc/gora/trunk/gora-sql/src/main/java/org/apache/gora/sql/store/SqlStore.java?view=markup

On Tue, Mar 6, 2012 at 3:29 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> +1 from me, Lewis, Looks awesome. RE: gora-sql: what are the next steps
> there?
> Is it something the legal committee can help out with? At worst, I'd
> imagine, we
> could move gora-sql to a non-released area of SVN and then push forward
> with
> an 0.2 that doesn't include it?
>
> Cheers,
> Chris
>
> On Mar 6, 2012, at 7:26 AM, Lewis John Mcgibbney wrote:
>
> > Hi All,
> >
> > Time of month again, we have monthly reporting for the first three months
> > after graduation so please review and comment accordingly.
> > I'll get it committed as of
> >
> > Apache Gora
> >
> > The Apache Gora open source framework provides an in-memory data model
> and
> > persistence for big data. Gora supports persisting to column stores, key
> > value stores, document stores and RDBMSs, and analyzing the data with
> > extensive Apache Hadoop MapReduce support.
> >
> > Project Releases
> >
> > The last official project release was made on 24/09/2011 which was the
> > 0.1.1-incubating release (2nd whilst in the Incubator).
> > Although there have been some commits to three Gora modules, some
> remaining
> > issues still need to be addressed before we are ready to roll out a 0.2
> > release.
> > This is rather frustrating, as the main issue which blocks a 0.2 release
> is
> > a licensing issue on the gora-sql store. It is widely acknowledged that
> > although
> > gora-sql is the least used module, it is the one which requires attention
> > to rectify this
> > licensing issue.
> >
> > Overall Project Activity since last report
> >
> > Since graduation all documentation, and infrastructure has been
> successfully
> > migrated over to TLP status. We've witnessed development and committs to
> > three
> > datastores and a number of issues addressed as a result. It is safe to
> say
> > that the gora-hbase
> > store seems to be attracting the most development, however there are also
> > a number of issues which have recently been opened for the gora-cassandra
> > module.
> > In the last report we stated that there were two new modules in the
> process
> > of being
> > integrated into the project (namely gora-accumulo and gora-solr), however
> > due to blocking issues
> > with releases for Solr and Accumulo, we are not able to release the gora
> > modules.
> >
> > How has the community developed since the last report?
> >
> > The Gora mailing lists have seen some activity with regards to
> > gora-accumulo,
> > however generally speaking traffic was quite low for the month until this
> > report.
> > We do however have some excellent news that we are submitting an
> > application
> > to Google Summer of Code. The project comprises a gora-dynamodb (Amazon
> > Dynamo
> > DB) module again making best efforts to open up Gora to a wider audience.
> >
> > Changes to PMC & Committers
> >
> > Since VOTE'ing Keither Turner on to the team no new members have been
> > accepted
> > into the Gora development team. Additionally, no new VOTE'ing has taken
> > place.
> >
> > PMC and Committer diversity
> >
> > We currently have committers from a wide variety of projects including,
> > Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an
> > exhaustive list). There is work to be
> > done with the Avro implementations, so once we are 100% ready to work on
> > these issues,
> > we will be looking to interest members of the Avro community in Gora.
> >
> > Project Branding or Naming issues
> >
> > We recently sorted out all branding and trademark issues through
> trademarks@
> > .
> > As this has been addressed there is no more to add at this stage.
> >
> > Legal issues
> >
> > We currently have an issue with one particular library being used within
> the
> > gora-sql store. It is the communities intention to remove this LGPL
> > licensed library
> > from the codebase replacing it with implementations from JOOQ an ASL 2.0
> > licensed library.
> > The re-write of the gora-sql module building from the JOOQ library has
> been
> > delayed
> > until after our 0.2 release.
> >
> > --
> > *Lewis*
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
*Lewis*

Re: Apache Gora March board report (draft)

["Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>]

+1 from me, Lewis, Looks awesome. RE: gora-sql: what are the next steps there?
Is it something the legal committee can help out with? At worst, I'd imagine, we 
could move gora-sql to a non-released area of SVN and then push forward with
an 0.2 that doesn't include it?

Cheers,
Chris

On Mar 6, 2012, at 7:26 AM, Lewis John Mcgibbney wrote:

> Hi All,
> 
> Time of month again, we have monthly reporting for the first three months
> after graduation so please review and comment accordingly.
> I'll get it committed as of
> 
> Apache Gora
> 
> The Apache Gora open source framework provides an in-memory data model and
> persistence for big data. Gora supports persisting to column stores, key
> value stores, document stores and RDBMSs, and analyzing the data with
> extensive Apache Hadoop MapReduce support.
> 
> Project Releases
> 
> The last official project release was made on 24/09/2011 which was the
> 0.1.1-incubating release (2nd whilst in the Incubator).
> Although there have been some commits to three Gora modules, some remaining
> issues still need to be addressed before we are ready to roll out a 0.2
> release.
> This is rather frustrating, as the main issue which blocks a 0.2 release is
> a licensing issue on the gora-sql store. It is widely acknowledged that
> although
> gora-sql is the least used module, it is the one which requires attention
> to rectify this
> licensing issue.
> 
> Overall Project Activity since last report
> 
> Since graduation all documentation, and infrastructure has been successfully
> migrated over to TLP status. We've witnessed development and committs to
> three
> datastores and a number of issues addressed as a result. It is safe to say
> that the gora-hbase
> store seems to be attracting the most development, however there are also
> a number of issues which have recently been opened for the gora-cassandra
> module.
> In the last report we stated that there were two new modules in the process
> of being
> integrated into the project (namely gora-accumulo and gora-solr), however
> due to blocking issues
> with releases for Solr and Accumulo, we are not able to release the gora
> modules.
> 
> How has the community developed since the last report?
> 
> The Gora mailing lists have seen some activity with regards to
> gora-accumulo,
> however generally speaking traffic was quite low for the month until this
> report.
> We do however have some excellent news that we are submitting an
> application
> to Google Summer of Code. The project comprises a gora-dynamodb (Amazon
> Dynamo
> DB) module again making best efforts to open up Gora to a wider audience.
> 
> Changes to PMC & Committers
> 
> Since VOTE'ing Keither Turner on to the team no new members have been
> accepted
> into the Gora development team. Additionally, no new VOTE'ing has taken
> place.
> 
> PMC and Committer diversity
> 
> We currently have committers from a wide variety of projects including,
> Nutch, Tika, OODT, Camel, Solr, Accumulo & Hadoop (this is not an
> exhaustive list). There is work to be
> done with the Avro implementations, so once we are 100% ready to work on
> these issues,
> we will be looking to interest members of the Avro community in Gora.
> 
> Project Branding or Naming issues
> 
> We recently sorted out all branding and trademark issues through trademarks@
> .
> As this has been addressed there is no more to add at this stage.
> 
> Legal issues
> 
> We currently have an issue with one particular library being used within the
> gora-sql store. It is the communities intention to remove this LGPL
> licensed library
> from the codebase replacing it with implementations from JOOQ an ASL 2.0
> licensed library.
> The re-write of the gora-sql module building from the JOOQ library has been
> delayed
> until after our 0.2 release.
> 
> -- 
> *Lewis*


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++