<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">As someone who only reads the manual as last resort, I think Section 7 of the MacPorts Guide could be retitled from “MacPorts Project” to “Contributing to MacPorts”. And then steps for creating pull requests via GitHub spelled out tutorial-wise. Perhaps <a href="https://yangsu.github.io/pull-request-tutorial/" class="">steal an existing tutorial</a>. But there are additional workflows and tricks like `git config receive.denyCurrentBranch updateInstead’ that might be worth sharing with contributors (the last trick is useful for syncing clones across multiple machines).<div class=""><br class=""></div><div class=""><div class="">While I appreciate the intent, I think “easing into” GitHub is more obfuscating, and actually adds an extra hurdle for contributors. For instance the section immediately following “Using Git and GitHub” is titled “New Ports” and proceeds with steps for contributing a Trac ticket.</div><div class=""><br class=""></div><div class="">Okay, so when all is said and done, am I actually prepared to make an actual contribution? Perhaps it merits a topic of discussion for the online meeting how MacPorts wants to present itself. I’d like to see one of MacPorts’s goals be towards non-profit status, and ultimately to attract the attention of Apple again. Apple needs MacPorts desperately, they just don’t know it yet…</div><div class="">-AM</div><div class=""> <div class=""><br class=""><blockquote type="cite" class="">On Apr 11, 2018, at 6:33 PM, Perry E. Metzger <<a href="mailto:pmetzger@macports.org" class="">pmetzger@macports.org</a>> wrote:<br class=""><br class="">On Wed, 11 Apr 2018 18:19:50 -0400 Andrew Moore <<a href="mailto:slewsys@gmail.com" class="">slewsys@gmail.com</a>><br class="">wrote:<br class=""><blockquote type="cite" class="">My impression from the mailing list is that going forward Trac<br class="">would be used exclusively for bug reports. Any code submissions<br class="">would ideally be submitted as pull requests to GitHub.<br class=""></blockquote><br class="">That's both true and not quite true. I think ultimately we'll be<br class="">going to that but for the moment we're easing in to it. The document<br class="">currently says, in effect, "we strongly prefer GitHub pulls over Trac<br class="">for code submissions."<br class=""><br class="">I figure that ultimately it will indeed say "please<br class="">only submit code by GitHub" but I don't think we have consensus on<br class="">that yet. (If I'm wrong and we do have consensus, someone should feel<br class="">free to make that even stronger in the document.)<br class=""><br class=""><blockquote type="cite" class="">If so, this<br class="">change needs to put front and center, in large display type.<br class=""><br class="">Section 7 “MacPorts Projects” should begin: SUBMIT CODE AS GITHUB<br class="">PULL. REQUESTS. IF YOU JUST WANT TO $#!@, PLEASE USE TRAC -AM<br class=""></blockquote><br class="">Perry<br class="">-- <br class="">Perry E. Metzger<span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><a href="mailto:pmetzger@macports.org" class="">pmetzger@macports.org</a><br class=""></blockquote><br class=""></div></div></div></body></html>