Issues with oudated ports / GitHub

Marcel Bischoff marcel at
Sat Oct 8 16:48:37 PDT 2016

On 16/10/08, Brandon Allbery wrote:
>On Sat, Oct 8, 2016 at 4:12 PM, Marcel Bischoff <marcel at>
>> I for one don't understand why one would carry around all that baggage
>> anyhow. Why not leave the old Trac as is and start fresh with a simple,
>> reduced issue tracker
>When the simple reduced tracker is, as already said, too simple. It is in
>fact the very "Only if it was really, really awful. But then they would have
>changed it a long time ago." you already mentioned: yes, it's simple for
>you the end user, but it doesn't do what the people who actually do the
>work need it to do (and this is true across many projects, some of which
>have had to build their own additional tooling to interface with Github and
>try to add all the functionality it doesn't provide).

I understand that. Many long-running projects are using their own Git
infrastructure with Trac, Redmine and others. What I don't understand is
why moving to GitHub at all when the tooling is clearly insufficient for
the project. The added exposure? The hope to attract new developers? If
the needs of the "people who actually do the work" are paramount, GitHub
is probably not adding much to improve ingrained workflows but rather
slow them down.

More information about the macports-dev mailing list