Does infra need to be told what to do with the notifications from Github like
Issues and PR's?
Should they come here with a prefix like [GEB-I] and [GEB-PR]?
Best regards,
Carl
On 1/19/26 4:51 AM, Paul King wrote:
Issue created:
https://issues.apache.org/jira/browse/INFRA-27578
On Mon, Jan 19, 2026 at 5:50 PM Paul King<[email protected]> wrote:
I was busy again, so apologies for the slightly longer than normal vote window.
This vote has passed with THREE +1 PMC votes, TWO additional +1 votes,
and no other votes.
I'll chat with admin about closing and/or archiving that list.
Cheers, Paul.
On Fri, Dec 19, 2025 at 8:42 PM Paul King<[email protected]> wrote:
Hi folks,
I promised a VOTE thread but got busy. Here is the VOTE thread as
promised to the following DISCUSS thread:
https://lists.apache.org/thread/27gz3m7xdpslo54q0tf6gdvdm2n3z198
Details:
When we created the Geb subproject, I went ahead and created what I
thought were the normal mailing lists including geb-users and geb-dev.
I have since refreshed my memory on what is recommended for
subprojects and having a separate geb-dev list is not recommended
within the ASF. Formal votes need to happen anyway on the Groovy dev
(or in rare cases private) list, and in the past some projects with
such lists suffered from fragmentation. The geb-dev traffic has been
super low, so I was going to ask infra to delete or archive it
(whatever they would normally do in such cases). I suggest we keep the
geb-users list for now.
The folks most involved in Geb have already suggested that geb-dev
isn't really needed. Instead of using the geb-dev list, we'd just use
the dev list and use a prefix such as [Geb] if the context isn't super
obvious.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 PMC votes are cast.
[ ] +1 Remove the list
[ ] 0 I don't have a strong opinion about this, but I assume it's ok
[ ] -1 Keep the list, because...
Here is my vote: +1
Cheers, Paul.
