On Feb 10, 2012, at 8:50 AM, Sumana Harihareswara wrote:
On 02/10/2012 08:10 AM, Chad wrote:
On Wed, Feb 1, 2012 at 8:15 PM, Arthur Richards arichards@wikimedia.org wrote:
Thanks for sharing these Sumana. One thing I haven't really seen mentioned anywhere is what's going to happen with the WIkimedia repository (rather than the MediaWiki repository) and how that figures into the roadmap/conversion schedule. Chad or Sumana, can you shed some light on this?
I totally want to apologize for delaying in responding on this. Somehow it got past my inbox and I missed it until I was looking for another e-mail.
The main point I want to reiterate for everyone is that there is no deadline. MediaWiki and its extensions are on a pretty firm migration path right now and we've got dates pencilled in for when we'd like to finish converting. Converting these parts of the repository are going to be the hardest anyway, so once we've cleared that hump hopefully it'll be trivial to migrate the remaining projects.
I know fundraising is on a different schedule than everyone else, so that's perfectly ok and we can look to a time after the main migrations are done that will work well for you guys too.
I've mentioned this number in a couple of places, but I think I'll say it here too so everyone's clear: I'd like to have the svn repository completely read-only by this time next year (very roughly). If you've got a project that you're maintaining in svn (other than core or extensions), now's the time to start thinking about where you want it to eventually end up. If you're wanting to move to git with the rest of us, the WMF git repo will obviously welcome any existing svn project. If you're wanting to stick with svn or go another route--let me know, I'll be happy to work with you to figure something out.
-Chad
(CC'ing Merlijn as he's been my liaison to pywikipediabot on this topic.)
Thanks for the timeline on that, Chad. I've added that mid-2013 hope to
https://www.mediawiki.org/wiki/Git/Conversion#Affected_development_projects
I want that to be a list of all the projects that live on svn.wikimedia.org (fundraising, Wikimedia analytics, mwdumper, etc.) so we can systematically reach out to them and help them figure out what to do.
I'm also collecting open git migration questions today at
https://www.mediawiki.org/wiki/Talk:Git/Conversion/issues#Topics_for_Chad.27...
so that Chad and I can work on an email and a blog post about 8 hours from now. Feel free to add your questions. (Example: "what about gerrit? when will it be not a UX nightmare?")
-- Sumana Harihareswara Volunteer Development Coordinator Wikimedia Foundation
On 02/10/2012 06:12 PM, Gregory Varnum wrote:
I might be missing something obvious - but when should/can extension
developers start working on git vs. svn?
Should we wait for the conversion of all extensions or will the
extensions area of the repo be available for use beforehand for any new extensions?
-greg aka varnent
Good question, Greg!
We had a meeting today to lay out some of the open questions and the answers. Really raw notes are at
https://www.mediawiki.org/wiki/Talk:Git/Conversion/issues#Topics_for_Chad.27...
It was so long that the email and blog post are going to happen early next week instead. But here are some key points:
* Please stop creating new extensions in Subversion, right now. It makes Chad's migration work more error-prone. If you want to create a new extension in git, ask Chad and he'll help you.
* Extension developers can start learning git now and will have a choice to move to git starting in March.
* As far as Chad knows, none of the gerrit bugs listed in https://labsconsole.wikimedia.org/wiki/Gerrit_bugs_that_matter are bad enough to block the migration. What, *specifically*, do people hate about gerrit? He needs to know specifics to make decisions that might delay the migration.
* In Chad's view, we can't use Phabricator as it is, mainly because it doesn't have LDAP support (and possibly doesn't have per-project permissions -- this needs investigating), and it is unlikely that our community can get those back-end features added and tested, to a quality comparable to gerrit's support for those features, by March. However, three months after MW core switches to git-and-gerrit, we'll have a serious tools overview and evaluate gerrit, git-review, gitweb, and all the other parts of our code management infrastructure, and revisit the gerrit decision. At that time we might find that Phabricator is a better fit, and git repos are more portable so switching would be feasible.
* There will be gerrit training documents available before MW core moves, and some kind of screen-sharing training by or before Monday, Feb. 27th.
* Chad is trying to get the real git repo up and running ASAP so people can start doing their real work there. He and RobLa believe we should encourage people to consider SVN indefinitely slushed. If you are going to do large things, they prefer you start doing them in git.
Please feel free to reply with questions in this thread, or start a new topic on that talk page. Thanks.