Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update documentation #203

Merged
merged 1 commit into from
Nov 14, 2024
Merged

update documentation #203

merged 1 commit into from
Nov 14, 2024

Conversation

paulk-asert
Copy link
Contributor

No description provided.

@paulk-asert paulk-asert merged commit 0613f58 into apache:master Nov 14, 2024
1 check passed
@paulk-asert paulk-asert deleted the prelim branch November 14, 2024 00:29
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).
Copy link
Contributor

@jonnybot0 jonnybot0 Nov 14, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

I realize this is already merged, so I'll open a PR to that effect.

Strike that, just realized Adam beat me to it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants