Re: [DISCUSS] consider 3.4.13/3.5.2/3.6.0 release

[Øyvind Sæbø]

Do we have an overview anywhere of which branches are frozen at any given
time? I have been assuming branches were automatically opened once their
releases were done, but I see now that that is not necessarily the case
Searching through the mailing list to figure out which branches are frozen
can be cumbersome, especially if we are not diligent about always informing
about it when a branch is open again.

tir. 18. jan. 2022 kl. 13:00 skrev Stephen Mallette :

> There's a fair bit of work happening on 3.5-dev right now. It's probably
> best to not slow down anyone's momentum on that to hold 3.5-dev frozen. If
> we have to do a small 3.5.3 release alongside 3.6.0 to ensure functional
> parity I guess that's fine. I think we can reopen 3.5-dev again. Please let
> me know if there are any concerns.
>
> On Wed, Jan 5, 2022 at 2:39 PM Stephen Mallette 
> wrote:
>
> > Hi folks, I've been away for a bit during the holiday but back now
> > thinking about this release. The issue for 3.4-dev that made me want to
> > hold release was resolved. The fix had nothing to do with the code itself
> > and more to do with the fact that memory requirements for the tests we'd
> > added over the years seemed to have quietly reached a point where they
> were
> > sometimes exceeding the memory available of the GH Actions instances
> > running them. After a bit of profiling Maven executions (something I've
> > never had to do ever) I was able to pretty drastically reduce the memory
> > consumption and now everything works smoothly.
> >
> > There is one PR out there that should be merged for 3.4-dev (it's been
> > open for a while pending the CI problem):
> >
> > https://github.com/apache/tinkerpop/pull/1534
> >
> > and will try to get that done immediately. As I'm not aware of any other
> > work, for 3.5-dev and 3.4-dev I think we can proceed as if this were code
> > freeze week and move to release. I think we should hold on release 3.6.0
> > and continue to land PRs on master during the release process and then
> keep
> > the freeze on 3.5-dev until 3.6.0 is out the door (recall that 3.4-dev is
> > basically retired now). Please let me know if there are concerns.
> >
> > On Wed, Dec 29, 2021 at 2:05 PM Stephen Mallette 
> > wrote:
> >
> >> I think we will need to take a bit of a delay on the code freeze for
> this
> >> Friday. 3.4-dev is unstable in CI - i've been trying to get to the root
> of
> >> the problem for a week now and it's still not completely resolved.
> That's
> >> prevented me from looking at other issues I wanted to get done and I
> think
> >> that there is definitely some outstanding work from folks who are off
> for
> >> the holidays. So, let's revisit code freeze a week from now and see
> where
> >> things are. Thanks!
> >>
> >> On Mon, Dec 13, 2021 at 3:37 PM Stephen Mallette 
> >> wrote:
> >>
> >>> In the worst case, if there were things we wanted added to 3.6.0 that
> >>> weren't quite ready for code freeze we could release 3.5.2 and hold the
> >>> freeze on its branch while 3.6.0 finished. I just wouldn't want a
> 3.6.0 to
> >>> force a few commits into a fast turnaround release of 3.5.3. That might
> >>> give some buffer if we wanted, but it would be nice if it could all
> just
> >>> land at once.
> >>>
> >>> On Mon, Dec 13, 2021 at 3:07 PM Kelvin Lawrence
> 
> >>> wrote:
> >>>
>  The work for adding a regex TextP is sitting on the TINKERPOP-2652
>  branch. I still need to write the docs and add one last Java test but
>  otherwise it's close to PR ready. I would like to try and get that
> into 3.6
>  which I think I should be able to do before the cutoff.
>  In general capturing what we have now into a set of releases makes
>  sense to start the year with a pretty clean mainline branch that we
> can
>  iterate on.
>  Kelvin
> 
>  On Monday, December 13, 2021, 06:44:46 AM CST, Stephen Mallette <
>  spmalle...@gmail.com> wrote:
> 
>   I'd like to propose we do a release for the new year, with code
> freeze
>  starting conveniently on Friday December 31.
> 
>  I think we should also consider making this the last release of 3.4.x.
> 
>  It occurred to me that 3.6.x doesn't have a name yet. Working in
> reverse
>  (never done it this way before), I have a Victorian/Steampunk sorta
>  Gremlin
>  image that could be used for a logo, and searching around for related
>  music
>  came across a whole genre of Steampunk Music. First artist group I
>  clicked
>  on, Deus Ex Vapore Machina, has a song called "Tinkerheart" - sorta
> just
>  fits I'd say.
> 
> >>>
> >>>
>

Re: gremlint dependencies

[Øyvind Sæbø]

Yes, I agree as long as we just use it as a means of notification it will
bring value.

tir. 18. jan. 2022 kl. 13:02 skrev Stephen Mallette :

> Thanks for fixing that. I don't expect dependabot to save any work, but I
> would like to know when there is a bad security problem that needs
> attention. I tend to think of its utility in that way.
>
> On Sun, Jan 16, 2022 at 11:57 AM Øyvind Sæbø 
> wrote:
>
> > I've updated the dependencies as CTR, but it was not straightforward and
> > not something npm audit was able to do on its own, which makes me a bit
> > skeptical of leaving dependency management to dependabot. A typical
> problem
> > is when the latest version of a package depends on an outdated package.
> > Then we need to force that that package uses a newer version of the
> > outdated package. Since packages then end up with versions they might not
> > have been designed for, we have to be careful to test that building and
> > running the app still works as before. It may be that dependabot handles
> > these cases well, but I'm not sure it would reduce the manual involvement
> > required.
> >
> >
> >
> https://github.com/apache/tinkerpop/commit/134180f87ef00b08e49dd96ec271e2bb47bd5029
> > (3.5-dev
> > <
> https://github.com/apache/tinkerpop/commit/134180f87ef00b08e49dd96ec271e2bb47bd5029(3.5-dev
> >
> > )
> >
> >
> https://github.com/apache/tinkerpop/commit/ec28bf7f2eaa76e6a5ba71ec7598c5f7db0c56b8
> > (master)
> >
> >
> >
> > fre. 14. jan. 2022 kl. 13:16 skrev Øyvind Sæbø :
> >
> > > I'll see if I can find time to look into it this weekend. I don't think
> > we
> > > need to be concerned about the Gremlint library itself being insecure.
> It
> > > has zero dependencies, so I assume the warnings are related to the
> > tooling
> > > we use to build or test the library or website. We should keep those up
> > to
> > > date, though, so adding dependabot would be nice.
> > >
> > > fre. 14. jan. 2022 kl. 12:57 skrev Stephen Mallette <
> > spmalle...@gmail.com
> > > >:
> > >
> > >> This post is mostly for Øyvind - I'm noticing that when I build
> > gremlint i
> > >> get a number of messages about "critical" dependency updates and
> similar
> > >> warnings. I was wondering if there were any there that we should be
> > >> concerned about?
> > >>
> > >> In addition, we've put dependabot to work for python and .NET to
> > success,
> > >> and figure that gremlin-javascript is next. What do you think about
> > >> enabling it for gremlint as well?
> > >>
> > >
> >
>

Re: gremlint dependencies

[Øyvind Sæbø]

I've updated the dependencies as CTR, but it was not straightforward and
not something npm audit was able to do on its own, which makes me a bit
skeptical of leaving dependency management to dependabot. A typical problem
is when the latest version of a package depends on an outdated package.
Then we need to force that that package uses a newer version of the
outdated package. Since packages then end up with versions they might not
have been designed for, we have to be careful to test that building and
running the app still works as before. It may be that dependabot handles
these cases well, but I'm not sure it would reduce the manual involvement
required.

https://github.com/apache/tinkerpop/commit/134180f87ef00b08e49dd96ec271e2bb47bd5029
(3.5-dev)
https://github.com/apache/tinkerpop/commit/ec28bf7f2eaa76e6a5ba71ec7598c5f7db0c56b8
(master)



fre. 14. jan. 2022 kl. 13:16 skrev Øyvind Sæbø :

> I'll see if I can find time to look into it this weekend. I don't think we
> need to be concerned about the Gremlint library itself being insecure. It
> has zero dependencies, so I assume the warnings are related to the tooling
> we use to build or test the library or website. We should keep those up to
> date, though, so adding dependabot would be nice.
>
> fre. 14. jan. 2022 kl. 12:57 skrev Stephen Mallette  >:
>
>> This post is mostly for Øyvind - I'm noticing that when I build gremlint i
>> get a number of messages about "critical" dependency updates and similar
>> warnings. I was wondering if there were any there that we should be
>> concerned about?
>>
>> In addition, we've put dependabot to work for python and .NET to success,
>> and figure that gremlin-javascript is next. What do you think about
>> enabling it for gremlint as well?
>>
>

Re: gremlint dependencies

[Øyvind Sæbø]

I'll see if I can find time to look into it this weekend. I don't think we
need to be concerned about the Gremlint library itself being insecure. It
has zero dependencies, so I assume the warnings are related to the tooling
we use to build or test the library or website. We should keep those up to
date, though, so adding dependabot would be nice.

fre. 14. jan. 2022 kl. 12:57 skrev Stephen Mallette :

> This post is mostly for Øyvind - I'm noticing that when I build gremlint i
> get a number of messages about "critical" dependency updates and similar
> warnings. I was wondering if there were any there that we should be
> concerned about?
>
> In addition, we've put dependabot to work for python and .NET to success,
> and figure that gremlin-javascript is next. What do you think about
> enabling it for gremlint as well?
>

Re: [VOTE] TinkerPop 3.5.2 Release

[Øyvind Sæbø]

VOTE +1

tir. 11. jan. 2022 kl. 17:14 skrev Jorge Bay Gondra <
jorgebaygon...@gmail.com>:

> VOTE +1
>
> On Tue, Jan 11, 2022 at 4:19 PM Kelvin Lawrence 
> wrote:
>
> > VOTE +1
> >
> > Cheers, Kelvin
> >
> >
> > > On Jan 11, 2022, at 05:39, Stephen Mallette 
> > wrote:
> > >
> > > Hello,
> > >
> > > We are happy to announce that TinkerPop 3.5.2 is ready for release.
> > >
> > > The release artifacts can be found at this location:
> > >https://dist.apache.org/repos/dist/dev/tinkerpop/3.5.2/
> > >
> > > The source distribution is provided by:
> > >apache-tinkerpop-3.5.2-src.zip
> > >
> > > Two binary distributions are provided for user convenience:
> > >apache-tinkerpop-gremlin-console-3.5.2-bin.zip
> > >apache-tinkerpop-gremlin-server-3.5.2-bin.zip
> > >
> > > The GPG key used to sign the release artifacts is available at:
> > >https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS
> > >
> > > The online docs can be found here:
> > >https://tinkerpop.apache.org/docs/3.5.2/ (user docs)
> > >https://tinkerpop.apache.org/docs/3.5.2/upgrade/ (upgrade docs)
> > >https://tinkerpop.apache.org/javadocs/3.5.2/core/ (core
> javadoc)
> > >https://tinkerpop.apache.org/javadocs/3.5.2/full/ (full
> javadoc)
> > >https://tinkerpop.apache.org/dotnetdocs/3.5.2/ (.NET API docs)
> > >https://tinkerpop.apache.org/jsdocs/3.5.2/ (Javascript API
> docs)
> > >
> > > The tag in Apache Git can be found here:
> > >https://github.com/apache/tinkerpop/tree/3.5.2
> > >
> > > The release notes are available here:
> > >
> https://github.com/apache/tinkerpop/blob/3.5.2/CHANGELOG.asciidoc
> > >
> > > The [VOTE] will be open for the next 72 hours --- closing Friday
> (January
> > > 14, 2022) at 6:30am ET.
> > >
> > > My vote is +1.
> >
> >
>

