[Jenkins-infra] Should we use setting app on github?

[R. Tyler Croy]

(replies inline)

On Wed, 23 Oct 2019, Olblak wrote:

> Hi Everybody,
> 
> Halkeye recently transferred[1] jenkins-wiki-exporter to the jenkins-infra
> organization on  GitHub and also requested at the same time to use the setting 
> [2]app which in short allow to configure a github repository from a .github/
> settings.yml
> For now I temporarily approved the request for that repository only, as I think
> it can bring visibility.
> 
> On the other side, it also means that everybody who has write permission to
> that repository can change the settings, so the admin permission becomes
> useless.
> Secondly since I don't expect those configuration to change really often,
> considering that everything is public by default, I am not sure to see the
> added value, excepted allowing everybody to audit the change through the git
> history.
> Finally  to me most important repository information for contributors is
> provided by the CODEOWNER with more granularity basically who's responsible for
> a specific part of a repository.
> 
> So I am gathering your feedback here, should we consider this app non relevant
> for the jenkins-infra organisation or should we generalize it?  
> 
> Ps: Halkeye also configure specific labels in his repository which I think
> should be configured as default labels at the organization level so for every
> repositories as defined [3]here


I think it's fine on a per-repository basis, not everything is at the same
trust-level in this organization for better or worse.



--
GitHub:  https://github.com/rtyler

GPG Key ID: 0F2298A980EE31ACCA0A7825E5C92681BEF6CEA2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 839 bytes
Desc: OpenPGP digital signature
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20191023/5b9c0928/attachment.asc>