[jira] [Commented] (TINKERPOP-2137) Gremlin Javascript can't be used in Angular applications

[Jean-Baptiste Musso (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16752138#comment-16752138
 ] 

Jean-Baptiste Musso commented on TINKERPOP-2137:


This could require different build steps and/or entrypoints so different 
runtimes (Node.js or browsers) can use the library with different dependencies. 
In theory, it shouldn't be that hard to bake in full support for both Node.js 
and browsers. It could require a bit of work to have a both secure and 
lightweight browser version though.

> Gremlin Javascript can't be used in Angular applications
> 
>
> Key: TINKERPOP-2137
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2137
> Project: TinkerPop
>  Issue Type: Bug
>  Components: javascript
>Affects Versions: 3.4.0
> Environment: "@angular/cdk": "^7.2.1",
>Reporter: Dominik Franek
>Priority: Major
>
> If you try to install gremlin using
> {code:java}
> ng add gremlin{code}
> it gets you:
> _The package that you are trying to add does not support schematics. You can 
> try using a different version of the package or contact the package author to 
> add ng-add support._
> If you try using
> {code:java}
> npm i gremlin{code}
> it is installed, however the gremlin package can't be used in Angular 
> Application. Is there any way to fix it to work for ng-add? If not, maybe the 
> documentation needs an update of what Javascript environments are supported, 
> because our project intended to use Gremlin (we tried using Java, that 
> Gremlin is perfect... now when developing we found out that it is not 
> possible in Angular :) ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [DISCUSS] Name of 3.4.x

[Jean-Baptiste Musso]

> Boyz II Men - ha, I hadn't considered that angle. I assumed the 4 Seasons
> was a Vivaldi reference.

Haha, me neither! I actually didn't know this group. That was indeed a
Vivaldi reference.

Jean-Baptiste

On Thu, Mar 1, 2018 at 2:33 PM, Jason Plurad  wrote:

> Boyz II Men - ha, I hadn't considered that angle. I assumed the 4 Seasons
> was a Vivaldi reference.
>
> How about David Bowie? The Gremlin Who Sold the World
> On Thu, Mar 1, 2018 at 8:06 AM Stephen Mallette 
> wrote:
>
> > I'm guessing at the reference for "4 Seasons of Gremlin" - are we talking
> > Boyz || Men and "4 Seasons of Loneliness"?
> >
> > >  Yeah, I'd like to see what Gremlyn Manson would look like!
> >
> > would he look that much different than our "Nine Inch Nails Gremlin"?
> >
> >
> >
> > On Tue, Feb 27, 2018 at 10:58 AM, Robert Dale  wrote:
> >
> > > Yeah, I'd like to see what Gremlyn Manson would look like!
> > >
> > > Robert Dale
> > >
> > > On Tue, Feb 27, 2018 at 10:40 AM, Daniel Kuppitz 
> > wrote:
> > >
> > > > Four Rusted Gremlins (reference
> > > > ) :)
> > > >
> > > > On Tue, Feb 27, 2018 at 7:47 AM, Stephen Mallette <
> > spmalle...@gmail.com>
> > > > wrote:
> > > >
> > > > > We need a release name and associated Gremlin logo for the 3.4.x
> > series
> > > > of
> > > > > TinkerPop. Recall that names should be related to music and
> include a
> > > > > number. Thus far we've had:
> > > > >
> > > > > * Gremlin Symphony #40 in G Minor (3.3.x)
> > > > > * Nine Inch Gremlins (3.2.x)
> > > > > * A 187 On The Undercover Gremlinz (3.1.x)
> > > > > * A Gremlin Rāga in 7/16 Time (3.0.x)
> > > > >
> > > > > Please submit a name with a logo idea - a name where we can't get a
> > > logo
> > > > > made doesn't really work too well. Thanks.
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Name of 3.4.x

[Jean-Baptiste Musso]

The 4 Seasons of Gremlin.

Also ok for TinkerPop 4. Works for 3.4.x series though!

Jean-Baptiste

On Tue, Feb 27, 2018 at 3:47 PM, Stephen Mallette 
wrote:

> We need a release name and associated Gremlin logo for the 3.4.x series of
> TinkerPop. Recall that names should be related to music and include a
> number. Thus far we've had:
>
> * Gremlin Symphony #40 in G Minor (3.3.x)
> * Nine Inch Gremlins (3.2.x)
> * A 187 On The Undercover Gremlinz (3.1.x)
> * A Gremlin Rāga in 7/16 Time (3.0.x)
>
> Please submit a name with a logo idea - a name where we can't get a logo
> made doesn't really work too well. Thanks.
>

