[Jenkins-infra] Handling GitHub Apps Requests

[R. Tyler Croy]

Starting a separate thread here because I believe this is going to get worse
before it gets better, unfortunately. I tried out the GitHub Marketplace flow
in an organization for which I am not admin, this screenshot shows basically
what a jenkinsci contributor might see:

    https://i.imgur.com/3zK3pCQ.png


Basically there's no information to pass between the org admins and the
requestor, as far as I can tell.

What makes this even *more* annoying is that it looks like the user can request
to install the App into repositories for which they're not even administrators.

Since GitHub doesn't support any type of "direct messages" to an individual
member, I'm not sure how easily we're going to be able to convert a github
username into an email address we can communicate with.


Basically, this flow looks like a disaster for sane org management >_<

I'm a bit of a loss for how to systematically manage these types of requests.
Some apps make sense to me, and we're obviously going to have differences of
opinions there, but I'm not sure how we can make this a sane community process
here.


Any ideas which aren't "yes" or "no" to everything? :-/


Cheers
-R Tyler Croy



-------------- 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/808b8481/attachment.asc>