We keep hitting the CLA+1 limits all the time

Out of curiosity, where are you hitting this? For the email alias?

Hi @pingou =)

Just about everywhere... :<

• Email alias I believe requires CLA+1
• Wiki editing is a big one...
• Discussing getting funded with Ambassadors for non-ambassador, a council member says "they don't even have a member group, not gonna fund them, they're not a contributor!!" - so it seems that in the public eyes FAS membership has bigger impact than actual contribution...

etc...

To avoid having to rename the group, we can keep it dotnet-sig with packager requirements, and the new relaxed group could be dotnet-team (or just dotnet-members or dotnet-sig-members or just about anything that makes sense haha)

Well, we don't have any way to rename groups easily. We could make a dotnet-packager-sig and then add all the people in the current dotnet-sig and remove the packager requirement on it. That seems easiest to me.

So I have done that. You will need to:

• create a new bugzilla account for dotnet-packager-sig (you can see the email bugzilla sends in the moderation queue for the list)

• add all the folks from dotnet-sig to dotnet-packager-sig

Let me know if you run into any problems with it.

:jack_o_lantern:

That sounds like an awful lot of trouble I don't have time for right now... it could have been just a new empty group that would not be packagers with any random name prefixed with dotnet- really...

ok, I didn't think it was that much trouble, but different perspectives I guess. :(

I switched dotnet-sig back to the pkgdb group and made a new dotnet-team group.

Let us know if that doesn't work or you can think of anything else we can do for you...

Uh I didn't mean it like that, It doesn't make much difference. I'm sorry for the confusion, I just meant that you didn't have to do so much work if it was easier to just create a new one with some other name. It's all much appreciated!

I'll get around to it tomorrow.

Okay it's all set, you can safely get rid of the dotnet-packager-sig :D

Hi @rhea

The script syncing default assignee and CC list from dist-git to bugzilla is reporting the following error:

  - Failed to update: `Fedora/dotnet-build-reference-packages`:
   <Fault 504: 'The name dotnet-packagers@lists.fedoraproject.org is not a valid username. Either you misspelled it, or the person has not registered for a Red Hat Bugzilla account.'>
   ({'initialcclist': ['omajid@...', 'rjanekov@...', 'dotnet-packagers@lists.fedoraproject.org '], 'product': 'Fedora', 'component': 'dotnet-build-reference-packages', 'initialowner': 'rjanekov@redhat.com'}, 504, 'The name dotnet-packagers@lists.fedoraproject.org is not a valid username. Either you misspelled it, or the person has not registered for a Red Hat Bugzilla account.')
  - Failed to update: `Fedora/dotnet3.1`:
   <Fault 504: 'The name dotnet-packagers@lists.fedoraproject.org is not a valid username. Either you misspelled it, or the person has not registered for a Red Hat Bugzilla account.'>

Could you create a bugzilla account for the email dotnet-packagers@lists.fedoraproject.org ?

Thanks!

Pretty sure this account exists already, created a few years ago. I am able to log-in with it.

@rhea the script keeps failing on that one account not existing. Could you double-check? Maybe there is a typo or so?

It sure is there, and the email from the error copy-pastes into exact match as well.

Hm, I've tried to reproduce the issue manually but I can't:

from bugzilla import Bugzilla

server = Bugzilla(
    url="https://bugzilla.redhat.com",
    user="pingou@pingoured.fr",
    password="***",
    cookiefile=None,
    tokenfile=None
)

user = server.getuser("dotnet-packagers@lists.fedoraproject.org")

So the problem is on my side, thanks for double-checking!

If it's a problem using a group email we can think about another solution

Turns out there is a trailing space in the address for the list in FAS. I've fixed the sync script to strip trailing spaces and checked with one of the two packages that it works.

The updated version of the script has been deployed in openshift. I'm going to leave this ticket open as a reminder to double-check after the next cron run that it worked properly and after that I think we'll finally have a clean sync between distgit and bugzilla :)

Indeed there is a whitespace even when I go to the FAS options for the group. I'll fix it there after we verify that the trim also works.

I've just checked the logs and the sync happened fine, so we're all good now :)

Thanks for your help @rhea!

Perhaps it would be worth having a trim on the FAS website input fields as well :)