Re: [TinkerPop] Re: Docker images: gremlin-server and gremlin-console

[Jean-Baptiste Musso]

 JIRA
> >>>>> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapi
> >>>> dView=25=INFRA
> >>>>> and we can add that repo to the org.
> >>>> Is that helpful for what we're talking about here? Are there other
> >>>> questions to ask?
> >>>>
> >>>>
> >>>>
> >>>> On Thu, Jun 8, 2017 at 2:36 AM, Florian Hockmann <
> >> f...@florian-hockmann.de
> >>>> wrote:
> >>>>
> >>>>> I think official images would be a very good idea as there exist
> >>>>> currently a lot of images, especially for Gremlin Server. Users
> >>> typically
> >>>>> search for the official image or just take the image with the most
> >>> pulls.
> >>>>> Images published directly by TinkerPop would get the most attention
> so
> >>>>> users don't end up with some image that isn't actively maintained.
> >>>>>
> >>>>> Another advantage of integrating the images in TinkerPop would
> >> probably
> >>>>> be that the deployment could be integrated into TinkerPop's usual
> >>> release
> >>>>> cycle. So new images can be published directly for each new version.
> >>>>>
> >>>>> Am Dienstag, 6. Juni 2017 18:39:09 UTC+2 schrieb Stephen Mallette:
> >>>>>> Would it be interesting to anyone for TinkerPop to have an official
> >>>>>> docker image?
> >>>>>>
> >>>>>> On Tue, Jun 6, 2017 at 12:22 PM, Benjamin Ricaud <
> >> benjami...@gmail.com
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Thanks Jean-Baptiste,
> >>>>>>>
> >>>>>>> I have also done a container for the gremlin-server 3.2.4,
> >> configured
> >>>>>>> to be used with gremlin-python:
> >>>>>>> https://hub.docker.com/r/bricaud/gremlin-server/
> >>>>>>>
> >>>>>>> I noticed that you do not need the IP trick for the server to be
> >>>>>>> accessed. If you set
> >>>>>>> host: 0
> >>>>>>> in your gremlin-conf.yaml, (and open the port with -p 8182:8182)
> you
> >>>>>>> can access the server.
> >>>>>>> (see my conf files on the github repo).
> >>>>>>>
> >>>>>>> Best,
> >>>>>>> Benjamin
> >>>>>>>
> >>>>>>> Le jeudi 1 juin 2017 00:37:07 UTC+2, Jean-Baptiste Musso a écrit :
> >>>>>>>> Dear TinkerPop,
> >>>>>>>>
> >>>>>>>> I published a couple automatically built Docker images for
> >>>>>>>> gremlin-server and gremlin-console (current image tags: latest,
> >>> 3.2.4, 3.2
> >>>>>>>> and 3):
> >>>>>>>>
> >>>>>>>> https://hub.docker.com/r/jbmusso/gremlin-server/
> >>>>>>>> https://hub.docker.com/r/jbmusso/gremlin-console/
> >>>>>>>>
> >>>>>>>> I built these because I needed to quickly start different
> >>>>>>>> configurations of gremlin-server when developing the
> >>> gremlin-javascript
> >>>>>>>> client.
> >>>>>>>> Source repository: https://github.com/jbmusso/docker-tinkerpop
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Start gremlin-server with:
> >>>>>>>>
> >>>>>>>> docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Defaults to conf/gremlin-server.yaml within that container, or
> pass
> >>>>>>>> another .yaml file:
> >>>>>>>>
> >>>>>>>> docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4
> >>>>>>>> conf/gremlin-server-modern.yaml
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Mounting your own config .yaml file with docker run -v argument
> >>> should
> >>>>>>>> also work (untested).
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> You can play with the console this way (make sure you run with the
> >>> -it
> >>>>>>>> flags so Docker don't quit and actually lets you type commands
> from
> >>> your
> >>>>>>>> shell):
> >>>>>>>>
> >>>>>>>> docker run -it jbmusso/gremlin-console:3.2.4
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> If you want to execute a file located on your host from within a
> >>>>>>>> gremin-console container (the following assumes that foobar.groovy
> >>> file
> >>>>>>>> exists in your $HOME dir):
> >>>>>>>>
> >>>>>>>> docker run -it -v ~/foobar.groovy:/script/foobar.groovy
> >>>>>>>> jbmusso/gremlin-console:3.2.4 -e /script/foobar.groovy
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Jean-Baptiste
> >>>>>>>>
> >>>>>>>> --
> >>>>>>> You received this message because you are subscribed to the Google
> >>>>>>> Groups "Gremlin-users" group.
> >>>>>>> To unsubscribe from this group and stop receiving emails from it,
> >> send
> >>>>>>> an email to gremlin-user...@googlegroups.com.
> >>>>>>> To view this discussion on the web visit
> >>> https://groups.google.com/d/ms
> >>>>>>> gid/gremlin-users/c8141999-2e9d-4fd3-a763-5630866e5c6b%40goo
> >>>>>>> glegroups.com
> >>>>>>> <https://groups.google.com/d/msgid/gremlin-users/c8141999-
> >>> 2e9d-4fd3-a763-5630866e5c6b%40googlegroups.com?utm_medium=
> >>> email_source=footer>
> >>>>>>> .
> >>>>>>>
> >>>>>>> For more options, visit https://groups.google.com/d/optout.
> >>>>>>>
> >>>>>> --
> >>>>> You received this message because you are subscribed to the Google
> >>> Groups
> >>>>> "Gremlin-users" group.
> >>>>> To unsubscribe from this group and stop receiving emails from it,
> send
> >>> an
> >>>>> email to gremlin-users+unsubscr...@googlegroups.com.
> >>>>> To view this discussion on the web visit
> >> https://groups.google.com/d/ms
> >>>>> gid/gremlin-users/8cf01027-2ef6-48d5-bc2a-34facea9c0f8%40
> >>> googlegroups.com
> >>>>> <https://groups.google.com/d/msgid/gremlin-users/8cf01027-
> >>> 2ef6-48d5-bc2a-34facea9c0f8%40googlegroups.com?utm_medium=
> >>> email_source=footer>
> >>>>> .
> >>>>>
> >>>>> For more options, visit https://groups.google.com/d/optout.
> >>>>>
> >>>>
>
>