Re: [VOTE] TinkerPop 3.5.1 Release

[Øyvind Sæbø]

VOTE +1

> 22. jul. 2021 kl. 20:08 skrev Joshua Shinavier :
> 
> +1
> 
> 
> On Thu, Jul 22, 2021 at 10:41 AM David Bechberger 
> wrote:
> 
>> Agreed, thanks for all the hard work.  +1
>> 
>> We should probably include something about Discord in any sort of email
>> communication as well.
>> 
>> Thanks,
>> Dave
>> 
>> On Thu, Jul 22, 2021 at 8:27 AM Kelvin Lawrence 
>> wrote:
>> 
>>> Thanks for all the hard work to get the release out. VOTE +1
>>> Kelvin
>>>On Wednesday, July 21, 2021, 01:00:34 PM CDT, Stephen Mallette <
>>> spmalle...@gmail.com> wrote:
>>> 
>>> It was an unfortunate omission but we probably should have had the
>>> gremlint
>>> library in the 3.5.1 upgrade docs. oh well, not something to retrigger
>> all
>>> that work over. Florian, please plan to call attention to it in the
>> release
>>> announcement in some way. I'll write something to add to the upgrade docs
>>> for 3.5.1 so it will be there in the future.
>>> 
>>> Other than that, bin/valdiate-distribution.sh worked fine so VOTE +1
>>> 
>>> On Wed, Jul 21, 2021 at 10:16 AM Florian Hockmann <
>> f...@florian-hockmann.de>
>>> wrote:
>>> 
 Hello,
 
 We are happy to announce that TinkerPop 3.5.1 is ready for release.
 
 The release artifacts can be found at this location:
   https://dist.apache.org/repos/dist/dev/tinkerpop/3.5.1/
 
 The source distribution is provided by:
   apache-tinkerpop-3.5.1-src.zip
 
 Two binary distributions are provided for user convenience:
   apache-tinkerpop-gremlin-console-3.5.1-bin.zip
   apache-tinkerpop-gremlin-server-3.5.1-bin.zip
 
 The GPG key used to sign the release artifacts is available at:
   https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS
 
 The online docs can be found here:
   https://tinkerpop.apache.org/docs/3.5.1/ (user docs)
   https://tinkerpop.apache.org/docs/3.5.1/upgrade/ (upgrade docs)
   https://tinkerpop.apache.org/javadocs/3.5.1/core/ (core
>> javadoc)
   https://tinkerpop.apache.org/javadocs/3.5.1/full/ (full
>> javadoc)
   https://tinkerpop.apache.org/dotnetdocs/3.5.1/ (.NET API docs)
   https://tinkerpop.apache.org/jsdocs/3.5.1/ (Javascript API
>> docs)
 
 The tag in Apache Git can be found here:
   https://github.com/apache/tinkerpop/tree/3.5.1
 
 The release notes are available here:
 
>> https://github.com/apache/tinkerpop/blob/3.5.1/CHANGELOG.asciidoc
 
 The [VOTE] will be open for the next 72 hours --- closing Saturday
>> (July
 24,
 2021) at 3pm UTC.
 
 My vote is +1.
 
 Thank you very much,
 Florian Hockmann
 
 
>>> 
>> 

Re: [DISCUSS] gremlint 3.5.1 release candidate

[Øyvind Sæbø]

Very cool! I gave it a quick test and it works!

tor. 15. jul. 2021 kl. 16:45 skrev Stephen Mallette :

> wow - first try:
>
> https://www.npmjs.com/package/gremlint
>
>
>
>
> On Mon, Jul 12, 2021 at 2:28 PM Øyvind Sæbø  wrote:
>
> >
> > I don’t have a strong opinion on this, so if this is consistent with how
> > it’s been done earlier it sounds good to me. Really excited to see we’re
> > getting close to releasing Gremlint as a library:)
> >
> > Øyvind
> >
> > > 12. jul. 2021 kl. 18:09 skrev Stephen Mallette :
> > >
> > > As we'd discussed elsewhere, 3.5.1 should be good to release gremlint
> as
> > a
> > > library. To ensure that it's all rigged up properly to deploy to npm on
> > > release day, i think it's worth trying to publish a release candidate
> > with
> > > a beta tag as we first did with gremlin-javascript for 3.4.0-rc1.
> > >
> > > I realize "-rc1" isn't exactly the way javascript numbers these sorts
> of
> > > things, but perhaps we should try to just stay consistent with what
> we've
> > > always done. My understanding is that the actual version number we use
> > has
> > > less to do with a "beta" or "alpha" version than the usage of the --tag
> > > value as in:
> > >
> > > npm publish --tag beta
> > >
> > > Assuming there are no concerns I'll go ahead with this initial try for
> > > 3.5.1-rc1 in the next day or so. Thanks!
> >
>

Re: [DISCUSS] gremlint 3.5.1 release candidate

[Øyvind Sæbø]

I don’t have a strong opinion on this, so if this is consistent with how it’s 
been done earlier it sounds good to me. Really excited to see we’re getting 
close to releasing Gremlint as a library:)

Øyvind

> 12. jul. 2021 kl. 18:09 skrev Stephen Mallette :
> 
> As we'd discussed elsewhere, 3.5.1 should be good to release gremlint as a
> library. To ensure that it's all rigged up properly to deploy to npm on
> release day, i think it's worth trying to publish a release candidate with
> a beta tag as we first did with gremlin-javascript for 3.4.0-rc1.
> 
> I realize "-rc1" isn't exactly the way javascript numbers these sorts of
> things, but perhaps we should try to just stay consistent with what we've
> always done. My understanding is that the actual version number we use has
> less to do with a "beta" or "alpha" version than the usage of the --tag
> value as in:
> 
> npm publish --tag beta
> 
> Assuming there are no concerns I'll go ahead with this initial try for
> 3.5.1-rc1 in the next day or so. Thanks!

Re: [VOTE] TinkerPop 3.5.0 Release

[Øyvind Sæbø]



VOTE +1

tor. 6. mai 2021 kl. 14:51 skrev Jorge Bay Gondra :

> Yay! 3.5.0!
>
> VOTE +1
>
> On Thu, May 6, 2021 at 10:08 AM  wrote:
>
> > VOTE +1
> >
> > One small issue I found while reviewing the upgrade docs though:
> > TINKERPOP-2317 removed support for Python lambdas in Gremlin Server, but
> > Gremlin.Net still supports sending them. This is also documented in the
> > reference docs:
> > https://tinkerpop.apache.org/docs/3.5.0/reference/#gremlin-dotnet-lambda
> > I unfortunately completely missed that until now, but I think that it's
> > not a big issue that we can also fix for 3.5.1. This should definitely
> not
> > stop the release in my opinion.
> >
> > -Ursprüngliche Nachricht-
> > Von: Stephen Mallette 
> > Gesendet: Mittwoch, 5. Mai 2021 22:50
> > An: dev@tinkerpop.apache.org
> > Betreff: [VOTE] TinkerPop 3.5.0 Release
> >
> > Hello,
> >
> > We are happy to announce that TinkerPop 3.5.0 is ready for release.
> >
> > The release artifacts can be found at this location:
> > https://dist.apache.org/repos/dist/dev/tinkerpop/3.5.0/
> >
> > The source distribution is provided by:
> > apache-tinkerpop-3.5.0-src.zip
> >
> > Two binary distributions are provided for user convenience:
> > apache-tinkerpop-gremlin-console-3.5.0-bin.zip
> > apache-tinkerpop-gremlin-server-3.5.0-bin.zip
> >
> > The GPG key used to sign the release artifacts is available at:
> > https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS
> >
> > The online docs can be found here:
> > https://tinkerpop.apache.org/docs/3.5.0/ (user docs)
> > https://tinkerpop.apache.org/docs/3.5.0/upgrade/ (upgrade docs)
> > https://tinkerpop.apache.org/javadocs/3.5.0/core/ (core javadoc)
> > https://tinkerpop.apache.org/javadocs/3.5.0/full/ (full javadoc)
> > https://tinkerpop.apache.org/dotnetdocs/3.5.0/ (.NET API docs)
> > https://tinkerpop.apache.org/jsdocs/3.5.0/ (Javascript API docs)
> >
> > The tag in Apache Git can be found here:
> > https://github.com/apache/tinkerpop/tree/3.5.0
> >
> > The release notes are available here:
> >
> https://github.com/apache/tinkerpop/blob/3.5.0/CHANGELOG.asciidoc
> >
> > The [VOTE] will be open for the next 72 hours --- closing Saturday (May
> 8,
> > 2021) at 5pm ET.
> >
> > My vote is +1.
> >
> >
>

Re: [VOTE] TinkerPop 3.4.11 Release

[Øyvind Sæbø]

VOTE +1

tor. 6. mai 2021 kl. 14:51 skrev Jorge Bay Gondra :

> VOTE +1
>
> On Wed, May 5, 2021 at 11:10 AM  wrote:
>
> > I mostly reviewed the docs and all looks good.
> >
> > VOTE +1
> >
> > -Ursprüngliche Nachricht-
> > Von: Stephen Mallette 
> > Gesendet: Dienstag, 4. Mai 2021 18:00
> > An: dev@tinkerpop.apache.org
> > Betreff: [VOTE] TinkerPop 3.4.11 Release
> >
> > Hello,
> >
> > We are happy to announce that TinkerPop 3.4.11 is ready for release.
> >
> > The release artifacts can be found at this location:
> > https://dist.apache.org/repos/dist/dev/tinkerpop/3.4.11/
> >
> > The source distribution is provided by:
> > apache-tinkerpop-3.4.11-src.zip
> >
> > Two binary distributions are provided for user convenience:
> > apache-tinkerpop-gremlin-console-3.4.11-bin.zip
> > apache-tinkerpop-gremlin-server-3.4.11-bin.zip
> >
> > The GPG key used to sign the release artifacts is available at:
> > https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS
> >
> > The online docs can be found here:
> > https://tinkerpop.apache.org/docs/3.4.11/ (user docs)
> > https://tinkerpop.apache.org/docs/3.4.11/upgrade/ (upgrade docs)
> > https://tinkerpop.apache.org/javadocs/3.4.11/core/ (core
> javadoc)
> > https://tinkerpop.apache.org/javadocs/3.4.11/full/ (full
> javadoc)
> > https://tinkerpop.apache.org/dotnetdocs/3.4.11/ (.NET API docs)
> > https://tinkerpop.apache.org/jsdocs/3.4.11/ (Javascript API
> docs)
> >
> > The tag in Apache Git can be found here:
> > https://github.com/apache/tinkerpop/tree/3.4.11
> >
> > The release notes are available here:
> >
> https://github.com/apache/tinkerpop/blob/3.4.11/CHANGELOG.asciidoc
> >
> > The [VOTE] will be open for the next 72 hours --- closing Friday (May 7,
> > 2021) at 12pm ET.
> >
> > My vote is +1.
> >
> >
>

