Re: 4.x branch for RDF4j updates.

[Jürgen Jakobitsch]

hi,

my 2 cents:

since this might look a little easier than it is in reality i'd give my +1
to a feature branch (4.0.0).
=> rather take a little more time and upgrade more deps and test
thoroughly.. note that you might scare
away NEW installations with old dependencies.. (when i first installed i'd
thought i'd rather upgrade deps myself than installing a five year old HDFS)

notes:

1. for us at semantic-web.com it would be really important to have the
latest rdf4j version
(note: we're upgrading to 2.3. due to some critical rdf4j 2.2* bug in
our product)
2. there won't be any backwards compatibility with respect to the
requirement of having to install accumulo/hdfs, mongo anew..
(note: we were testing our installation with accumulo 1.8.1 + hadoop
2.9.5 on DC/OS and with a relatively new version of mongo on premise).
(note: later accumulo versions depend on a newer libthrift version,
which requires a knowledgeable person to take a look)

kr jürgen

[1] https://semver.org/

*Jürgen Jakobitsch*
Innovation Director
Semantic Web Company GmbH
EU: +43-14021235 <+43%201%204021235>
US: (415) 800-3776
Mobile: +43-676-6212710 <+43%20676%206212710>
https://www.poolparty.biz
https://www.semantic-web.com

*Download now

**IDC
White Paper*
*Get certified!  **PoolParty Academy*


*PoolParty selected as a KMWorld Trend-Setting Product for 2017*


PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#;
| blockchain : https://onename.com/turnguard

2018-04-09 19:55 GMT+02:00 Jeff Dasch :

> The simplest thing for the community is to have a single branch of
> development that is being supported/maintained.  Otherwise we're always
> forward/backporting new features that apply to both versions which is a
> pain.  I do think we should push a 3.x branch so we can always do a future
> 3.2.13 release if requested by the community.  Then someone should bump
> master to 4.0.0-SNAPSHOT, and then we should pull in PR 245.
>
> There have been a couple commits on master since the 3.2.12 release.  Do we
> want to cut a 3.2.13 release with just those remaining commits, or should
> they all get rolled into the 4.0.0 release?
>
>
>
> On Mon, Apr 9, 2018 at 12:30 PM, Chilton, Kevin  >
> wrote:
>
> > Hey Rya devs,
> >
> > I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big
> > dependency change, and should probably involve a major version increment
> to
> > 4.0.0.  Could we get a discussion going on the devlist about if we want
> to
> > support a 3.x branch and a 4.x branch going forward, or just update
> master
> > to 4.x.
> >
> > Thanks,
> > Kevin
> >
> > NOTICE: This email message and all attachments transmitted with it may
> > contain privileged and confidential information, and information that is
> > protected by, and proprietary to, Parsons Corporation, and is intended
> > solely for the use of the addressee for the specific purpose set forth in
> > this communication. If the reader of this message is not the intended
> > recipient, you are hereby notified that any reading, dissemination,
> > distribution, copying, or other use of this message or its attachments is
> > strictly prohibited, and you should delete this message and all copies
> and
> > backups thereof. The recipient may not further distribute or use any of
> the
> > information contained herein without the express written authorization of
> > the sender. If you have received this message in error, or if you have
> any
> > questions regarding the use of the proprietary information contained
> > therein, please contact the sender of this message immediately, and the
> > sender will provide you with further instructions.
> >
>

Re: April Rya podling report draft - please comment

[Josh Elser]

A little late, but it looks good to me too.

When are you submitting paperwork to graduate? :)

On 4/2/18 1:54 PM, Adina Crainiceanu wrote:

Hi,

I started the podling report for the ASF board due Wednesday April 4th.
Please review it and let me know of any recommendations/changes.

I'll submit a version tomorrow evening, and we can still modify it until
Wednesday.

Thanks,
Adina

Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system built
on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and query
processing techniques that scale to billions of triples across multiple
nodes.
Rya provides fast and easy access to the data through SPARQL, a conventional
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:

   1. Increase diversity of committers

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No