Re: [DISCUSS] Gremlin JavaScript release

[Jean-Baptiste Musso]

Hmm. It looks like you can only grant access to team of developers for
@scoped package, but not for standard (unscoped) packages.
I can make the "tinkerpop" user owner of that "gremlin" package, if that
helps.

Jean-Baptiste

On Tue, Feb 13, 2018 at 9:58 AM, Jorge Bay Gondra <jorgebaygon...@gmail.com>
wrote:

> Jean-Baptiste, could you grant tinkerpop:developers team access to the
> gremlin package?
>
> Once we all have access, it would be nice to have a beta release of
> 3.2.8/3.3.2 as soon as possible, to allow users to start giving it a try.
>
> There aren't any others tickets in JIRA affecting the javascript GLV that I
> could find. It has been a long road for the GLV but being an scripting
> language, I expect it to be easier to maintain than the C# GLV :)
>
> If there aren't any blockers, it would be nice to start discussing a
> timeline for 3.2.8/3.3.2.
>
> Cheers,
> Jorge
>
>
> On Mon, Feb 12, 2018 at 1:43 PM, Stephen Mallette <spmalle...@gmail.com>
> wrote:
>
> > I've added The Baptist to the the org in npm - all done
> >
> > On Mon, Feb 5, 2018 at 12:20 PM, Stephen Mallette <spmalle...@gmail.com>
> > wrote:
> >
> > > I have no objections to using "gremlin" since it sounds like we have
> ways
> > > to make sure users don't break in unclear ways. I'll give others a
> chance
> > > to respond and barring no additional discussion will get The Baptist
> > added
> > > to the org in npm. i guess we can proceed to the next step from there.
> > >
> > > On Mon, Feb 5, 2018 at 3:55 AM, Jorge Bay Gondra <
> > jorgebaygon...@gmail.com
> > > > wrote:
> > >
> > >> Reusing the existing package name while adding a deprecation message,
> > >> sounds good to me then.
> > >>
> > >> Keep in mind we will be releasing both for 3.2.x and 3.3.x branches,
> so
> > >> any
> > >> deprecation message should be for versions lower than 3.2.
> > >>
> > >> If all agree, the next step will be to add jbmusso to tinkerpop org on
> > npm
> > >> and add him to the "developers" team. I can't do it, as I'm not an
> > "owner"
> > >> of the organization.
> > >> Once you have the proper access rights, you should grant write access
> to
> > >> package "tinkerpop:developers".
> > >>
> > >> Thanks,
> > >> Jorge
> > >>
> > >>
> > >> On Sat, Feb 3, 2018 at 12:45 PM, Jean-Baptiste Musso <
> jbmu...@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > npm (and yarn) now freeze versions aggressively in package.json and
> > >> > package-lock.json or yarn.lock, respectively. Publishing a new
> version
> > >> on
> > >> > the v3.y.z (v.3.3.2) shouldn't be a concern for most users since,
> > >> luckily,
> > >> > I never published past the 2.y.z major version on npm.
> > >> >
> > >> > What I'm thinking is that we could add a deprecation message that
> > users
> > >> > will see when installing all releases prior to using v3.3.2 when
> it's
> > >> > published. https://docs.npmjs.com/cli/deprecate should be helpful.
> > >> >
> > >> > I don't think that will break anything unless people added
> "gremlin":
> > >> "*"
> > >> > in their package.json, but I guess very few people did that. What
> will
> > >> > break is example in live docs, such as Microsoft Azure CosmosDB,
> where
> > >> > installation requirements are "npm install gremlin": this will
> install
> > >> > v3.3.2, and break things. The quick fix for them is to update their
> > doc
> > >> to
> > >> > "npm install gremlin@v2" - that should work.
> > >> >
> > >> > I also need to deprecate "gremlin-javascript" on npm (that lib still
> > >> gets
> > >> > downloaded!), since I was pushing using this name before I was
> donated
> > >> the
> > >> > "gremlin" package name (I think 2-3 years ago). That'll be the
> second
> > >> time
> > >> > this package name is transferred, actually - back in the days, it
> was
> > a
> > >> > Node.js/JVM bridge using node-java.
> > >> >
> > >> > Another option is to publish under "@tinkerpop/gremlin", but I thi

