Awesome! Should Github issue tracking be enabled on it and the scriptom repo? If not, should we disable issue tracking on the windows installer repo?-KeeganOn Tue, Jul 21, 2015 at 6:33 PM, Guillaume Laforge <email@example.com> wrote:It's now here!I've updated the readme (from text to asciidoc) and removed the reference to the old content from the Groovy wiki.Whenever we have a pointer for a new home for its doc, we should add that back in the description.Guillaume--On Wed, Jul 22, 2015 at 12:14 AM, Keegan Witt <firstname.lastname@example.org> wrote:That'd be the way to avoid creating any work for Ben :) I don't think it matters too much either way. Unless you think it'd be confusing for users to see a read-only repo as the apparent "upstream" repo. It's probably pretty obvious though.-KeeganOn Tue, Jul 21, 2015 at 5:54 PM, Guillaume Laforge <email@example.com> wrote:Ah right, as it wasn't in a module in the old groovy repo, it's still there through the codehaus->github migration!Should we fork it under the groovy github repo? I guess that's the way to go?On Tue, Jul 21, 2015 at 11:52 PM, Keegan Witt <firstname.lastname@example.org> wrote:
https://github.com/codehaus/groovy-native-launcher unless I'm misinformed.
-KeeganOn Jul 21, 2015 5:47 PM, "Guillaume Laforge" <email@example.com> wrote:Where is the native launcher repo?I'm happy to help as long as someone helps maintain it :-)On Tue, Jul 21, 2015 at 11:28 PM, Keegan Witt <firstname.lastname@example.org> wrote:Also, how are we going to handle the Native Launcher repo? Do we want to transfer from codehaus to groovy? Or have groovy fork the codehaus repo?-KeeganOn Tue, Jul 21, 2015 at 5:23 PM, Keegan Witt <email@example.com> wrote:Cool. I transferred my repo to the groovy org. Should we create a new team under the groovy org for this?-KeeganOn Tue, Jul 21, 2015 at 4:58 PM, Guillaume Laforge <firstname.lastname@example.org> wrote:The empty groovy-windows-installer is now gone, Keegan.--On Tue, Jul 21, 2015 at 4:46 PM, Keegan Witt <email@example.com> wrote:Actually, if you look at the Windows installer (https://github.com/keeganwitt/groovy-windows-installer), you'll see it's including binaries from the native installer. I believe this was done for Windows file-association purposes.Speaking of which, if you remove the empty repo currently under the org (https://github.com/groovy/groovy-windows-installer), I'll transfer ownership of aforementioned repo to replace it.-KeeganOn Mon, Jul 20, 2015 at 12:09 PM, Russel Winder <firstname.lastname@example.org> wrote:On Sat, 2015-07-18 at 10:36 +0200, Guillaume Laforge wrote:
> With GroovyServ (https://kobo.github.io/groovyserv/) I don't think we
> a native launcher, do we?
I have never used either, but then I am not actually using Groovy.
I'll hang on to the repository for a while in case we want to do
something with it later.
Dr Russel Winder t: +44 20 7585 2200 voip: sip:email@example.com
41 Buckmaster Road m: +44 7770 465 077 xmpp: firstname.lastname@example.org
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder