Skip to content
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

Use aliases as a way to merge groups #79

Open
jwflory opened this issue Jan 31, 2016 · 0 comments
Open

Use aliases as a way to merge groups #79

jwflory opened this issue Jan 31, 2016 · 0 comments
Labels
A: needs review Pending a peer review before merging or closing D: research Research and more data is needed to make a decision help wanted Anyone is welcome to help us with this! T: new change Adds new capabilities or functionality

Comments

@jwflory
Copy link
Member

jwflory commented Jan 31, 2016

Many different sub-projects and groups in Fedora are inconsistent with the meeting names they use when starting meetings with zodbot. Sometimes this is unintentional, sometimes it is just not being aware that consistent meeting names are important.

Until recently, my understanding was that aliases were a solution to this by "merging" different group names together under a singular, common group name. However, it does not seem to work this way.

Solution

Proposed solution is to have groups defined in the category_mappings.json file or similar. Groups could then have multiple aliases for what their meeting names could be, and then all meetings with those meeting names are lumped together via aliases.

Use Case

  • Group that is meeting: Fedora LATAM Ambassadors
  • Group name in møte: latam_ambassadors
  • Potentially used meeting names:
    • fedora_latam_ambassadors
    • latam_ambassadors
    • latam
    • fedora_latam
    • fedora_latam_ambassadors_meeting

And so on. If any of these meeting names were used, via aliases, they would all be sorted together under the meetings for "Fedora LATAM Ambassadors".

@cydrobolt cydrobolt added T: improvement Improves on something that already exists blocked Progress blocked by another task or issue labels Feb 1, 2016
@jwflory jwflory added A: needs review Pending a peer review before merging or closing D: research Research and more data is needed to make a decision help wanted Anyone is welcome to help us with this! T: new change Adds new capabilities or functionality and removed T: improvement Improves on something that already exists blocked Progress blocked by another task or issue labels Oct 9, 2020
@jwflory jwflory changed the title Use alises as a way to merge groups Use aliases as a way to merge groups Oct 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: needs review Pending a peer review before merging or closing D: research Research and more data is needed to make a decision help wanted Anyone is welcome to help us with this! T: new change Adds new capabilities or functionality
Projects
No open projects
Development

No branches or pull requests

2 participants