Re: [DISCUSS] Gremlin JavaScript release

[Jean-Baptiste Musso]

npm (and yarn) now freeze versions aggressively in package.json and
package-lock.json or yarn.lock, respectively. Publishing a new version on
the v3.y.z (v.3.3.2) shouldn't be a concern for most users since, luckily,
I never published past the 2.y.z major version on npm.

What I'm thinking is that we could add a deprecation message that users
will see when installing all releases prior to using v3.3.2 when it's
published. https://docs.npmjs.com/cli/deprecate should be helpful.

I don't think that will break anything unless people added "gremlin": "*"
in their package.json, but I guess very few people did that. What will
break is example in live docs, such as Microsoft Azure CosmosDB, where
installation requirements are "npm install gremlin": this will install
v3.3.2, and break things. The quick fix for them is to update their doc to
"npm install gremlin@v2" - that should work.

I also need to deprecate "gremlin-javascript" on npm (that lib still gets
downloaded!), since I was pushing using this name before I was donated the
"gremlin" package name (I think 2-3 years ago). That'll be the second time
this package name is transferred, actually - back in the days, it was a
Node.js/JVM bridge using node-java.

Another option is to publish under "@tinkerpop/gremlin", but I think it's
best if we can force people to no longer use the current "gremlin" package,
and use the official GLV, also under that same name. Having many package
names will add a lot of confusion in the next month/years, and I think it's
best to risk breaking few things in the short term rather than adding *a
lot* of confusion on the long term.

Jean-Baptiste

On Fri, Feb 2, 2018 at 1:32 PM, Stephen Mallette 
wrote:

> It stinks that we would break 3K+ downloads. I don't know the npm
> environment too well. Can a break be expected for people? The current
> version of https://www.npmjs.com/package/gremlin is at 2.6.0 and we would
> publish at 3.x which people could expect as a breaking change, no?
>
> On Tue, Jan 30, 2018 at 9:54 AM, Jorge Bay Gondra <
> jorgebaygon...@gmail.com>
> wrote:
>
> > Hi,
> > Now that the JavaScript GLV has been merged, it will be nice to have an
> > official pre-release (RC / beta) on the npm package manager as soon as
> > possible to allow users to start giving it a try.
> >
> > The package name identifier in the package.json is currently
> > gremlin-javascript ,
> > which is under the tinkerpop organization created by Stephen:
> > https://www.npmjs.com/org/tinkerpop
> > npm orgs are a nice feature as it let's you handle the team members that
> > can be collaborators (publish versions).
> >
> > Jean-Baptiste offered
> >  to
> > transfer ownership of gremlin 
> > package to TinkerPop, so we can publish the GLV under that package name.
> My
> > only concern would be to break the functionality for current users, as
> the
> > existent package has 3K downloads per month. I would prefer to include a
> > message on the gremlin package explaining the difference with
> > gremlin-javascript (or recommending the GLV for future development), but
> I
> > don't feel strongly either way.
> >
> > Cheers,
> > Jorge
> >
>

Re: Transferring "gremlin" package name on npmjs.org for upcoming GLV

[Jean-Baptiste Musso]

I forgot to add: Stephen mentioned using the name "@tinkerpop/gremlin"
thanks to npmjs.org support for @scoped/ packages.
This is neat because part of gremlin-javascript official GLV could also be
published as other modules under that same namespace, such as
@tinkerpop/graphson, etc., so people could only consume these (helps with
bundle size for browser environments). Not strictly needed right now but
could be useful in the future.

