Blazegraph fork?

[berezovskyi]

Now that it seems Amazon has acquired Blazegraph (https://www.trademarkia.com/blazegraph-86498414.html etc), does it make sense for the OSS community to fork Blazegraph and restart the development (at least processing the PRs)?

[ianwdunlop]

Another goal of a forked/reborn blazegraph would be to migrate the sesame dependency to org.eclipse.rdf4j.

[ianwdunlop]

Anyone still interested in forking blazegraph and trying to keep it alive in the OSS community? Maybe someone already has. If so where is the project? Maybe a possible strategy is to fork and try to build from master and the latest unreleased branch (maybe 2.2.0). I've tried building but there are some test failures. Has anyone else tried building from source?

[beebs-systap]

@ianwdunlop @berezovskyi We've had some recent discussions on this and there seems to be community interest, which we're working to gather together. Feel free to update this interest for folks that would be interested.

@smalyshev @thompsonbry

[nyurik]

I propose we set up a project, e.g. bigblaze or blazebig seem to be non-trademarked, and add anyone interested from the community as members. Of course it would be great if the original authors of Blazegraph would participate in this development.

[ianwdunlop]

@nyurik That's a fair proposal. It would be good to hear more from @beebs-systap and folks about what their intentions are - whether they would like to keep the original blazegraph repo going or if it is time to start a new project based on the existing code.

[thompsonbry]

There have been some discussions about moving the project to wikidata / wikimedia and some strong expressions of interest for that from the their community. Adding Stas and Beebs.. Bryan

…

On Wed, Dec 5, 2018 at 01:55 Ian Dunlop ***@***.***> wrote: @nyurik <https://github.com/nyurik> That's a fair proposal. It would be good to hear more from @beebs-systap <https://github.com/beebs-systap> and folks about what their intentions are - whether they would like to keep the original blazegraph repo going or if it is time to start a new project based on the existing code. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACdv4Om1bJrQQYFtPT0wwL5mEC5_CeoDks5u15ghgaJpZM4TSFRN> .

[nyurik]

I think @smalyshev is doing an amazing job with various Blazegraph improvements, and certainly should be one of the key people driving this project forward, but I do not think Blazegraph fork should be under Wikimedia's umbrella, using less convenient or familiar tooling (gerrit/phabricator), or managed by WMF management. Rather, I think it should remain in GitHub e.g. a separate organization as a typical open source project, with a low barrier of entry, a wide community of contributing and reviewing developers, and WMF developers actively participating.

[thompsonbry]

I suspect that the project could stay where it is in terms of tooling. The question is more about the responsibility for producing releases. Brad has discussed some options for providing CI resources. It would be great to get a sense of how many people would be interested in leaning in to help wikimedia support the open source blazegraph platform. That might help them make this transition happen. Thanks, Bryan

…

On Wed, Dec 5, 2018 at 7:54 AM Yuri Astrakhan ***@***.***> wrote: I think @smalyshev <https://github.com/smalyshev> is doing an amazing job with various Blazegraph improvements, and certainly should be one of the key people driving this project forward, but I do not think Blazegraph fork should be under Wikimedia's umbrella, using less convenient or familiar tooling (gerrit/phabricator), or managed by WMF management. Rather, I think it should remain in GitHub e.g. a separate organization as a typical open source project, with a low barrier of entry, a wide community of contributing and reviewing developers, and WMF developers actively participating. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACdv4DEpGkS2h7KNyYWDf_IGmP6xjAPMks5u1-wWgaJpZM4TSFRN> .

[turbolent]

In https://github.com/turbolent/embergraph I've took 2.1.5-RC and started renaming the code to Embergraph (to avoid inflicting on trademarks), cleaning up the code base, and updating it (Java 8).

I plan on mostly updating the SPARQL server (probably replacing Jetty and servlets with something else) and will try to update dependencies (e.g. migrate to RDF4J).

[thompsonbry]

Awesome for getting involved. However, you might consider just issuing CRs. Stas should have access to a CI setup and he and/or Brad can cut releases. Bryan

…

On Sat, Jan 12, 2019 at 22:51 Bastian Müller ***@***.***> wrote: In https://github.com/turbolent/embergraph I've took 2.1.5-RC and started renaming the code to Embergraph (to avoid inflicting on trademarks), cleaning up the code base, and updating it (Java 8). I plan on mostly updating the SPARQL server (probably replacing Jetty and servlets with something else) and will try to update dependencies (e.g. migrate to RDF4J). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#86 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACdv4DUIYPRwxxyzwvX7u44rTqdYgcwyks5vCtdXgaJpZM4TSFRN> .

[thompsonbry]

CR == pull request On Sun, Jan 13, 2019 at 16:41 Bryan B. Thompson <thompsonbry@gmail.com> wrote:

…

Awesome for getting involved. However, you might consider just issuing CRs. Stas should have access to a CI setup and he and/or Brad can cut releases. Bryan On Sat, Jan 12, 2019 at 22:51 Bastian Müller ***@***.***> wrote: > In https://github.com/turbolent/embergraph I've took 2.1.5-RC and > started renaming the code to Embergraph (to avoid inflicting on > trademarks), cleaning up the code base, and updating it (Java 8). > > I plan on mostly updating the SPARQL server (probably replacing Jetty and > servlets with something else) and will try to update dependencies (e.g. > migrate to RDF4J). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#86 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ACdv4DUIYPRwxxyzwvX7u44rTqdYgcwyks5vCtdXgaJpZM4TSFRN> > . >

[beebs-systap]

@turbolent Would you be amenable to setting up a CLA to push the changes back into the core Blazegraph?

[ianwdunlop]

2 quick comments. Why do we need a CLA to push changes (via pull request I assume) back into the core blazegraph repo? Is this a different repo from this one? Isn't all this covered by the current licence (GPL 2)?
From recent comments it seems that you would like to restart blazegraph development using this repo rather than fork off to anywhere else. I like that idea.

[nyurik]

In https://github.com/turbolent/embergraph I've took 2.1.5-RC and started renaming the code to Embergraph (to avoid inflicting on trademarks), cleaning up the code base, and updating it (Java 8).

I plan on mostly updating the SPARQL server (probably replacing Jetty and servlets with something else) and will try to update dependencies (e.g. migrate to RDF4J).

I do like the Embergraph name, but there does seem to be another project by that name. Not sure if that's a problem.

I am not sure what you meant by renaming the code to Embergraph - IANAL, but it seems MariaDB who went through the similar process did not modified the actual code - as that would make the code incompatible with extensions/external modifications. There is a difference between classnames that use Blazegraph or Bigdata internally, and the branding of the product. I suspect we only need to modify the later.