Re: Goodbye Mac OS Forge, hello GitHub
Hi Craig, On Fri, Sep 16, 2016 at 11:01:25AM -0400, Craig Treleaven wrote: > Where does the migration stand now? Buildbots and mirror infrastructure is moved, the GitHub org is mostly configured as far as I can see. We have a new Trac instance with GitHub integration set up, but do not have the ticket database to test whether we need to do any migration on the data. Rainer and I are waiting for Ryan to give us a dump for testing. We have a copy of Guide & Website running, but we do not have automatic updates for those yet. We want to use a buildbot job to do this so failures are easier to debug and more visible. The buildslave that is supposed to run this job isn't available yet. We need a converted Git repository set up to automatically import new SVN commits so that our infrastructure that relies on input from repositories (e.g. the buildbots) can be switched to Git. I think the conversion rules should be good to go, but IIRC Ryan wanted to do some commit message rewriting for ticket references. I'm not sure what the state on this is. -- Clemens Lang ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
> On Aug 20, 2016, at 2:07 AM, Lawrence Velázquez wrote: > >> On Aug 19, 2016, at 8:18 PM, Ryan Schmidt wrote: >> >> And our new buildbot automated build system announced earlier this month is >> being hosted by me on my hardware, outside of Apple, and will just need >> minor changes to monitor GitHub instead of Subversion. > > FYI I've made some progress on this tonight and hope to make initial commits > tomorrow or Sunday. Where does the migration stand now? Craig ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
On Sat, Aug 20, 2016 at 4:11 AM, Joshua Root wrote: > > I share these concerns and brought them up during the discussions. And TBH > I think Mercurial is a better tool. But we did come to a consensus that > GitHub is overall the best choice at this time. > As I see it, mercurial doesn't have feature parity with git. E.g. I consider the index to be an indispensable feature. Combine that with smartgit and you've got a system that lets you check in lean, to-the-point changes. It's an indispensable part of my workflow. First-class stashes (not a bolt on) are another life-saver. I had an opportunity to port repositories at work from subversion to either mercurial or git. After a short evaluation, git became a no-brainer. Yes, if all you're using in a workflow are mercurial features, then git seems like an unnecessary complication, although it does have feature parity with mercurial AFAIK. Once you start using all that git has to offer, there's no going back - at least not for me. These days for repositories that aren't monstrous (i.e. gigabytes worth of content), I use git to access subversion repos as well. > And as Mark mentioned, one of the advantages of a DVCS is that the full > repository history isn't locked away on a single server, so if GitHub goes > down or turns evil, we can easily pack up and go elsewhere. (This of > applies to source code but not to things like issues, which is another good > reason to keep them on our own server.) > Subversion repositories can be cloned with full history. An easy way to do it is using git :) I better don my Nomex now and slink away ;) Cheers, Kuba Ober ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
Dear Ryan, On 20 Aug 2016, at 02:18 , Ryan Schmidt wrote: > I'm pleased to announce that MacPorts will be moving its source code to > GitHub. in general I applaud this move! Congratulations to all those involved to make this change happen!!! > great collaboration features such as pull requests which some of our > contributors have been wishing for. +1 !!! > Hopefully, in addition to the other benefits, moving to GitHub will help > us attract and keep new developer talent. Yes, indeed! > In a January survey on this list, most developers indicated a preference for > git, or that they were happy with the Subversion client. GitHub accommodates > both. More on that in a separate mail to follow. Well, I voted for Mercurial, but it is unfortunately not as popular as git. > We also considered converting to Jira or BugZilla, but in the end, > we decided that staying with Trac is the best and least disruptive choice > for now. We will migrate the data from our Trac installation to a new > server, taking the opportunity to upgrade to the latest version of Trac and > make some other improvements. Sounds like the way to go! > And our new buildbot automated build system announced earlier this month is > being hosted by me on my hardware, outside of Apple, and will just need > minor changes to monitor GitHub instead of Subversion. On your own hardware?!? I guess this means that apart from the MLs Apple doesn’t want any association with MacPorts anymore!? That I find sad, but I do appreciate the support for this community driven activity through all these years. Well, let’s hope that MacPorts will attract more users and maintainers due to its move to GitHub! Thanks once again to all of ye, Marko ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
On 2016-8-20 11:04 , Kevin Walzer wrote: On 8/19/16 8:18 PM, Ryan Schmidt wrote: Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the decade since Mac OS Forge was created, collaborative software development platforms like GitHub and BitBucket have become very popular and successful, and when I was hired as Mac OS Forge sysadmin last year, part of my job was to evaluate whether such services could be a suitable replacement for those offered by Mac OS Forge. We determined that the answer was yes, and that GitHub was the best choice, due to its overwhelming popularity. Other Mac OS Forge projects including XQuartz, CUPS and CalendarServer are already in the process of moving to GitHub, and the time has now come for MacPorts to likewise bid a fond farewell to Mac OS Forge and move on. This is certainly an interesting development. I hope this works out well for the MacPorts project. What will become of MacOS Forge if all its projects migrate off it? Is Apple ceasing support for MacOS Forge? I can't speak for Apple, but I imagine if all the projects move somewhere else, Mac OS Forge will simply cease to exist. Is it still a hosting service if it isn't hosting anything? :) Pretty much every project on Mac OS Forge apart from us was run by Apple employees, and I'm sure Apple projects will continue to get the server resources they need. I can't imagine WebKit would just disappear, for example. Whether it will still be under the Mac OS Forge banner I don't know. I understand that a lot of thought has gone into this decision, but it's also not hard to view one of its primary motivators--"all the cool projects are on Github, and it's crucial for developer mindshare"--as something to view with concern. Competition in this space is healthy. A decade ago SourceForge occupied the place in the community that Github does now, and there was hardly any place else to go if their site was down. One reason Tcl/Tk moved off SF to their own Fossil repo was because of a serious outage at the site that prevented commits for weeks. This is more of a hope that Github does not become the kind of monoculture that SF was than any criticism of Github--as long as Bitbucket and other platforms are around and still have some volume, that will help. I share these concerns and brought them up during the discussions. And TBH I think Mercurial is a better tool. But we did come to a consensus that GitHub is overall the best choice at this time. And as Mark mentioned, one of the advantages of a DVCS is that the full repository history isn't locked away on a single server, so if GitHub goes down or turns evil, we can easily pack up and go elsewhere. (This of applies to source code but not to things like issues, which is another good reason to keep them on our own server.) - Josh ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
> On Aug 19, 2016, at 8:18 PM, Ryan Schmidt wrote: > > And our new buildbot automated build system announced earlier this month is > being hosted by me on my hardware, outside of Apple, and will just need > minor changes to monitor GitHub instead of Subversion. FYI I've made some progress on this tonight and hope to make initial commits tomorrow or Sunday. vq ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
Yeah, no one wants Github to be the new SF. Thankfully, git helps there, we can pick up and move anytime. Also, it's a bit less once size fits all thing than SF. SF had everything. Github is more focused. The lack of ads and the pay to play system makes me feel better about it. —Mark ___ Mark E. Anderson On Fri, Aug 19, 2016 at 9:04 PM, Kevin Walzer wrote: > On 8/19/16 8:18 PM, Ryan Schmidt wrote: > >> Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the >> decade since Mac OS Forge was created, collaborative software development >> platforms like GitHub and BitBucket have become very popular and >> successful, >> and when I was hired as Mac OS Forge sysadmin last year, part of my job >> was >> to evaluate whether such services could be a suitable replacement for >> those >> offered by Mac OS Forge. We determined that the answer was yes, and that >> GitHub was the best choice, due to its overwhelming popularity. Other Mac >> OS >> Forge projects including XQuartz, CUPS and CalendarServer are already in >> the >> process of moving to GitHub, and the time has now come for MacPorts to >> likewise bid a fond farewell to Mac OS Forge and move on. >> > > This is certainly an interesting development. I hope this works out well > for the MacPorts project. What will become of MacOS Forge if all its > projects migrate off it? Is Apple ceasing support for MacOS Forge? > > I understand that a lot of thought has gone into this decision, but it's > also not hard to view one of its primary motivators--"all the cool projects > are on Github, and it's crucial for developer mindshare"--as something to > view with concern. Competition in this space is healthy. A decade ago > SourceForge occupied the place in the community that Github does now, and > there was hardly any place else to go if their site was down. One reason > Tcl/Tk moved off SF to their own Fossil repo was because of a serious > outage at the site that prevented commits for weeks. > > This is more of a hope that Github does not become the kind of monoculture > that SF was than any criticism of Github--as long as Bitbucket and other > platforms are around and still have some volume, that will help. > > --Kevin > > -- > Kevin Walzer > Code by Kevin/Mobile Code by Kevin > http://www.codebykevin.com > http://www.wtmobilesoftware.com > > > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
On 8/19/16 8:18 PM, Ryan Schmidt wrote: Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the decade since Mac OS Forge was created, collaborative software development platforms like GitHub and BitBucket have become very popular and successful, and when I was hired as Mac OS Forge sysadmin last year, part of my job was to evaluate whether such services could be a suitable replacement for those offered by Mac OS Forge. We determined that the answer was yes, and that GitHub was the best choice, due to its overwhelming popularity. Other Mac OS Forge projects including XQuartz, CUPS and CalendarServer are already in the process of moving to GitHub, and the time has now come for MacPorts to likewise bid a fond farewell to Mac OS Forge and move on. This is certainly an interesting development. I hope this works out well for the MacPorts project. What will become of MacOS Forge if all its projects migrate off it? Is Apple ceasing support for MacOS Forge? I understand that a lot of thought has gone into this decision, but it's also not hard to view one of its primary motivators--"all the cool projects are on Github, and it's crucial for developer mindshare"--as something to view with concern. Competition in this space is healthy. A decade ago SourceForge occupied the place in the community that Github does now, and there was hardly any place else to go if their site was down. One reason Tcl/Tk moved off SF to their own Fossil repo was because of a serious outage at the site that prevented commits for weeks. This is more of a hope that Github does not become the kind of monoculture that SF was than any criticism of Github--as long as Bitbucket and other platforms are around and still have some volume, that will help. --Kevin -- Kevin Walzer Code by Kevin/Mobile Code by Kevin http://www.codebykevin.com http://www.wtmobilesoftware.com ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
On Aug 19, 2016, at 7:28 PM, C. R. Oldham wrote: > On August 19, 2016 at 6:19:06 PM, Ryan Schmidt wrote: > >> I'm pleased to announce that MacPorts will be moving its source code to >> GitHub. > This is fantastic and phenomenal. > > Does this mean that updates to ports can be submitted via GitHub Pull Request? We have not worked out exactly how all of our processes and procedures will work on GitHub after the move. There will probably be a period of experimentation. But I do hope we will be able to make good use of pull requests. Our current attach-patchfiles-to-ticket method can be error-prone for non-trivial patches. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
This is super exciting. I can ditch my weird github workflow and have my own proper fork. And I agree, github issues really are terrible, glad to see we're sticking with trac. —Mark ___ Mark E. Anderson On Fri, Aug 19, 2016 at 8:28 PM, C. R. Oldham wrote: > > > > On August 19, 2016 at 6:19:06 PM, Ryan Schmidt (ryandes...@macports.org) > wrote: > > I'm pleased to announce that MacPorts will be moving its source code to > GitHub. > > This is fantastic and phenomenal. > > Does this mean that updates to ports can be submitted via GitHub Pull > Request? > > > --cro > > > > ___ > macports-dev mailing list > macports-dev@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-dev > > ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
On August 19, 2016 at 6:19:06 PM, Ryan Schmidt (ryandes...@macports.org) wrote: I'm pleased to announce that MacPorts will be moving its source code to GitHub. This is fantastic and phenomenal. Does this mean that updates to ports can be submitted via GitHub Pull Request? --cro ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
Re: Goodbye Mac OS Forge, hello GitHub
Hey Ryan, 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 Looking forward to to the move and a big welcome to the next generation of MacPorts! > On Aug 19, 2016, at 5:18 PM, Ryan Schmidt wrote: > > I'm pleased to announce that MacPorts will be moving its source code to > GitHub. The exact date for the move has not yet been set; this message is > just to let you know that these changes are coming soon. > > Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the > decade since Mac OS Forge was created, collaborative software development > platforms like GitHub and BitBucket have become very popular and successful, > and when I was hired as Mac OS Forge sysadmin last year, part of my job was > to evaluate whether such services could be a suitable replacement for those > offered by Mac OS Forge. We determined that the answer was yes, and that > GitHub was the best choice, due to its overwhelming popularity. Other Mac OS > Forge projects including XQuartz, CUPS and CalendarServer are already in the > process of moving to GitHub, and the time has now come for MacPorts to > likewise bid a fond farewell to Mac OS Forge and move on. > > The other MacPorts managers and I, and some other members of the community, > have discussed this change at length. Over the years, several developers > have asked why we're not on GitHub. The perception is that "everybody" is on > GitHub, and some developers don't take your project seriously if it's not on > GitHub. Part of our answer to such questions has been that it would be a > pain to move, and that what we had at Mac OS Forge was good enough. But now > that we have to leave Mac OS Forge anyway, it makes sense to convert to git > and take the opportunity to do some much needed and overdue restructuring > and splitting of our repository, and to move to GitHub to make use of their > great collaboration features such as pull requests which some of our > contributors have been wishing for. Hopefully, in addition to the other > benefits, moving to GitHub will help us attract and keep new developer > talent. > > In a January survey on this list, most developers indicated a preference for > git, or that they were happy with the Subversion client. GitHub accommodates > both. More on that in a separate mail to follow. > > We've given much thought to the way we use our Trac ticket system, and after > extensive discussion on how we might be able to use GitHub Issues, and even > performing a trial conversion of our tickets, we came to the realization > that moving to GitHub Issues would be a step back for us. (GitHub Issues > doesn't have custom fields, which we use to indicate the name of the port(s) > affected by the ticket, and the available workarounds are unsatisfactory. > And the original author of the ticket or comment cannot be preserved when > importing to GitHub Issues. In short, converting to GitHub Issues would be > lossy.) We also considered converting to Jira or BugZilla, but in the end, > we decided that staying with Trac is the best and least disruptive choice > for now. We will migrate the data from our Trac installation to a new > server, taking the opportunity to upgrade to the latest version of Trac and > make some other improvements. > > We've already completed several steps of this transition. Earlier in the > year, we announced that we started using MaxCDN in front of our primary file > server to distribute our files faster. Earlier this month, we announced the > new home for our primary file server at the Friedrich-Alexander University. > And our new buildbot automated build system announced earlier this month is > being hosted by me on my hardware, outside of Apple, and will just need > minor changes to monitor GitHub instead of Subversion. > > MacPorts domain names were already owned by the project, and have been moved > to NameCheap. DNS will move from Apple to NameCheap. @macports.org email > forwarding will move to a new server. The www.macports.org and > guide.macports.org web sites will move to a new server while retaining the > same functionality for now. Apple will continue to host our mailing lists. > > This transition should be mostly transparent to users. A separate email will > be sent to the announcement and users lists closer to the time of the move > detailing what steps users might need to take. > > On behalf of portmgr, thanks to Clemens Lang for writing the MacPorts > Subversion to git conversion rules we're going to use, and to Larry > Velázquez for registering the "macports" username on GitHub years ago in > anticipation of this day. Thanks again to our former Mac OS Forge sysadmins > Keith Dart, Henry Groen, Shreeraj Karulkar, and Bill Siegrist for keeping > everything running all these years. And our most appreciative and humble > thanks to Apple for supporting open source software by allowing its > developers to create the
Goodbye Mac OS Forge, hello GitHub
I'm pleased to announce that MacPorts will be moving its source code to GitHub. The exact date for the move has not yet been set; this message is just to let you know that these changes are coming soon. Since 2006, Apple has hosted MacPorts on its Mac OS Forge service. In the decade since Mac OS Forge was created, collaborative software development platforms like GitHub and BitBucket have become very popular and successful, and when I was hired as Mac OS Forge sysadmin last year, part of my job was to evaluate whether such services could be a suitable replacement for those offered by Mac OS Forge. We determined that the answer was yes, and that GitHub was the best choice, due to its overwhelming popularity. Other Mac OS Forge projects including XQuartz, CUPS and CalendarServer are already in the process of moving to GitHub, and the time has now come for MacPorts to likewise bid a fond farewell to Mac OS Forge and move on. The other MacPorts managers and I, and some other members of the community, have discussed this change at length. Over the years, several developers have asked why we're not on GitHub. The perception is that "everybody" is on GitHub, and some developers don't take your project seriously if it's not on GitHub. Part of our answer to such questions has been that it would be a pain to move, and that what we had at Mac OS Forge was good enough. But now that we have to leave Mac OS Forge anyway, it makes sense to convert to git and take the opportunity to do some much needed and overdue restructuring and splitting of our repository, and to move to GitHub to make use of their great collaboration features such as pull requests which some of our contributors have been wishing for. Hopefully, in addition to the other benefits, moving to GitHub will help us attract and keep new developer talent. In a January survey on this list, most developers indicated a preference for git, or that they were happy with the Subversion client. GitHub accommodates both. More on that in a separate mail to follow. We've given much thought to the way we use our Trac ticket system, and after extensive discussion on how we might be able to use GitHub Issues, and even performing a trial conversion of our tickets, we came to the realization that moving to GitHub Issues would be a step back for us. (GitHub Issues doesn't have custom fields, which we use to indicate the name of the port(s) affected by the ticket, and the available workarounds are unsatisfactory. And the original author of the ticket or comment cannot be preserved when importing to GitHub Issues. In short, converting to GitHub Issues would be lossy.) We also considered converting to Jira or BugZilla, but in the end, we decided that staying with Trac is the best and least disruptive choice for now. We will migrate the data from our Trac installation to a new server, taking the opportunity to upgrade to the latest version of Trac and make some other improvements. We've already completed several steps of this transition. Earlier in the year, we announced that we started using MaxCDN in front of our primary file server to distribute our files faster. Earlier this month, we announced the new home for our primary file server at the Friedrich-Alexander University. And our new buildbot automated build system announced earlier this month is being hosted by me on my hardware, outside of Apple, and will just need minor changes to monitor GitHub instead of Subversion. MacPorts domain names were already owned by the project, and have been moved to NameCheap. DNS will move from Apple to NameCheap. @macports.org email forwarding will move to a new server. The www.macports.org and guide.macports.org web sites will move to a new server while retaining the same functionality for now. Apple will continue to host our mailing lists. This transition should be mostly transparent to users. A separate email will be sent to the announcement and users lists closer to the time of the move detailing what steps users might need to take. On behalf of portmgr, thanks to Clemens Lang for writing the MacPorts Subversion to git conversion rules we're going to use, and to Larry Velázquez for registering the "macports" username on GitHub years ago in anticipation of this day. Thanks again to our former Mac OS Forge sysadmins Keith Dart, Henry Groen, Shreeraj Karulkar, and Bill Siegrist for keeping everything running all these years. And our most appreciative and humble thanks to Apple for supporting open source software by allowing its developers to create the initial version of MacPorts and release it as open source software, and by providing hardware and network bandwidth to host it. We are very grateful. I'm sure you'll have questions. More information will follow. Thank you all for bearing with us during this transition. ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-d
