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

For first-time issue filers, bot notifies about WHATWG workmode and process #114

Closed
travisleithead opened this issue Sep 27, 2018 · 4 comments

Comments

@travisleithead
Copy link
Member

Hi WHATWG!

(was considering titling this: "Proposal: replace @annevk with a bot" :-)

Noted in several issues that 1st-time issue filers tend to get a courtesy note about the WHATWG working mode and policies. E.g.:

I think these notices are good. These courtesy notices help ensure newbies are aware of the process. Also noticed that the message has to be carefully crafted so as to not be percieved as a knock against the idea/issue. Hence having a bot deliever the message is probably good for PR.

(and yes, this is my first time filing an issue in this repo...)

@annevk
Copy link
Member

annevk commented Sep 28, 2018

I thought about this while doing it a few times and I might have even discussed it, but I think I like the personal touch. It only takes a couple seconds and a human has to read the issue anyway.

@domenic
Copy link
Member

domenic commented Sep 30, 2018

We could also try to make the CONTRIBUTING.md links contain some more of this information, since GitHub automatically links to those. E.g. https://github.com/whatwg/html/blob/master/CONTRIBUTING.md is rather focused on the mechanics of pull request contributions, and not on "how should I approach this community when filing issues".

@jfbrennan
Copy link

I created whatwg/html#3627 (the little autoselect proposal) and I liked having someone reach out like @annevk did.

The comment did give me the impression that I got something wrong, but later understood it was just a courtesy/reminder. Maybe something like, "Thank you, and in an effort to ensure all requests meet expectations we ask all new filers to read the following guidelines..." would make it clear that the person isn't replying because something is wrong.

@annevk
Copy link
Member

annevk commented Sep 26, 2019

We haven't hit scaling issues yet, but I'll dupe this to #107 which now has PR #145 for what @domenic proposes above.

@annevk annevk closed this as completed Sep 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants