| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 16:48 |
|---|---|---|
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 16:49 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 16:59 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 17:00 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 17:04 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 17:23 |
| opendevreview | Ivan Anfimov proposed openstack/openstack-manuals master: Region / Availability Zone - update Glossary https://review.opendev.org/c/openstack/openstack-manuals/+/946986 | 17:37 |
| cardoe | So case in point about maintenance of projects. I’m trying to fix the links to the bug tracker for the ansible modules. Nobody really knows who is able to approve it. | 17:40 |
| fungi | cardoe: got a link to the change | 17:41 |
| fungi | ? | 17:41 |
| fungi | we can check which acl the repo uses and then look up the group name in gerrit where it will give a list of the members who have that permission | 17:42 |
| fungi | oh, was it 946161? | 17:43 |
| fungi | so the ansible-collections-openstack repo? | 17:43 |
| fungi | or are you talking about a different change? | 17:44 |
| cardoe | https://review.opendev.org/c/openstack/ansible-collections-openstack/+/946161 | 17:44 |
| fungi | cardoe: there's no acl-file override in gerrit/projects.yaml so it should use permissions from https://opendev.org/openstack/project-config/src/branch/master/gerrit/acls/openstack/ansible-collections-openstack.config#L4-L10 which means you need to reach out to people listed at https://review.opendev.org/admin/groups/ansible-collections-openstack-core,members | 17:47 |
| fungi | and also the included https://review.opendev.org/admin/groups/openstacksdk-core,members | 17:48 |
| fungi | which i guess means i have approval perms on that repo, and for a change like this i don't mind exercising them | 17:48 |
| cardoe | Okay. Just highlighting we can make this stuff easier. Cause if I was a small contributor it’s demotivating. | 18:06 |
| cardoe | I’ve got some things for Argo CD and Argo Workflows that I was fixing a bunch of reported bugs with a small change with added tests. They ignored my change. Merged their own stuff in. Created conflicts. I rebased a few times. But have given up. They told me it’s hard to have cycles to review and they need more reviewers when I posted about this in their ML. | 18:08 |
| cardoe | Just more following up on our PTG talk. And what I was trying to say fungi. Not trying to change our tools. But make it possible for people to know where to go or what to look for. | 18:11 |
| fungi | sounds entirely familiar. i feel like every open source project i participate in has this same challenge | 18:11 |
| cardoe | Absolutely. | 18:11 |
| fungi | yes, i agree it would be great if we could come up with a way to make it clearer who has approval rights over any arbitrary change | 18:11 |
| cardoe | It’s hard to figure out who to ping currently. So I think we can make that easier. | 18:11 |
| fungi | i mean, i can probably approve (without cheating by elevating my perms with admin access) changes in several hundred openstack repos. there's no way i'm reviewing all those of course | 18:12 |
| cardoe | No of course not. GitHub abstracts it with an @maintainers do I don’t see | 18:13 |
| fungi | but by the same token, if every person with a change waiting for each of those repos tried to reach out to me, i'd be even more overwhelmed than i currently am | 18:13 |
| fungi | making things easier for casual contributors while not making things harder on the maintainers than they already are is probably the biggest challenge with that | 18:14 |
| fungi | in my case i'm included in a lot of groups as a fallback to be able to approve infrastructure-related changes, but i'm not typically going to have time or expertise to review software-oriented changes in the same repos | 18:16 |
| cardoe | Yeah it’s not just like “here annoy these people” | 18:26 |
| cardoe | I don’t have answers. Just more highlighting the feeling of new contributors | 18:31 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!