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

Don't send a teahouse invite to experienced users #55

Open
enterprisey opened this Issue Mar 21, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@enterprisey
Member

enterprisey commented Mar 21, 2015

If the user whose draft is getting declined has more than X edits, the "Send Teahouse invite" checkbox shouldn't be checked by default. I propose that X be 2000, but I have no compelling reason to set it there.

Also, if the user has a user right that's seen as "advanced" (e.g. sysop, template editor(?), crat, autopatrolled (although why they would be submitting drafts is beyond me)), the checkbox also shouldn't be checked.

And, if the user's already been invited to the Teahouse, again, the checkbox shouldn't be checked.

@enterprisey enterprisey changed the title from Don't send a teahouse invite to experienced users to Don't send a teahouse invite to experienced or invited users May 11, 2015

@enterprisey

This comment has been minimized.

Show comment
Hide comment
@enterprisey

enterprisey Sep 5, 2015

Member

Hey, they might find the teahouse useful anyway. Unless we're getting complaints from annoyed experienced users (who would probably just go through mainspace anyway), I think this can safely be closed.

And, I fixed the third point (the already invited one) anyway.

Member

enterprisey commented Sep 5, 2015

Hey, they might find the teahouse useful anyway. Unless we're getting complaints from annoyed experienced users (who would probably just go through mainspace anyway), I think this can safely be closed.

And, I fixed the third point (the already invited one) anyway.

@enterprisey enterprisey closed this Sep 5, 2015

@Technical-13

This comment has been minimized.

Show comment
Hide comment
@Technical-13

Technical-13 Sep 5, 2015

The best way to handle this is to have the script respect a {{nobots}} situation to allow experienced users to opt-out of invites.

Technical-13 commented Sep 5, 2015

The best way to handle this is to have the script respect a {{nobots}} situation to allow experienced users to opt-out of invites.

@Technical-13 Technical-13 reopened this Sep 5, 2015

@enterprisey enterprisey changed the title from Don't send a teahouse invite to experienced or invited users to Don't send a teahouse invite to experienced users Sep 5, 2015

@enterprisey

This comment has been minimized.

Show comment
Hide comment
@enterprisey

enterprisey Sep 5, 2015

Member

I'm not sure that the {{bots}} template would work here, as there are essentially two "levels" of messages the script sends: important ones, like {{Afc decline}}, and less-important ones, like the teahouse invite. {{bots}} blocks both or neither, but it can't be (ab)used to allow only the important messages.

Member

enterprisey commented Sep 5, 2015

I'm not sure that the {{bots}} template would work here, as there are essentially two "levels" of messages the script sends: important ones, like {{Afc decline}}, and less-important ones, like the teahouse invite. {{bots}} blocks both or neither, but it can't be (ab)used to allow only the important messages.

@Technical-13

This comment has been minimized.

Show comment
Hide comment
@Technical-13

Technical-13 Sep 5, 2015

  • {{Nobots}} blocks both unless there is an |allow=
  • {{Bots|deny=}} blocks whichever is denied
    • AFCteahouse for teahouse invite
    • AFCstatus for accept/decline messages

Not sure if those are the best names, so totally open for discussion.

Technical-13 commented Sep 5, 2015

  • {{Nobots}} blocks both unless there is an |allow=
  • {{Bots|deny=}} blocks whichever is denied
    • AFCteahouse for teahouse invite
    • AFCstatus for accept/decline messages

Not sure if those are the best names, so totally open for discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment