[Jenkins-infra] Talking points for GitHub?

Baptiste Mathus bmathus at batmat.net
Wed Nov 15 08:51:37 UTC 2017

Thanks a lot for this nice summary Tyler!

2017-11-15 1:01 GMT+01:00 R. Tyler Croy <tyler at monkeypox.org>:

> Following up on this thread since I had my meeting with GitHub today.
> I discussed all of the talking points sent to me with them and shared some
> general feedback and thoughts on how GitHub.com could improve. The one
> thing we
> identified pretty early on was that our challenges and problems are not too
> disimmilar for what "enterprises" encounter. I hope this provides a strong
> incentive to fix some things.
> GitHub also seems much more motivated than they were a couple years ago to
> accomodate and help large projects like Jenkins be successful and stay on
> GitHub. It doesn't hurt that GitLab and Phabricator are encouraging some
> notable projects to use GitHub as a read-only Git mirror. :)
> Much of the discussion centered around managing policy and access control.
> I
> don't have any commitments from GitHub on making either of these easier
> for us
> in the near future but the GitHubbers took fastidious notes, so maybe? We
> also
> discussed at some length the user experience challenges of a large
> many-repositories project which they didn't have specific suggestions on
> how
> they might address repo and/or team discoverability though they did
> understand
> the problem.
> Some reporting or "overall visibility into the org" topics were discussed,
> again with not specific suggestions for how they might solve the issues,
> but an
> empathetic understanding that there is a problem for folks like Daniel who
> are
> trying to answer certain questions about unused repos, teams, users, etc.
> Finally I stressed to them that we're here not to administer a large
> project,
> but to contribute to the large project, and everything they can do to make
> it
> easier "to keep the lights on" will directly impact our ability to submit
> code
> to Jenkins. I conveyed this with a budget analogy: if I have 1/24th of my
> time
> to contribute to Jenkins, I would rather not spend time dealing with
> administrative minutia but instead fix a bug, implement a feature, etc.
> This
> resonated strongly with them and resulted in many many notes being taken,
> so
> maybe good things will come from my kvetching :)
> In essence, I feel more confident after this discussion that GitHub
> actually
> gives a shit about our (big org) problems AND has the staffing to actually
> address those problems.
> Thanks everybody for your talking points, they were really helpful.
> Cheers
> - R. Tyler Croy
> ------------------------------------------------------
>      Code: <https://github.com/rtyler>
>   Chatter: <https://twitter.com/agentdero>
>      xmpp: rtyler at jabber.org
>   % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
> ------------------------------------------------------
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20171115/8225b2b6/attachment-0001.html>

More information about the Jenkins-infra mailing list