The email is copr-team@redhat.com.

I went ahead, and created coprteam with believe that I will be able to
request "bot=True" attribute change. Is that possible? (TASK1)

I was not able to create copr-team user, - is not allowed in names by FAS ui :-(.

I registered that list to bugzilla as Copr Team. So some progress..

What I need though is to create something like @copr-team group in
src.fedoraproject.org (I could create that in pagure.io, but not in src.f.o). (TASK2)

Ah, you mentioned an user but in fact you're looking for a group, is that correct?

I initially wanted user in FAS, but I created the user manually in the end.

Then I realized that I need group probably, from "maintenance" POV
(we can assign group of people to every package, which effectively
gives them write access).

Ah, you mentioned an user but in fact you're looking for a group, is that correct?

Shortly, I probably wanted to say YES here :-)

Can the group be crated?

I have:
- Created the copr-sig group in FAS (type: pkgdb, pre-requisite: packager)
- Set the mailing list address of the group to be copr-team@redhat.com which I assume is qualified to receive private bugs (security sensitive), so no need for a new mailing list here.
- Created the group on src.fp.o

Before you start using it on src.fp.o you will have to
- Create a bugzilla account for this email (if there isn't already one)
- Add user to the group in FAS (if you want :))

Then you can give people access to package by granting access to the group in the package's settings page and make the group by the default point of contact using the @copr-sig in the bugzilla overrides.

Final note: new members added in FAS will have to log out and back in on src.fp.o for their membership to be updated.

Let us know if we can do anything else.

One remaining thing, let me know if you want separate ticket.

We'd like to subscribe the copr-team@redhat.com mailing list as CC to several
Fedora components. But we can not do that via @copr-sig, or can we?

So - since the user in FAS doesn't have signed Fedora agreemend, we can not
in src.f.o "watch" any package using that account. I suppose that marking
that account as 'bot=True' could help. Or any other idea?

We'd like to subscribe the copr-team@redhat.com mailing list as CC to several Fedora components. But we can not do that via @copr-sig, or can we?

You can, IIRC giving commit rights to @copr-sig will add the group to the watchlist synced to bugzilla.

Wwhen looking at the watchers of a projects: https://src.fedoraproject.org/api/0/rpms/copr-backend/watchers those watching "issues" are synced to bugzilla.

ah, nice, thanks for the api link!

Sorry, reopening once again. We still want to be able to add "watch" on packages which
we do not have commit access to.

Sorry, reopening once again. We still want to be able to add "watch" on packages which
we do not have commit access to.

This is not currently possible :(

So should I request new feature against pagure?

I could way-around this, and log into src.f.o as @coprteam,
and start watching what we need to watch. But now I see:

You must sign the FPCA (Fedora Project Contributor Agreement) to use pagure

Though... I'm not sure it is correct to sign FPCA for that user. Can this be granted?
Would setting bot=True for that user help?

So should I request new feature against pagure?

You could :)

I could way-around this, and log into src.f.o as @coprteam,
and start watching what we need to watch. But now I see:

You must sign the FPCA (Fedora Project Contributor Agreement) to use pagure

Though... I'm not sure it is correct to sign FPCA for that user. Can this be granted?

I have signed it for the few "bot" accounts I created

Would setting bot=True for that user help?

I'll let @kevin answer this one, but my understanding is that the bot status
doesn't bring much (I may very well be wrong though)

Is there still something needed to be done on that ticket ? Or are we good to close it ?

Yea, we'd still like to subscribe our "bot" user to packages we don't directly
maintain.

@praiskup can you file a RFE for pagure on this?. I guess group members would see (in addition to their own account) the group account in the 'watch' pull down (so they could add the group to watch).

https://pagure.io/pagure/issue/4811

Is it OK to sign the FPCA for now?

Yes, thats fine, and sorry, missed the other question... the 'bot' status doesn't get you much. The only thing we have used it for in the past was to except those users from mandatory password changes, but if we ever do another I would want them to change too, so I don't think we would use it for that again either.

Any further questions or issues outstanding (aside from the pagure one?) or can we close this now?

Thanks for the answer!