Re: 3.5.0 Announcement Volunteers

[Øyvind Sæbø]

I can write a post about the introduction of Gremlint to TinkerPop and its
future possibilities.

fre. 30. apr. 2021 kl. 15:55 skrev Marko Rodriguez :

> Hello mein freunden,
>
> I’d love to contribute a body of work from mm-ADT that is one of the main
> issues with the Gremlin language: every step should support pipeline
> arguments (i.e., every argument can be a dynamically/traversal determined
> value). I solved this problem in mm-ADT elegantly and efficiently. A
> beautiful feature indeed.
>
> ….unfortunately, Apache Board overruled the TinkerPop PMC and had me
> forcefully removed from the PMC for being (how do you say in American
> English?) “Nazi Troll.” If the Board is willing to look past the SS on my
> uniform and put me back in my rightful place as Obergruppenführer of the
> PMC, then we shall be unstoppable!
>
> Those are my terms. Boohaha.
>
> Marko.
>
> > On Apr 30, 2021, at 7:34 AM, Stephen Mallette 
> wrote:
> >
> > Wow, this is great - lots of volunteers! Here's a running list of what we
> > have so far:
> >
> > * UnifiedChannelizer - Stephen
> > * gremlin-language - Josh
> > * Gremlin.Net - Florian
> > * gremlin-python - Kelvin
> >
> > There's definitely a lot more topics to tackle. Let's keep expanding the
> > list.
> >
> >
> >
> > On Fri, Apr 30, 2021 at 9:27 AM Kelvin Lawrence  >
> > wrote:
> >
> >> I am happy to help. The area I have been closest too is probably the
> >> enhancements to the Python client. I could write something around those
> >> features.
> >>
> >> Cheers, Kelvin
> >>
> >>> On Apr 30, 2021, at 04:30, f...@florian-hockmann.de wrote:
> >>>
> >>> I could write something for .NET. Added GraphBinary support and
> >> switching the JSON library could be interesting for some Gremlin.Net
> users.
> >>>
> >>> -Ursprüngliche Nachricht-
> >>> Von: Stephen Mallette 
> >>> Gesendet: Donnerstag, 29. April 2021 21:32
> >>> An: dev@tinkerpop.apache.org
> >>> Betreff: Re: 3.5.0 Announcement Volunteers
> >>>
> >>> Right now, I think it's fine for these to just have each person's
> >> individual style - might make the posts more interesting assuming we
> get a
> >> few more volunteers. If you can come up with a neat image that could go
> >> with a tweet to promote the announcement (that we will push through the
> >> TinkerPop account), that would be cool. We've not really come up with
> >> anything that sort of iconifies the gremlin-language module, so if you
> feel
> >> like thinking about that, that would be neat.
> >>>
> >>>
> >>>
>  On Thu, Apr 29, 2021 at 2:45 PM Joshua Shinavier 
> >> wrote:
> 
>  Sounds good. I'll write the announcement. If you have thoughts on the
>  format, please feel free to share.
> 
>  Josh
> 
>  On Thu, Apr 29, 2021 at 10:56 AM Stephen Mallette
>  
>  wrote:
> 
> > On Thu, Apr 29, 2021 at 1:38 PM Joshua Shinavier 
> > wrote:
> >
> >> I would be happy to collaborate on gremlin-language if there is
>  something
> >> which needs doing.
> >>
> >> Josh
> >>
> >>
> > great josh - thanks! The upgrade docs sorta tuck that feature away
> > in the provider section
> >
> >
> 
> https://tinkerpop.apache.org/docs/3.5.0-SNAPSHOT/upgrade/#_gremlin_lan
>  guage
> >
> > because at this point it doesn't have direct user impact, but i
> > think it might be useful to the community to write something in an
> > announcement
>  that
> > helps describe what this module lays the foundation for. you've had
> > some interesting ideas in this area that i'm not sure have gotten
> > outside of
>  the
> > dev list as of yet.
> >
> 
> >>>
> >>
> >>
>
>

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

I think that sounds like a good approach. I'll see if I can get started on
that this week.

man. 1. mar. 2021 kl. 13:12 skrev Stephen Mallette :

> Øyvind, We've discussed a few different ways to bring the code in at this
> point. Here's some first steps on your end that I think would be in order:
>
> 1. Submit a pull request with the gremlint code. We'd earlier discussed a
> gremlint directory at the root of the repository. I think that still makes
> sense.
> 2. Make the appropriate modifications to your gremlint repository to point
> users to the Apache repository and to "retire" that old repo
> 3. We use JIRA for issue tracking[1]. I've created a Component type for
> gremlint. Consider migrating any of your GitHub Issues you think relevant
> to JIRA so that they may be tracked in this project.
>
> How's that for a start?
>
> [1] https://issues.apache.org/jira/projects/TINKERPOP/summary/statistics
>
> On Fri, Feb 26, 2021 at 10:37 AM Stephen Mallette 
> wrote:
>
> > The IP Clearance lazy consensus was achieved. I've closed the thread:
> >
> >
> >
> https://lists.apache.org/thread.html/r207e7f7b4de1b1fa4699012b9d9f53fcf5b43cc3efb80559aea0741f%40%3Cgeneral.incubator.apache.org%3E
> >
> > i think we can now focus on bringing in the code!
> >
> > On Mon, Feb 22, 2021 at 10:51 AM Stephen Mallette 
> > wrote:
> >
> >> I just closed the VOTE thread and it passed as expected:
> >>
> >>
> >>
> https://lists.apache.org/thread.html/r1006ed56b5d92628f3378f9baef854da6fef3f83d8492b746b467ab6%40%3Cdev.tinkerpop.apache.org%3E
> >>
> >> I've updated the IP Clearance document:
> >>
> >>
> >>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
> >>
> >> I think my last step is to write a post to Incubator to point to the
> >> document and to request lazy consensus. I will get that out soon enough.
> >>
> >>
> >>
> >> On Wed, Feb 17, 2021 at 8:26 AM Øyvind Sæbø 
> >> wrote:
> >>
> >>> Very nice! The process seems a bit backwards to me too, but oh well.
> >>>
> >>> ons. 17. feb. 2021 kl. 13:37 skrev Stephen Mallette <
> >>> spmalle...@gmail.com>:
> >>>
> >>> > I believe that the IP Clearance document is all complete now:
> >>> >
> >>> >
> >>> >
> >>>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
> >>> >
> >>> > The process seems a bit backward to me, but I'd read elsewhere that
> the
> >>> > preferred method is to get this document complete and then issue a
> VOTE
> >>> > thread to confirm completeness and then add that thread link to the
> >>> doc. At
> >>> > that point, I then go get lazy consensus from Apache Incubator on the
> >>> > submission. At that point we can work on the actual bits of bringing
> >>> this
> >>> > in. Almost there!
> >>> >
> >>> > On Fri, Feb 12, 2021 at 3:55 PM Øyvind Sæbø 
> >>> wrote:
> >>> >
> >>> > > Sounds good!
> >>> > >
> >>> > > I've always considered the gremlint repo and the gremlint.com repo
> >>> to be
> >>> > > the same project, distributed between two repos just for the sake
> of
> >>> > > separation of concerns. So both repos have the ASF license headers
> in
> >>> > their
> >>> > > source files, saying that they are licensed to the ASF under one or
> >>> more
> >>> > > contributor license agreements. I imagined we could just include
> the
> >>> > latest
> >>> > > commit id both from the gremlint master branch and from the
> >>> gremlint.com
> >>> > > master branch in the IP Clearance Document. However, if it turns
> out
> >>> to
> >>> > be
> >>> > > necessary to handle the IP clearance of the gremlint.com website
> in
> >>> a
> >>> > more
> >>> > > specific manner, we'll do what we can to accommodate that.
> >>> > >
> >>> > > fre. 12. feb. 2021 kl. 20:57 skrev Stephen Mallette <
> >>> > spmalle...@gmail.com
> >>> > > >:
> >>> > >
> >>> > > > I've updated the IP Clearance form with the latest information
> >&g

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Very nice! The process seems a bit backwards to me too, but oh well.

ons. 17. feb. 2021 kl. 13:37 skrev Stephen Mallette :

> I believe that the IP Clearance document is all complete now:
>
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
>
> The process seems a bit backward to me, but I'd read elsewhere that the
> preferred method is to get this document complete and then issue a VOTE
> thread to confirm completeness and then add that thread link to the doc. At
> that point, I then go get lazy consensus from Apache Incubator on the
> submission. At that point we can work on the actual bits of bringing this
> in. Almost there!
>
> On Fri, Feb 12, 2021 at 3:55 PM Øyvind Sæbø  wrote:
>
> > Sounds good!
> >
> > I've always considered the gremlint repo and the gremlint.com repo to be
> > the same project, distributed between two repos just for the sake of
> > separation of concerns. So both repos have the ASF license headers in
> their
> > source files, saying that they are licensed to the ASF under one or more
> > contributor license agreements. I imagined we could just include the
> latest
> > commit id both from the gremlint master branch and from the gremlint.com
> > master branch in the IP Clearance Document. However, if it turns out to
> be
> > necessary to handle the IP clearance of the gremlint.com website in a
> more
> > specific manner, we'll do what we can to accommodate that.
> >
> > fre. 12. feb. 2021 kl. 20:57 skrev Stephen Mallette <
> spmalle...@gmail.com
> > >:
> >
> > > I've updated the IP Clearance form with the latest information such as
> I
> > > have it. I cant remember how to regenerate the site so here's the raw
> xml
> > > for the file:
> > >
> > >
> > >
> >
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
> > >
> > > Note that the only remaining piece is the CLA that you just submitted.
> I
> > > don't think we'll get confirmation on that from the secretary on our
> end
> > so
> > > I will keep checking Apache records. Also note that I've used the
> current
> > > commit id from the gremlint master branch to denote the code that would
> > be
> > > donated. If I should use something else, please let me know.
> > >
> > > Finally, I wonder if we need to be concerned with the gremlint.com
> repo
> > > since you mention that there isn't much there tying it to GitHub Pages.
> > It
> > > almost seems like the "deployed site" isn't really the artifact that
> this
> > > IP Clearance doc is about. That is more of an implementation detail we
> > can
> > > handle separately, likely with the transfer of the domain name.
> > >
> > > Well, hopefully this process is getting close to being complete.
> Excited
> > to
> > > finally see it settling up.
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Thu, Feb 11, 2021 at 4:14 PM Øyvind Sæbø 
> > wrote:
> > >
> > > > Yes, since it's still hosted on my GitHub account, I would be the one
> > > > responsible for coordinating the actual transfer, so you can give
> them
> > my
> > > > email:)
> > > >
> > > > As for the website itself, there's very little GitHub pages-specific
> > > about
> > > > it, so even if they don't support GitHub pages, I assume very few
> > changes
> > > > would be required to accommodate other hosting solutions.
> > > >
> > > > tor. 11. feb. 2021 kl. 20:17 skrev Stephen Mallette <
> > > spmalle...@gmail.com
> > > > >:
> > > >
> > > > > > Correct, the two repositories plus the domain name would be
> > > transferred
> > > > > to Apache.
> > > > >
> > > > > From what I can tell, I think i would just need to create an issue
> in
> > > > JIRA
> > > > > for Apache Infra and someone from their team would step in to
> handle
> > > the
> > > > > transfer. I would need to provide them an email address I guess for
> > > them
> > > > to
> > > > > get in touch with the "owner". Would you be the person responsible
> > for
> > > > > coordinating that transferral on your end or someone else at your
> > > > company?
> > > > >
> > > > > I'm still trying to u

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Sounds good!

