[Jenkins-infra] Request to install Slack in jenkinsci
R. Tyler Croy
tyler at monkeypox.org
Thu Sep 6 18:32:39 UTC 2018
(replies inline)
On Thu, 06 Sep 2018, Kohsuke Kawaguchi wrote:
> I suggest somebody have a quick chat with David to understand where he's
> coming from, explain the concern, and see if you all can come to the same
> understanding.
>
> The thing you should avoid, IMO, is to reject something without trying to
> understand the motivation nor providing an explanation.
Before I saw this thread, I approved the application, and another one for
Codecov for the organization.
That said, I think has been some misunderstanding about what this GitHub App
does, it provides integration between a Slack instance and a GitHub
organization (read more here: https://slack.github.com/).
To me this makes total sense for the _numerous_ organizations contributing to
plugins who may wish to discuss or reference pull requests/issues in their
Slack environments. As far as I can tell from the integration, this will allow
external companies and organizations work more effectively with the
repositories they contribute to in the Jenkins project.
This doesn't mean that the project is using Slack in any way.
IMHO, managing these apps on a per-repository grant is absurd. There are over
2k repositories in jenkinsci and assuming there are no side effects which will
bleed over to other repositories, and no unnecessary Write access being
requested, I believe we should just grant these and move on.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20180906/340d9d12/attachment.asc>
More information about the Jenkins-infra
mailing list