Greetings, Geb Devs!
The Geb maintainers (Adam Pounder, Sergio del Amo, and me, Jonny Carter) met today to talk about the next key moves for Geb as we integrate into Apache Groovy and return to life as an actively maintained project. Here are some key updates from the face-to-face conversations: How We Communicate First, we plan to continue to use GitHub Discussions and Issues as the primary means of communication about the project while still using this mailing list as appropriate to communicate about decisions, releases, and other announcements. GitHub Discussions and Issues will forward to this mailing list, so if you’re subscribed to both, you may want to setup some email filters. Infrastructure Updates Second, work continues to move Geb onto Apache Software Foundation infrastructure. This should help eliminate some needless expenses for hosting, DNS, and deployment while making the infrastructure more approachable for the wider Groovy community. Specifically, Sergio will be looking at migrating our website publication to a static website more in line with the ASF guidelines. Watch https://github.com/apache/groovy-geb/issues/208 and https://github.com/apache/groovy-geb/issues/207 for updates on that. Likewise, we would like to move off the CircleCI system and onto the Apache Software Foundation's Jenkins instance. Our rationale for using that rather than Groovy’s TeamCity instance is that Adam & Jonny have some background with Jenkins, which also has a nice Groovy DSL for jobs <https://www.jenkins.io/doc/pipeline/steps/job-dsl/>. There’s no hard timeline on either move beyond “sooner rather than later.” One last bit of book-keeping will be to shutdown the old mailing lists on Google Groups and direct folks currently subscribed to them here. Jonny will be tackling that soon. Documentation Looking forward, one improvement we’d all like to see would be improvements to the tutorials and examples for Geb. We’re looking to Micronaut’s Guides <https://guides.micronaut.io/latest/index.html> and the JMH Samples submodule <https://github.com/openjdk/jmh/tree/master/jmh-samples> for inspiration here. The Geb example projects for maven <https://github.com/geb/geb-example-maven>, Gradle <https://github.com/geb/geb-example-gradle>, and Cucumber <https://github.com/geb/geb-example-cucumber-jvm> will most likely get superseded by these efforts, or folded into them as appropriate. Community Engagement As a final note, Jonny submitted a couple of Geb workshops to the upcoming Selenium Conference in March <https://seleniumconf.com/>. We would like to get some folks in the wider ecosystems where Geb resides to get their hands on it, offer feedback, and perhaps discover Geb for the first time. This seems a good venue to do that. Any tips or feedback from the community in that regard is welcome! Big thanks to Adam and Sergio for their ongoing support of Geb. Also, thanks to Paul King for his assistance so far with the project’s transition into the Apache Software Foundation as a Groovy subproject. Finally, thanks to everyone on the list who cares about the project and its future. Best, Jonny Carter Geb Maintainer