I've always considered the gremlint repo and the gremlint.com repo to be
the same project, distributed between two repos just for the sake of
separation of concerns. So both repos have the ASF license headers in their
source files, saying that they are licensed to the ASF under one or more
contributor license agreements. I imagined we could just include the latest
commit id both from the gremlint master branch and from the gremlint.com
master branch in the IP Clearance Document. However, if it turns out to be
necessary to handle the IP clearance of the gremlint.com website in a more
specific manner, we'll do what we can to accommodate that.

fre. 12. feb. 2021 kl. 20:57 skrev Stephen Mallette :

> I've updated the IP Clearance form with the latest information such as I
> have it. I cant remember how to regenerate the site so here's the raw xml
> for the file:
>
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
>
> Note that the only remaining piece is the CLA that you just submitted. I
> don't think we'll get confirmation on that from the secretary on our end so
> I will keep checking Apache records. Also note that I've used the current
> commit id from the gremlint master branch to denote the code that would be
> donated. If I should use something else, please let me know.
>
> Finally, I wonder if we need to be concerned with the gremlint.com repo
> since you mention that there isn't much there tying it to GitHub Pages. It
> almost seems like the "deployed site" isn't really the artifact that this
> IP Clearance doc is about. That is more of an implementation detail we can
> handle separately, likely with the transfer of the domain name.
>
> Well, hopefully this process is getting close to being complete. Excited to
> finally see it settling up.
>
>
>
>
>
>
> On Thu, Feb 11, 2021 at 4:14 PM Øyvind Sæbø  wrote:
>
> > Yes, since it's still hosted on my GitHub account, I would be the one
> > responsible for coordinating the actual transfer, so you can give them my
> > email:)
> >
> > As for the website itself, there's very little GitHub pages-specific
> about
> > it, so even if they don't support GitHub pages, I assume very few changes
> > would be required to accommodate other hosting solutions.
> >
> > tor. 11. feb. 2021 kl. 20:17 skrev Stephen Mallette <
> spmalle...@gmail.com
> > >:
> >
> > > > Correct, the two repositories plus the domain name would be
> transferred
> > > to Apache.
> > >
> > > From what I can tell, I think i would just need to create an issue in
> > JIRA
> > > for Apache Infra and someone from their team would step in to handle
> the
> > > transfer. I would need to provide them an email address I guess for
> them
> > to
> > > get in touch with the "owner". Would you be the person responsible for
> > > coordinating that transferral on your end or someone else at your
> > company?
> > >
> > > I'm still trying to understand from Infra how they would deal with the
> > web
> > > site itself. I'm not sure if they support GitHub pages or if they would
> > > require something else.
> > >
> > > On Thu, Feb 11, 2021 at 3:44 AM Øyvind Sæbø 
> > wrote:
> > >
> > > > I actually think I misread the guidelines for subitting the CCLA and
> > > ICLA,
> > > > believing hte ICLA had to be submitted together with the CCLA, but it
> > > seems
> > > > I can just submit the ICLA myself, so I have done that today.
> > > >
> > > > ons. 10. feb. 2021 kl. 22:29 skrev Øyvind Sæbø <
> oyvind.s...@gmail.com
> > >:
> > > >
> > > > > Hi, Stephen, thanks for confirming the confirmation of the CCLA. I
> > > > > actually specifically instructed them to send my ICLA together with
> > the
> > > > > CCLA as described here
> > > > > <https://www.apache.org/licenses/contributor-agreements.html>, but
> > it
> > > > > does indeed seem they only sent the CCLA. I'll ask them to resend
> > them
> > > > > again together.
> > > > >
> > > > > Correct, the two repositories plus the domain name would be
> > transferred
> > > > to
> > > > > Apache.
> > > > >
> > > > > I'm not sure I have an opinion about where to place the project in
> > the
> > > > > hierarchy, but keeping it independent of the Maven build sounds
> > > sensible
> > > > to
> > &

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Yes, since it's still hosted on my GitHub account, I would be the one
responsible for coordinating the actual transfer, so you can give them my
email:)

As for the website itself, there's very little GitHub pages-specific about
it, so even if they don't support GitHub pages, I assume very few changes
would be required to accommodate other hosting solutions.

tor. 11. feb. 2021 kl. 20:17 skrev Stephen Mallette :

> > Correct, the two repositories plus the domain name would be transferred
> to Apache.
>
> From what I can tell, I think i would just need to create an issue in JIRA
> for Apache Infra and someone from their team would step in to handle the
> transfer. I would need to provide them an email address I guess for them to
> get in touch with the "owner". Would you be the person responsible for
> coordinating that transferral on your end or someone else at your company?
>
> I'm still trying to understand from Infra how they would deal with the web
> site itself. I'm not sure if they support GitHub pages or if they would
> require something else.
>
> On Thu, Feb 11, 2021 at 3:44 AM Øyvind Sæbø  wrote:
>
> > I actually think I misread the guidelines for subitting the CCLA and
> ICLA,
> > believing hte ICLA had to be submitted together with the CCLA, but it
> seems
> > I can just submit the ICLA myself, so I have done that today.
> >
> > ons. 10. feb. 2021 kl. 22:29 skrev Øyvind Sæbø :
> >
> > > Hi, Stephen, thanks for confirming the confirmation of the CCLA. I
> > > actually specifically instructed them to send my ICLA together with the
> > > CCLA as described here
> > > <https://www.apache.org/licenses/contributor-agreements.html>, but it
> > > does indeed seem they only sent the CCLA. I'll ask them to resend them
> > > again together.
> > >
> > > Correct, the two repositories plus the domain name would be transferred
> > to
> > > Apache.
> > >
> > > I'm not sure I have an opinion about where to place the project in the
> > > hierarchy, but keeping it independent of the Maven build sounds
> sensible
> > to
> > > me at least.
> > >
> > > Correct, currently Gremlint is hosted on GitHub pages.
> > >
> > > ons. 10. feb. 2021 kl. 18:21 skrev Stephen Mallette <
> > spmalle...@gmail.com
> > > >:
> > >
> > >> Øyvind,
> > >>
> > >> I probably should have waited to send that last email as it turned
> out I
> > >> didn't need to dig around too long. I did see some confirmation from
> > >> secretary on the CCLA, but don't yet see it in Apache records, nor do
> I
> > >> yet
> > >> see your ICLA. I'll keep an eye out for it all.
> > >>
> > >> Speaking specifically toward the code contribution, there are two
> > >> repositories which compose gremlint:
> > >>
> > >> https://github.com/OyvindSabo/gremlint/
> > >> https://github.com/OyvindSabo/gremlint.com/
> > >>
> > >> and the domain name itself which, if i recall correctly, would be
> > >> transferred to Apache as well. Is that correct?
> > >>
> > >> Next, I'd envisioned that gremlint code would join our repository and
> > for
> > >> now we would just simply bring it to the master branch as a top level
> > >> directory independent of the maven build. good start? (perhaps that
> > >> question is for everyone)
> > >>
> > >> Finally, for gremlint.com how is that deployed right now? is that
> just
> > >> hosted as github pages or something? We might have to contact Apache
> > Infra
> > >> to figure out how that piece would best transfer?
> > >>
> > >>
> > >>
> > >> On Wed, Feb 10, 2021 at 11:43 AM Stephen Mallette <
> spmalle...@gmail.com
> > >
> > >> wrote:
> > >>
> > >> > Thanks for the update - I'll reacquaint myself with the process and
> > get
> > >> > things moving along again on our end now that this step is settled.
> :)
> > >> >
> > >> > On Mon, Feb 8, 2021 at 1:41 PM Øyvind Sæbø 
> > >> wrote:
> > >> >
> > >> >> Hi, I'm back again with an update on the ongoing Gremlint IP
> > clearance
> > >> >> progress:
> > >> >> Today the CCLA was signed by our CEO, so we aim to have my signed
> > ICLA
> > >> and
> > >> >> the CCLA sent to secret...@apache.org as soon as possible.
> &g

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

I actually think I misread the guidelines for subitting the CCLA and ICLA,
believing hte ICLA had to be submitted together with the CCLA, but it seems
I can just submit the ICLA myself, so I have done that today.

ons. 10. feb. 2021 kl. 22:29 skrev Øyvind Sæbø :

