It looks like we have a wide consensus on starting a new channel for development discussions, but different opinions on whether we should directly create a dedicated channel for FoundationDB and also

Sorry I just saw this discussions. Thanks for pinging me, Misha. As Misha and Florian had mentioned, we did some investigating and exploring which "chat" tool we will use for JanusGraph. We chose

I think Misha has good arguments for staying on Gitter. I personally don't think that we need a high entry barrier for a developer chat as we currently also don't get many non-dev questions in the

For anyone following this thread. My primary query was to implement multi-get type implementation w.r.t. to my backend. Do check Marko's comment

This vote is now closed with a total of 4 +1s, no +0s and no -1s. The results are: BINDING VOTES: +1 (3 -- Oleksandr Porunov, Jan Jansen, Florian Hockmann) 0 (0) -1 (0) NON-BINDING VOTES: +1 (1 --

I thought about the separation of google groups. I think just a different channel of wouldn’t help because some people just ignore these rules. For example github issues, you have a template for

Are you trying to have the same separation on Gitter as we do with janusgraph-users@ and janusgraph-dev@ mailing lists? Would creating separate channels on Gitter not address this? Or are you saying

Hi Misra, Some of your reason are exactly the reason why I’m against Gitter. Currently Gitter is for JanusGraph just support chat. This channel would be hard to use for the developer focused talks.

So, we keep this VOTE thread for this release? In that case: I tested the new distributions by starting JanusGraph Server with the in-memory backend on both as described in the docs and then connected

FWIW, when we originally started JanusGraph, Henry Saputra (cc'd) lead an extensive evaluation of various chat options and we settled on Gitter, primarily because: unlike Slack, Gitter doesn't

Sounds good Jan. Let's go with the option where we have maximum developers/committers involved/or use it. So that the query posters / users can reach the maximum of our community :-)

Hi We have three different chat options. If no one wants to add something, i will open up a vote to decide which platform we want to use. (This will happen tomorrow.) Here the options

Hi All, Well the title may be misleading, as I couldnt think of better title. Let me give a brief about the issue we are talking about, the possible solutions we are thinking, and will need your

Hi Evgeniy Ignatiev. Sorry about late response. Might have missed out the message. Was really busy with trying all sorts of possible explorations to make SnowFlake + JanusGraph faster, but not much

I rarely check Gitter but I am totally OK with adding new specific channels. My vote is +1

gremlin-server has been fixed. Release jars, Sonatype artifacts and git tag have been updated

Makes sense. If we have enough persons interested in specific to a topic, we can create a separate channel for the same. :-) I would say +1 for this. If we can have Slack it will be lot better. Wider

I have submitted PR to fix the problem with default gremlin-server : https://github.com/JanusGraph/janusgraph/pull/2067 I also checked that gremlin server has the same problem with version 0.4.0.

It fails for both versions. The big problem I see with this is that our docs say about this: so it should really not expect some externally running Cassandra or Elasticsearch. This problem was

Florian, thank you for catching it. I didn't check yet but does "./bin/gremlin-server.sh start" fails on both truncated and full JanusGraph versions? I.e. I assume you should run CQL and ES externally