Let's do this the same way as Views' issue queue guidelines with a brief message in the hard coded setting and a link to the handbook.

Here's what I propose for the hard coded text:

Before submitting an issue, you are responsible for reading and understanding the Rules issue queue guidelines. It will help you effectively participate with other Rules users and quickly work toward a resolution.

Comments

mitchell’s picture

mitchell commented

One major change is that I didn't keep the recommendation to users to post support requests / usage questions in the discussion group. See #1498854: [Meta] Refocus discussion group to announcements and development

mitchell’s picture

mitchell commented
Component: Miscellaneous » Project Maintenence

Updated component.

mitchell’s picture

mitchell commented
Component: Project Maintenence » Project Maintenance

Updated component.

mitchell’s picture

mitchell commented
Component: Project Maintenance » Forms Support
Status: Needs review » Fixed

Thanks for updating it klausi.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Fixed » Needs work

Use "" wrappers to make development code, exports, and error messages more readable.

I think that doesn't read correctly, I guess some tags are missing here?

fago’s picture

fago
Primary language German
Location Vienna
commented
Assigned: fago » Unassigned
mitchell’s picture

mitchell commented
Component: Forms Support » Project Maintenance
Status: Needs work » Fixed

> Use "" wrappers to make development code, exports, and error messages more readable.
Got it.

I'm sure it can still use some work, but we can deal with that as new issues come up.

Next, I'd like to prepare some #1115636: Issue Macros and Templates for maintainers.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

(not verified) commented
Issue summary: View changes

a