jonnybot0 commented on code in PR #203: URL: https://github.com/apache/groovy-geb/pull/203#discussion_r1842861669
########## README.md: ########## @@ -12,5 +12,9 @@ Please see [CONTRIBUTING.md](https://github.com/geb/geb/blob/master/CONTRIBUTING ## Submitting issues -If you'd like to submit an issue against Geb then please use [the issue tracker for geb/issues GitHub project](https://github.com/geb/issues/issues). -Please avoid submitting usage questions as issues and use [the user mailing list](https://groups.google.com/forum/#!forum/geb-user) instead. \ No newline at end of file +If you'd like to submit an issue against Geb then please use the [Geb GitHub issue tracker](https://github.com/apache/groovy-geb/issues). Review Comment: This section does need changed, but I think we need to build some consensus. @Poundex and @sdelamo have both expressed a preference for using GitHub discussions. I know that the mailing list is mandatory for Apache projects, but can we point folks to https://github.com/apache/groovy-geb/discussions first, out of deference to the contributors? I think a better wording would be: ``` If you'd like to submit an issue against Geb then please use the [GitHub Discussions](https://github.com/apache/groovy-geb/discussions) first. Those are better suited to the back-and-forth required to clarify an issue into something actionable. + Please avoid submitting usage questions as issues and instead join and ask your question on the `[email protected]` mailing list: + [Browse](https://lists.apache.org/[email protected]) + [Subscribe]([email protected]) + [Unsubscribe]([email protected]) ``` In short, if your question is, "How do I...", mailing list. If your problem is, "This doesn't work..." go to the discussions and we'll work with you to write an issue. Would that work? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
