As for me the main page of any product is important to make a good first impression. When I open the main page of JanusGraph it looks like the site was constructed in the 90s (sorry for criticism). I

I think it worth to create a Wikipedia page for JanusGraph and then add it into the list of notable graph databases. Here is a draft page: https://en.wikipedia.org/wiki/Draft:JanusGraph Here is a list

Thanks Henry. The policy has been updated already. https://github.com/JanusGraph/janusgraph/blob/master/docs/development.adoc

I am +1 for the suggestions to augment with RTC plus lazy consensus I am sorry for lag of responses for the proposal. - Henry

JanusGraph was built to use the TinkerPop APIs. For storage backends if you think that TinkerPop has an abstract class with an in-memory graph JanusGraph adds more storage backends that extend that

Hi Chris, Thank you very much for your reply. I am trying to join in the development of janusgraph, so I tried to understand the code architecture of janus. But I am confused about the what janusgraph

Hi Raul, This is more of a question for the JanusGraph users google group. That being said, here are some links that help explain the relationship. Here's the architecture overview from the

I am a little confused about the relationship between JanusGraph and gremlin, the storage backend(HBase, Cassandra, .etc) is configured by JanusGraph, but and the core traversal

Hi developers: I am a newbie to the group, I have used JanusGraph for a period and now I want one step further to take part in the development of janus graph. I have wathed the source code for a few

No, not at the moment, but it really isn't that difficult to pull together. Bringing attention to the PRs that need reviews is a much higher priority than automating this report.

Please tell me compiling this is at least partially automated.

Open Pull Requests 2018-09-04This report contains a summary of the open pull requests in the JanusGraph project ecosystem. Everybody interested is encouraged to submit review comments and approvals,

Apologies for the slow response. Back from a long holiday weekend in the USA. My opinion is that we need to keep pushing forward on releases and actively encourage users to move up to the latest

I'm not against merging this into 0.2, but I'm actually not sure whether we want to do that. My understanding is that new features go mainly into master and that the 0.2 branch mostly gets bug fixes

@Jason: I created a initial PR#2 to merge my codebase into official JanusGraph-Python repo you created. While the PR was successful, I wasn't able to add any reviewers, you or Florian or Misha. I'll

Hi Florian, Thanks for the link to PR. Didn't know I had stumbled upon the same issue already. Oops :-P Anyways, quick questions, are there any plan to merge those changes to 0.2 branch? Reason I'm

Ok, I moved Mr. Pounds code over into my fork of the new repo and put a "scratch" PR in: https://github.com/JanusGraph/janusgraph-docker/pull/1 Let's move our discussion/feedback on approach over to

JanusGraph currently uses Coverity as a static code analysis tool. While this already led to some findings, it can unfortunately not be used to analyse code changes from pull requests. I wondered

The PR for this issue is here: https://github.com/JanusGraph/janusgraph/pull/1231 I would appropriate if someone could review it. Best regards, Alexandr

I think that makes sense as a starting point. I'm assuming there will be a fair amount of testing, discussions, and iterations before it gets pushed up as an official image.