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
> 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
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 fea
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
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
su
> 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 thi
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
_
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 F
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 GitH
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
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
___
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 pl
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 F
13 matches
Mail list logo
