<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hey Ryan,<div class=""><br class=""></div><div class="">This is AWESOME news! Been hoping to hear this for a while now, and it will definitely make my qbs port maintainership a bit easier. :D</div><div class=""><br class=""></div><div class="">Looking forward to to the move and a big welcome to the next generation of MacPorts!</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Aug 19, 2016, at 5:18 PM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">I'm pleased to announce that MacPorts will be moving its source code to<br class="">GitHub. The exact date for the move has not yet been set; this message is<br class="">just to let you know that these changes are coming soon.<br class=""><br class="">Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the<br class="">decade since Mac OS Forge was created, collaborative software development<br class="">platforms like GitHub and BitBucket have become very popular and successful,<br class="">and when I was hired as Mac OS Forge sysadmin last year, part of my job was<br class="">to evaluate whether such services could be a suitable replacement for those<br class="">offered by Mac OS Forge. We determined that the answer was yes, and that<br class="">GitHub was the best choice, due to its overwhelming popularity. Other Mac OS<br class="">Forge projects including XQuartz, CUPS and CalendarServer are already in the<br class="">process of moving to GitHub, and the time has now come for MacPorts to<br class="">likewise bid a fond farewell to Mac OS Forge and move on.<br class=""><br class="">The other MacPorts managers and I, and some other members of the community,<br class="">have discussed this change at length. Over the years, several developers<br class="">have asked why we're not on GitHub. The perception is that "everybody" is on<br class="">GitHub, and some developers don't take your project seriously if it's not on<br class="">GitHub. Part of our answer to such questions has been that it would be a<br class="">pain to move, and that what we had at Mac OS Forge was good enough. But now<br class="">that we have to leave Mac OS Forge anyway, it makes sense to convert to git<br class="">and take the opportunity to do some much needed and overdue restructuring<br class="">and splitting of our repository, and to move to GitHub to make use of their<br class="">great collaboration features such as pull requests which some of our<br class="">contributors have been wishing for. Hopefully, in addition to the other<br class="">benefits, moving to GitHub will help us attract and keep new developer<br class="">talent.<br class=""><br class="">In a January survey on this list, most developers indicated a preference for<br class="">git, or that they were happy with the Subversion client. GitHub accommodates<br class="">both. More on that in a separate mail to follow.<br class=""><br class="">We've given much thought to the way we use our Trac ticket system, and after<br class="">extensive discussion on how we might be able to use GitHub Issues, and even<br class="">performing a trial conversion of our tickets, we came to the realization<br class="">that moving to GitHub Issues would be a step back for us. (GitHub Issues<br class="">doesn't have custom fields, which we use to indicate the name of the port(s)<br class="">affected by the ticket, and the available workarounds are unsatisfactory.<br class="">And the original author of the ticket or comment cannot be preserved when<br class="">importing to GitHub Issues. In short, converting to GitHub Issues would be<br class="">lossy.) We also considered converting to Jira or BugZilla, but in the end,<br class="">we decided that staying with Trac is the best and least disruptive choice<br class="">for now. We will migrate the data from our Trac installation to a new<br class="">server, taking the opportunity to upgrade to the latest version of Trac and<br class="">make some other improvements.<br class=""><br class="">We've already completed several steps of this transition. Earlier in the<br class="">year, we announced that we started using MaxCDN in front of our primary file<br class="">server to distribute our files faster. Earlier this month, we announced the<br class="">new home for our primary file server at the Friedrich-Alexander University.<br class="">And our new buildbot automated build system announced earlier this month is<br class="">being hosted by me on my hardware, outside of Apple, and will just need<br class="">minor changes to monitor GitHub instead of Subversion.<br class=""><br class="">MacPorts domain names were already owned by the project, and have been moved<br class="">to NameCheap. DNS will move from Apple to NameCheap. @<a href="http://macports.org" class="">macports.org</a> email<br class="">forwarding will move to a new server. The <a href="http://www.macports.org" class="">www.macports.org</a> and<br class=""><a href="http://guide.macports.org" class="">guide.macports.org</a> web sites will move to a new server while retaining the<br class="">same functionality for now. Apple will continue to host our mailing lists.<br class=""><br class="">This transition should be mostly transparent to users. A separate email will<br class="">be sent to the announcement and users lists closer to the time of the move<br class="">detailing what steps users might need to take.<br class=""><br class="">On behalf of portmgr, thanks to Clemens Lang for writing the MacPorts<br class="">Subversion to git conversion rules we're going to use, and to Larry<br class="">Velázquez for registering the "macports" username on GitHub years ago in<br class="">anticipation of this day. Thanks again to our former Mac OS Forge sysadmins<br class="">Keith Dart, Henry Groen, Shreeraj Karulkar, and Bill Siegrist for keeping<br class="">everything running all these years. And our most appreciative and humble<br class="">thanks to Apple for supporting open source software by allowing its<br class="">developers to create the initial version of MacPorts and release it as open<br class="">source software, and by providing hardware and network bandwidth to host it.<br class="">We are very grateful.<br class=""><br class="">I'm sure you'll have questions. More information will follow. Thank you all<br class="">for bearing with us during this transition.<br class=""><br class="">_______________________________________________<br class="">macports-dev mailing list<br class=""><a href="mailto:macports-dev@lists.macosforge.org" class="">macports-dev@lists.macosforge.org</a><br class="">https://lists.macosforge.org/mailman/listinfo/macports-dev<br class=""></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">-- <br class="">Jake Petroules - jake.petroules at <a href="http://petroules.com" class="">petroules.com</a><br class=""></div>
</div>
<br class=""></div></body></html>