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 <[email protected]> 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 < > [email protected]> 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 <[email protected]> >> Sent: Tuesday, June 7, 2016 4:05:16 PM >> To: [email protected] >> 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 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/ >> Adding and editing wiki pages locally - User Documentation< >> https://help.github.com/articles/adding-and-editing-wiki-pages-locally/> >> help.github.com >> Cloning wikis locally to your computer. Every wiki provides an easy way to >> clone its contents down to your computer: If you're using GitHub Desktop, >> click Clone in ... >> >> >> >> >> 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 >>