Jean-Baptiste

On Fri, Dec 1, 2017 at 12:57 PM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> Thanks for offering the "gremlin" name up for use. Does anyone think we
> should stick with "gremlin-javascript" as opposed to just "gremlin" (this
> of course refers to npm naming - our project module will still be
> gremlin-javascript in our code base).
>
> I hope the CosmosDB folks are subscribed to this list to follow along with
> development :) but if not perhaps you could direct them to this thread so
> that they are aware of what's is being discussed.
>
> Good to know that we don't have trouble with versioning. I really would
> like all things TinkerPop to be released on the same version number.
> Ideally the first release of gremlin-javascript should go into play for
> 3.3.2/3.2.8.
>
> On Fri, Dec 1, 2017 at 5:09 AM, Jean-Baptiste Musso <jbmu...@gmail.com>
> wrote:
>
> > Hi TinkerPop,
> >
> > With the recent work on gremlin-javascript by Jorge [1], I see no reason
> > for the "gremlin" package currently published on npmjs.org [2] to
> continue
> > to exist as a distinct project. Newcomers would be so confused, and I
> don't
> > think fragmentation is a good idea here. I think it should be replaced by
> > the official gremlin-javascript GLV that is being developed here. I'm ok
> to
> > transfer/donate the "gremlin" package name to the Apache TinkerPop
> project
> > if we think it's a good idea to use that name.
> >
> > However, the current "gremlin" JS package has been mentioned by some
> > implementers (Microsoft Azure CosmosDB [3]), so maybe we want to sync
> with
> > them first so they get a chance to update their documentation/examples
> > considering there will be several breaking changes. Maybe I can help on
> > that.
> >
> > Also, there shouldn't be issues with versions since I only published on
> the
> > v2.x branch there (npmjs package versions are basically immutable). The
> GLV
> > can safely be published there as 3.3.x and 3.2.x once ready. I think I
> can
> > flag previously published versions as "deprecated" so people get soft
> > warnings when attempting to install these, encouraging them to upgrade to
> > the official GLV (need to check that).
> >
> > Jean-Baptiste
> >
> > [1] https://github.com/apache/tinkerpop/pull/695
> > [2] npmjs.com/package/gremlin
> > [3] https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-nodejs
> >
>

Transferring "gremlin" package name on npmjs.org for upcoming GLV

[Jean-Baptiste Musso]

Hi TinkerPop,

With the recent work on gremlin-javascript by Jorge [1], I see no reason
for the "gremlin" package currently published on npmjs.org [2] to continue
to exist as a distinct project. Newcomers would be so confused, and I don't
think fragmentation is a good idea here. I think it should be replaced by
the official gremlin-javascript GLV that is being developed here. I'm ok to
transfer/donate the "gremlin" package name to the Apache TinkerPop project
if we think it's a good idea to use that name.

However, the current "gremlin" JS package has been mentioned by some
implementers (Microsoft Azure CosmosDB [3]), so maybe we want to sync with
them first so they get a chance to update their documentation/examples
considering there will be several breaking changes. Maybe I can help on
that.

Also, there shouldn't be issues with versions since I only published on the
v2.x branch there (npmjs package versions are basically immutable). The GLV
can safely be published there as 3.3.x and 3.2.x once ready. I think I can
flag previously published versions as "deprecated" so people get soft
warnings when attempting to install these, encouraging them to upgrade to
the official GLV (need to check that).

Jean-Baptiste

[1] https://github.com/apache/tinkerpop/pull/695
[2] npmjs.com/package/gremlin
[3] https://docs.microsoft.com/en-us/azure/cosmos-db/create-graph-nodejs

Docker images: gremlin-server and gremlin-console

[Jean-Baptiste Musso]

Dear TinkerPop,

I published a couple automatically built Docker images for gremlin-server
and gremlin-console (current image tags: latest, 3.2.4, 3.2 and 3):

https://hub.docker.com/r/jbmusso/gremlin-server/
https://hub.docker.com/r/jbmusso/gremlin-console/

I built these because I needed to quickly start different configurations of
gremlin-server when developing the gremlin-javascript client.
Source repository: https://github.com/jbmusso/docker-tinkerpop


Start gremlin-server with:

docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4


Defaults to conf/gremlin-server.yaml within that container, or pass another
.yaml file:

docker run -p 8182:8182 jbmusso/gremlin-server:3.2.4
conf/gremlin-server-modern.yaml


Mounting your own config .yaml file with docker run -v argument should also
work (untested).


