Dne 28.4.2017 v 10:44 Dominic Cleal napsal(a):
> On 27/04/17 12:10, Vít Ondruch wrote:
>>
>> Dne 26.4.2017 v 16:38 Vít Ondruch napsal(a):
>>> Dne 26.4.2017 v 14:06 Dominic Cleal napsal(a):
>>>> Would setting ownership or admin automatically provide commit access to
>>>> members of ruby-packagers-sig?
>>>>
>>> I assume that once the group is added as an admin of the package, then
>>> every member of the group can adjust his/her rights. If the group has
>>> commit bit, then every member of the group can commit. If I am right,
>>> then it really depends what is the best practice here. Because this
>>> means to answer questions such as: "how much credit we want to give
each
>>> contributor", because somebody might be proud to be listed explicitly
as
>>> a maintainer and somebody else probably does not care.
>> So if I get this [1] right (and actually I discussed this with Pingou on
>> IRC), then the ideal setup should be:
>>
>> 1) Group cannot be administrator, so there have to be at least one
>> explicit "human" administrator (this is to prevent individual from the
>> group to take control over the package).
>> 2) Group should have commit bit, this allows everybody from the group to
>> do changes to package in dist-git.
> I wasn't able to set this on rubygem-Ascii85 in PkgDB, it showed an error:
>
> User "ruby-packagers-sig" is not in the packager group
>> 3) Group should have "watchbugzilla" to allow group to be notified
about
>> BZ associated with the package.
> And when trying to set just watch*, PkgDB showed another error:
>
> User "ruby-packagers-sig" could not be found in FAS
>
> Have you been able to update ACLs to the group on any packages? I was
> using the PkgDB page at
>
https://admin.fedoraproject.org/pkgdb/acl/rpms/rubygem-Ascii85/give/ to
> try and grant access.
>
Have you followed this [1]?
~~~
For groups, the packager name will then have the format
group::<fas_group_name>. If you do not respect this format, pkgdb2 will
refuse to add the group as co-maintainer.
~~~
Ah, thanks - I missed that step. All working now.
--
Dominic Cleal
dominic(a)cleal.org