action #122053
closed
coordination #121486: [epic] Improve of internal process in Yam squad
Update Yam Mailing List in source code, openQA job groups and other occurences
Added by JERiveraMoya over 1 year ago.
Updated over 1 year ago.
Description
Motivation¶
With the new squad name came some additional task like updting Yam Mailing List
Replace header in all the files in os-autoinst-distri-opensuse:
# Maintainer: QA SLE YaST team <qa-sle-yast@suse.de>
by the following:
# Maintainer: QE YaST and Migration (QE Yam) <qe-yam suse de>
Notice the ML is not not written as qe-ya@suse.de in the header of the files, according to admin filters needs more fine tuning and unfortunately we receive too many spam. One option could be to block external requests (Yam squad didn't receive any external mail for a lot of time, so it is a good option to consider). But for now writing the ML like that we can actually avoid most of the spam and any human could fill the gaps.
Acceptance criteria¶
AC1: Update header for all the files belonging to QE Yam as described above
AC2: Update description of job groups owned by Yam squad
Additional information¶
Search for other places, like in Confluence for example.
- Subject changed from Replace in all files to Update Mailing List in source code and openQA job groups
- Description updated (diff)
- Description updated (diff)
- Description updated (diff)
- Subject changed from Update Mailing List in source code and openQA job groups to Update Yam Mailing List in source code, openQA job groups and other occurences
- Description updated (diff)
- Status changed from Workable to In Progress
- Assignee set to zoecao
If updating it to qe-yam suse de, there would be a ci error in PR like: Missing '# Maintainer: ' in tests/yast2_gui/yast2_users.pm
So I'm going to update the mailing list to qe-yam@suse.de
Updated the mailing list in openQA job groups owned by Yam squad and Confluence pages.
zoecao wrote:
If updating it to qe-yam suse de, there would be a ci error in PR like: Missing '# Maintainer: ' in tests/yast2_gui/yast2_users.pm
So I'm going to update the mailing list to qe-yam@suse.de
Then let's do this in the CI:
'# Maintainer: .+(@| at ).+'
that would allow us to write it like:
# Maintainer: QE YaST and Migration (QE Yam) <qe-yam at suse de>
with the hope we don't receive so much junk in the future :)
And write a comment above that line in 'check_metadata' file and in your commit with something like:
'Due to internal spam filters are not so well tuned at the moment, instead of configuring Mailing list only for internal use we can allow ' at ' to specify the email'.
we missed in the refinement to update source code headers for migration files, will you make it part of this ticket? otherwise, please create new one under the same epic for this action.
JERiveraMoya wrote:
we missed in the refinement to update source code headers for migration files, will you make it part of this ticket? otherwise, please create new one under the same epic for this action.
Yes, I'll update the source code headers for migration files in this ticket.
- Status changed from In Progress to Resolved
Also available in: Atom
PDF