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.


From: Chad Horohoe <chorohoe@wikimedia.org>
To: Pywikipedia discussion list <pywikipedia-l@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
3) What to do with submodules. A concise list of all the current externals
will make this easier.

Thanks everyone!


On Tue, Jun 4, 2013 at 8:30 AM, Amir Ladsgroup <ladsgroup@gmail.com> wrote:
I agree with "sooner is better", I will help in updating
documentations and everything I can

Tell me what I can do :)


On 6/2/13, Chad Horohoe <chorohoe@wikimedia.org> wrote:
> On Sun, Jun 2, 2013 at 5:32 AM, legoktm <legoktm.wikipedia@gmail.com>
> wrote:
>> One thing I didn't notice on the plan is that right now we have a lot of
>> externals set up, some of which are also dependent on the Toolserver.
>> Should we be converting these to git submodules? Or what?
> 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).
>> Also, I added a comment on the page about giving all current commiters +2
>> since that wasn't explicitly stated, and drafted a list on the talk page
>> of
>> some things we should do/update after the migration (update docs, update
>> nightlies source, etc)
> 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


Pywikipedia-l mailing list

Pywikipedia-l mailing list