[SciPy-Dev] Using more functionalities from GitHub?

[Ralf Gommers]

On Sun, Feb 28, 2021 at 8:48 PM Pamphile Roy <roy.pamphile at gmail.com> wrote:

>
>
> On 27.02.2021, at 17:25, Ralf Gommers <ralf.gommers at gmail.com> wrote:
>
>
> The most related GitHub feature is CODEOWNERS:
> https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners.
> It can be used to automatically request PR reviews from individuals or from
> a team.
>
> So there's at least three approaches:
> 1. Teams per submodule and other area
> 2. A bot to subscribe to labels
> 3. Using CODEOWNERS
>
> The trouble with (1) is that it's a lot of overhead managing teams in the
> GitHub UI, and only people with owner/maintainer status can do it.
>
> My preference is (3) I think: it solves both problems to some extent, it's
> the most granular (you can get notifications for individual files as well
> as blog patterns), and it's a plain file in the repo that everyone can
> propose changes to via a PR. For pinging people outside of PRs, we can use
> the same file as documentation (just look at it, find the submodule/file of
> interest, and see who is subscribed to it to @-mention them). Should we try
> that?
>
>
> Thanks for pointing out CODEOWNERS, I didn’t know about this! I agree with
> you, this looks like a good idea and would bring more value than just
> grouping members by tags.
> This would also not prevent to also have, if needed, some grouping for
> convenience, like maintainer team, review team, build team, etc.
>
> So, I vote in favor of this solution.
>

It took a while, but I followed up on using CODEOWNERS in
https://github.com/scipy/scipy/pull/13810

Cheers,
Ralf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.python.org/pipermail/scipy-dev/attachments/20210405/917c317d/attachment.html>