Port and patch submissions via ticket vs. via PR.

[Jan Stary]

> > Also, Mojca brought the question of the hundreds of open tickets with
> > port submissions a while back. It might be neat if we had some code
> > that caused a special Github account to generate a PR for a port
> > submission in trac. I wouldn't want this automatically invoked (at
> > least not yet!), but if a human (like me!) could manually invoke it on
> > a few ports at a time when they had free time, it might help to
> > clear out the backlog.
> 
> I'm a afraid this requires human labor that cannot be much helped
> by any automation. The gist of it is to work on the port itself,
> motivatad by need and/or love. The only way for any of
> https://trac.macports.org/query?status=new&type=submission
> to become an actual port is that _some_guy_ cares enough
> to _have_that_ in MP to turn it into a port, test etc,
> and prefrably create a PR to be merged. Whether this guy
> downloads the attached Portfile from a trac ticket or
> clones somebody's branch is a technicality compared to that.
> 
> For example, if anyone cared about dbxml
> https://trac.macports.org/ticket/24429
> we would have a dbxml port by now. The reason we don't
> is not that it's a trac submission, instead of a PR.

Come to think of it, automatically turning those trac port submissions
that have been rotting there for years into github PRs now
would only make it look like they are not rotting for years.

For example, https://trac.macports.org/ticket/22255
has been dead for eight years. But turn it into a PR,
and hey, there's a PR opened today!
But nothing has changed, really.