As many of you know, MacPorts is loosely governed by the "PortMgr"
team, which is currently made up of three people: Markus Weissmann,
Juan Manual Palacios, and James Berry.
We each love MacPorts, and hope to see it continue to prosper and grow
in the future. And we want to continue to contr
Sounds like a good plan. +1
On Sep 30, 2008, at 9:18 AM, James Berry wrote:
> As many of you know, MacPorts is loosely governed by the "PortMgr"
> team, which is currently made up of three people: Markus Weissmann,
> Juan Manual Palacios, and James Berry.
>
> We each love MacPorts, and hope to se
Not sure about the name but I love the idea. It'd be great to have a
shorter release cycle between 1.x MacPorts releases.
Paul.
On 30 Sep 2008, at 17:18, James Berry wrote:
> As many of you know, MacPorts is loosely governed by the "PortMgr"
> team, which is currently made up of three people:
I can't say that I've been a part of this community for very long.
However, I think some of my experience speaks to this.
First off, Thanks to Markus, Juan and James for the job they've done
in getting Macports to where it is now. I was mentally comparing my
experience with Macports to the
There had been no response to my previous post (quoted below), so I
decided to try again. Could one of the MacPorts maintainers take a
look at the patch, please? This is actually quite a trivial change
that will make the user configuration much more convenient.
Best regards
Adam Byrtek
On Fri, A
On Sep 30, 2008, at 9:18 AM, James Berry wrote:
> We have asked Jordan Hubbard, the father of MacPorts, to join us on
> the Elder Council, and he has given his tentative acceptance.
First, let me thank James, Markus and Juan for having both the insight
and the courage to recognize their own
Hi Jordan,
On Sep 30, 2008, at 12:32 PM, Jordan K. Hubbard wrote:
> I think it's more accurate to refer to me as the "Godfather" of
> MacPorts
> since I got the project initially created and funded, and you can see
> my fingerprints here and there in the design
> so I really hope people will
I agree it's an awkward scenario; those changes were actually a user
submitted patch, but I reviewed and considered the issues you're
pointing out.
While it's impossible to anticipate all usecases, it seems that
Sphinx's userbase is almost entirely mysql-exclusive, so the general
ideas in
Adam,
Thanks for the patch. This looks good to me. Does anybody have a use
case where inheritance is not the right thing here?
James
On Sep 30, 2008, at 12:03 PM, Adam Byrtek wrote:
There had been no response to my previous post (quoted below), so I
decided to try again. Could one of the M
Adam Byrtek wrote:
> There had been no response to my previous post (quoted below), so I
> decided to try again. Could one of the MacPorts maintainers take a
> look at the patch, please? This is actually quite a trivial change
> that will make the user configuration much more convenient.
Sometimes
10 matches
Mail list logo