divmod-dev team mailing list archive

[Glyph <glyph@xxxxxxxxxxxxxxxxx>]

On Dec 31, 2012, at 4:04 AM, Florent <florent.xicluna@xxxxxxxxx> wrote:

> 2012/12/31 Glyph <glyph@xxxxxxxxxxxxxxxxx>
> 
> You have been added to the team.  Use your powers wisely :).
> 
> -glyph
> 
> 
> 
> Thank you.
> 
> I redid a full export of the PyFlakes code (with history) and published it in the PyFlakes project
> ( bzr branch lp:pyflakes )
> 
> In details, these are the commands played (using plugins bzr-git and bzr-fastimport):
> bzr fast-export --no-plain divmod.org divmod.fi.gz
> bzr fast-import-filter -i Pyflakes/ divmod.fi.gz > pyflakes.fi
> bzr init pyflakes-fi
> bzr fast-import ../pyflakes.fi
> bzr push lp:flakes
> 
> Regarding the existing merge proposals, I think that each one should be resubmitted against this branch. I will have a look.
> And no more development should happen in the Divmod,org repository for Pyflakes.
> 
> I rebased the GitHub mirror on this branch too.
> 
> Now it's time to celebrate New Year's Eve.
> More to come later.

Florent,

This is not what I meant by "wisely".  Please do not do things unilaterally.  There are other maintainers and you should get their assent before changing things.

Thank you very much for explaining how to filter part of a Bazaar tree in a history-preserving way. This is an extremely useful tidbit and likely something that should be done in the future.  Perhaps even the near future.

But it is disrespectful to the people who tried to submit merge proposals in the proper way and contribute to upstream development, despite the difficulties and confusion that you cited earlier, despite numerous forks, by telling them they have to figure out how to re-base their work without providing instructions.  There is even a merge proposal approved and pending for landing.  If you are going to move code around it is also your responsibility to _first_ look at every outstanding branch on https://code.launchpad.net/divmod.org and look for relevant changes to pyflakes, not to throw away all that data and hope that someone else will re-collect it for you later.  Not to mention the fact that you will need to submit a merge proposal to remove the Pyflakes directory from ~divmod-dev/divmod.org/trunk.

It's especially inappropriate to do this halfway while others are on holiday then disappear yourself after doing it.

I have un-linked your branch from the pyflakes project; since you did not change the descriptive text (it still points at https://launchpad.net/divmod.org) things are still as they were.

Nevertheless, I hope you still stick around and do actual useful stuff for pyflakes beyond just moving the code around :).

-glyph