Hi folks, The Geb project[1][2] has been a pre-eminent web testing/browser automation solution in the Groovy ecosystem for some time. Recently it has become mostly a one-person project with the main maintainer now being drawn in other directions. It has been proposed to bring Geb to the ASF and with the CRA regulatory environment approaching, this seems to make a lot of sense.
There are three paths by which this could happen: (1) Geb could become a sub-module for Groovy. But since Geb is already a focused self-contained project, I don't think it would be a good fit. (2) Geb could become its own top-level project and enter via the Incubator (or with the Groovy project sponsoring). (3) Geb can be a sub-project of Groovy with its own repos and mailing lists. This is what I am proposing. There are a number of folks who have expressed interest in building a community around Geb. Assuming we can grow that community, there is nothing stopping Geb becoming a top-level project later. If it's only a handful of folks who end up contributing, it would make sense for Geb to remain a sub-project of Groovy. Assuming folks are happy with path (3), the next step would be us voting on accepting the donation. I'll do a separate VOTE thread assuming successful discussion. The subsequent step is for an IP clearance through the ASF Incubator Project. With that in mind I have created the template for that[3]. Filling out the template also makes it easier for us to understand the donation. So, let me know if you agree with (3) as the correct path and please read [3] which explains what the donation is. Note: there are some other repos of examples under GitHub/geb. I see no problem with us moving those too at a later date, so I wasn't going to focus on those in this discussion. Cheers, Paul. [1] https://gebish.org/ [2] https://github.com/geb/geb [3] https://incubator.apache.org/ip-clearance/groovy-geb.html