> Hi, Stephen, thanks for confirming the confirmation of the CCLA. I
> actually specifically instructed them to send my ICLA together with the
> CCLA as described here
> <https://www.apache.org/licenses/contributor-agreements.html>, but it
> does indeed seem they only sent the CCLA. I'll ask them to resend them
> again together.
>
> Correct, the two repositories plus the domain name would be transferred to
> Apache.
>
> I'm not sure I have an opinion about where to place the project in the
> hierarchy, but keeping it independent of the Maven build sounds sensible to
> me at least.
>
> Correct, currently Gremlint is hosted on GitHub pages.
>
> ons. 10. feb. 2021 kl. 18:21 skrev Stephen Mallette  >:
>
>> Øyvind,
>>
>> I probably should have waited to send that last email as it turned out I
>> didn't need to dig around too long. I did see some confirmation from
>> secretary on the CCLA, but don't yet see it in Apache records, nor do I
>> yet
>> see your ICLA. I'll keep an eye out for it all.
>>
>> Speaking specifically toward the code contribution, there are two
>> repositories which compose gremlint:
>>
>> https://github.com/OyvindSabo/gremlint/
>> https://github.com/OyvindSabo/gremlint.com/
>>
>> and the domain name itself which, if i recall correctly, would be
>> transferred to Apache as well. Is that correct?
>>
>> Next, I'd envisioned that gremlint code would join our repository and for
>> now we would just simply bring it to the master branch as a top level
>> directory independent of the maven build. good start? (perhaps that
>> question is for everyone)
>>
>> Finally, for gremlint.com how is that deployed right now? is that just
>> hosted as github pages or something? We might have to contact Apache Infra
>> to figure out how that piece would best transfer?
>>
>>
>>
>> On Wed, Feb 10, 2021 at 11:43 AM Stephen Mallette 
>> wrote:
>>
>> > Thanks for the update - I'll reacquaint myself with the process and get
>> > things moving along again on our end now that this step is settled. :)
>> >
>> > On Mon, Feb 8, 2021 at 1:41 PM Øyvind Sæbø 
>> wrote:
>> >
>> >> Hi, I'm back again with an update on the ongoing Gremlint IP clearance
>> >> progress:
>> >> Today the CCLA was signed by our CEO, so we aim to have my signed ICLA
>> and
>> >> the CCLA sent to secret...@apache.org as soon as possible.
>> >>
>> >> fre. 8. jan. 2021 kl. 09:24 skrev Øyvind Sæbø :
>> >>
>> >> > Happy new year!
>> >> >
>> >> > Update on the Gremlint IP clearance process:
>> >> > We filled out the CCLA yesterday and are just waiting for it to be
>> >> signed
>> >> > by our CEO.
>> >> > We'll submit it together with the ICLA as soon as it's ready.
>> >> >
>> >> > man. 7. des. 2020 kl. 13:18 skrev Stephen Mallette <
>> >> spmalle...@gmail.com>:
>> >> >
>> >> >> Thanks for all the updates - it sounds as though we are getting
>> closer
>> >> to
>> >> >> having to do more things on this side. Once the I/CCLAs are
>> >> acknowledged
>> >> >> by
>> >> >> Apache I'll go back and revisit the documentation on this process to
>> >> see
>> >> >> what happens next.
>> >> >>
>> >> >> On Thu, Dec 3, 2020 at 9:05 AM Øyvind Sæbø 
>> >> wrote:
>> >> >>
>> >> >> > Hi again, I'm here with an update on the Gremlint IP clearance
>> >> process:)
>> >> >> >
>> >> >> > Yesterday I added the ASF source file headers to all the gremlint
>> >> source
>> >> >> > files (link to commit
>> >> >> > <
>> >> >> >
>> >> >>
>> >>
>> https://github.com/OyvindSabo/gremlint/commit/9010a706ceaa4102886294a860d5fbac152ca08b
>> >> >> > >)
>> >> >> > and all the gremlint.com source files (link to commit
>> >> >> > <
>> >> >> >
>> >> >>
>> >>
>> https://github.com/

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Hi, Stephen, thanks for confirming the confirmation of the CCLA. I actually
specifically instructed them to send my ICLA together with the CCLA as
described here <https://www.apache.org/licenses/contributor-agreements.html>,
but it does indeed seem they only sent the CCLA. I'll ask them to resend
them again together.

Correct, the two repositories plus the domain name would be transferred to
Apache.

I'm not sure I have an opinion about where to place the project in the
hierarchy, but keeping it independent of the Maven build sounds sensible to
me at least.

Correct, currently Gremlint is hosted on GitHub pages.

ons. 10. feb. 2021 kl. 18:21 skrev Stephen Mallette :

> Øyvind,
>
> I probably should have waited to send that last email as it turned out I
> didn't need to dig around too long. I did see some confirmation from
> secretary on the CCLA, but don't yet see it in Apache records, nor do I yet
> see your ICLA. I'll keep an eye out for it all.
>
> Speaking specifically toward the code contribution, there are two
> repositories which compose gremlint:
>
> https://github.com/OyvindSabo/gremlint/
> https://github.com/OyvindSabo/gremlint.com/
>
> and the domain name itself which, if i recall correctly, would be
> transferred to Apache as well. Is that correct?
>
> Next, I'd envisioned that gremlint code would join our repository and for
> now we would just simply bring it to the master branch as a top level
> directory independent of the maven build. good start? (perhaps that
> question is for everyone)
>
> Finally, for gremlint.com how is that deployed right now? is that just
> hosted as github pages or something? We might have to contact Apache Infra
> to figure out how that piece would best transfer?
>
>
>
> On Wed, Feb 10, 2021 at 11:43 AM Stephen Mallette 
> wrote:
>
> > Thanks for the update - I'll reacquaint myself with the process and get
> > things moving along again on our end now that this step is settled. :)
> >
> > On Mon, Feb 8, 2021 at 1:41 PM Øyvind Sæbø 
> wrote:
> >
> >> Hi, I'm back again with an update on the ongoing Gremlint IP clearance
> >> progress:
> >> Today the CCLA was signed by our CEO, so we aim to have my signed ICLA
> and
> >> the CCLA sent to secret...@apache.org as soon as possible.
> >>
> >> fre. 8. jan. 2021 kl. 09:24 skrev Øyvind Sæbø :
> >>
> >> > Happy new year!
> >> >
> >> > Update on the Gremlint IP clearance process:
> >> > We filled out the CCLA yesterday and are just waiting for it to be
> >> signed
> >> > by our CEO.
> >> > We'll submit it together with the ICLA as soon as it's ready.
> >> >
> >> > man. 7. des. 2020 kl. 13:18 skrev Stephen Mallette <
> >> spmalle...@gmail.com>:
> >> >
> >> >> Thanks for all the updates - it sounds as though we are getting
> closer
> >> to
> >> >> having to do more things on this side. Once the I/CCLAs are
> >> acknowledged
> >> >> by
> >> >> Apache I'll go back and revisit the documentation on this process to
> >> see
> >> >> what happens next.
> >> >>
> >> >> On Thu, Dec 3, 2020 at 9:05 AM Øyvind Sæbø 
> >> wrote:
> >> >>
> >> >> > Hi again, I'm here with an update on the Gremlint IP clearance
> >> process:)
> >> >> >
> >> >> > Yesterday I added the ASF source file headers to all the gremlint
> >> source
> >> >> > files (link to commit
> >> >> > <
> >> >> >
> >> >>
> >>
> https://github.com/OyvindSabo/gremlint/commit/9010a706ceaa4102886294a860d5fbac152ca08b
> >> >> > >)
> >> >> > and all the gremlint.com source files (link to commit
> >> >> > <
> >> >> >
> >> >>
> >>
> https://github.com/OyvindSabo/gremlint.com/commit/60150a52d1baed330e16d2b70a8ac84f0aa5d4b4
> >> >> > >)
> >> >> > and updated both repos to use the Apache License Version 2.0. I
> hope
> >> I
> >> >> did
> >> >> > that correctly.
> >> >> > I also filled out the ICLA and will submit it together with the
> CCLA
> >> >> once
> >> >> > it's signed by the right people at Ardoq. I was hoping to see this
> >> done
> >> >> by
> >> >> > the end of the week, but seeing as it's only one workday left, I
> >> guess
> >> >> > we'll just 

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Hi, I'm back again with an update on the ongoing Gremlint IP clearance
progress:
Today the CCLA was signed by our CEO, so we aim to have my signed ICLA and
the CCLA sent to secret...@apache.org as soon as possible.

fre. 8. jan. 2021 kl. 09:24 skrev Øyvind Sæbø :

> Happy new year!
>
> Update on the Gremlint IP clearance process:
> We filled out the CCLA yesterday and are just waiting for it to be signed
> by our CEO.
> We'll submit it together with the ICLA as soon as it's ready.
>
> man. 7. des. 2020 kl. 13:18 skrev Stephen Mallette :
>
>> Thanks for all the updates - it sounds as though we are getting closer to
>> having to do more things on this side. Once the I/CCLAs are acknowledged
>> by
>> Apache I'll go back and revisit the documentation on this process to see
>> what happens next.
>>
>> On Thu, Dec 3, 2020 at 9:05 AM Øyvind Sæbø  wrote:
>>
>> > Hi again, I'm here with an update on the Gremlint IP clearance process:)
>> >
>> > Yesterday I added the ASF source file headers to all the gremlint source
>> > files (link to commit
>> > <
>> >
>> https://github.com/OyvindSabo/gremlint/commit/9010a706ceaa4102886294a860d5fbac152ca08b
>> > >)
>> > and all the gremlint.com source files (link to commit
>> > <
>> >
>> https://github.com/OyvindSabo/gremlint.com/commit/60150a52d1baed330e16d2b70a8ac84f0aa5d4b4
>> > >)
>> > and updated both repos to use the Apache License Version 2.0. I hope I
>> did
>> > that correctly.
>> > I also filled out the ICLA and will submit it together with the CCLA
>> once
>> > it's signed by the right people at Ardoq. I was hoping to see this done
>> by
>> > the end of the week, but seeing as it's only one workday left, I guess
>> > we'll just have to wait and see.
>> >
>> > fre. 27. nov. 2020 kl. 19:24 skrev Øyvind Sæbø :
>> >
>> > > By
>> > >> the way, can gremlint still run completely in browser or does it need
>> > >> nodejs at this point?
>> > >
>> > > Yes, it's still possible to run it purely in the browser. This is
>> still
>> > > how it's used on Gremlint.com.
>> > >
>> > > Would it help make any of your work easier if there were an actual
>> antlr
>> > >> grammar for Gremlin?
>> > >
>> > > I'm not sure. I don't have any experience with it, but I'll look into
>> it.
>> > >
>> > > .NET might not be hard to format but I sense translation will not be
>> easy
>> > >> given how easily Gremlin loses types
>> > >>
>> > > Good point.
>> > >
>> > > As for progress news, we managed to wrap up the internal Gremlint IP
>> > > transfer process this week, so I hope we can fill out the ICLA and
>> CCLA
>> > > next week. I'll add the ASF licence headers to the files early next
>> week
>> > as
>> > > well.
>> > >
>> > > ons. 25. nov. 2020 kl. 12:57 skrev Stephen Mallette <
>> > spmalle...@gmail.com
>> > > >:
>> > >
>> > >> On Fri, Nov 20, 2020 at 3:49 PM Øyvind Sæbø 
>> > >> wrote:
>> > >>
>> > >> > Yes, I think it makes sense to continue with the general
>> discussion in
>> > >> the
>> > >> > meantime:) It could also help make sure that I don't develop
>> Gremlint
>> > >> in a
>> > >> > direction which will impose unnecessary restrictions in the future.
>> > I've
>> > >> > included some of my thoughts to your questions below:
>> > >> >
>> > >> > 1.
>> > >> > Gremlint is currently an installable JavaScript package, so for all
>> > >> > JavaScript projects using npm it can already be installed and
>> called
>> > as
>> > >> a
>> > >> > function. I imagine it would also be easy to set up a
>> > >> Gremlint-as-a-service
>> > >> > API with Node.js to work with non-JavaScript projects.
>> > >> >
>> > >>
>> > >> At the risk of greater complexity to documentation generation
>> perhaps a
>> > >> local nodejs service might work. A shame nashorn never quite took
>> off or
>> > >> else we could have perhaps embedded it for more direct usage with
>> > Gremlin
>> > >> Console. I wonder if we could actually get rid 

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Happy new year!