How has the community developed since the last report?
  * Apache Rya 3.2.12 (incubating) released
  * More people expressed interest in contributing to Rya
  * More discussions about graduation

How has the project developed since the last report?
  * Apache Rya 3.2.12 (incubating) released
  * Improved documentation for deploying Rya PCJ Updater
  * Created a Rya Shell for MongoDB
  * Integrated RyaStreams with the Rya Shell
  * Added PCJ indexer support for MongoDB backend
  * Implemented a forward-chaining rules engine that runs as a batch
process, operates on user-defined SPIN rules, and inserts derived
information back in Rya
  * Added the ability to use the MongoDB aggregation pipeline to evaluate
simple SPARQL expressions for MongoDB backend
  * Implemented single node Kafka streams incremental SPARQL processor

How would you assess the podling's maturity?
Please feel free to add your own commentary.

   [ ] Initial setup
   [ ] Working towards first release
   [ ] Community building
   [x] Nearing graduation
   [ ] Other:

Date of last release:

   2018-03-04

When were the last committers or PPMC members elected?

  * PPMC member Caleb Meier elected on Jan 3rd, 2017


Signed-off-by:

   [ ](rya) Josh Elser
  Comments:
   [ ](rya) Edward J. Yoon
  Comments:
   [ ](rya) Venkatesh Seetharam
  Comments:
   [ ](rya) Billie Rinaldi
  Comments:

IPMC/Shepherd notes:

Re: April Rya podling report draft - please comment

[Josh Elser]

Hi Jürgen,

These reports are more focused around the project's "health" with 
respect to its community as opposed to technical changes being made. So, 
it's usually not appropriate to call out specific changes which have 
been made.


That said, if the report hasn't already been submitted (I'm catching up 
myself), it would be nice to mention the recent contributions by Jürgen 
(and team?) as these are in the spirit of open source :)


On 4/3/18 9:28 AM, Jürgen Jakobitsch wrote:

hi adina..

might be important for your report.. i've created a set of improvement
issues in jira [1].
all related to the SPARQL endpoint.
note that those issues are basically not interferring with existing code,
but are mainly
a drive towards known standards from the semantic web/linked data community.

we (semantic web company) are actively developing on those issues and will
come up with
1. a sample sparql endpoint showcasing all the features we mentioned
 (this is gonna be just a tiny sample so people can take a look at those
features)
 it's a small maven spring project, so that it is possible to test the
features without
 having to rebuild the  whole of ra
2. if 1 = ok
 an integration into existing rya codebase with unit tests as a pull
request.

kind regards
jürgen

[1] https://issues.apache.org/jira/browse/RYA-477



*Jürgen Jakobitsch*
Innovation Director
Semantic Web Company GmbH
EU: +43-14021235 <+43%201%204021235>
US: (415) 800-3776
Mobile: +43-676-6212710 <+43%20676%206212710>
https://www.poolparty.biz
https://www.semantic-web.com

*Download now

**IDC
White Paper*
*Get certified!  **PoolParty Academy*


*PoolParty selected as a KMWorld Trend-Setting Product for 2017*


PERSONAL INFORMATION
| web   : http://www.turnguard.com
| foaf  : http://www.turnguard.com/turnguard
| g+: https://plus.google.com/111233759991616358206/posts
| skype : jakobitsch-punkt
| xmlns:tg  = "http://www.turnguard.com/turnguard#;
| blockchain : https://onename.com/turnguard

2018-04-03 15:11 GMT+02:00 Billie Rinaldi :


Sounds good to me.

On Mon, Apr 2, 2018 at 10:54 AM, Adina Crainiceanu  wrote:


Hi,

I started the podling report for the ASF board due Wednesday April 4th.
Please review it and let me know of any recommendations/changes.

I'll submit a version tomorrow evening, and we can still modify it until
Wednesday.

Thanks,
Adina

