Hi Chad, In December, I think the consensus was to move to Gerrit [1] - basically with the goal to keep it as close as possible to mediawiki, hopefully also easing contributions (to mw for pwb developers and vice versa). I have put some initial work into the migration (see https://github.com/pywikibot/svn2git ), but I have not had the time to smooth out the wrinkles. Will you be at the Hackathon next week? I think this would be a good topic to discuss there. Merlijn [1] http://lists.wikimedia.org/pipermail/pywikipedia-l/2012-December/007657.html On 15 May 2013 01:37, Chad Horohoe <chorohoe(a)wikimedia.org> wrote:

I'm guessing we could have pywikipedia/trunk and pywikipedia/rewrite in Gerrit.   Hazard-SJ ________________________________ From: Chad Horohoe <chorohoe(a)wikimedia.org> To: Merlijn van Deen <valhallasw(a)arctus.nl> Cc: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org> Sent: Wednesday, May 15, 2013 6:33 AM Subject: Re: [Pywikipedia-l] SVN reaching end of life - migration plan needed On Wed, May 15, 2013 at 4:19 AM, Merlijn van Deen <valhallasw(a)arctus.nl> wrote: Hi Chad, Ooh, you found my tool :) Cleaning up those rule files should be pretty trivial, then we can convert all of the wanted history pretty quickly. I've gone ahead and drafted a page on mw.org based on the rules you wrote along with a survey of the existing SVN layout. https://www.mediawiki.org/wiki/Git/Conversion/pywikipedia   Will you be at the Hackathon next week? I think this would be a good I'm afraid I won't be making it this year. -Chad  _______________________________________________ Pywikipedia-l mailing list Pywikipedia-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Looks fine by me, and the sooner, the better (or so I want to think :P).   Hazard-SJ ________________________________ From: Chad Horohoe <chorohoe(a)wikimedia.org> To: Merlijn van Deen <valhallasw(a)arctus.nl> Cc: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org> Sent: Saturday, June 1, 2013 7:10 AM Subject: Re: [Pywikipedia-l] SVN reaching end of life - migration plan needed On Wed, May 15, 2013 at 4:19 AM, Merlijn van Deen <valhallasw(a)arctus.nl> wrote: Hi Chad, So, this can be done easily, I'm just wondering when we should go ahead with things? It'll only take a few hours, so it's just a matter of picking a date that people are ok with. Also, if anyone has anything they want to add to the page on mw.org, I'd welcome the input. https://www.mediawiki.org/wiki/Git/Conversion/pywikipedia -Chad _______________________________________________ Pywikipedia-l mailing list Pywikipedia-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

On Sun, Jun 2, 2013 at 5:32 AM, legoktm <legoktm.wikipedia(a)gmail.com> wrote: If they're available via Git too, then yes, we can switch them over to Git submodules once everything's migrated. For stuff coming from SVN, we'll have to find another way (but it's not impossible). As I said on-wiki, that sounds like a reasonable list of people to start with for having +2 access on the repo. The group will be self-managing, so you guys can add new people to it as you see fit. The docs/nightlies stuff is more in your guys' court, but it's good to keep a list of such things, sure. -Chad

Everyone seems to be ok with doing this sooner rather than later, so how about we pencil in the date of June 14th (next Friday)? That gives us enough time to figure out the parts we don't know as well as get notifications out to the relevant places. Things I think we need to figure out: 1) Exact repo structure. I think we've gotten a good discussion started on the wiki, but I'd like to see more input (and please, feel free to edit it mercilessly, this was all written based on my naïve understanding of how you guys work) 2) Who gets initial permissions on the repo(s). I've seen suggestions for a select list, all committers in 2013...any of these is fine by me. Remember this is permission for +2'ing and merging, all registered users will be able to submit changes for review (just like everywhere else in Gerrit) 3) What to do with submodules. A concise list of all the current externals will make this easier. Thanks everyone! -Chad On Tue, Jun 4, 2013 at 8:30 AM, Amir Ladsgroup <ladsgroup(a)gmail.com> wrote:

Hi Chad, Op 5-6-2013 16:49, Chad Horohoe schreef: Hold your horses please. I appreciate you putting effort in this, but I don't want to rush this. We should at least have: * Good plan * A timeline * An overlapping test period Also all our bugs are still at Sourceforge. If we're going to move, it would be good to move that to bugzilla so we have the integration. We should really think things through and not make hasty decisions. Maarten

1. The repo structure looks fine (to me, at least) 2. That suggestion also seems fine. (Just saying that I've been trying to get access for some time now, but I'm probably no closer than when I just started :P) 3. As for the externals, someone suggested using git submodules, but since they wouldn't be included in the clones (and checkouts, for that matter), I've just done a bit of reading and subtree merge could be considered. I also found this.   Hazard-SJ ________________________________ From: Chad Horohoe <chorohoe(a)wikimedia.org> To: Pywikipedia discussion list <pywikipedia-l(a)lists.wikimedia.org> Sent: Wednesday, June 5, 2013 9:49 AM Subject: Re: [Pywikipedia-l] SVN reaching end of life - migration plan needed Everyone seems to be ok with doing this sooner rather than later, so how about we pencil in the date of June 14th (next Friday)? That gives us enough time to figure out the parts we don't know as well as get notifications out to the relevant places. Things I think we need to figure out: 1) Exact repo structure. I think we've gotten a good discussion started on the wiki, but I'd like to see more input (and please, feel free to edit it mercilessly, this was all written based on my naïve understanding of how you guys work) 2) Who gets initial permissions on the repo(s). I've seen suggestions for a select list, all committers in 2013...any of these is fine by me. Remember this is permission for +2'ing and merging, all registered users will be able to submit changes for review (just like everywhere else in Gerrit) 3) What to do with submodules. A concise list of all the current externals will make this easier. Thanks everyone! -Chad On Tue, Jun 4, 2013 at 8:30 AM, Amir Ladsgroup <ladsgroup(a)gmail.com> wrote: I agree with "sooner is better", I will help in updating _______________________________________________ Pywikipedia-l mailing list Pywikipedia-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l

Hi Chad, As we discussed on IRC, my suggestion is the following: On 5 June 2013 16:49, Chad Horohoe <chorohoe(a)wikimedia.org> wrote: Let's get the conversion working, but without allowing patches in Gerrit. This allows us to do the migration in a somewhat slower pace, updating e.g. the nightly generation and making it easier to check if the conversion works as expected. This also makes it easier to get feedback on the conversion, hopefully. As a timeline, I would suggest to have continuous updates from svn to git, roughly weekly updates to the conversion code and a transition period of maybe 6 weeks, starting next friday? I think it is realistic as a time frame to update most things that depend on svn. Things I think we need to I have added a new proposed structure on the wiki. Basically, I'd like to formally separate trunk and rewrite, and to rename them to something like 'compat' and 'core'. After discussing it with you and translatewiki people, I think having i18n as submodule is the easiest option. I think we should not have the same method with external libraries svn:external'ed in. I'd be more interested in including a pip-style requirements.txt, with an optional 'external libraries' zip package. Merlijn

The conversion is now up and running! https://git.wikimedia.org/project/pywikibot Gerrit mirrors SVN (hourly), so please do not submit any patches you actually want merged. Test patches are, of course, welcome. Merlijn