Skip to content
This repository has been archived by the owner on May 20, 2024. It is now read-only.

Ansibullbot to promote IRC Working groups #820

Closed
gundalow opened this issue Nov 23, 2017 · 3 comments
Closed

Ansibullbot to promote IRC Working groups #820

gundalow opened this issue Nov 23, 2017 · 3 comments

Comments

@gundalow
Copy link
Collaborator

gundalow commented Nov 23, 2017

I wonder if the bot could/should promote the different IRC channels we have.

For example if labels for "azure, aws, network, vmware, windows" then say

Hi $PERSON,
Thank you for the issue/PR, just so you are aware we have dedicated Working Group for $TOPIC.
You can find other people interested in this in #ansible-$TOPIC on Freenode IRC

@gregdek
Copy link
Contributor

gregdek commented Nov 29, 2017

Oooo. Yespls.

@gundalow
Copy link
Collaborator Author

I guess given that the list of Working Groups doesn't change that often we would be OK to hard-coded this.

Perhaps BOTMETA.yml could be extended to contains a mapping of labels to Working Groups (defined as the name of the IRC channel after #ansible-)

working_groups:
# mapping from label to working group name
  - aws: aws
  - networking: network #notice difference 
 ... 

As well as IRC, I wonder if we should link to the index of the the community page, which in turn has links to to Working Groups agenda, wiki, etc.

@gundalow
Copy link
Collaborator Author

gundalow commented Jul 19, 2018

This should trigger on issues and PRs.

Input

working_groups:
# mapping from GitHub label to working group name
  - aws: aws
  - azure: azure
  - jboss: jboss
  - networking: network #notice difference 
  - vmware: vmware
  - windows: windows
 ... 

Triggers
Given that all working groups already exist as labels in ansible/ansible I think we can use the existing labels that Ansibullbot adds.

This should allow modules, module_utils, inventory scripts, etc to all be processed.

Outputs
Add a comment (only once)

Hi $PERSON,
Thank you for the issue/PR, just so you are aware we have dedicated Working Group for $TOPIC.
You can find other people interested in this in #ansible-$TOPIC on Freenode IRC
For more information about communities, meetings and agendas see https://github.com/ansible/community

Maybe skip adding this message if more than one would apply, as it's most likely a large refactor and not relevant.

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

No branches or pull requests

2 participants