Update on the Gremlint IP clearance process:
We filled out the CCLA yesterday and are just waiting for it to be signed
by our CEO.
We'll submit it together with the ICLA as soon as it's ready.

man. 7. des. 2020 kl. 13:18 skrev Stephen Mallette :

> Thanks for all the updates - it sounds as though we are getting closer to
> having to do more things on this side. Once the I/CCLAs are acknowledged by
> Apache I'll go back and revisit the documentation on this process to see
> what happens next.
>
> On Thu, Dec 3, 2020 at 9:05 AM Øyvind Sæbø  wrote:
>
> > Hi again, I'm here with an update on the Gremlint IP clearance process:)
> >
> > Yesterday I added the ASF source file headers to all the gremlint source
> > files (link to commit
> > <
> >
> https://github.com/OyvindSabo/gremlint/commit/9010a706ceaa4102886294a860d5fbac152ca08b
> > >)
> > and all the gremlint.com source files (link to commit
> > <
> >
> https://github.com/OyvindSabo/gremlint.com/commit/60150a52d1baed330e16d2b70a8ac84f0aa5d4b4
> > >)
> > and updated both repos to use the Apache License Version 2.0. I hope I
> did
> > that correctly.
> > I also filled out the ICLA and will submit it together with the CCLA once
> > it's signed by the right people at Ardoq. I was hoping to see this done
> by
> > the end of the week, but seeing as it's only one workday left, I guess
> > we'll just have to wait and see.
> >
> > fre. 27. nov. 2020 kl. 19:24 skrev Øyvind Sæbø :
> >
> > > By
> > >> the way, can gremlint still run completely in browser or does it need
> > >> nodejs at this point?
> > >
> > > Yes, it's still possible to run it purely in the browser. This is still
> > > how it's used on Gremlint.com.
> > >
> > > Would it help make any of your work easier if there were an actual
> antlr
> > >> grammar for Gremlin?
> > >
> > > I'm not sure. I don't have any experience with it, but I'll look into
> it.
> > >
> > > .NET might not be hard to format but I sense translation will not be
> easy
> > >> given how easily Gremlin loses types
> > >>
> > > Good point.
> > >
> > > As for progress news, we managed to wrap up the internal Gremlint IP
> > > transfer process this week, so I hope we can fill out the ICLA and CCLA
> > > next week. I'll add the ASF licence headers to the files early next
> week
> > as
> > > well.
> > >
> > > ons. 25. nov. 2020 kl. 12:57 skrev Stephen Mallette <
> > spmalle...@gmail.com
> > > >:
> > >
> > >> On Fri, Nov 20, 2020 at 3:49 PM Øyvind Sæbø 
> > >> wrote:
> > >>
> > >> > Yes, I think it makes sense to continue with the general discussion
> in
> > >> the
> > >> > meantime:) It could also help make sure that I don't develop
> Gremlint
> > >> in a
> > >> > direction which will impose unnecessary restrictions in the future.
> > I've
> > >> > included some of my thoughts to your questions below:
> > >> >
> > >> > 1.
> > >> > Gremlint is currently an installable JavaScript package, so for all
> > >> > JavaScript projects using npm it can already be installed and called
> > as
> > >> a
> > >> > function. I imagine it would also be easy to set up a
> > >> Gremlint-as-a-service
> > >> > API with Node.js to work with non-JavaScript projects.
> > >> >
> > >>
> > >> At the risk of greater complexity to documentation generation perhaps
> a
> > >> local nodejs service might work. A shame nashorn never quite took off
> or
> > >> else we could have perhaps embedded it for more direct usage with
> > Gremlin
> > >> Console. I wonder if we could actually get rid of Gremlin Console
> usage
> > >> though if there was a more convenient way to do
> formatting/translation.
> > By
> > >> the way, can gremlint still run completely in browser or does it need
> > >> nodejs at this point?
> > >>
> > >>
> > >> > 2 & 4.
> > >> > I think Gremlint as a translator could make sense. Currently it
> > >> essentially
> > >> > just translates Groovy-Gremlin to an (almost) language-agnostic
> syntax
> > >> > tree, adds formatting information based on a config object and then
> > >> > recreates a Groovy Gremlin query. But it could j

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Hi again, I'm here with an update on the Gremlint IP clearance process:)

Yesterday I added the ASF source file headers to all the gremlint source
files (link to commit
<https://github.com/OyvindSabo/gremlint/commit/9010a706ceaa4102886294a860d5fbac152ca08b>)
and all the gremlint.com source files (link to commit
<https://github.com/OyvindSabo/gremlint.com/commit/60150a52d1baed330e16d2b70a8ac84f0aa5d4b4>)
and updated both repos to use the Apache License Version 2.0. I hope I did
that correctly.
I also filled out the ICLA and will submit it together with the CCLA once
it's signed by the right people at Ardoq. I was hoping to see this done by
the end of the week, but seeing as it's only one workday left, I guess
we'll just have to wait and see.

fre. 27. nov. 2020 kl. 19:24 skrev Øyvind Sæbø :

> By
>> the way, can gremlint still run completely in browser or does it need
>> nodejs at this point?
>
> Yes, it's still possible to run it purely in the browser. This is still
> how it's used on Gremlint.com.
>
> Would it help make any of your work easier if there were an actual antlr
>> grammar for Gremlin?
>
> I'm not sure. I don't have any experience with it, but I'll look into it.
>
> .NET might not be hard to format but I sense translation will not be easy
>> given how easily Gremlin loses types
>>
> Good point.
>
> As for progress news, we managed to wrap up the internal Gremlint IP
> transfer process this week, so I hope we can fill out the ICLA and CCLA
> next week. I'll add the ASF licence headers to the files early next week as
> well.
>
> ons. 25. nov. 2020 kl. 12:57 skrev Stephen Mallette  >:
>
>> On Fri, Nov 20, 2020 at 3:49 PM Øyvind Sæbø 
>> wrote:
>>
>> > Yes, I think it makes sense to continue with the general discussion in
>> the
>> > meantime:) It could also help make sure that I don't develop Gremlint
>> in a
>> > direction which will impose unnecessary restrictions in the future. I've
>> > included some of my thoughts to your questions below:
>> >
>> > 1.
>> > Gremlint is currently an installable JavaScript package, so for all
>> > JavaScript projects using npm it can already be installed and called as
>> a
>> > function. I imagine it would also be easy to set up a
>> Gremlint-as-a-service
>> > API with Node.js to work with non-JavaScript projects.
>> >
>>
>> At the risk of greater complexity to documentation generation perhaps a
>> local nodejs service might work. A shame nashorn never quite took off or
>> else we could have perhaps embedded it for more direct usage with Gremlin
>> Console. I wonder if we could actually get rid of Gremlin Console usage
>> though if there was a more convenient way to do formatting/translation. By
>> the way, can gremlint still run completely in browser or does it need
>> nodejs at this point?
>>
>>
>> > 2 & 4.
>> > I think Gremlint as a translator could make sense. Currently it
>> essentially
>> > just translates Groovy-Gremlin to an (almost) language-agnostic syntax
>> > tree, adds formatting information based on a config object and then
>> > recreates a Groovy Gremlin query. But it could just as well recreate the
>> > query as a JavaScript or Python Gremlin query. I think it would be
>> > relatively easy to make Gremlint translate from any Groovy-esque Gremlin
>> > implementation to another Gremlin implementation by simply replacing the
>> > function which is currently used to recreate the query from the
>> formatted
>> > syntax tree.
>> >
>>
>> Would it help make any of your work easier if there were an actual antlr
>> grammar for Gremlin?
>>
>>
>> > 3.
>> > I've already tried to keep Gremlint a bit language agnostic by leaving
>> all
>> > non-Gremlin code around and between queries unaltered. In most cases,
>> any
>> > code Gremlint doesn't understand inside a query is just handled as if it
>> > was a single word, and left as is. I'm not too familiar with
>> > language-specific differences between different Gremlin-implementations,
>> > but it is my impression that it should already handle JavaScript Gremlin
>> > quite well. For .NET I assume I would need to add support for more than
>> > just single-quote strings (this would come in handy for all languages),
>> and
>> > for Python Gremlin it would need to handle backslashes between each new
>> > line of the query. Gremlin for Clojure would probably be more
>> challenging
>> > (fun fact: The Gremlint parser is actually based on a Cl

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

>
> By
> the way, can gremlint still run completely in browser or does it need
> nodejs at this point?

Yes, it's still possible to run it purely in the browser. This is still how
it's used on Gremlint.com.

Would it help make any of your work easier if there were an actual antlr
> grammar for Gremlin?

I'm not sure. I don't have any experience with it, but I'll look into it.

.NET might not be hard to format but I sense translation will not be easy
> given how easily Gremlin loses types
>
Good point.

As for progress news, we managed to wrap up the internal Gremlint IP
transfer process this week, so I hope we can fill out the ICLA and CCLA
next week. I'll add the ASF licence headers to the files early next week as
well.

ons. 25. nov. 2020 kl. 12:57 skrev Stephen Mallette :

> On Fri, Nov 20, 2020 at 3:49 PM Øyvind Sæbø  wrote:
>
> > Yes, I think it makes sense to continue with the general discussion in
> the
> > meantime:) It could also help make sure that I don't develop Gremlint in
> a
> > direction which will impose unnecessary restrictions in the future. I've
> > included some of my thoughts to your questions below:
> >
> > 1.
> > Gremlint is currently an installable JavaScript package, so for all
> > JavaScript projects using npm it can already be installed and called as a
> > function. I imagine it would also be easy to set up a
> Gremlint-as-a-service
> > API with Node.js to work with non-JavaScript projects.
> >
>
> At the risk of greater complexity to documentation generation perhaps a
> local nodejs service might work. A shame nashorn never quite took off or
> else we could have perhaps embedded it for more direct usage with Gremlin
> Console. I wonder if we could actually get rid of Gremlin Console usage
> though if there was a more convenient way to do formatting/translation. By
> the way, can gremlint still run completely in browser or does it need
> nodejs at this point?
>
>
> > 2 & 4.
> > I think Gremlint as a translator could make sense. Currently it
> essentially
> > just translates Groovy-Gremlin to an (almost) language-agnostic syntax
> > tree, adds formatting information based on a config object and then
> > recreates a Groovy Gremlin query. But it could just as well recreate the
> > query as a JavaScript or Python Gremlin query. I think it would be
> > relatively easy to make Gremlint translate from any Groovy-esque Gremlin
> > implementation to another Gremlin implementation by simply replacing the
> > function which is currently used to recreate the query from the formatted
> > syntax tree.
> >
>
> Would it help make any of your work easier if there were an actual antlr
> grammar for Gremlin?
>
>
> > 3.
> > I've already tried to keep Gremlint a bit language agnostic by leaving
> all
> > non-Gremlin code around and between queries unaltered. In most cases, any
> > code Gremlint doesn't understand inside a query is just handled as if it
> > was a single word, and left as is. I'm not too familiar with
> > language-specific differences between different Gremlin-implementations,
> > but it is my impression that it should already handle JavaScript Gremlin
> > quite well. For .NET I assume I would need to add support for more than
> > just single-quote strings (this would come in handy for all languages),
> and
> > for Python Gremlin it would need to handle backslashes between each new
> > line of the query. Gremlin for Clojure would probably be more challenging
> > (fun fact: The Gremlint parser is actually based on a Clojure parser I
> > wrote earlier).
> >
>
> .NET might not be hard to format but I sense translation will not be easy
> given how easily Gremlin loses types
>
>
> > Food for thought:
> > One thing I've been a bit back and forth on is whether it would be
> > preferable if Gremlint is super-robust and accepts and formats any
> language
> > you pass it with minimal configuration, or if it should only accept one
> > Gremlin implementation "at once" and require the user to manually specify
> > the language of their input.
> >
>
> From the perspective of a user interface, I don't think it's necessary to
> have too much magic. Ifi t could simply detect a language and make a good
> guess at it and then allow users more fine grained control from there that
> would be pretty impressive, but if they had to wholly make the step of
> selecting the language themselves I don't think that's terrible.
>
>
> >
> > fre. 20. nov. 2020 kl. 14:53 skrev Stephen Mallette <
> spmalle...@gmail.com
> > >:
> >
> > > Thanks for another update. Nice to know y

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Yes, I think it makes sense to continue with the general discussion in the
meantime:) It could also help make sure that I don't develop Gremlint in a
direction which will impose unnecessary restrictions in the future. I've
included some of my thoughts to your questions below:

1.
Gremlint is currently an installable JavaScript package, so for all
JavaScript projects using npm it can already be installed and called as a
function. I imagine it would also be easy to set up a Gremlint-as-a-service
API with Node.js to work with non-JavaScript projects.

2 & 4.
I think Gremlint as a translator could make sense. Currently it essentially
just translates Groovy-Gremlin to an (almost) language-agnostic syntax
tree, adds formatting information based on a config object and then
recreates a Groovy Gremlin query. But it could just as well recreate the
query as a JavaScript or Python Gremlin query. I think it would be
relatively easy to make Gremlint translate from any Groovy-esque Gremlin
implementation to another Gremlin implementation by simply replacing the
function which is currently used to recreate the query from the formatted
syntax tree.

3.
I've already tried to keep Gremlint a bit language agnostic by leaving all
non-Gremlin code around and between queries unaltered. In most cases, any
code Gremlint doesn't understand inside a query is just handled as if it
was a single word, and left as is. I'm not too familiar with
language-specific differences between different Gremlin-implementations,
but it is my impression that it should already handle JavaScript Gremlin
quite well. For .NET I assume I would need to add support for more than
just single-quote strings (this would come in handy for all languages), and
for Python Gremlin it would need to handle backslashes between each new
line of the query. Gremlin for Clojure would probably be more challenging
(fun fact: The Gremlint parser is actually based on a Clojure parser I
wrote earlier).

Food for thought:
One thing I've been a bit back and forth on is whether it would be
preferable if Gremlint is super-robust and accepts and formats any language
you pass it with minimal configuration, or if it should only accept one
Gremlin implementation "at once" and require the user to manually specify
the language of their input.

fre. 20. nov. 2020 kl. 14:53 skrev Stephen Mallette :

> Thanks for another update. Nice to know you're still moving along with
> improvements there. Perhaps we could continue with general discussions
> about Gremlint while we wait for legal issues to settle? For instance, one
> of the things on my mind is how to make gremlint functionality as available
> as possible to the various use cases we say each day. Obviously, it
> currently handles the most common one of providing a place to paste some
> Gremlin in a UI and get back formatted Gremlin. What about other things:
>
> 1. there are many Gremlin "development environments (e.g. gremlify, Gremlin
> Console, notebooks, etc) - how can gremlint be available to them?
> 2. we are working on Gremlin translators in all languages - which might
> actually allow us to generate documentation using a single source for
> Gremlin with translation to all the others. But, that can only work if we
> have something like Gremlint to format those translations. How would
> gremlint fit in there?
> 3. gremlint (i think) is generally good at formatting the Groovy/Java
> syntax - what will it entail to make it so that it's capable of dealing
> with other languages like Python, .NET etc.
> 4. thinking more about 2, I wonder how gremlint fits with translators. the
> two seem quite related to me, but i'm not sure what that means. it seems
> cool if you could take a bit of Gremlin Groovy, paste it into gremlint then
> translate/lint to Gremlin Javascript.
>
> I'm just posing questions here for us to discuss a bit. Answers are great
> but more questions would also be welcome if anyone has any.
>
>
>
> On Fri, Nov 20, 2020 at 2:11 AM Øyvind Sæbø  wrote:
>
> > Hello everyone and happy November.
> >
> > I requested another update on when the Gremlint paperwork process would
> be
> > done yesterday. It seems like it has been pushed back once again, the new
> > estimate being two weeks from now.
> >
> > I figured I should give some context on why this is taking longer than
> > expected. After all, filling out the ICLA and CCLA shouldn't take more
> than
> > a day. Since I developed Gremlint in my spare time, and we want to donate
> > it on behalf of Ardoq, where I work, we have an internal IP transfer
> > process as well, and this is what has been dragging out.
> >
> > In the meantime I've been trying to make the best of the situation by
> > working my way through the remaining Gremlint issues on GitHub. As part
> of
> 

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Hello everyone and happy November.

I requested another update on when the Gremlint paperwork process would be
done yesterday. It seems like it has been pushed back once again, the new
estimate being two weeks from now.

I figured I should give some context on why this is taking longer than
expected. After all, filling out the ICLA and CCLA shouldn't take more than
a day. Since I developed Gremlint in my spare time, and we want to donate
it on behalf of Ardoq, where I work, we have an internal IP transfer
process as well, and this is what has been dragging out.

In the meantime I've been trying to make the best of the situation by
working my way through the remaining Gremlint issues on GitHub. As part of
that I've rewritten Gremlint  to be
a separate package which can be imported in the Gremlint.com website, which
now resides in a different repository
.

Let's hope I can report on more progress next time.

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Hi, yes, it's (finally) progressing.

Our legal department had a meeting yesterday and started going through the
documents and gave me an update today. I asked for an updated time
estimation for when we would have the documents filled out and submitted.
The new estimate is "the next couple of weeks". I can unfortunately not be
more specific than that.

I'll make sure to forward any questions we need input on during the process.

ons. 28. okt. 2020 kl. 13:01 skrev Stephen Mallette :

> Hello Øyvind, I hope things are still progressing along on your end since
> your last update. Please let us know if there are any questions we might
> answer as the process continues at your organization. Thanks.
>
> On Thu, Oct 15, 2020 at 11:32 AM Øyvind Sæbø 
> wrote:
>
> > It's been a while since I've given an update about where we are in the
> > process of the Gremlint IP Clearance. We're in October, so I asked our
> > legal department for a more specific estimated time for filling out the
> > CCLA. The hope is still to do it in October, but at best it won't be
> until
> > the last week of the month. Thank you all for your patience.
> >
> > tor. 17. sep. 2020 kl. 21:16 skrev Øyvind Sæbø :
> >
> > > I've created a pull request for adding ASF licence headers to all the
> > > files of the project here:
> > https://github.com/OyvindSabo/gremlint/pull/57
> > >
> > > I'll merge it once the legal department at Ardoq has had time to fill
> out
> > > the CCLA. I requested an estimate for when they would have time for
> this,
> > > and unfortunately it might not be until October, so I guess that indeed
> > > leaves me some time to do some clean-up.
> > >
> > > ons. 16. sep. 2020 kl. 16:01 skrev Stephen Mallette <
> > spmalle...@gmail.com
> > > >:
> > >
> > >> Sorry - to be clear, I will start the VOTE thread once the IP
> Clearance
> > >> form is complete.
> > >>
> > >> On Wed, Sep 16, 2020 at 9:53 AM Stephen Mallette <
> spmalle...@gmail.com>
> > >> wrote:
> > >>
> > >> > Interestingly there is a similar process going on right now in the
> > >> Apache
> > >> > Cassandra community where they are going through IP Clearance. In
> > >> watching
> > >> > that it seems an actual VOTE thread is better than a "consensus"
> > >> thread, so
> > >> > I will start that now for completeness purposes and to lower
> friction
> > >> as we
> > >> > head toward incubator.
> > >> >
> > >> > On Wed, Sep 16, 2020 at 7:05 AM Stephen Mallette <
> > spmalle...@gmail.com>
> > >> > wrote:
> > >> >
> > >> >> >1. I can create a GitHub issue for adding the required headers
> > in
> > >> >> all the source files.
> > >> >>
> > >> >> excellent. I'm still not completely clear on that step being a
> > >> >> prerequisite from the documentation as i saw some IP Clearance
> > examples
> > >> >> with and without it, but if I know one thing about Apache and its
> > Ways,
> > >> >> it's best not to use "what other projects do" as your reasoning for
> > >> doing
> > >> >> something. anyway, once that commit is in place we can reference
> that
> > >> >> commit id (or any after it) for the donation. I suppose that if
> there
> > >> were
> > >> >> any other "clean-up" you wanted to do before that time, now would
> be
> > >> the
> > >> >> time to do it.
> > >> >>
> > >> >> >   2. There should be no issues there.
> > >> >> >   3. The project has zero dependencies, so there should be no
> > issues
> > >> >> there either.
> > >> >>
> > >> >> well - that's easy then!
> > >> >>
> > >> >> a quick side note as we continue this process - the incubator site
> > has
> > >> >> regenerated itself so our page is available now:
> > >> >>
> > >> >> https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html
> > >> >>
> > >> >> you can see what steps remain - i've updated the document to
> reflect
> > >> your
> > >> >> responses to items 2 and 3 above.
> > >> >>
> > >> >> On Tue,

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

It's been a while since I've given an update about where we are in the
process of the Gremlint IP Clearance. We're in October, so I asked our
legal department for a more specific estimated time for filling out the
CCLA. The hope is still to do it in October, but at best it won't be until
the last week of the month. Thank you all for your patience.

tor. 17. sep. 2020 kl. 21:16 skrev Øyvind Sæbø :

