<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 8, 2016 at 7:48 PM, Marcel Bischoff <span dir="ltr"><<a href="mailto:marcel@herrbischoff.com" target="_blank">marcel@herrbischoff.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1ud" class="a3s aXjCH m157a6b6b0c10870a">I understand that. Many long-running projects are using their own Git<br>
infrastructure with Trac, Redmine and others. What I don't understand is<br>
why moving to GitHub at all when the tooling is clearly insufficient for<br>
the project. The added exposure? The hope to attract new developers? If<br>
the needs of the "people who actually do the work" are paramount, GitHub<br>
is probably not adding much to improve ingrained workflows but rather<br>
slow them down.</div></blockquote></div><div class="gmail_extra"><br></div>I prefer to let someone more official address this, but suffice it to say it wasn't entirely the MacPorts folks' idea.<br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>