Rya

Rya (pronounced "ree-uh" /rēə/) is a cloud-based RDF triple store that
supports SPARQL queries. Rya is a scalable RDF data management system

built

on
top of Accumulo. Rya uses novel storage methods, indexing schemes, and
query
processing techniques that scale to billions of triples across multiple
nodes.
Rya provides fast and easy access to the data through SPARQL, a
conventional
query mechanism for RDF data.

Rya has been incubating since 2015-09-18.

Three most important issues to address in the move towards graduation:

   1. Increase diversity of committers

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

No

How has the community developed since the last report?
  * Apache Rya 3.2.12 (incubating) released
  * More people expressed interest in contributing to Rya
  * More discussions about graduation

How has the project developed since the last report?
  * Apache Rya 3.2.12 (incubating) released
  * Improved documentation for deploying Rya PCJ Updater
  * Created a Rya Shell for MongoDB
  * Integrated RyaStreams with the Rya Shell
  * Added PCJ indexer support for MongoDB backend
  * Implemented a forward-chaining rules engine that runs as a batch
process, operates on user-defined SPIN rules, and inserts derived
information back in Rya
  * Added the ability to use the MongoDB aggregation pipeline to evaluate
simple SPARQL expressions for MongoDB backend
  * Implemented single node Kafka streams incremental SPARQL processor

How would you assess the podling's maturity?
Please feel free to add your own commentary.

   [ ] Initial setup
   [ ] Working towards first release
   [ ] Community building
   [x] Nearing graduation
   [ ] Other:

Date of last release:

   2018-03-04

When were the last committers or PPMC members elected?

  * PPMC member Caleb Meier elected on Jan 3rd, 2017


Signed-off-by:

   [ ](rya) Josh Elser
  Comments:
   [ ](rya) Edward J. Yoon
  Comments:
   [ ](rya) Venkatesh Seetharam
  Comments:
   [ ](rya) Billie Rinaldi
  Comments:

IPMC/Shepherd notes:


--
Dr. Adina Crainiceanu
Associate Professor
Computer Science Department
United States Naval Academy
410-293-6822
ad...@usna.edu
http://www.usna.edu/Users/cs/adina/

Re: 4.x branch for RDF4j updates.

[Jeff Dasch]

The simplest thing for the community is to have a single branch of
development that is being supported/maintained.  Otherwise we're always
forward/backporting new features that apply to both versions which is a
pain.  I do think we should push a 3.x branch so we can always do a future
3.2.13 release if requested by the community.  Then someone should bump
master to 4.0.0-SNAPSHOT, and then we should pull in PR 245.

There have been a couple commits on master since the 3.2.12 release.  Do we
want to cut a 3.2.13 release with just those remaining commits, or should
they all get rolled into the 4.0.0 release?



On Mon, Apr 9, 2018 at 12:30 PM, Chilton, Kevin 
wrote:

> Hey Rya devs,
>
> I'd like to get PR #245 (RYA-405) pulled in.  This is a pretty big
> dependency change, and should probably involve a major version increment to
> 4.0.0.  Could we get a discussion going on the devlist about if we want to
> support a 3.x branch and a 4.x branch going forward, or just update master
> to 4.x.
>
> Thanks,
> Kevin
>
> NOTICE: This email message and all attachments transmitted with it may
> contain privileged and confidential information, and information that is
> protected by, and proprietary to, Parsons Corporation, and is intended
> solely for the use of the addressee for the specific purpose set forth in
> this communication. If the reader of this message is not the intended
> recipient, you are hereby notified that any reading, dissemination,
> distribution, copying, or other use of this message or its attachments is
> strictly prohibited, and you should delete this message and all copies and
> backups thereof. The recipient may not further distribute or use any of the
> information contained herein without the express written authorization of
> the sender. If you have received this message in error, or if you have any
> questions regarding the use of the proprietary information contained
> therein, please contact the sender of this message immediately, and the
> sender will provide you with further instructions.
>