Rename Slack channel from #forum-jötnar to #forum-ymir-package-automation - #419
Conversation
…tion Assisted-by: Claude Opus 4.6
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the Slack channel name from #forum-jötnar-package-automation to #forum-ymir-package-automation across the documentation and agent constants. The review feedback suggests expanding the list of legacy 'jotnar' references in the README for better clarity and applying consistent backtick formatting to the Slack channel name across all files.
| This repository is an AI-powered RHEL package maintenance automation system (codename "Ymir", formerly "Jötnar") that triages Jira issues, creates merge requests for package rebases and backports, and can handle quality processes. | ||
|
|
||
| > **Note on naming:** The project used the codename "Jötnar" during the pilot phase. "Ymir" is the name of our working group, and we adopted it as the project name to avoid confusion with other working groups. Some internal references still use "jotnar" (e.g. service accounts, bot usernames, Kerberos principals, container registry namespace, Slack channel) as those have not been migrated yet. | ||
| > **Note on naming:** The project used the codename "Jötnar" during the pilot phase. "Ymir" is the name of our working group, and we adopted it as the project name to avoid confusion with other working groups. Some internal references still use "jotnar" (e.g. service accounts, bot usernames, Kerberos principals, container registry namespace) as those have not been migrated yet. |
There was a problem hiding this comment.
Since the email address and Jira component still use the jotnar name (as seen in lines 88 and 90), it would be helpful to include them in the list of examples in this note to provide full clarity to users regarding the remaining legacy references.
| > **Note on naming:** The project used the codename "Jötnar" during the pilot phase. "Ymir" is the name of our working group, and we adopted it as the project name to avoid confusion with other working groups. Some internal references still use "jotnar" (e.g. service accounts, bot usernames, Kerberos principals, container registry namespace) as those have not been migrated yet. | |
| > **Note on naming:** The project used the codename "Jötnar" during the pilot phase. "Ymir" is the name of our working group, and we adopted it as the project name to avoid confusion with other working groups. Some internal references still use "jotnar" (e.g. service accounts, bot usernames, Kerberos principals, container registry namespace, email addresses, Jira components) as those have not been migrated yet. |
|
|
||
| - **Email**: jotnar@redhat.com | ||
| - **Slack**: #forum-jötnar-package-automation | ||
| - **Slack**: #forum-ymir-package-automation |
There was a problem hiding this comment.
For consistency with the formatting used in monitoring.md, consider wrapping the Slack channel name in backticks.
| - **Slack**: #forum-ymir-package-automation | |
| - **Slack**: `#forum-ymir-package-automation` |
| "## 📞 Questions or Issues?\n" | ||
| "\n" | ||
| "**Contact:** jotnar@redhat.com | **Slack:** #forum-jötnar-package-automation | " | ||
| "**Contact:** jotnar@redhat.com | **Slack:** #forum-ymir-package-automation | " |
There was a problem hiding this comment.
Consider wrapping the Slack channel name in backticks for consistency with the documentation in monitoring.md and to make it easier to identify as a technical identifier in the generated MR descriptions.
| "**Contact:** jotnar@redhat.com | **Slack:** #forum-ymir-package-automation | " | |
| "**Contact:** jotnar@redhat.com | **Slack:** `#forum-ymir-package-automation` | " |
2 participants
No description provided.