You can play with the console this way (make sure you run with the -it
flags so Docker don't quit and actually lets you type commands from your
shell):

docker run -it jbmusso/gremlin-console:3.2.4


If you want to execute a file located on your host from within a
gremin-console container (the following assumes that foobar.groovy file
exists in your $HOME dir):

docker run -it -v ~/foobar.groovy:/script/foobar.groovy
jbmusso/gremlin-console:3.2.4 -e /script/foobar.groovy




Jean-Baptiste

[jira] [Commented] (TINKERPOP-1672) Use python-style syntax for YAML configuration files

[Jean-Baptiste Musso (JIRA)]

[ 
https://issues.apache.org/jira/browse/TINKERPOP-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15990763#comment-15990763
 ] 

Jean-Baptiste Musso commented on TINKERPOP-1672:


Heh, yup - I kind of opened this issue thinking I should be committing that 
patch if feasible ;).

> Use python-style syntax for YAML configuration files
> 
>
> Key: TINKERPOP-1672
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1672
> Project: TinkerPop
>  Issue Type: Improvement
>  Components: console, server
>Affects Versions: 3.1.6, 3.2.4
>    Reporter: Jean-Baptiste Musso
>    Assignee: Jean-Baptiste Musso
>Priority: Trivial
>  Labels: beginner, easyfix
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> YAML configuration files could be made less verbose and more 
> human-readable/editable by removing curly braces and commas.
> Indeed, according to [Wikipedia|https://fr.wikipedia.org/wiki/YAML]:
> {quote}
> YAML 1.2 is a superset of JSON, another minimalist data serialization format 
> where braces and brackets are used instead of indentation.
> {quote}
> Most .yaml configuration files in the current codebase have these extra curly 
> braces and commas. We could clean these files and use python-style 
> nesting/indendation. Tools such as http://www.yamllint.com could help with 
> the transition.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (TINKERPOP-1672) Use python-style syntax for YAML configuration files

[Jean-Baptiste Musso (JIRA)]

Jean-Baptiste Musso created TINKERPOP-1672:
--

 Summary: Use python-style syntax for YAML configuration files
 Key: TINKERPOP-1672
 URL: https://issues.apache.org/jira/browse/TINKERPOP-1672
 Project: TinkerPop
  Issue Type: Improvement
  Components: console, server
Affects Versions: 3.2.4, 3.1.6
Reporter: Jean-Baptiste Musso
Assignee: Jean-Baptiste Musso
Priority: Trivial


YAML configuration files could be made less verbose and more 
human-readable/editable by removing curly braces and commas.

Indeed, according to [Wikipedia|https://fr.wikipedia.org/wiki/YAML]:
{quote}
YAML 1.2 is a superset of JSON, another minimalist data serialization format 
where braces and brackets are used instead of indentation.
{quote}

Most .yaml configuration files in the current codebase have these extra curly 
braces and commas. We could clean these files and use python-style 
nesting/indendation. Tools such as http://www.yamllint.com could help with the 
transition.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: [TinkerPop] New PMC Member: Robert Dale

[Jean-Baptiste Musso]

Cheers Robert!

Jean-Baptiste

On Tue, Apr 18, 2017 at 5:16 PM, Stephen Mallette 
wrote:

> We would like to announce that Robert Dale is now a member of the Apache
> TinkerPop PMC. Robert has been a helpful to the TinkerPop community in a
> variety of ways for some time now as a committer and has demonstrated
> ongoing interest in the growth of the project which makes him a welcome
> member to the PMC.
>
> As per tradition, I include with this announcement the TinkerPop Guild
> portrait as a reminder of the olden and golden days of doing graphs:
>
> https://upload.wikimedia.org/wikipedia/commons/c/ce/Jan_de_Bray_002.jpg
>
> Welcome to the PMC, Robert - we'll have to get the portrait amended to
> include you. Or you can just be the guy with the big cookie thing.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Gremlin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gremlin-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/gremlin-users/CAA-H438zY86jjnKK1XD241%3DUorZA1tKoacXUbdSRfq4g1zETYQ%
> 40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

Re: [DISCUSS] Add HGraphDB to graph system listing

[Jean-Baptiste Musso]

Interesting thing. +1 to adding HGraphDB to the list.

Minor concern: I'm not sure if we want to manage a curated list of
implementations and maybe restrict to more mature projects. I'm just
thinking out loud here: I'm not targeting HGraphDB specifically (and I wish
them good luck - *cheers*). My main concern is that the project is very
young, but graph databases need as much publicity as they can.

Jean-Baptiste

On Thu, Nov 10, 2016 at 8:58 PM, Ted Wilmes  wrote:

> Hello everyone,
> Robert Yokota notified us today that he has developed an
> Apache TinkerPop enabled graph db: https://github.com/rayokota/hgraphdb.
> Correct me if I'm wrong Robert, but it looks like it's at the TinkerPop
> 3.2.3 version.
>
> I think HGraphDB meets our index listing requirements but I wanted to bring
> it up
> just in case anyone felt differently.  Unless there are any objections,
> I'll assume lazy
> consensus in three days (Sunday, November 13, 2016 2:00 CST) and add
> HGraphDB
> to the graph systems listing.
>
> Thanks,
> Ted
>

Re: [TinkerPop] New Committer: Robert Dale

[Jean-Baptiste Musso]

Welcome aboard Robert!

On Thursday, 27 October 2016, Stephen Mallette  wrote:

> The Project Management Committee (PMC) for Apache TinkerPop has asked
> Robert Dale to become a committer and we are pleased to announce that he
> has accepted.
>
> Robert has submitted a number of quality pull requests to TinkerPop
> covering both new features and bug/documentation fixes and has been engaged
> in many different development discussions that have shaped the direction
> TinkerPop has taken. He's also been helpful on the user mailing list,
> providing some nice answers to those who have needed support. All of that
> activity made him a sound choice for committership.
>
> Let this proclamation traverse the entirety of The TinkerPop so that all
> may know to welcome Robert to the TinkerPop Guild!
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Gremlin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gremlin-users+unsubscr...@googlegroups.com
> 
> .
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/gremlin-users/CAA-H43-DpGHAAxxgb6ib-qXKML-etQnP%
> 2BRP5jfeJm4hRGrt_vg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Jean-Baptiste

Re: Store and Aggregate

[Jean-Baptiste Musso]

I also recall Daniel mentioning in a post that .store() in OLAP works like
.aggregate() in OLTP so this change could help users distinguish between
both worlds and BFS/DFS.

On Wednesday, 21 September 2016, Dylan Millikin <dylan.milli...@gmail.com>
wrote:

> yeah I like the barrier().store() best as well.
>
> On Wed, Sep 21, 2016 at 11:46 AM, Jean-Baptiste Musso <jbmu...@gmail.com
> <javascript:;>>
> wrote:
>
> > I think barrier().store() for .aggregate() is very appropriate and fully
> > tells what is going on.
> >
> > I like both, +1 for one or the other.
> >
> > People also tend to confuse .as() and .store()/.aggregate().
> >
> > On Tuesday, 20 September 2016, Marko Rodriguez <okramma...@gmail.com
> <javascript:;>>
> > wrote:
> >
> > > Hi,
> > >
> > > I was thinking that store() and aggregate() should simply be “store().”
> > >
> > > store() -> store(local)
> > > aggregate() -> store(global)
> > >
> > > Or:
> > >
> > > aggregate() ->  barrier().store()
> > >
> > > Random thoughts…
> > >
> > > Marko.
> > >
> > > http://markorodriguez.com
> > >
> > >
> > >
> > >
> >
> > --
> > Jean-Baptiste
> >
>


-- 
Jean-Baptiste

Re: Documentation deprecation warning on Github Wikis

[Jean-Baptiste Musso]

Done - I just updated all Wiki pages on the tinkerpop/blueprints
Github repository.

Jean-Baptiste

On Tue, Jul 12, 2016 at 1:44 AM, Jason Plurad <plur...@gmail.com> wrote:
> +1
>
> Could you also update these? I've fielded lots of questions referring to
> these old graph I/O pages.
>
> https://github.com/tinkerpop/blueprints/wiki/GraphSON-Reader-and-Writer-Library
>
> https://github.com/tinkerpop/blueprints/wiki/GraphML-Reader-and-Writer-Library
>
> https://github.com/tinkerpop/blueprints/wiki/GML-Reader-and-Writer-Library
>
> https://github.com/tinkerpop/blueprints/wiki/Batch-Implementation
>
> Thanks!
> -- Jason
> On Mon, Jul 11, 2016 at 6:36 PM Jean-Baptiste Musso <jbmu...@gmail.com>
> wrote:
>
>> Quick follow up - the changes to the TP2 Gremlin documentation are now
>> live. Props to Dylan since I couldn't remember where this was first
>> mentioned.
>>
>> See for example
>> https://github.com/tinkerpop/gremlin/wiki/Depth-First-vs.-Breadth-First
>>
>> Editing several pages on GitHub wikis was indeed as simple as cloning
>> the wiki repository and doing commits (git clone
>> https://github.com/tinkerpop/gremlin.wiki). Anything that hits the
>> master branch goes live once pushed to Github.
>>
>> Jean-Baptiste
>>
>> On Wed, Jun 8, 2016 at 2:20 PM, Stephen Mallette <spmalle...@gmail.com>
>> wrote:
>> > Jean-Baptiste, +1 for the wiki changes - and thanks for volunteering.
>> I've
>> > given you access to all the old repos in github so you should be free to
>> > make the changes. Maybe give this thread another day to make sure no
>> other
>> > comments trickle in before you go to work on the changes. I think we
>> might
>> > want to go the extra step of adding your header to the READMEs and
>> replace
>> > our current gremlinbusters image - that way everything is consistent.
>> >
>> > Dylan, the gremlin-users info was very out of date, so I updated the
>> About
>> > description:
>> >
>> > https://groups.google.com/forum/#!aboutgroup/gremlin-users
>> >
>> > and included a welcome message that points to the latest docs/website:
>> >
>> > https://groups.google.com/forum/#!forum/gremlin-users
>> >
>> > Everyone good with those changes?
>> >
>> >
>> >
>> > On Tue, Jun 7, 2016 at 4:54 PM, Dylan Bethune-Waddell <
>> > dylan.bethune.wadd...@mail.utoronto.ca> wrote:
>> >
>> >> I believe I mentioned this on the Titan or Tinkerpop mailing list but it
>> >> was off-topic at the time, so I will restate here:
>> >>
>> >>
>> >> What about a pinned post on the gremlin-users mailing lists linking to
>> the
>> >> most recent docs and website as another guidepost for users in line with
>> >> this one? Does this edit to all the old wikis etc. make such a thing
>> >> redundant? My thinking on this is that it would be similar to the pinned
>> >> post titled "On proper issue submission" at the top of the Titan mailing
>> >> list - short and sweet, saving Tinker-time solving problems on the list
>> >> that are not easily reproducible or particularly
>> relevant/straightforward.
>> >> It could also prevent some posts based on outdated information that
>> beget
>> >> more relevant questions posted deep down in the thread, which now has a
>> >> misleading title that does not match the core of its content.
>> >>
>> >> 
>> >> From: Jean-Baptiste Musso <jbmu...@gmail.com>
>> >> Sent: Tuesday, June 7, 2016 4:05:16 PM
>> >> To: dev@tinkerpop.apache.org
>> >> Subject: Documentation deprecation warning on Github Wikis
>> >>
>> >> Dear devs,
>> >>
>> >> I was thinking recently that we could add a deprecation warning
>> >> message on top of all former Github Wiki pages and warn visitors that
>> >> a new version of TinkerPop is available. I think this was also brought
>> >> up recently on the mailing list so I'm opening a discussion here.
>> >>
>> >> I feel that some newcomers are still hitting old school TinkerPop 2
>> >> material when google'ing for graphs, Gremlin and TinkerPop. Adding a
>> >> warning message on top of old Wiki pages pointing them to the freshest
>> >> development on the Apache TinkerPop website could certainly help.
>> >>
>> >> If everyone agre

Documentation deprecation warning on Github Wikis

[Jean-Baptiste Musso]

Dear devs,

I was thinking recently that we could add a deprecation warning
message on top of all former Github Wiki pages and warn visitors that
a new version of TinkerPop is available. I think this was also brought
up recently on the mailing list so I'm opening a discussion here.

I feel that some newcomers are still hitting old school TinkerPop 2
material when google'ing for graphs, Gremlin and TinkerPop. Adding a
warning message on top of old Wiki pages pointing them to the freshest
development on the Apache TinkerPop website could certainly help.

If everyone agrees, I'm volunteering to git clone the Wiki on all
repositories and edit all pages. As Stephen noted on HipChat, it's as
simple as following these steps:
https://help.github.com/articles/adding-and-editing-wiki-pages-locally/

Here's an example of such header we could add:

https://gist.github.com/jbmusso/802cf97ceb20547ba6abf0b4112ac3ee

Thoughts? Feel free to iterate. The wording could be improved.

Cheers,

Jean-Baptiste

Re: [DISCUSS] Thinking on Release

[Jean-Baptiste Musso]

I think this is a good idea. This could make these releases look more
"stable": I've often felt that the -incubating suffix somehow made
releases look "alpha-ish" / "beta-ish", even though they were not.

Naming aside, bug fixes never hurt.

Jean-Baptiste

On Wed, May 25, 2016 at 12:49 AM, Stephen Mallette  wrote:
> We've seen a lot of good fixes/optimizations to 3.1.3 and 3.2.1 and I
> wonder if we shouldn't exercise our new found TLP powers to do a release
> and get rid of the "-incubating" at the end of our "current" distributions
> and artifacts. thoughts?