divmod-dev team mailing list archive

[Florent <florent.xicluna@xxxxxxxxx>]

2012/12/31 Glyph <glyph@xxxxxxxxxxxxxxxxx>

>
>
> 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.
>
>
Hello Divmod team,

First, I did not intend to be disrespectful to anyone.
I did not delete anything, and I did not remove any existing work from
anyone.

The only thing I did is to extract the history of PyFlakes and publish it
under lp:pyflakes (owned by divmod-dev, part of the Divmod Projects). As
you figured out, this did not cause any damage and is completely reversible.

Then when I concluded the e-mail with "More to come later", I mean that I
plan to invest some time to merge the approved merge proposal, and
review/resubmit the other merge proposals on the new repository.

Then the question I've read on the #divmod channel, is "why we don't
continue development in lp:divmod.org repository?"
I see many positive reasons to host the code for PyFlakes in a separate
repository. As I said in a previous e-mail, it is less confusing for all
the actors (users, developers, etc...) to find the project at a single
place: the source code, the issue tracker, the downloads...
Second reason, is that it makes it easier for external contributions. You
only clone the PyFlakes project, without need to download the code of all
the unrelated Divmod's projects. Same benefit when someone want to mirror
code on any other VCS.
And the PyFlakes project is so widely used, that it deserves to have its
own repository.

Now, I expect some positive criticism about this approach, and any
side-effect we need to take into account.
I already know that I need to take care of the 4 (now 3) branches or MP
which are linked to bugs. I already had a look at them, and I will resubmit
them as soon as we agree on it.
Anything else I missed?

Thank you for your feedback.

Best wishes for the year 2013,

-- 
Florent Xicluna