> I've created a pull request for adding ASF licence headers to all the
> files of the project here: https://github.com/OyvindSabo/gremlint/pull/57
>
> I'll merge it once the legal department at Ardoq has had time to fill out
> the CCLA. I requested an estimate for when they would have time for this,
> and unfortunately it might not be until October, so I guess that indeed
> leaves me some time to do some clean-up.
>
> ons. 16. sep. 2020 kl. 16:01 skrev Stephen Mallette  >:
>
>> Sorry - to be clear, I will start the VOTE thread once the IP Clearance
>> form is complete.
>>
>> On Wed, Sep 16, 2020 at 9:53 AM Stephen Mallette 
>> wrote:
>>
>> > Interestingly there is a similar process going on right now in the
>> Apache
>> > Cassandra community where they are going through IP Clearance. In
>> watching
>> > that it seems an actual VOTE thread is better than a "consensus"
>> thread, so
>> > I will start that now for completeness purposes and to lower friction
>> as we
>> > head toward incubator.
>> >
>> > On Wed, Sep 16, 2020 at 7:05 AM Stephen Mallette 
>> > wrote:
>> >
>> >> >1. I can create a GitHub issue for adding the required headers in
>> >> all the source files.
>> >>
>> >> excellent. I'm still not completely clear on that step being a
>> >> prerequisite from the documentation as i saw some IP Clearance examples
>> >> with and without it, but if I know one thing about Apache and its Ways,
>> >> it's best not to use "what other projects do" as your reasoning for
>> doing
>> >> something. anyway, once that commit is in place we can reference that
>> >> commit id (or any after it) for the donation. I suppose that if there
>> were
>> >> any other "clean-up" you wanted to do before that time, now would be
>> the
>> >> time to do it.
>> >>
>> >> >   2. There should be no issues there.
>> >> >   3. The project has zero dependencies, so there should be no issues
>> >> there either.
>> >>
>> >> well - that's easy then!
>> >>
>> >> a quick side note as we continue this process - the incubator site has
>> >> regenerated itself so our page is available now:
>> >>
>> >> https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html
>> >>
>> >> you can see what steps remain - i've updated the document to reflect
>> your
>> >> responses to items 2 and 3 above.
>> >>
>> >> On Tue, Sep 15, 2020 at 11:19 AM Øyvind Sæbø 
>> >> wrote:
>> >>
>> >>> Yes, I'm following along. Cool to hear that we can move forward with
>> >>> this.
>> >>>
>> >>> I and Ardoq (the company that the project will be donated on behalf
>> of)
>> >>> will start filling out the required ICLA
>> >>> <https://www.apache.org/licenses/icla.pdf> and CCLA
>> >>> <https://www.apache.org/licenses/cla-corporate.pdf>.
>> >>>
>> >>> Regarding the points you mentioned:
>> >>>
>> >>>1. I can create a GitHub issue for adding the required headers in
>> all
>> >>>the source files.
>> >>>2. There should be no issues there.
>> >>>3. The project has zero dependencies, so there should be no issues
>> >>> there
>> >>>either.
>> >>>
>> >>>
>> >>> tir. 15. sep. 2020 kl. 15:48 skrev Stephen Mallette <
>> >>> spmalle...@gmail.com>:
>> >>>
>> >>> > I've set up the IP Clearance form for incubator here (website hasn't
>> >>> > generated the HTML yet I guess):
>> >>> >
>> >>> >
>> >>> >
>> >>>
>> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
>> >>> >
>> >>> > In the checklist of items there there are few items pertaining to
>> the
>&g

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

I've created a pull request for adding ASF licence headers to all the files
of the project here: https://github.com/OyvindSabo/gremlint/pull/57

I'll merge it once the legal department at Ardoq has had time to fill out
the CCLA. I requested an estimate for when they would have time for this,
and unfortunately it might not be until October, so I guess that indeed
leaves me some time to do some clean-up.

ons. 16. sep. 2020 kl. 16:01 skrev Stephen Mallette :

> Sorry - to be clear, I will start the VOTE thread once the IP Clearance
> form is complete.
>
> On Wed, Sep 16, 2020 at 9:53 AM Stephen Mallette 
> wrote:
>
> > Interestingly there is a similar process going on right now in the Apache
> > Cassandra community where they are going through IP Clearance. In
> watching
> > that it seems an actual VOTE thread is better than a "consensus" thread,
> so
> > I will start that now for completeness purposes and to lower friction as
> we
> > head toward incubator.
> >
> > On Wed, Sep 16, 2020 at 7:05 AM Stephen Mallette 
> > wrote:
> >
> >> >1. I can create a GitHub issue for adding the required headers in
> >> all the source files.
> >>
> >> excellent. I'm still not completely clear on that step being a
> >> prerequisite from the documentation as i saw some IP Clearance examples
> >> with and without it, but if I know one thing about Apache and its Ways,
> >> it's best not to use "what other projects do" as your reasoning for
> doing
> >> something. anyway, once that commit is in place we can reference that
> >> commit id (or any after it) for the donation. I suppose that if there
> were
> >> any other "clean-up" you wanted to do before that time, now would be the
> >> time to do it.
> >>
> >> >   2. There should be no issues there.
> >> >   3. The project has zero dependencies, so there should be no issues
> >> there either.
> >>
> >> well - that's easy then!
> >>
> >> a quick side note as we continue this process - the incubator site has
> >> regenerated itself so our page is available now:
> >>
> >> https://incubator.apache.org/ip-clearance/tinkerpop-gremlint.html
> >>
> >> you can see what steps remain - i've updated the document to reflect
> your
> >> responses to items 2 and 3 above.
> >>
> >> On Tue, Sep 15, 2020 at 11:19 AM Øyvind Sæbø 
> >> wrote:
> >>
> >>> Yes, I'm following along. Cool to hear that we can move forward with
> >>> this.
> >>>
> >>> I and Ardoq (the company that the project will be donated on behalf of)
> >>> will start filling out the required ICLA
> >>> <https://www.apache.org/licenses/icla.pdf> and CCLA
> >>> <https://www.apache.org/licenses/cla-corporate.pdf>.
> >>>
> >>> Regarding the points you mentioned:
> >>>
> >>>1. I can create a GitHub issue for adding the required headers in
> all
> >>>the source files.
> >>>2. There should be no issues there.
> >>>3. The project has zero dependencies, so there should be no issues
> >>> there
> >>>either.
> >>>
> >>>
> >>> tir. 15. sep. 2020 kl. 15:48 skrev Stephen Mallette <
> >>> spmalle...@gmail.com>:
> >>>
> >>> > I've set up the IP Clearance form for incubator here (website hasn't
> >>> > generated the HTML yet I guess):
> >>> >
> >>> >
> >>> >
> >>>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
> >>> >
> >>> > In the checklist of items there there are few items pertaining to the
> >>> code
> >>> > base itself:
> >>> >
> >>> > 1. Check and make sure that the files that have been donated have
> been
> >>> > updated to reflect the new ASF copyright
> >>> > 2. Check and make sure that for all items included with the
> >>> distribution
> >>> > that is not under the Apache license, we have the right to combine
> with
> >>> > Apache-licensed code and redistribute.
> >>> > 3. Check and make sure that all items depended upon by the project is
> >>> > covered by one or more of the following approved licenses: Apache,
> BSD,
> >>> > Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the
> >>> 

Re: [DISCUSS] Accepting gremlint donation

[Øyvind Sæbø]

Yes, I'm following along. Cool to hear that we can move forward with this.

I and Ardoq (the company that the project will be donated on behalf of)
will start filling out the required ICLA
 and CCLA
.

Regarding the points you mentioned:

   1. I can create a GitHub issue for adding the required headers in all
   the source files.
   2. There should be no issues there.
   3. The project has zero dependencies, so there should be no issues there
   either.


tir. 15. sep. 2020 kl. 15:48 skrev Stephen Mallette :

> I've set up the IP Clearance form for incubator here (website hasn't
> generated the HTML yet I guess):
>
>
> https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/tinkerpop-gremlint.xml
>
> In the checklist of items there there are few items pertaining to the code
> base itself:
>
> 1. Check and make sure that the files that have been donated have been
> updated to reflect the new ASF copyright
> 2. Check and make sure that for all items included with the distribution
> that is not under the Apache license, we have the right to combine with
> Apache-licensed code and redistribute.
> 3. Check and make sure that all items depended upon by the project is
> covered by one or more of the following approved licenses: Apache, BSD,
> Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially the same
> terms.
>
> For item 1 I assume that means the code base state at which we accept the
> it should have the ASF license header in it with it an appropriate NOTICE
> file if necessary:
>
> https://www.apache.org/legal/src-headers.html
>
> For 2 and 3, I don't think we have any issues there but would need to
> confirm.
>
> Øyvind, I believe you're on the list following along - could you please
> comment on the above for us?
>
>
>
>
> On Tue, Sep 15, 2020 at 7:30 AM Stephen Mallette 
> wrote:
>
> > As there haven't been any objections here, it sounds like we can go ahead
> > with this process. I believe that we will need to go through the IP
> > Clearance process in incubator:
> >
> > https://incubator.apache.org/ip-clearance/
> >
> > and engage Apache Infra about a gremlint.com domain transfer. And then
> of
> > course we will need to figure out "how" we make it part of the code base
> > (where it goes, how it fits in the release process, etc.) - my preference
> > would be to see it come in on 3.4.x so that we can immediately have an
> > official release of it, but we'll see how it goes. I suppose we will
> > continue to use this thread for all this sort of discussion for now
> unless
> > it gets too busy in which case we can spawn off other threads as needed..
> >
> > On Thu, Sep 10, 2020 at 6:31 PM David Bechberger 
> > wrote:
> >
> >> I definitely agree that having this sort of tool freely available would
> be
> >> very helpful to the community as a whole.
> >>
> >> I also would be able to help create the translator between GLV's and
> text
> >> representations as this is something I and many others have struggled
> with
> >> many times.
> >>
> >> Thanks,
> >> Dave
> >>
> >> On Thu, Sep 10, 2020 at 2:14 PM Kelvin Lawrence
>  >> >
> >> wrote:
> >>
> >> > I really like the idea of having an Apache TinkerPop hosted linter and
> >> > style guide "enforcer". I have spent many wasted hours hand formatting
> >> long
> >> > Gremlin queries people have asked me to look at over the years and the
> >> > latest version of Gremlint makes that so much easier. I also really
> like
> >> > the idea of extending the tool in the direction of "Gremlin
> converter".
> >> I
> >> > hear from a lot of users that porting from (let's say) Gremlin Console
> >> to
> >> > Gremlin Python (and vice-versa) is painful and hard to get right.
> >> >
> >> > Cheers
> >> > Kelvin
> >> >
> >> > On 2020/09/10 11:07:46, Stephen Mallette  wrote:
> >> > > I've had some on and off discussions with the developer of>
> >> > >
> >> > > https://gremlint.com/>
> >> > >
> >> > > whose name is Øyvind btw, about the possibility of making gremlint
> >> the>
> >> > > canonical Gremlin code stylizer, and by that I mean, his donating
> the
> >> > code>
> >> > > (and domain name) to the Apache Software Foundation under our
> project.
> >> > That>
> >> > > situation seems possible now and has been offered to the TinkerPop>
> >> > > Community.>
> >> > >
> >> > > I like the idea of bringing this code here because I feel our style
> >> > guide>
> >> > > in Gremlin Recipes can only suggest convention and I'd much like to
> >> see
> >> > a>
> >> > > code library managed by our project enforce a proper Gremlin style
> >> that
> >> > can>
> >> > > be used not only as the neat single HTML page of gremlint.com but
> >> also
> >> > as a>
> >> > > code library to Gremlin tool builders.>
> >> > >
> >> > > I also see the opportunity to grow this tool into an online
> translator
> >> > to>
> >> > > get you from one Gremlin dialect to another which is a