On 4 January 2013 15:19, Florent <[email protected]> wrote: > Hello Divmod team, > > I would like to highlight the proposal of moving PyFlakes to its own > repository. > For those who already read the previous discussion, this is exactly the same > proposal (which received positive feedback from two members). > > I see many good 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 wants to mirror > the code on any other VCS. > And the PyFlakes project is so widely used, that it deserves to have its own > repository. > > The proposal is tracked with issue #1095248: > https://bugs.launchpad.net/divmod.org/+bug/1095248 > More technical details in the bug report. > > Thank you for your feedback on the bug tracker, or on this mailing list.
Three questions: 1. Will history be preserved? Your earlier thread with fast-import/fast-export seems to imply yes. (Thanks for the tip!) 2. What will happen to branches in-progress? This was raised in the earlier thread. I guess the plan on the bug needs to be updated. 3. How can we minimize disruption during & around the migration? Maybe all we need is a pre-migration announcement including a time and date, followed by something afterwards saying it all went smoothly & pointing to the updated docs. Those are all the concerns I can think of. Thanks for driving this! jml -- Mailing list: https://launchpad.net/~divmod-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~divmod-dev More help : https://help.launchpad.net/ListHelp
