On Wednesday, June 29, 2022 1:24:07 PM CDT Maxwell G via devel wrote:
> On Wednesday, June 29, 2022 1:09:07 PM CDT Vitaly Zaitsev via devel wrote:
> > Newly added EPEL maintainers can make any changes to Fedora branches. I
> > don't like that.
>
> I'm a bit confused. You say this sounds like a "pa
On 29/06/2022 21:23, zebo...@gmail.com wrote:
What do you mean it is not possible? Isn't the new "collaborator" role
exactly for this?
Yes, didn't know about it. My bad. Thanks for the info.
Collaborator: A user or a group with this level of access can do everything
what a user/group with ti
On 6/29/22 8:45 PM, Vitaly Zaitsev via devel
wrote:
On 29/06/2022 20:24, Maxwell G wrote:
> I'm a bit confused. You say this sounds like a "package hijack attempt," but
> then you also say you don't like that it only allows access to epel* branches.
It is not possible to restrict access to onl
On 29/06/2022 20:24, Maxwell G wrote:
I'm a bit confused. You say this sounds like a "package hijack attempt," but
then you also say you don't like that it only allows access to epel* branches.
It is not possible to restrict access to only selected branches. EPEL
maintainers can commit to Fedo
On Wednesday, June 29, 2022 1:09:07 PM CDT Vitaly Zaitsev via devel wrote:
> On 29/06/2022 18:47, Robbie Harwood wrote:
> > I don't see how you got there. Nowhere does it say that the
> > maintainer(s) are removed - just that one is added, and made contact for
> > EPEL bugs.
>
> Newly added EPEL
