Re: [Wikitech-l] Some labs beta cluster milestones
Good work, especially many thanks to Antoine (hashar), he did a lot of hard work On Wed, Aug 1, 2012 at 9:33 PM, Mark A. Hershberger m...@everybody.org wrote: On 08/01/2012 03:05 PM, Chris McMahon wrote: The labs beta cluster is becoming an important part our software development environment. It makes me very happy to read this. Mark. ___ 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] Try the new Wiki Loves Monuments Android App!
Hi John, Op 2 aug 2012 om 08:39 heeft John Vandenberg jay...@gmail.com het volgende geschreven:\ It hangs when talking to the satellites here in Oz. Probably because OZ isnt part of WLM?.. :( Or because we're still using the Toolserver as a backend in this beta. It would be good to have a generic Commons uploader app, with WLM app built as a front-end on top. We're doing it the other way around. First we build an app for WLM. Based on that experience a more general app will be build. Maarten Is the source available? On Aug 2, 2012 3:19 PM, Philip Chang pch...@wikimedia.org wrote: Announcing the Wiki Loves Monuments Android App, V1.1 beta 1! This app enables mobile monument discovery and photo uploads for the first time, both in terms of mobile functionality overall and for the Wiki Loves Monuments contest. Please turn on Unknown sources in Settings = Applications, click on the link below and install. Then go out and take lots of photos! Uploads will go to test wiki so feel free to upload whatever you like (and want to share with the world). http*://* http://bit.ly/OFS82Ibit.ly/wlmappv1 http://bit.ly/ OFS82I This is the first public release and is not quite feature-complete. Comments and bugs can go on this page: http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feedback Please try the following: * Browse by campaign (this will become browse by country/region/city) * Sort the list by name and address * Search with a search term * Open a monument, click on Get directions * Click on add a photo * Login or create a Commons account * Choose from gallery or take a photo * Start uploading * Go back to the opening screen * Click on Use my current location * Move around the map, open a cluster (a group of monuments close together) * Click on a pin, open the monument * Add a photo (login should be retained) * Start uploading Let us know what you think! Known issues: * Browse by country/region/city not fully implemented * Full-text search is slow * Map attribution is missing * Sort by distance appears when browsing by country * List view should have a more link when lists exceed 100 monuments * Map view will have two types of pins to distinguish monuments with and without photos * Upload later is not yet implemented Please forward this email as appropriate. Initial distribution: mobile-l, wmfall, internal-l, wikitech-l -- Phil Inje Chang Product Manager, Mobile Wikimedia Foundation 415-812-0854 m 415-882-7982 x 6810 ___ 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 mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Captcha for non-English speakers II
I made some mockups to illustrate some of the ideas on captchas that could be less problematic for non-English speakers, improve the general UX and rely on images from commons. - Panorama captcha: http://commons.wikimedia.org/wiki/File:Panorama-captcha-idea.png Based on tagging parts of a panorama picture with the appropriate word (in the UI language or Basic English words). - 'Who is who' captcha: http://commons.wikimedia.org/wiki/File:Find-all-captcha-idea.png Based on finding from a set of similar images the ones that fit a specific criteria (with an image describing also the criteria). - 'Find the different' captcha: http://commons.wikimedia.org/wiki/File:Find-the-different-captcha-idea.png Based on finding the image that is different from a set of images. These captchas will probably generate new problems for the technical side, require adjustments to reduce the chance of a machine to solve them, or may just be unfeasible to generate, but I wanted to provide these ideas in case anybody else may use it as a base for improve on any technical weakness they may have and make them at least as hard to solve for a machine as text-based captchas are. Pau On Wed, Aug 1, 2012 at 5:53 PM, Helder . helder.w...@gmail.com wrote: On Thu, Jul 26, 2012 at 10:53 AM, Everton Zanella Alvarenga ezalvare...@wikimedia.org wrote: After working on campus with new editors in Brazil, I've checked this is a real obstacle, since most people here cannot ready English at all. I'd like to know if there are plans to solve this issue - I hope I don't sound rude, maybe this can be a minor issue when we don't see the difficulties people from a different place can face. I think this is important for Wikipedias other than the English one (just read people comments in the bug) and we can be loosing new contributors because of their first impressions. Thanks, It should be noted that this is the only Wikipedia where the captcha is triggered for any edits made by anonymous or unconfirmed users[1], not just for edits which add urls. So, those users are affected by any issues of captcha on ALL their edits. Best regards, Helder [1] https://gerrit.wikimedia.org/r/gitweb?p=operations/mediawiki-config.git;a=blob;f=wmf-config/InitialiseSettings.php;h=5dd1bb63d399f0ba7bc49a4656dfed9109b550da;hb=HEAD#l8470 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Pau Giner Interaction Designer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Welcoming Srikanth Lakshmanan to the i18n engineering team
A most warm welcome, Srikanth. Great to have you on board! -- Siebrand Mazeland M: +31 6 50 69 1239 Skype: siebrand Op 1 aug. 2012 om 19:22 heeft Alolita Sharma asha...@wikimedia.org het volgende geschreven: Hi All, Please join me in welcoming Srikanth Lakshmanan as outreach coordinator/QA engineer (contractor) in WMF’s Internationalization (i18n) / Localization (L10n) engineering team. As the team’s technical liaison, Srikanth will be actively reaching out and working with our language communities to get feedback on new i18n/L10n features being planned or rolled out to Wikimedia sites. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Try the new Wiki Loves Monuments Android App!
It hangs when talking to the satellites here in Oz. Probably because OZ isnt part of WLM?.. :( It would be good to have a generic Commons uploader app, with WLM app built as a front-end on top. Is the source available? Yes, she says the source is available here: https://github.com/wikimedia/WLMMobile Thank you, Derric Atzrott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia engineering July 2012 report
Hi, The report covering Wikimedia engineering activities in July 2012 is now available. Wiki version: https://www.mediawiki.org/wiki/Wikimedia_engineering_report/2012/July Blog version: https://blog.wikimedia.org/2012/08/02/engineering-july-2012-report/ -- Guillaume Paumier Technical Communications Manager — Wikimedia Foundation https://donate.wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Nightly tarballs?
Rob Laphier writes: For testing reasons, I think this would be a great thing to have. ... Don't read I think this would be great to mean that this is a high priority thing, since I can't promise this won't get stalled behind other priorities Fair enough. Given that Chad has pointed out the un-cached nature of the gitweb links, though, this sounds like the thing to do. Since it sounds like the WMF is at least willing to provide the infrastructure (Git, Jenkins and Swift), can those of us outside the WMF who want to make this happen work with Chad, Antoine, and Ben to figure out how we can handle the nitty-gritty work that needs to be done? It sounds like some knowledge transfer (which I hope would be minimally invasive) and the already-existing infrastructure would be a all that is required from the WMF to make this happen. The rest (changes for Jenkins) could be done by volunteers. -- http://hexmode.com/ Human evil is not a problem. It is a mystery. It cannot be solved. -- When Atheism Becomes a Religion, Chris Hedges ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Nightly tarballs?
Le 01/08/12 21:29, Mark A. Hershberger a écrit : Is there any interest in having nightly snapshots of MediaWiki available? snip I have created a new Jenkins job to generate nightly snapshots of mediawiki/core.git : https://integration.mediawiki.org/ci/job/Nightly%20-%20MediaWiki%20Core/ Files are available at: https://integration.mediawiki.org/nightly/mediawiki/core/ mediawiki-latest.zip being a symbolic link to the latest build. The job is triggered everyday at 3am UTC which has been a low activity hour for the last 4 months or so. There is no process to cleanup the old snapshot, something we will have to think about later. The build script needed a git-archive macro: https://gerrit.wikimedia.org/r/#/c/17416/ And the Jenkins + ant target is at: https://gerrit.wikimedia.org/r/#/c/17417/ cheers, -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Extensions form building
Le 31/07/12 10:54, Bedhed a écrit : [2] Introduction: http://www.mediawiki.org/wiki/HTMLForm [3] Tutorial: http://www.mediawiki.org/wiki/HTMLForm/tutorial Thanks for sharing those links Clément! I have added them to HTMLForm class documentation with https://gerrit.wikimedia.org/r/17434 -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikidata blockers overview
Hi all, here is our update on last weeks blocker email. Most of them are very small, besides the well known gorrilas in the gerrit... == Ongoing from last week == * Changeset https://gerrit.wikimedia.org/r/#/c/14084/, bug https://bugzilla.wikimedia.org/show_bug.cgi?id=38705 about adding ll_local to the languagelinks table: as per discussion, there's a -2 from Tim Starling and further comments which were answered by Jeroen. Awaiting either further reply by Tim, or a merge. Development of core parts of our Phase I functionality is blocked by this, and not having this merged is causing hassle for people that want to setup their own working Wikidata repo-client install. * Changeset https://gerrit.wikimedia.org/r/#/c/14295/, bug https://bugzilla.wikimedia.org/show_bug.cgi?id=38705 about handling sites: Wikidata could benefit from some refactoring of the interlanguage and interwiki link handling in core. The idea is to migrate from the interwiki table to the new Sites facility. RobLa mentioned that Chad seems to be working in a similar direction, but haven't seen comments there. Besides that there were a few comments going back and forth. A Postgres-compatibility is being requested by saper, which will soon be added, but the question is are there any further issues that prevent us from merging? * Merging the Wikidata branch (ContentHandler) is still in discussion, see https://bugzilla.wikimedia.org/show_bug.cgi?id=38622. Daniel Kinzler hopes to have the discussion here on wikitech-l about this. Right now there seems a bit of a confusion due to Gerrit (if you look at the bug comments), but otherwise ongoing. == New in the list == * Changeset https://gerrit.wikimedia.org/r/#/c/8924/, 'usecheckboxes' option implemented for HTMLMultiSelectField. Helps us with displaying some preferences nicely with a scrollable multiselect-list. Hanging around for a while and needs review and merge. Some discussion last week. * New hook 'AfterFinalPageOutput' which is called at the end of OutputPage::output() https://gerrit.wikimedia.org/r/#/c/14303/: Got a little stuck and is required by the STTLanguage extension. (in parallel, this is in the Wikidata branch of core already, but would be removed from there if accepted here). * Linker::link() handles strings in $query parameter properly now, changeset: https://gerrit.wikimedia.org/r/#/c/14301/. Some concerns were raised whether this should be fixed in other places instead. Fixing this in all other places and especially testing it there could be rather expensive. This is required by the STTLanguage extension. If this isn't fixed, the function might fail in some places, e.g. on the latest changes page. (in parallel, this is in the Wikidata branch of core already, but would be removed from there if accepted here) * A change to the skin that will allow us to add the description of an item: changeset https://gerrit.wikimedia.org/r/#/c/17073/. There discussion and development is ongoing. I hope this helps, Cheers, Denny -- Project director Wikidata Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. +49-30-219 158 26-0 | http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Doxygen Not Working?
Hey, I'm not sure whether anybody was aware of this, but the Doxygen documentation at http://svn.wikimedia.org/doc has suddenly broken down. It's still online, but all the actual class and function definitions have disappeared. *--* *Tyler Romeo *(Parent5446) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Doxygen Not Working?
I'm not sure whether anybody was aware of this, but the Doxygen documentation at http://svn.wikimedia.org/doc has suddenly broken down. It's still online, but all the actual class and function definitions have disappeared. On IRC, 10:20 hashar Amgine_: I broke it 10:20 hashar will be fixed next time the doc is regenerated So it's known, and apparently fixed. -- Mark Holmquist Contractor, Wikimedia Foundation mtrac...@member.fsf.org http://marktraceur.info ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Try the new Wiki Loves Monuments Android App!
On Wed, Aug 1, 2012 at 11:39 PM, John Vandenberg jay...@gmail.com wrote: It hangs when talking to the satellites here in Oz. Probably because OZ isnt part of WLM?.. :( Sounds like a nasty bug. I'm pretty sure I can replicate this and know what's causing it but yes.. essentially it is due to a lack of monuments in your area :-( Have opened a bug = https://bugzilla.wikimedia.org/show_bug.cgi?id=38983 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] About outreach and tech events (as suggested by Sumana!)
Hi all, I'm Julien Dorra, I build creative communities using events. ex: http://museomix.com, http://artgameweekend.com, http://dorkbotparis.org, http://codinggouter.org. After a short discussion with Adrienne Alix from Wikimedia France, I took my chances and applied for the new role of Engineering Outreach Coordinator a few days ago!! Wish me luck!! (It's basically what I'm doing here in France with maybe the difference that we mix devs and non-devs, like designers and others professionals. We found that mixing is good for the cohesiveness of the communities built out of the events, because they are issue-oriented communities, mostly. Doing it for Wikimedia would be a dream job :) I also got a very nice answer from Sumana, encouraging me to email this list with proposals/ideas of what the Wikimedia community ought to be doing in term of engineering outreach. This application is a great occasion (excuse??) for me to divert some time and better understand the tech-side of the wikimedia community. I have collaborated with the non-tech side of the french community on issues like museum innovation and photography, but never directly with the tech-side of the community. I read with great interest the draft Wikimedia Engineering/2012-13 Goals ( http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals). It's super-rich and very exciting in term of focus. - - So, I wanted to start with a couple of questions I was curious about: 1. In term of outreach to engineers, devs or other technical talents, in your experience is there a specific community that is harder to reach to than others for Wikimedia? 2. Also, would like to see even more effort toward the students? (as in the future professionals!). What about the web startuppers? (AFAISee in Paris, they don't really consider Wikimedia as a software project.) 3. Do you sometimes think there is not enough ux designers on this list? And during hackatons? What about other skills? - - Then, to engage the conversation further, I wanted to test on you some specific ideas around hackatons and technical events ;-) The wider issue of testing, of setting up a more robust test culture is one of the key goals for 2012-2013, if I understand well. I personally know at least 3 developers that are passionate about testing, love to evangelize Test Driven Dev, and that might attend a test-oriented, or TDD-oriented event – but they would probably *not* attend a Wikimedia or MediaWiki generalist event. They have so many event to attend! They even organize events themselves… These 3 devs I know personnaly are the kind of test-oriented mentors we want to be part of the wikimedia community, if for a weekend or a week, because they are good at mentoring and showing the path to others. So, how can we bring them in? That made me (re)think about the limits of generic events, and the importance of issue-oriented event. The idea I would like to put up to discussion would be to organize more fine grained events around specific issues: «Testing Wikipedia» could be a nice catchy name for a series for events in various cities around TDD, with experienced dev mentoring less experienced community members, etc. Even if the experts come and go, everybody learn, some test and process get done, and the community grow and learn. Another issue is engaging other orgs, so why not engage startups: «Wikimedia for fun and profit!» Ok, this title is a joke -- but we should do a series of events focused on encouraging startups to build products on top of MediaWiki, APIs and Wikipedia sites. The rationale here is that the more startups invest on the wikimedia tech, the more they contribute in return. The documentation of MediaWiki is also an issue. Let's not wait to have a big team to launch more sprints, let's the sprints build the team: «DocDocDc Sprints» Realspace events are a powerful way to focus people on a goal. So to build a stronger documentation team, we could start designing an engaging and inclusive event format, setting up dates and places for a series of events. That could boost interest, and gather people that wouldn't have think of helping on MediaWiki. Of course the challenge is to keep the momentum going in between realspace sprints. So that means building an strong doc community online too. Obviously, setting up events, even small ones, takes a lot of effort! Scaling them can seems too much to do, too, when resources are limited. The good news is that we have successful examples of worldwide scaled event formats, like Startup weekend, Dorkbot. It's doable. And the rewards can be huge. So the strategy here would be to kickstart local chapters with recipes for events and by connecting them with I call 'serial-collaborators', (people that love to attend hackatons and creative weekends - they know a lot about these events, and are precious resource for advice and support). Identifying and contacting partners and places usually helps a lot, too, for helping
Re: [Wikitech-l] Wikidata blockers overview
And drop the following one, it was just abandoned after internal discussion. Yay, less work! 2012/8/2 Denny Vrandečić denny.vrande...@wikimedia.de: * Changeset https://gerrit.wikimedia.org/r/#/c/14084/, bug https://bugzilla.wikimedia.org/show_bug.cgi?id=38705 about adding ll_local to the languagelinks table: as per discussion, there's a -2 from Tim Starling and further comments which were answered by Jeroen. Awaiting either further reply by Tim, or a merge. Development of core parts of our Phase I functionality is blocked by this, and not having this merged is causing hassle for people that want to setup their own working Wikidata repo-client install. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikidata blockers overview
Hi Denny, Thanks for the update! More inline... On Thu, Aug 2, 2012 at 9:28 AM, Denny Vrandečić denny.vrande...@wikimedia.de wrote: == Ongoing from last week == [...] * Changeset https://gerrit.wikimedia.org/r/#/c/14295/, bug https://bugzilla.wikimedia.org/show_bug.cgi?id=38705 about handling sites: Wikidata could benefit from some refactoring of the interlanguage and interwiki link handling in core. The idea is to migrate from the interwiki table to the new Sites facility. RobLa mentioned that Chad seems to be working in a similar direction, but haven't seen comments there. Besides that there were a few comments going back and forth. A Postgres-compatibility is being requested by saper, which will soon be added, but the question is are there any further issues that prevent us from merging? This one probably deserves its own thread on the list, which you all probably shouldn't wait for me to start (please don't reply to this without changing the subject) * Merging the Wikidata branch (ContentHandler) is still in discussion, see https://bugzilla.wikimedia.org/show_bug.cgi?id=38622. Daniel Kinzler hopes to have the discussion here on wikitech-l about this. Right now there seems a bit of a confusion due to Gerrit (if you look at the bug comments), but otherwise ongoing. Looking forward to the discussion. I spoke with Tim last night about this one, so I'm glad things are moving now. I'm a little dismayed that it was possible to scramble Gerrit like it was. == New in the list == * Changeset https://gerrit.wikimedia.org/r/#/c/8924/, 'usecheckboxes' option implemented for HTMLMultiSelectField. Helps us with displaying some preferences nicely with a scrollable multiselect-list. Hanging around for a while and needs review and merge. Some discussion last week. Andrew totally cookie-licked this one, which I just pointed out to him in person. You have my blessing to set up a cron job to remind him to follow through :-) * New hook 'AfterFinalPageOutput' which is called at the end of OutputPage::output() https://gerrit.wikimedia.org/r/#/c/14303/: Got a little stuck and is required by the STTLanguage extension. (in parallel, this is in the Wikidata branch of core already, but would be removed from there if accepted here). Looks like there's a -1 on this one as of this writing. * Linker::link() handles strings in $query parameter properly now, changeset: https://gerrit.wikimedia.org/r/#/c/14301/. Some concerns were raised whether this should be fixed in other places instead. Fixing this in all other places and especially testing it there could be rather expensive. This is required by the STTLanguage extension. If this isn't fixed, the function might fail in some places, e.g. on the latest changes page. (in parallel, this is in the Wikidata branch of core already, but would be removed from there if accepted here) If you all are blocked, the short term fix is to fix your usage of this API, but not worry about enforcing the array convention everywhere. If you have code that takes this variable as input, that's probably where the backwards-compatibility cruft should temporarily go. What would be a better core change is a test there marking use of string as deprecated, so that we can start cleaning up the deprecation warnings. * A change to the skin that will allow us to add the description of an item: changeset https://gerrit.wikimedia.org/r/#/c/17073/. There discussion and development is ongoing. Okee doke. Rob ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About outreach and tech events (as suggested by Sumana!)
Hi all, I'm Julien Dorra, I build creative communities using events. ex: http://museomix.com, http://artgameweekend.com, http://dorkbotparis.org, http://codinggouter.org. After a short discussion with Adrienne Alix from Wikimedia France, I took my chances and applied for the new role of Engineering Outreach Coordinator a few days ago!! Wish me luck!! (It's basically what I'm doing here in France with maybe the difference that we mix devs and non-devs, like designers and others professionals. We found that mixing is good for the cohesiveness of the communities built out of the events, because they are issue-oriented communities, mostly. Doing it for Wikimedia would be a dream job :) I also got a very nice answer from Sumana, encouraging me to email this list with proposals/ideas of what the Wikimedia community ought to be doing in term of engineering outreach. This application is a great occasion (excuse??) for me to divert some time and better understand the tech-side of the wikimedia community. I have collaborated with the non-tech side of the french community on issues like museum innovation and photography, but never directly with the tech-side of the community. I read with great interest the draft Wikimedia Engineering/2012-13 Goals ( http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals). It's super-rich and very exciting in term of focus. - - So, I wanted to start with a couple of questions I was curious about: 1. In term of outreach to engineers, devs or other technical talents, in your experience is there a specific community that is harder to reach to than others for Wikimedia? 2. Also, would like to see even more effort toward the students? (as in the future professionals!). What about the web startuppers? (AFAISee in Paris, they don't really consider Wikimedia as a software project.) 3. Do you sometimes think there is not enough ux designers on this list? And during hackatons? What about other skills? - - Then, to engage the conversation further, I wanted to test on you some specific ideas around hackatons and technical events ;-) The wider issue of testing, of setting up a more robust test culture is one of the key goals for 2012-2013, if I understand well. I personally know at least 3 developers that are passionate about testing, love to evangelize Test Driven Dev, and that might attend a test-oriented, or TDD-oriented event – but they would probably *not* attend a Wikimedia or MediaWiki generalist event. They have so many event to attend! They even organize events themselves… These 3 devs I know personnaly are the kind of test-oriented mentors we want to be part of the wikimedia community, if for a weekend or a week, because they are good at mentoring and showing the path to others. So, how can we bring them in? That made me (re)think about the limits of generic events, and the importance of issue-oriented event. The idea I would like to put up to discussion would be to organize more fine grained events around specific issues: «Testing Wikipedia» could be a nice catchy name for a series for events in various cities around TDD, with experienced dev mentoring less experienced community members, etc. Even if the experts come and go, everybody learn, some test and process get done, and the community grow and learn. Another issue is engaging other orgs, so why not engage startups: «Wikimedia for fun and profit!» Ok, this title is a joke -- but we should do a series of events focused on encouraging startups to build products on top of MediaWiki, APIs and Wikipedia sites. The rationale here is that the more startups invest on the wikimedia tech, the more they contribute in return. The documentation of MediaWiki is also an issue. Let's not wait to have a big team to launch more sprints, let's the sprints build the team: «DocDocDc Sprints» Realspace events are a powerful way to focus people on a goal. So to build a stronger documentation team, we could start designing an engaging and inclusive event format, setting up dates and places for a series of events. That could boost interest, and gather people that wouldn't have think of helping on MediaWiki. Of course the challenge is to keep the momentum going in between realspace sprints. So that means building an strong doc community online too. Obviously, setting up events, even small ones, takes a lot of effort! Scaling them can seems too much to do, too, when resources are limited. The good news is that we have successful examples of worldwide scaled event formats, like Startup weekend, Dorkbot. It's doable. And the rewards can be huge. So the strategy here would be to kickstart local chapters with recipes for events and by connecting them with I call 'serial-collaborators', (people that love to attend hackatons and creative weekends - they know a lot about these events, and are precious resource for advice and support).
[Wikitech-l] WMF Site nginx problem?
I'm getting 502 bad gateways / nginx error from all attempts to hit WMF sites including en.wikipedia and wikimedia.org and others, right now... -- -george william herbert george.herb...@gmail.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
...And back for me. On Thu, Aug 2, 2012 at 2:17 PM, George Herbert george.herb...@gmail.com wrote: I'm getting 502 bad gateways / nginx error from all attempts to hit WMF sites including en.wikipedia and wikimedia.org and others, right now... -- -george william herbert george.herb...@gmail.com -- -george william herbert george.herb...@gmail.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
On 02/08/2012 22:26, George Herbert wrote: ...And back for me. On Thu, Aug 2, 2012 at 2:17 PM, George Herbert george.herb...@gmail.com wrote: I'm getting 502 bad gateways / nginx error from all attempts to hit WMF sites including en.wikipedia and wikimedia.org and others, right now... -- -george william herbert george.herb...@gmail.com From #wikimedia-operations [22:24:08] Lcawte What happened? [22:24:43] LeslieCarr you know, everyone else gets vacation, the wiki takes a 5 minute bathroom break and everyone's upset ! [22:26:13] LeslieCarr in reality, looks like a bad squid config was pushed, then when it was rolled back, the site came back up ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About outreach and tech events (as suggested by Sumana!)
«Testing Wikipedia» could be a nice catchy name for a series for events in various cities around TDD, with experienced dev mentoring less experienced community members, etc. Even if the experts come and go, everybody learn, some test and process get done, and the community grow and learn. I'm the QA Lead for WMF, and I can say a little about what we've done so far, and things we'd like to do in the future. In May we collaborated with the Weekend Testers (Americas)[1] in an online test exercise to validate the new frequent rollout schedule of new software to all of the Wikipedia wikis. WTA meets on the first Saturday of every month, and conveniently, we had deployed the latest version to all of the wikis except English Wikipedia at that time, so we had quite a few professional software testers looking for anomalies in the new wiki software, using English Wikipedia as an oracle for correct behavior. It went well, but the scope was a bit ambitious, so we were lucky that the testers were very professional. In June we collaborated online with Openhatch.org to validate a near-final version of the new Article Feedback system. This was a much more focused exercise, and it went really well, we found a number of real issues with AFT that we were able to address before rolling it out widely. Some of participants from the previous test event with WTA helped out, so there was a mix of skill and experience among the testers, and several people remarked about how they had not expected to have so much fun. We would like to do some more sessions like these. One strong suggestion is to have a test event addressing outstanding Bugzilla issues for particular extensions. This could be an ongoing exercise, either in collaboration with other groups or as a pure-Wikipedia exercise. I have discussed doing this with the leader of WTA who is also one of the instructors of the Association for Software Testing[2] 'Bug Advocacy' course, but haven't pursued it much farther than that. In the long run we would like these sorts of exercises to foster a critical spirit among Wikipedia users, improve the quality of issue reporting and follow-up in Bugzilla, build liaisons with communities like WTA and Openhatch that would not otherwise exist, and foster a general sense that all the Wikipedia software can be tested at any time, and Bugzilla is always open for all sorts of improvements. So now to address what you actually said :-)... Although I've read my share of unit tests in many languages, I'm not expert at it, nor do I have a background in PHP. But I am nearly certain that our existing unit test arrangements could be improved in many ways. Threads on the subject show up on this list from time to time, and I think I can say accurately that we could make better use of mocks and stubs instead of e.g. real database tables, we could do more TDD, our code coverage is probably not very high, and improving that coverage would entail not only writing more unit tests, but also refactoring existing code to make it more testable. I think improving unit testing would be a great ongoing project. [1] http://weekendtesting.com/chapters/america [2] http://www.associationforsoftwaretesting.org/training/courses/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
On 2 August 2012 22:38, Lewis Cawte lewisca...@googlemail.com wrote: From #wikimedia-operations [22:24:08] Lcawte What happened? [22:24:43] LeslieCarr you know, everyone else gets vacation, the wiki takes a 5 minute bathroom break and everyone's upset ! [22:26:13] LeslieCarr in reality, looks like a bad squid config was pushed, then when it was rolled back, the site came back up This outage just got a press query from the BBC Newsroom! Out of interest (if anyone has it quickly to hand), what is our uptime like? I recall it came through email in the last week or two, but I can't find the message ... - d. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
On Thu, Aug 2, 2012 at 6:07 PM, David Gerard dger...@gmail.com wrote: This outage just got a press query from the BBC Newsroom! Out of interest (if anyone has it quickly to hand), what is our uptime like? I recall it came through email in the last week or two, but I can't find the message ... There's some #s at http://status.wikimedia.org/ but they don't go back in time too far. -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About outreach and tech events (as suggested by Sumana!)
Thanks Bawolff for your feedback! It's great, as it helps me think even more about it! I gather from what you said above that your specialty is in-person events, More the combination of in-person events with unfocused (unaware of themselves) existing web communities. OrsayCommons for example (more here: http://side-creative.ncl.ac.uk/communities/symposium11/julien-dorra/) was actually a series of live photo-streaming events happening both inside the Orsay museum, and, of course, on Twitter. Online and offline were indissociable in event series, and it allowed us to focus a community of museum photo lovers against the ban on picture taking in this museum. Also, my co-organizers and I always try to include online participants during the in-person hackatons event. It's hard! It's actually a huge part of the new event organization for Museomix 2012 (random fact: we had two wikipedians at Museomix 2011) So there is multiple ways to combine realspace and cyberspace: you can build your realspace event as a focal moment where participants produce and share online. You could design your event with hooks and touchpoints for online participants. but perhaps it would be interesting to have virtual events of some sort via IRC focusing on a very fine grained topic. I'm not sure how exactly that would work, but I think it might be interesting. Virtual events could take the form of challenges like Ludum Dare, or the monthly Mozilla Dev derby. I would argue that the strength of online is in asynchronous events, where people from all timezone can participate. Having a continuously open channel during a challenge is a good idea. People can then come and ask question, be mentored by some 'elders'… One thing that I'd love to see exploited more is Etherpad-like (or Google Docs-like) simultaneous, realtime writing. The simple act of writing collectively in realtime is exhilarating and put you in a incredible flow state. I think there is a lot of potential for documentation sprints here. If you never tried to write an article or a blog post in realtime with one or more others, you should do it! It's a beautiful experience that is literally impossible to live with paper or a single computer. (Related to realtime writing: Unishared is a very young startup that want to push every university students to take class notes live, collaboratively and publicly! Nice goal) I personally think (and I imagine many people think differently), that perhaps retention rather than recruitment is what should be focused on. Yes, retention is a key issue. Also, ramping up people from casual participation to more and more complex involvement. Giving people a path, new goals, new focus. In any case, any community also have to account for people leaving or more frequently just gradually winding down their participation (like, when they become parents, or take a new job). I had that experience myself in 2009, when I was very active in the local Drupal community, helping gather people, find sponsors for a big event -- and then had to step down from my community roles, because of… my second daughter :-) After all, we power wikipedia. Wikipedia has a huge user base, some of which know how to program, and many of those will at the very least look our way, even if they don't explicitly drop in and say hi. Those are the people we should attract. Even though probably 90% of our contributor base come from a wiki project, I still think this is a vastly untapped pool. People generally join open source projects to scratch an itch (so the saying goes). The Wikipedians (not to mention the oft neglected sister projects) are the one's who would be itchy. I remember John Resig (from jQuery) saying: Treat every user as a potential contributor. Very Wikipedian, isn't it? Wikipedia does of course treat every reader as a contributor by nature for the content!! * Question for you all: On the technical side, from your experience, what would make an user/visitor/editor feel she/he *is* a potential tech contributor, not just a potential content contributor? In many ways I've noticed a trend where it seems people on some projects, especially en Wikipedia, treat the foundation as more of a host than an entity meant to serve their interests. As a result they start to feel that MediaWiki is a product that is being developed for them (in a similar way how something like facebook or google is developed for its users) rather than by them (or by their community). Maybe there was always such setiment, and I just never noticed it in earlier times, but I find such sentiment disturbing. I think in order to best reach out to new contributors, we need to start at home so to speak. Yes, from my experience too people tend to rapidly put themselves in consumer mode :-) I suppose it's (for the moment!) the default mode and we have to make a conscious and specific effort to get them out of that consumer mode. * Question for you all: do you
Re: [Wikitech-l] Doxygen Not Working?
On 8/2/12 10:38 AM, Mark Holmquist wrote: I'm not sure whether anybody was aware of this, but the Doxygen documentation at http://svn.wikimedia.org/doc has suddenly broken down. It's still online, but all the actual class and function definitions have disappeared. On IRC, 10:20 hashar Amgine_: I broke it 10:20 hashar will be fixed next time the doc is regenerated So it's known, and apparently fixed. I had to give up using those pages anyway due to the massive inclusion graphs :( Ryan Kaldari ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
On 2 August 2012 23:12, Jeremy Baron jer...@tuxmachine.com wrote: There's some #s at http://status.wikimedia.org/ but they don't go back in time too far. That's great :-) Here's what I sent them. Seems Wikipedia is *rather important* to the BBC newsroom at the moment ... - d. -- Forwarded message -- From: David Gerard dger...@gmail.com Date: 2 August 2012 23:23 Subject: Re: Query from the BBC Newsroom To: [snip] Technical hiccups happen occasionally, unfortunately :-) Most pass momentarily, more noteworthy ones tend to get noted on the technical mailing list. I would guess you experienced the problem detailed here: http://lists.wikimedia.org/pipermail/wikitech-l/2012-August/062111.html There's a status page here: http://status.wikimedia.org/ Someone emailed our uptime over the last year to one of the lists recently, but I can't find it ... We're not perfect - as a charity, we run on a shoestring - but we do our best and admit our hiccups and errors :-) - d. On 2 August 2012 22:37, [snip] wrote: Dear Mr Gerard, We noticed that Wikipedia was down for a short period of time this evening. We wondered if there was a specific problem. If you could either ring or email me that would be appreciated. Regards, [snip] Tel No:[snip] http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Captcha for non-English speakers II
On Thu, Aug 2, 2012 at 1:59 AM, Pau Giner pgi...@wikimedia.org wrote: I made some mockups to illustrate some of the ideas on captchas that could be less problematic for non-English speakers, improve the general UX and rely on images from commons. - Panorama captcha: http://commons.wikimedia.org/wiki/File:Panorama-captcha-idea.png Based on tagging parts of a panorama picture with the appropriate word (in the UI language or Basic English words). - 'Who is who' captcha: http://commons.wikimedia.org/wiki/File:Find-all-captcha-idea.png Based on finding from a set of similar images the ones that fit a specific criteria (with an image describing also the criteria). - 'Find the different' captcha: http://commons.wikimedia.org/wiki/File:Find-the-different-captcha-idea.png Based on finding the image that is different from a set of images. These captchas will probably generate new problems for the technical side, require adjustments to reduce the chance of a machine to solve them, or may just be unfeasible to generate, but I wanted to provide these ideas in case anybody else may use it as a base for improve on any technical weakness they may have and make them at least as hard to solve for a machine as text-based captchas are. Thanks Pau, that's really helpful. :) Since we've progressed from just the idea stage to mockups, but we still have a lot of different options, I've started an RfC on MediaWiki.org where we can list all the issues and potential solutions. I don't personally think we need to come to a consensus right now, but CAPTCHAs are going to keep coming up even if no action is taken in the short term, so we should document all our ideas. https://www.mediawiki.org/wiki/Requests_for_comment/CAPTCHA Steven ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMF Site nginx problem?
As a guess... They probably wanted to make sure it was accidental and not some denial of service attack (i.e., newsworthy). Were say Anonymous to jump on us for some unforseeable reason, it would be newsworthy, and I am sure the newsies would come running to everyone ever publicly identified as knowing anything about ops at the site... -george On Thu, Aug 2, 2012 at 3:27 PM, David Gerard dger...@gmail.com wrote: On 2 August 2012 23:12, Jeremy Baron jer...@tuxmachine.com wrote: There's some #s at http://status.wikimedia.org/ but they don't go back in time too far. That's great :-) Here's what I sent them. Seems Wikipedia is *rather important* to the BBC newsroom at the moment ... - d. -- Forwarded message -- From: David Gerard dger...@gmail.com Date: 2 August 2012 23:23 Subject: Re: Query from the BBC Newsroom To: [snip] Technical hiccups happen occasionally, unfortunately :-) Most pass momentarily, more noteworthy ones tend to get noted on the technical mailing list. I would guess you experienced the problem detailed here: http://lists.wikimedia.org/pipermail/wikitech-l/2012-August/062111.html There's a status page here: http://status.wikimedia.org/ Someone emailed our uptime over the last year to one of the lists recently, but I can't find it ... We're not perfect - as a charity, we run on a shoestring - but we do our best and admit our hiccups and errors :-) - d. On 2 August 2012 22:37, [snip] wrote: Dear Mr Gerard, We noticed that Wikipedia was down for a short period of time this evening. We wondered if there was a specific problem. If you could either ring or email me that would be appreciated. Regards, [snip] Tel No:[snip] http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- -george william herbert george.herb...@gmail.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About outreach and tech events (as suggested by Sumana!)
Wow, thanks Chris for this great feedback! In May we collaborated with the Weekend Testers (Americas)[1] I love the name! They also seem to have an interesting history in term of organic community growth. In June we collaborated online with Openhatch.org participants from the previous test event with WTA helped out, so there was a mix of skill and experience among the testers, and several people remarked about how they had not expected to have so much fun. I'm very interested in reading more about this session! What would you say was the main expertise/know-how that the OpenHatch team brought? How would you say they brought the fun in testing? Also, does the OpenHatch process guide people of varied skills, or did you set up a set of pre-requisites? We would like to do some more sessions like these. One strong suggestion is to have a test event addressing outstanding Bugzilla issues for particular extensions. This could be an ongoing exercise, either in collaboration with other groups or as a pure-Wikipedia exercise. A regular test day could anchor the idea. Maybe Monthly Test 13th, so there would be added luck ;-) About the two events you had, did you somehow also regroup in-person, say 2 or 3 testers together, or was everybody at home? I think improving unit testing would be a great ongoing project. I'm probably brain-washed by the test driven developers I met, but I'm under the impression that there is no downside to better tests! (I'm a purely hobbyist coder myself, learned when I was a kid and along the way, so I took a *lot* of bad patterns and habits. Never learned to write a test before writing functional code, obviously. But I'm seeing the way, now ;-) Julien ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] linker
hello,
I'm reading Linker.php source.
I want to take a wikitext like this [{{fullurl:{{PAGENAME}}|
action=edit}} Edit this page]
edit it to get:
index.php?title=AddArticleaction=editpreload=Template:one
And then I'd like to get only the href content in a php variable.
In Linker.php I have found a lot of private functions.
Can you help me?
I'm going to user $wgOut-redirect($url); for an internal link.
regards,
ADM
signature.asc
Description: This is a digitally signed message part
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About outreach and tech events (as suggested by Sumana!)
Julian,Welcome. Here are my ideas: 1. Tag along - hold an event before or after a larger event, such as OSCON. This event might even be a charity event. Semi-example: http://railsconf.austinonrails.org/ignite 2. Create videos of ways to contribute. 3. Create a link/list of small changes/bugs - spelling errors, change copyright everywhere, etc. 4. Use Google Hangouts to hold regular events. Use Skype/etc if video is too much bandwidth. 5. Hold a contest. Here is one that just finished a month-long contest: http://rubyosc.com/ 6. Dual/joint hack event with other projects: Bugzilla, Mozilla, Mysql, php, perl, ... By the way, here is my collection of hack days/etc that I have been collecting for the 13 months: https://sites.google.com/site/patchworklabs/ Help this helps,Al Snow From: juliendo...@juliendorra.com Date: Thu, 2 Aug 2012 20:16:47 +0200 To: wikitech-l@lists.wikimedia.org CC: adrienne.a...@wikimedia.fr Subject: [Wikitech-l] About outreach and tech events (as suggested by Sumana!) Hi all, I'm Julien Dorra, I build creative communities using events. ex: http://museomix.com, http://artgameweekend.com, http://dorkbotparis.org, http://codinggouter.org. After a short discussion with Adrienne Alix from Wikimedia France, I took my chances and applied for the new role of Engineering Outreach Coordinator a few days ago!! Wish me luck!! (It's basically what I'm doing here in France with maybe the difference that we mix devs and non-devs, like designers and others professionals. We found that mixing is good for the cohesiveness of the communities built out of the events, because they are issue-oriented communities, mostly. Doing it for Wikimedia would be a dream job :) I also got a very nice answer from Sumana, encouraging me to email this list with proposals/ideas of what the Wikimedia community ought to be doing in term of engineering outreach. This application is a great occasion (excuse??) for me to divert some time and better understand the tech-side of the wikimedia community. I have collaborated with the non-tech side of the french community on issues like museum innovation and photography, but never directly with the tech-side of the community. I read with great interest the draft Wikimedia Engineering/2012-13 Goals ( http://www.mediawiki.org/wiki/Wikimedia_Engineering/2012-13_Goals). It's super-rich and very exciting in term of focus. - - So, I wanted to start with a couple of questions I was curious about: 1. In term of outreach to engineers, devs or other technical talents, in your experience is there a specific community that is harder to reach to than others for Wikimedia? 2. Also, would like to see even more effort toward the students? (as in the future professionals!). What about the web startuppers? (AFAISee in Paris, they don't really consider Wikimedia as a software project.) 3. Do you sometimes think there is not enough ux designers on this list? And during hackatons? What about other skills? - - Then, to engage the conversation further, I wanted to test on you some specific ideas around hackatons and technical events ;-) The wider issue of testing, of setting up a more robust test culture is one of the key goals for 2012-2013, if I understand well. I personally know at least 3 developers that are passionate about testing, love to evangelize Test Driven Dev, and that might attend a test-oriented, or TDD-oriented event – but they would probably *not* attend a Wikimedia or MediaWiki generalist event. They have so many event to attend! They even organize events themselves… These 3 devs I know personnaly are the kind of test-oriented mentors we want to be part of the wikimedia community, if for a weekend or a week, because they are good at mentoring and showing the path to others. So, how can we bring them in? That made me (re)think about the limits of generic events, and the importance of issue-oriented event. The idea I would like to put up to discussion would be to organize more fine grained events around specific issues: «Testing Wikipedia» could be a nice catchy name for a series for events in various cities around TDD, with experienced dev mentoring less experienced community members, etc. Even if the experts come and go, everybody learn, some test and process get done, and the community grow and learn. Another issue is engaging other orgs, so why not engage startups: «Wikimedia for fun and profit!» Ok, this title is a joke -- but we should do a series of events focused on encouraging startups to build products on top of MediaWiki, APIs and Wikipedia sites. The rationale here is that the more startups invest on the wikimedia tech, the more they contribute in return. The documentation of MediaWiki is also an issue. Let's not wait to have a big team to launch more sprints, let's the sprints build the team: «DocDocDc Sprints» Realspace
[Wikitech-l] Several Bug Triage Questions
Hi - I'm Al Snow. Applied for the Bug Wrangler position a week ago. Started today setting up accounts and reading about the internals. Also did some archaeology on Bugzilla and have some questions.Appears CLOSED status is not used much - do we stop at RESOLVED or VERIFIED status? How about PRIORITY? See lots of UNPRIORITIZED that have a active (ACTIVE, RESOLVED) status. Will double-check docs, but unclear how DUPLICATE tickets are set to CLOSED.How long does a ticket stay in one status before we need to flag it? Created a couple of personal Bugzilla monitors (whiners), but any help with bug triage dashboard/graphs/reports/wizards/extensions would be appreciated. Also saw reference to Bug Squad in 2012-2013 Goals. (Thanks - Julian) ..My bug triage ideas, beside the Bug Squad, include looking into:Semi-automatic detection of duplicates (see Bugzilla e-group)Semi-automatic assignment of Assignee (saw some external references)Create wizard to improve bug creation (similar to Google's BITE project ;) Wrestle that bug to the ground!Al PS. Today's notes - if you have questions about what I found in the last several days. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] linker
Hey,
Somebody correct me if I'm wrong, but I believe the function you're looking
for is
$title = Title::newFromText( 'AddArticle' );
$title-getLocalURL( array( 'action' = 'edit', 'preload' = 'Template:one'
) );
*--*
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Thu, Aug 2, 2012 at 8:06 PM, linuxlover linuxloverst...@gmail.comwrote:
hello,
I'm reading Linker.php source.
I want to take a wikitext like this [{{fullurl:{{PAGENAME}}|
action=edit}} Edit this page]
edit it to get:
index.php?title=AddArticleaction=editpreload=Template:one
And then I'd like to get only the href content in a php variable.
In Linker.php I have found a lot of private functions.
Can you help me?
I'm going to user $wgOut-redirect($url); for an internal link.
regards,
ADM
___
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] Several Bug Triage Questions
I don't know much about why we stop at RESOLVED, but what is most likely the preferred path would be to have some sort of QA team that goes through all RESOLVED bugs, tests them, and marks them as VERIFIED accordingly. Then finally it can be closed. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Thu, Aug 2, 2012 at 9:35 PM, Al Snow jas...@hotmail.com wrote: Hi - I'm Al Snow. Applied for the Bug Wrangler position a week ago. Started today setting up accounts and reading about the internals. Also did some archaeology on Bugzilla and have some questions.Appears CLOSED status is not used much - do we stop at RESOLVED or VERIFIED status? How about PRIORITY? See lots of UNPRIORITIZED that have a active (ACTIVE, RESOLVED) status. Will double-check docs, but unclear how DUPLICATE tickets are set to CLOSED.How long does a ticket stay in one status before we need to flag it? Created a couple of personal Bugzilla monitors (whiners), but any help with bug triage dashboard/graphs/reports/wizards/extensions would be appreciated. Also saw reference to Bug Squad in 2012-2013 Goals. (Thanks - Julian) ..My bug triage ideas, beside the Bug Squad, include looking into:Semi-automatic detection of duplicates (see Bugzilla e-group)Semi-automatic assignment of Assignee (saw some external references)Create wizard to improve bug creation (similar to Google's BITE project ;) Wrestle that bug to the ground!Al PS. Today's notes - if you have questions about what I found in the last several days. ___ 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
