Moving to GitHub: Status Update, Action Required

Mojca Miklavec mojca at
Mon Oct 24 10:47:18 PDT 2016

On 24 October 2016 at 19:15, Lawrence Velázquez wrote:
>> On Oct 24, 2016, at 12:50 PM, Mojca Miklavec wrote:
>> (not?) related to the above question: One thing I'm confused about is
>> that whenever I'm listed as a reporter or in CC, my name would be
>> replaced by all the three data (my macports handle, my full email, my
>> github account), while the tickets where I'm the owner only contain my
>> macports email. Tickets where the owner has been assigned later
>> contain full info about that owner. I didn't investigate too closely
>> yet.
> Can you provide some examples?

I can send you a screenshot comparing the version I opened two hours
ago and the same page reloaded just now. The result changed in the
meantime. In any case I can no longer provide you any broken example
(there are still some for other developers, but I cannot judge about
whether other developers did the migration already or not).

The problem I have right now though is how to list the tickets owned /
reported by me. The query I used on the old trac no longer works.

For example:
[[TicketQuery(status=assigned|new|reopened&owner~=mojca at]]

>> May I suggest creating a clone of the port repository on GitHub (in
>> whatever state it is now) and let it serve as a playground for testing
>> different strategies of pushing, using pull requests, merging,
>> properly rebasing, merging several commits of a pull request together,
>> editing pull requests by non-committers (when a pull request needs
>> just a tiny bit of fixing: will that be one commit or original commit
>> + edits by "committer"), ...
>> It would help a lot if we had at least some idea how we want to
>> proceed after the official switch. And some "grace period" to test
>> what we want to do and what we want to avoid. Some playground for
>> people that are new to git & and github wouldn't hurt either.
> I'm not sure it's necessary to host such a sandbox repository in the
> macports organization. The "macports-ports" repository
> ( already contains
> a stale version of the ports tree; you can fork it and play around with
> it as you wish.

The idea is not to play with it on my own. I know how trivial git
commands work. What is not yet clear to me is whether we would be
clicking the gui buttons to accept pull requests or do some
non-conventional steps of merging multiple commits, adding our changes
on top, rebasing to master etc. (My preference would be to keep linear
history for master and not to keep ten broken revisions of a Portfile
resulting from stepwise improvements in a pull request, but it would
be nice to do some testing first.)


More information about the macports-dev mailing list