[Wikitech-l] Wikimedia engineering February report
Hi, The February report of what was accomplished by the Wikimedia engineering team is now available: http://techblog.wikimedia.org/2011/03/wikimedia-engineering-february-report/ As far as I know, we haven't advertised these reports on this list in the past. I'd like to ask the list if you would prefer: * to keep the status quo: you're content with the RSS feeds from the blog and there's no need to post here; * posting a link here is a good practice that you'd like us to continue; * posting a link here is good, but you'd also like to get the content of the report in the e-mail; * something else? Thanks, -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
Hi, Thanks for the info. In favor of posting only the link. Nico On Fri, Mar 4, 2011 at 10:58 AM, Guillaume Paumier gpaum...@wikimedia.orgwrote: Hi, The February report of what was accomplished by the Wikimedia engineering team is now available: http://techblog.wikimedia.org/2011/03/wikimedia-engineering-february-report/ As far as I know, we haven't advertised these reports on this list in the past. I'd like to ask the list if you would prefer: * to keep the status quo: you're content with the RSS feeds from the blog and there's no need to post here; * posting a link here is a good practice that you'd like us to continue; * posting a link here is good, but you'd also like to get the content of the report in the e-mail; * something else? Thanks, -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Regarding GSoC 2011
Hello members, I am Ashish Mittal, a pre-final year BE student of Computer Engineering from Sardar Patel College of Engineering, India. I intend and am very keen to take part in GSoC 2011 with MediaWiki as my mentoring organization this year. I am new to this list and to this organization and I wish to contribute here as a developer. I have already participated in GSoC 2010 under Sakai Foundation where I created a subsystem ‘Event Explorer’ [0] for them. I have experience with the mentioned required tools and technologies like Eclipse, Maven, Ant, Git, SVN, MySQL, Struts, Grails, JSP, Servlet, HTML, CSS, Javascript/JQuery, AJAX, JUnit and Mockito. I am good with UI interfacing and web 2.0 tools. I got a local copy of MediaWiki and have installed it. I want to start getting to grip with the architecture of MediaWiki. I saw that MediaWiki has already started preparing for SoC 2011 [1]. I have been through some documentations and this year’s project ideas. I am primarily interested in *MediaWiki core* [2]. If you could plase give me some important and relevant pointers which would help me understand the project more, it would be very appreciated. Also I wanted to know if there are some tasks which I could work on prior to timeline so as to get a better understanding of the architecture and code base. So if you could please give me some information on the above, it will be very helpful to me. Thanks in advance. [0] - https://confluence.sakaiproject.org/display/KERNDOC/KERN-717+Event+Explorer [1] - http://www.mediawiki.org/wiki/Summer_of_Code_2011 [2] - http://www.mediawiki.org/wiki/Summer_of_Code_2011#MediaWiki_core Regards, Ashish -- Ashish Mittal Student at University of Mumbai Yahoo: av_mit...@ymail.com Gtalk: ashishmittal.m...@gmail.com Phone: +919930820950 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Regarding GSoC 2011
2011/3/4 ashish mittal ashishmittal.m...@gmail.com: I saw that MediaWiki has already started preparing for SoC 2011 [1]. I have been through some documentations and this year’s project ideas. I am primarily interested in *MediaWiki core* [2]. If you could plase give me some important and relevant pointers which would help me understand the project more, it would be very appreciated. Also I wanted to know if there are some tasks which I could work on prior to timeline so as to get a better understanding of the architecture and code base. So if you could please give me some information on the above, it will be very helpful to me. Thanks in advance. Have you read https://secure.wikimedia.org/wikipedia/mediawiki/wiki/How_to_become_a_MediaWiki_hacker ? Roan Kattouw (Catrope) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
Guillaume Paumier wrote: * posting a link here is a good practice that you'd like us to continue; This. I'd also to thank everyone who works on these reports. I know that many people appreciate them (myself included). MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Liquid Threads
After I heard about Liquid Threads in Berlin in April 2010, I immediately asked for it to be activated on sv.wikisource. This request took 4 months. A similar request for sv.wiktionary has still not been granted because it is better to wait for some future version. Now, during the 1.17 upgrade, the namespaces Thread: and Summary: disappeared from sv.wikisource and this was reported on February 16, https://bugzilla.wikimedia.org/show_bug.cgi?id=27533 Still after two weeks, no response has been given. The central discussion / village pump is still broken. Early on the Swedish community was very enthusiastic over LT and soon wanted it for the Swedish Wikipedia as well, but that enthusiasm is now hard to sustain. Should we conclude that the switch to LT was a big mistake, and try to go back to plain old talk pages, never to attempt LT again? I think that question has already been answered by the fact that no comment has been given to the bug report of February 16, not even a time estimate. -- Lars Aronsson (l...@aronsson.se) Aronsson Datateknik - http://aronsson.se ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Liquid Threads
Hoi, We are really happy using LiquidThreads at translatewiki.net. We use it in the most heady way at the cutting edge of its development and, while it has its glitches, I do not want to get back to the bad old days of talk pages. At translatewiki.net we do not have the long and winding discussions that blight other projects so much so it may not be representative of what it will be like elsewhere, but in my opinion, perfection is the enemy of the good here. Thanks, GerardM On 4 March 2011 16:17, Lars Aronsson l...@aronsson.se wrote: After I heard about Liquid Threads in Berlin in April 2010, I immediately asked for it to be activated on sv.wikisource. This request took 4 months. A similar request for sv.wiktionary has still not been granted because it is better to wait for some future version. Now, during the 1.17 upgrade, the namespaces Thread: and Summary: disappeared from sv.wikisource and this was reported on February 16, https://bugzilla.wikimedia.org/show_bug.cgi?id=27533 Still after two weeks, no response has been given. The central discussion / village pump is still broken. Early on the Swedish community was very enthusiastic over LT and soon wanted it for the Swedish Wikipedia as well, but that enthusiasm is now hard to sustain. Should we conclude that the switch to LT was a big mistake, and try to go back to plain old talk pages, never to attempt LT again? I think that question has already been answered by the fact that no comment has been given to the bug report of February 16, not even a time estimate. -- Lars Aronsson (l...@aronsson.se) Aronsson Datateknik - http://aronsson.se ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Liquid Threads
Lars Aronsson wrote: After I heard about Liquid Threads in Berlin in April 2010, I immediately asked for it to be activated on sv.wikisource. This request took 4 months. A similar request for sv.wiktionary has still not been granted because it is better to wait for some future version. Now, during the 1.17 upgrade, the namespaces Thread: and Summary: disappeared from sv.wikisource and this was reported on February 16, https://bugzilla.wikimedia.org/show_bug.cgi?id=27533 Still after two weeks, no response has been given. The central discussion / village pump is still broken. This is unacceptable. Looking at the bug history, the Bugmeister updated the bug on February 19. I think in situations like this, the Bugmeister needs to be responsible for escalating these issues to the appropriate people, mostly as the Bugmeister is the person who will have read these bugs and will understand the impact. Marking the bugs as critical or shell is helpful, to a point. However, in cases where sites become unusable, people need to be e-mailed, poked on IRC, etc. until the problem is resolved. It isn't acceptable to have sites in this state (to say nothing of the damage these types of issues do to LiquidThreads adoption). MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
On 4 March 2011 09:58, Guillaume Paumier gpaum...@wikimedia.org wrote: * posting a link here is a good practice that you'd like us to continue; +1 - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
On 4 March 2011, David Gerard wrote: On 4 March 2011 09:58, Guillaume Paumier gpaum...@wikimedia.org wrote: * posting a link here is a good practice that you'd like us to continue; +1 - d. +1 -- Krinkle ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Topic and cathegory analyser
On 3/3/2011 7:12 PM, Dávid Tóth wrote: Would it be useful to make a program that would create topic relations for each wikipedia article based on the links and the distribution of semantic structures? This would be very useful for me. I'm thinking about attack this problem by discovering 'low hanging fruits'. To some extent you can assume that :X :wikiLink :Y - :X skos:related :Y but the nature and strength of links is hard to estimate. I've developed a good metric for approximating the importance of topic :X, but I've yet to get a handle on relationship strength. To take an example, there's a link from :Metallica to :Yale_University because :Metallica :Sued :Yale_University That's not a very strong connection. Now, if Wikipedia mentioned the Dead at Cornell recording which was made when Jerry Garcia had just gotten hooked on opium and the band was playing at it's best, we might say :Grateful_Dead :PlayedAt :Cornell_University maybe you think that's a stronger connection than the above, maybe you don't. Then again, :Rod_Serling :TaughtAt :Ithaca_College is one of the stronger links involving :Ithaca_College in my opinion. There are two angles I see for extracting better relationships from Wikipedia and these are (i) databases such as Freebase and DBPedia, in particular, these have certain relationships already semantized and other information that can be used to infer about possible relationships. For instance, :Brown_Bear :Sued :Pelican doesn't make any sense and should be rejected. (ii) analysis of the text around a link. You could certainly see certain language patterns that are frequently used, for instance A is a B, C married D, E was born at F you could either find some of these by hand or you could write something that uses machine learning techniques to discover these. Information from type (i) could be useful here. For instance, we could find a bunch of relationships that exist in Freebase and use these as positive training examples. The trouble I see here is the creation of a good set of negative training examples, which has a few aspects: one is that examples that should be positive will slip into a negative sample, attempts to automatically exclude positives will probably also exclude 'near miss' negatives that would be especially important to include training set, and generally, the number of negatives would be 1000 or more times prevalent than positives, which gives most ML methods Bayesian priors that destroy recall. Another issue is that you'll see the patterns E was born at F [[E]] was born at F E was born at [[F]] [[E]] was born at [[F]] all occur (sometimes they make the text describing the subject a link, sometimes they don't.) Getting good recall then means solving the named entity extraction problem as well, however, making this part of a 'whole system' might create the kind of feedback control loop that's necessary for high-performing A.I. The best attack on this, I think, is to pick one particular relationship that you want to extract, particularly one that has a bit of a 'closed world' aspect in that you can presume that that property ought to exist for all members of a type. For instance, we can say that any person was born at some location but even there you can get into trouble quick, if you look at :Joan_of_arc, you see that wikipedia says that she was A peasant http://en.wikipedia.org/wiki/Peasant girl born in eastern France you note that A peasant girl == :Joan_of_arc and that a more specific birthplace can be found in the infobox. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
Hi, Le vendredi 04 mars 2011 à 17:25 +0100, Krinkle a écrit : On 4 March 2011, David Gerard wrote: On 4 March 2011 09:58, Guillaume Paumier gpaum...@wikimedia.org wrote: * posting a link here is a good practice that you'd like us to continue; +1 +1 Thanks to those who answered. I don't think it's necessary to continue to +1; this seems to be the consensus so far, so I'll just do that. -- Guillaume Paumier ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Topic and cathegory analyser
2011/3/4 Paul Houle p...@ontology2.com Briefly, atthe border of OT: I see the magic word ontology into your mail address. :-) :-) I discovered ontology ... well, a long history. Ontological classification is used to collect data on cancer by National Cancer Insititute; and, strange to tell, I discovered it as an unexpected result of posting a picture on Commons, a low grade prostatic PIN... then I found that NCI use SemanticWiki. In other terms: from wiki, to wiki again. :-) My aim about ontologies is very, very simpler; it's simply to create something I called catwords, t.i. a system of categorization (wiki sistem is perfect) that can be used too as a list of keywords. I can't wait for installation of DynamicPageList into it.source, since the engine I need is simply a good method to get intersection of categories; but I found that it's not sufficient, some peculiar conventions in categorization are needed too, far from complex well, I'll tell you news as soon as I will get my tool. :-) Alex ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Liquid Threads
MZMcBride z...@mzmcbride.com writes: Looking at the bug history, the Bugmeister updated the bug on February 19. I think in situations like this, the Bugmeister needs to be responsible for escalating these issues to the appropriate people, mostly as the Bugmeister is the person who will have read these bugs and will understand the impact. I agree that it is my responsibility to make sure that these things get handled in a timely manner. When something is escalated here on wikitech-l, it does show how I could be doing a better job. Obviously, I'm still learning how to do things and how to make sure that things get done. In this case I would prefer to have the ticket updated instead of having a someone post to wikitech-l. But I understand that my preferences are not paramount and that wiki-users' frustration has grown with each day this is not addressed. Since this is a shell request, I'm requesting RobH to look at it ASAP. Mark. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Commons-l] PhotoCommons Wordpress plugin
I've re-added wikitech-l to the header since it was originally addressed to both and your question and my answer will update them at the same time. And since it's now mostly tech-oriented feedback from them would be nice as well. A general note: If you're filing a new bug or feature request [0], be sure to check open tickets [1] first ;-) Right now the purpose / features of the plugin are: * Easy searching of images on commons with autosuggested subjects * Click-and-pick from the results to insert it in the page or post. A WordPress shortcode is inserted into the post ([photocommons file=Example.jpg with=200 align=right]) which will be made into a linked thumbnail with hover tooltip when parsed * No need to maintain your posts if a file is moved on Commons, redirects work finen (since there are no paths or img-tags hardcoded * No need to download/upload locally * Promote Wikimedia Commons as an easy-to-use source to add images to your blog or website and avoid people from googling for images and uploading or hotlinking random copyvios. On March 4 2011, Teofilo wrote: 1) I have never used wordpress. What do I need to try wordpress and your tool as a beginner easily for the first time ? 2) How does your tool attribute photographers ? Can you provide a screenshot showing attribution ? Is the attribution printed on paper when the user prints the resulting page ? 3) Are you using http://wiki.creativecommons.org/RDFa ? If relevant, see my remarks at http://commons.wikimedia.org/wiki/MediaWiki_talk:Stockphoto.js#.22Use_this_file.22_box_html_code_for_videos 1) Like for MediaWiki, you need a simple local AMP environment (eg. Apache, MySQL, PHP. So install something like LAMP or XAMPP, or get FTP access to an existing server with this). Then these 4 steps: * Install WordPress from the control panel of your webhost (if you have one) or download it from http://wordpress.org/, upload files, browse to them, follow instructions on-screen * Right now it's a development plugin, meaning not a plug-and-play for the general public yet, but for commos users and developers to see how it works and how it could be made better. To install the PhotoCommons plugin, check out most recent version from SVN [2] or download zip[3] * Follow install instructions (unzip, upload to /wp-content/plugins/wp- content, browse to your wp-admin - Manage Plugins - Click Activate) * Create or edit a new page or post on the wordpress site, next to the buttons to upload files locally to your blog there now is a Commons icon above the editor. Click it and have fun! * There's no step 5. 2) Since it is impossible right now to reliably extract such information we have choosen not to attempt to regex, hack, uglify our way out of it one way or another. We are waiting for the License integration project to finish at which point we will be able to dynamically extract this information from the API in a snap and cache it and display attribution and license under the thumbnail. For now we are taking the same approach as the Wikimedia wikis do (slightly better actually [4]), linking the thumnail directly to the Commons file page and the title of the image as tooltip when hovering the thumbnail. 3) We are not, see 2). I'm totally convinced this should be done, and we will as soon as licenses are integrated this will be done. -- Krinkle [0] https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimedia%20Toolsproduct=PhotoCommons [1] https://bugzilla.wikimedia.org/buglist.cgi?query_format=advancedcomponent=PhotoCommonsresolution=---product=Wikimedia%20Tools [2] * http://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/wp-photocommons/ * http://www.mediawiki.org/wiki/SVN#Check_out * $ cd mywordpress/wp-content/plugins * $ svn checkout http://svn.wikimedia.org/svnroot/mediawiki/trunk/tools/wp-photocommons [3] http://files.wmnederland.nl/downloads/latest.zip [4] Slightly better in that Wikimedia wikis link to the local cached/ transclusion instead of Commons directly. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Regarding GSoC 2011
ashish mittal wrote: I got a local copy of MediaWiki and have installed it. I want to start getting to grip with the architecture of MediaWiki. I saw that MediaWiki has already started preparing for SoC 2011 [1]. I have been through some documentations and this year’s project ideas. I am primarily interested in *MediaWiki core* [2]. If you could plase give me some important and relevant pointers which would help me understand the project more, it would be very appreciated. MediaWiki core refers to the core of mediawiki (the one which lives in trunk/phase3), each bullet is a project proposal. Maybe they are expressed in terms unclear for outsiders. Is there something you don't grasp? Also, feel free to poke us at #mediawiki at freenode irc. Also I wanted to know if there are some tasks which I could work on prior to timeline so as to get a better understanding of the architecture and code base. So if you could please give me some information on the above, it will be very helpful to me. Thanks in advance. First, you should be familiar with how is the wiki used. If you notice some bit worth fixing, do try it. You could also try to fix some bug from our bugtracker [1], although I recommend to get a second opinion that you are in the right track before doing too much. The link that Roan gave [2] should give you a start. Look at the code, search at concepts such as what is $wgMemc, or how to use the db object returned by wfGetDB(). 1- https://bugzilla.wikimedia.org/ 2- http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Topic and cathegory analyser
Paul Houle wrote: A peasant http://en.wikipedia.org/wiki/Peasant girl born in eastern France you note that A peasant girl == :Joan_of_arc and that a more specific birthplace can be found in the infobox. You will find that the infoboxes are the best article pieces to mine. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia engineering February report
On Mar 4, 2011, at 6:36 PM, Guillaume Paumier wrote: Hi, Le vendredi 04 mars 2011 à 17:25 +0100, Krinkle a écrit : On 4 March 2011, David Gerard wrote: On 4 March 2011 09:58, Guillaume Paumier gpaum...@wikimedia.org wrote: * posting a link here is a good practice that you'd like us to continue; +1 +1 Thanks to those who answered. I don't think it's necessary to continue to +1; this seems to be the consensus so far, so I'll just do that. +1 Domas ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] a procedure for setting up a prototype Wikimedia wiki
Is there some kind of a procedure for setting up a prototype Wikimedia wiki for testing? For example, which articles, templates and special pages should be copied there from the corresponding live wiki? In the Arabic prototype ( http://prototype.wikimedia.org/release-ar/ ) there are very few articles and all of them have Arabic titles. It makes it impossible to test Bug 26665. I created an article called ABCDE to test it, but to save time and ensure better testing in the first place, creating articles in various scripts and directionalities must be a part of the standard procedure for creating a prototype. And since i'm mentioning it, http://prototype.wikimedia.org/deployment-ar/ doesn't seem to work at all. -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com We're living in pieces, I want to live in peace. - T. Moore ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code Review of InterWiki Transclusion branch
Mark A. Hershberger wrote: In the next few weeks, I'd like to get Peter Potrowl's Summer of Code project for InterWiki Transclusion (fixes Bug 9890 https://bugzilla.wikimedia.org/9890) reviewed and merged from his branch into the trunk. I think it'd be nice to list things like this at the Review queue: http://www.mediawiki.org/wiki/Review_queue Can you show that page some love? MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Berlin hackathon in May: focus and dates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In article 4d6faefd.5030...@panix.com, Sumana Harihareswara suma...@panix.com wrote: * toolserver's purpose and services, since we'll be in Berlin I wasn't planning to attend this event, but I might come if people are discussing the Toolserver... do you have any more details on this? (The wiki page just says Toolserver, which is not especially informative.) - river. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (NetBSD) iEYEARECAAYFAk1xXcMACgkQIXd7fCuc5vJp/ACfffVrFbIDPEgMQN+gzzWzS3TO dNUAn1sjbR23TeDNBoX9kTAeq6OYI9gL =1jWN -END PGP SIGNATURE- ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Liquid Threads
Hi Lars, Thanks for raising these issues on wikitech-l. On Sat, Mar 5, 2011 at 2:17 AM, Lars Aronsson l...@aronsson.se wrote: After I heard about Liquid Threads in Berlin in April 2010, I immediately asked for it to be activated on sv.wikisource. This request took 4 months. A similar request for sv.wiktionary has still not been granted because it is better to wait for some future version. For context, here's a link to the full text of my comment on further pilot deployments. https://bugzilla.wikimedia.org/show_bug.cgi?id=19699#c10 Now, during the 1.17 upgrade, the namespaces Thread: and Summary: disappeared from sv.wikisource and this was reported on February 16, https://bugzilla.wikimedia.org/show_bug.cgi?id=27533 Still after two weeks, no response has been given. The central discussion / village pump is still broken. I've fixed this this afternoon. My apologies for this oversight — I've been travelling and busy and not reading my bug mail. In future, if you want to escalate an issue with me, you can do it by private e-mail. I always read email sent directly to me, but I will sometimes ignore automatic bug mail because of the volume I receive. Should we conclude that the switch to LT was a big mistake, and try to go back to plain old talk pages, never to attempt LT again? I think that question has already been answered by the fact that no comment has been given to the bug report of February 16, not even a time estimate. Further pilot deployments to other Wikimedia projects is a high priority for us, but in order to do that, we need time to address some serious architectural shortcomings that have been causing pain on several projects. Saying that we are not intending to continue to test LiquidThreads is not accurate — we will be very happy to make further rollouts when our updates are completed in a few months. I don't see our existing rollouts as mistakes — they've been invaluable in exposing the functional and technical limitations of LiquidThreads as it stands today, and they've helped shape the decisionmaking around the work that we're doing right now. I realise that you've been very patient so far, and that I've not always been prompt in my dealings with the issue of deploying LiquidThreads to the Swedish projects that you'd like to see it on. Unfortunately, I can only ask that you are patient for another few months, while we prepare ourselves for a second round of pilots. Thanks very much, Andrew -- Andrew Garrett http://werdn.us/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Regarding GSoC 2011
Hi, Thanks Roan and Platonides for the pointers and instructions. I read the link Roan gave [1] and found it a good place to get started. I am currently surfing the Developers Hub [2] and trying to get a good understanding of things. After this as Platonides suggested, I will be looking at bugs and will sure consult on the list before proceeding with one. Thanks and Regards, Ashish On Sat, Mar 5, 2011 at 2:32 AM, Platonides platoni...@gmail.com wrote: ashish mittal wrote: I got a local copy of MediaWiki and have installed it. I want to start getting to grip with the architecture of MediaWiki. I saw that MediaWiki has already started preparing for SoC 2011 [1]. I have been through some documentations and this year’s project ideas. I am primarily interested in *MediaWiki core* [2]. If you could plase give me some important and relevant pointers which would help me understand the project more, it would be very appreciated. MediaWiki core refers to the core of mediawiki (the one which lives in trunk/phase3), each bullet is a project proposal. Maybe they are expressed in terms unclear for outsiders. Is there something you don't grasp? Also, feel free to poke us at #mediawiki at freenode irc. Also I wanted to know if there are some tasks which I could work on prior to timeline so as to get a better understanding of the architecture and code base. So if you could please give me some information on the above, it will be very helpful to me. Thanks in advance. First, you should be familiar with how is the wiki used. If you notice some bit worth fixing, do try it. You could also try to fix some bug from our bugtracker [1], although I recommend to get a second opinion that you are in the right track before doing too much. The link that Roan gave [2] should give you a start. Look at the code, search at concepts such as what is $wgMemc, or how to use the db object returned by wfGetDB(). 1- https://bugzilla.wikimedia.org/ 2- http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Ashish Mittal Student at University of Mumbai Yahoo: av_mit...@ymail.com Gtalk: ashishmittal.m...@gmail.com Phone: +919930820950 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Code review — let us know you're testing code
Mark A. Hershberger wrote: As Ashar pointed out this week, we've fallen behind in code review. On Robla's page (http://toolserver.org/~robla/crstats/crstats.html) you can see that commits marked “new” is beginning to edge up again. To help with code review, Roan introduced “sign-offs” for developers who are not as familiar with the MediaWiki code base. I'm sure he'll correct me if I'm wrong, but I would like to encourage any developer who isn't ready to mark code “OK” to use the sign-off feature — to indicate that they've tested or inspected the code. If you're running trunk in your testing or (heaven forfend!) production, please try to see if you're exercising new code and give us feedback by marking the sign-off as “tested”. This is one of the best ways to get acquainted with the code base — if you miss something in your testing, we'll be sure to let you know! I don't currently have time for code review, but I'll try to report bugs for all issues I encounter. FYI I'm one of those crazy people running a small production website[1] off trunk. I only update the site every few weeks, because I want to test the changes locally before they go live, but I do read the commit messages from mediawiki-cvs almost daily, so I know of any urgent issues. (Small wish: it would be very helpful if every commit message referencing a bug would also include the one-line summary of the bug; that makes it much easier to quickly determine what the bug is about and if a bug is relevant for a specific environment. Thanks to all developers that already add this information!) Of course, if you've been reviewing code, THANK YOU and keep up the good work. I want to add my THANK YOU! To both developers and code reviewers: you do a very valuable job! Best regards Thomas Bleher [1]: http://spiele.j-crew.de ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
