[tahoe-dev] github plan?

Randall Mason clashthebunny at gmail.com
Thu Mar 21 09:42:25 UTC 2013

On Fri, Mar 15, 2013 at 8:07 AM, Brian Warner <warner at lothar.com> wrote:

> * get everyone who's forked from me to delete their repos and re-fork
>   from the official one, then once my repo has no fork-children, I can
>   do the same.

This would result in lost history, including pull requests.  We need
to make sure that all old pull requests on the children of your
(warner's) repo are closed before this happens.

> or
> * submit a github support request to have them jiggle the database and
>   accomplish the same thing without doing a bunch of shady and/or risky
>   deletes
> I'll do the latter when I get a round tuit.

This is the best option if it's possible.

> But yes, pull requests will target the fork-parent by default, and we'd
> like all pull-requests to be aimed at the official repo, so all
> committers can respond to (and close) them, not just me.

What is the current preferred structure of development?  Should pull
requests be used at all?  Can trac interact with a github pull
request?  I think we should use a URL to a git repo be used so that
bitbucket, and personal git repos can also be used.

Randall Mason
ClashTheBunny at gmail.com

More information about the tahoe-dev mailing list