> The idea seems cool, but at the same time, I'm wondering if we should be > investing the money in the project instead, there > are a variety of things that could be done, e.g. start pushing more > aggressively towards code quality (PMD, findbugs and the like in the > builds), > refreshing CITE tests, or even getting more people to help on the user > list somehow. >
I am open to ideas here, and have one of my own. For CITE tests I am thinking of making it an OSGeo priority (it says interoperability in the goals but funding such would be action rather than words). I get t-shirts help morale and pride, but will this turn into more > participation? Cause that's what we actually need :-) > I would like to try this t-shirt idea in that it is something I think I can get done (even just using sprint funds) in calendar year 2018. As for recruiting more, the Geoserver developers workshop Ian and myself did was not half bad. Perhaps we could set that up as a better use of these "foss4g sprints" (use it explicitly for promoting participation rather than bug fixing). Check out the AWS OpenJDK long term support move... it's on Java 8: > https://aws.amazon.com/it/corretto/ > > So be mindful of that, Java on AWS seems like it will mean Java 8 for > quite some time. > (at least, they are not mentioning a java 11 version of it) > Actually it is on more than AWS, they have bundles for macOS and even an MSI for windows (allowing it to by managed windows shops). Wow this is a great response, and yeah Java 8 forever apparently. Can you ping me before publishing it, I'd like to help, there is a lot of > work that did not make into twitter and mails, > mostly because the european team passed the current status in an oral way > as opposed to mails. > Blog post is stuck no the previous items :P > >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
