The i3 SIG needs to bridge their telegram group to the IRC channel - i3 SIG - #fedora-i3 - For now, nothing to ignore
Metadata Update from @jflory7: - Issue priority set to: waiting on assignee (was: awaiting triage) - Issue tagged with: type - new bot
Confirming receipt of the Telegram API token and chat ID to the TeleIRC SIG email alias.
In #fedora-commops, we mentioned using this ticket as a way to on-board new folks into the SIG. @tjzabel and I are very familiar with it at this point.
#fedora-commops
@x3mboy, do you want to try pushing this bridge into production? Or should we ping someone else if you are overloaded right now?
@jflory7 I want to take it. I will try to do it tonight.
@jflory7: How do I request the Ansible Vault passphrase?
@x3mboy: Currently the sponsors is: @jflory7 , Once he shares the Vault passphrase, you would be able to push the bridge.
@jflory7 how do we want to handle the vault passphrase? One method could be new contributors send the bridge credentials via email, and filling out the roles/jwflory.teleirc/vars/main.yml in a PR. Then, one of the SIG maintainers pushes the vault credentials to that PR afterwards.
roles/jwflory.teleirc/vars/main.yml
Given that the vault houses all of the credentials for all of the bridges, it may not be a good idea to hand that info out to new contributors.
Thoughts?
We forgot to close this ticket as complete. Closing! :clapper:
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.