<!-- Use this template when you have an idea and would like others to comment on it. 1. Give your issue a good title 1. Complete all four sections below 1. Set a due date 1. Let relevant people know you're looking for their input 1. On the due date, read the comments and decide what to do next (e.g. start a 'Request a change' issue) See this blog post for the inspiration for this approach: https://candost.blog/how-to-stop-endless-discussions/ --> # Request for comments ## Need <!-- Describe the problem, what is missing or what could be better: "I am hungy!" --> I think it would be useful to have groups in Slack and GitLab to contain all ASEs. ## Approach The actual creation of the groups is trivial, but we should discuss **who** should be a member, and **how many** groups we should have. I see two obvious approaches: 1. Create a single group that contains ASEs and ASE managers. This would be simpler, but could increase noise for managers as they get notified for things they don't need to action. It could also create hesitation for non-ASE folks who want to reach all ASEs quickly, but worry about notifying a manager unnecessarily. 2. Create two separate groups, one for ASEs and one for ASE managers. This is more complicated, but has the upshot of being able to target exactly the group of people you want. An additional downside though is that users would need to remember to tag two separate groups if both need to be notified. If you have no strong thoughts, but would still like to provide your input, please react with a :one: or a :two: to indicate your support for one of the approaches above. ## Benefit The groups serve a few purposes: 1. Allow for quick notification and escalation of items that pertain to all ASEs 2. Allow for more consistent notification of all members as the team grows (instead of trying to remember everyone to notify) 3. It serves as a quick check to see who is currently an ASE (for those who might be moving swiftly on an emergency, or not know where to check for all ASEs) 4. Let's us stop using `@here` in Slack, which is annoying for folks who might be in the ASE channel but not be an ASE 5. I think this would satisfy a prerequisite for setting up reviewer roulette for ASE MRs and stuff? ## Competition / Alternatives <!-- This part is very important! Describe alternatives: "We could go McDonald's - the price is similar, but it's twice as far away." --> 1. Continue manually mentioning all ASEs for items that need input from the whole team