Re: [Wikitech-l] Proposed release timeline
On Wed, 2013-09-25 at 21:48 -0400, Mark A. Hershberger wrote: According to the Version lifecycle[1], MediaWiki 1.22 is slated for release on November 30th, at the very latest. In that vein, we've come up with a timeline for the release[2]. If we use this timeline and shoot for the latest date, we'll need to start the release process no later than October 19th. Please look over the timeline and the TBD section and provide feedback. Quick Bugzilla info: Currently 24 open tickets in Bugzilla have Target Milestone set to 1.22.0: https://bugzilla.wikimedia.org/buglist.cgi?target_milestone=1.22.0%20releaseproduct=MediaWikiresolution=--- 15 of them have patches (some need review, some rework, ...). Keep in mind that anybody can set the Target Milestone, so some of them might be wishful thinking instead and could be reset. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Inline bug report history in Bugzilla
Hola, if you have found yourself clicking the History link in Bugzilla tickets way too often (to check who has set the Priority, or who has changed the assignee and when), Bugzilla now has an opt-in to display such metadata changes inline, between the comments of the bug report. You can enable this by going to https://bugzilla.wikimedia.org/userprefs.cgi?tab=settings and setting When viewing a bug, show all bug activity to On. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
On Mon, 2013-10-07 at 03:00 +, reporter wrote: MediaWiki Bugzilla Report for September 30, 2013 - October 07, 2013 Reports created this week: 608 The number is exceptionally large due to importing ~340 Pywikibot tickets from Sourceforge to Bugzilla (see bug 52692 for more info). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New API options problem
Hi Aran, On Wed, 2013-10-09 at 16:53 -0300, Aran wrote: I'm trying to set a user's realname option on a local wiki (1.21.1) using the API. I can login successfully, confirm my login token fine and then I can get the options token and make the call to change options using the token. I get Success returned when I change the realname (or any other valid option such as password etc). But when I look in the user's preferences, or directly in the user db table there's nothing changed. Could you provide the exact command, so somebody else could try to reproduce? andre (Also, for future reference, please avoid replying to other emails and replacing the subject line with your topic. Start a new thread instead.) -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] HTTP 500 error at tools.wmflabs.org
On Wed, 2013-10-09 at 12:53 +0100, Magnus Manske wrote: It's on-and-off again. Two tools of mine have been identified as the culprits, apparently hogging all resources. Which is strange, because they worked fine for months. Personally, I suspect an underlying problem (nfs, PHP setup, like that). The two tools are deactivated now, so if they alone were at fault, everything should work peachy. Thanks. For the records, this was also filed under https://bugzilla.wikimedia.org/show_bug.cgi?id=55498 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Google Code-in: are you in?
On Thu, 2013-10-10 at 11:11 -0700, Quim Gil wrote: I'm pretty sure that there is a task that most of us could mentor. It doesn't need to be related with the MediaWiki codebase. Come on, think harder! ;) I organized GNOME's participation in Google Code-In (and its predecessor GHOP) three times in the past. == Stuff that takes time when preparing / taking part == What takes most of the time for admins is 1) before contest starts, nag developers and community members to become mentors and to provide a large number of really well-defined and well-documented tasks which are not too small and not too big, and 2) when the contest is running, make sure mentors respond quickly. Students could come across as impatient due to Code-In's competition system (students get points for tasks, you cannot claim a new task until the old one has been reviewed and finished, and students with most points get a trip to Google HQ. Last time organizations had to agree that reviews must happen within 36 hours, also on weekends/holidays). This nagging often took me about an hour per day, every day. But maybe rules / ToS have changed again this year, don't know. == Aspects to consider whether to try or not == In 2012, GNOME did not apply for taking part. The reasons that I see are: 1) translation tasks were not allowed anymore, 2) Google reduced the number of orgs to 10 so preparation work might have not paid off in the end, 3) time spent mentoring students took often longer than if mentors did the task themselves, 4) tasks only take a few days (no creation of strong binding to mentor/org), 5) students often didn't stick with the org afterwards but maybe were more after t-shirt/money/Google invitation. These are the topics that I consider important to discuss before deciding. Of course, the setup and structure of Google Code-In might work totally well for other mentoring organizations, or communities that are less lazy and have more (wo)manpower than the GNOME one. ;-) andre PS: Lydia of WMDE organized GCI for KDE in 2012 who successfully took part, so her feedback on this thread could also be pretty helpful. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Inline bug report history in Bugzilla
On Fri, 2013-10-11 at 16:44 -0700, Quim Gil wrote: On 10/11/2013 03:37 PM, Andre Klapper wrote: I failed to make up my mind if it's helpful for the *majority* of Bugzilla users (reporters, testers, triagers, developers, managers) or if it might clutter the Comments view too much for some people, so I kept it as an opt-in setting. I'm happy to revise but don't know how I could find out. :) I think it's useful for some and instructive for the rest. Thanks everybody for the helpful feedback. Inline history functionality is enabled by default now for every user who is logged into Bugzilla. Bugzilla users can switch it off again by setting When viewing a bug, show all bug activity to Off on https://bugzilla.wikimedia.org/userprefs.cgi?tab=settings Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Google Code-in: are you in?
On Wed, 2013-10-16 at 13:40 +0800, Liangent wrote: Is Lua / ParserFunctions templating or Lua conversion, either generic (meta-templates / -modules) or for a specific purpose (requested by local community etc.), eligible as a task, in Code or User Interface category? I don't see why it should not be, if you feel able to mentor the student, if the task is well-defined, and if the timeframe works. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
On Fri, 2013-10-25 at 10:28 +0200, Željko Filipin wrote: Would anybody else like to see Top 5 bug report creators list, or is it just me? Feel free to file an enhancement request at http://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimediacomponent=Bugzilla And if somebody feels like hacking, the code is at operations/puppet.git/templates/misc/bugzilla_report.php andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Google Code-in: are you in?
Hi, On Tue, 2013-10-29 at 21:58 +0530, Aarti K. Dwivedi wrote: Most probably I am late but can we still add tasks or volunteer for mentoring? Thanks for your interest! Yes you can, and they are welcome! However I'd turn that into add tasks *AND* volunteer for mentoring, because having potential mentor(s) already defined for a task makes planning way easier. :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia Bugzilla Guided Bug Entry Form available
Since last Friday, Bugzilla has a guided bug entry form. Together with documentation at https://www.mediawiki.org/wiki/How_to_report_a_bug (which needs an update now) this should make it easier for users to create better bug reports. You can link to and access the guided form by attaching ?format=guided to the enter_bug.cgi URL, like e.g. https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimediacomponent=Bugzillaformat=guided If you don't pass product/component parameters in the URL link to https://bugzilla.wikimedia.org/enter_bug.cgi?format=guided the first page (where a bug reporter has to choose a product) still looks the same as usual. I would like to thank the WMF design team and community liaisons for reviews and early feedback. Happy bug reporting, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
In general: I am happy to change Bugzilla settings, whatever is agreed on in the end. On Wed, 2013-11-06 at 07:38 -0800, Rob Lanphier wrote: On Wed, Nov 6, 2013 at 5:24 AM, MZMcBride z...@mzmcbride.com wrote: Our Bugzilla installation at https://bugs.wikimedia.org/ currently restricts the capabilities of new users as a knee-jerk response to prior Bugzilla-related vandalism. There are further details at https://bugzilla.wikimedia.org/40497. As I recall, Mark Hershberger and Ariel Glenn were the ones that dealt with most of the aftermath of the attacks that we received that ultimately led to it being turned off. It was not a knee jerk response. We temporarily turned it off and turned it back on a few days later, only to have dozens (hundreds?) of bugs altered in a way that was not easily reversed. Bugzilla does not allow centrally reverting all actions by a specific person: https://bugzilla.mozilla.org/show_bug.cgi?id=735213 In consulting with the Bugzilla developers (I believe I may have sent a public mail about this to their list), their answer was essentially that Bugzilla was never designed for giving editbugs to untrusted users, and that by doing so, we had what was coming to us. [...] We can certainly do something different than what we're doing, though. It should be easy to get editbugs; just not so easy that a vandal can get it. Anyone have any ideas how to mitigate the vandalism problem? Refering to the recent problem in Wikimedia Bugzilla, setting the assignee field is only possible when having editbugs permissions. There are no permissions which are more fine-grained and I could not find a request upstream asking for a specific be able to change the assignee without editbugs permissions request (plus docs suck anyway, see https://bugzilla.mozilla.org/show_bug.cgi?id=481859 ). I have no good spontaneous idea how to solve this problem. My guess is hacking the code as described in http://www.bugzilla.org/docs/4.4/en/html/cust-change-permissions.html I've asked on the upstream mailing list: https://groups.google.com/forum/#!topic/mozilla.support.bugzilla/6GCB7ufa7nc The wider picture regarding vandalism: Related unresolved upstream bugs refering to blocking IPs: https://bugzilla.mozilla.org/show_bug.cgi?id=904698 https://bugzilla.mozilla.org/show_bug.cgi?id=536110 Mozilla Bugzilla had a spam problem a few days ago, and they ended up temporarily disabling account creation for specific domains *manually*, instead of trying to fix it properly in https://bugzilla.mozilla.org/show_bug.cgi?id=467763 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
On Thu, 2013-11-07 at 08:33 -0800, Chad wrote: On Wed, Nov 6, 2013 at 10:04 PM, Rob Lanphier ro...@wikimedia.org wrote: I like the idea of giving everyone who has editbugs the right to give other people the editbugs permission. That's certainly worth a try assuming it's possible to configure. I want to underscore this again. I think this is a great idea and I haven't seen any objections to it yet. Can we go ahead with this proposal? There seems to be sufficient support to grant users who have editbugs rights the permission to hand out (and revert) editbugs rights to/of other users. If we did this, users with editbugs rights can go to Links Administration Users, enter the email address of a user, and hand out editbugs to other users. However, the right to hand out editbugs rights to other users cannot be handed out recursively: If I give user X the right to hand out editbugs permissions to other users, then user X can only give editbugs to user Y him/herself, but user Y will NOT automatically be able to hand out editbugs to user Z. For the records: Currently 14744 Wikimedia Bugzilla users have editbugs permissions (so this is something to do via an SQL command instead of me clicking myself to death in Bugzilla's web interface). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
On Thu, 2013-11-07 at 08:28 -0800, Quim Gil wrote: In order to get somewhere with this discussion, it would be useful to know the current practice of other free software projects, using Bugzilla or not. As a newcomer, can I assign bugs to myself in GNOME, KDE, Ubuntu, Debian... etc? In case any projects which use Bugzilla allow this: I just learned it's a bad idea [1]. The assignee of a bug report who is not member of the editbugs group defacto has editbugs permissions for that specific bug report. So you could mass-assign bug reports to you in order to bypass your missing editbugs permissions. andre [1] https://groups.google.com/forum/#!topic/mozilla.support.bugzilla/6GCB7ufa7nc -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
On Thu, 2013-11-07 at 12:06 -0500, C. Scott Ananian wrote: I'm a little puzzled here: this whole discussion is because new owners want to have the bug actually assigned to them, instead of just commenting, I'm working on this in the bug? Let's look at the github model -- there's no assignment at all. I just file a bug, maybe make some comments on it to say I'm working on it, and some time later I submit a pull request referencing the bug and saying, I fixed it. That seems to work fine for collaboration, and offers no roadblocks. Maybe we should be turning off bugzilla features instead of trying to 'fix' them. The whole 'file a bug in bugzilla' process is already far too complicated with a dozen fields which are either irrelevant or just confusing to newcomers. Can we just hide all this cruft (including the 'assigned to' field) for most users? Everything below only refering to enter_bug.cgi, not show_bug.cgi: After clicking Hide Advanced fields in the upper left corner on https://bugzilla.wikimedia.org/enter_bug.cgi , the Assignee field is not shown anymore on the Report a bug page. By default, the advanced fields are hidden on enter_bug.cgi: http://bzr.mozilla.org/bugzilla/trunk/view/head:/template/en/default/bug/create/create.html.tmpl#L142 If we wanted, we could probably hide more fields (OS, Hardware, ...) by wrapping the corresponding trs in tbody class=expert_fields. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
On Sat, 2013-11-09 at 09:40 -0500, C. Scott Ananian wrote: More agressive use of tagging (or something like it) would help here. Tagging: For the records, Bugzilla offers 1) static global keywords in the Keywords field (see the list of keywords at https://bugzilla.wikimedia.org/describekeywords.cgi ), 2) public entries in the Status Whiteboard field (e.g. I sometimes set aklapper-moreinfo there), and 3) non-public, personal tags; completely unusable in our version 4.2 also thanks to our custom CSS; but acceptable in version 4.4 (see https://bugzilla.wikimedia.org/show_bug.cgi?id=56183 ). I also list using the 'my bugs' feature of bugzilla. But that doesn't actually necessarily need to be reflected as 'assignment'. If there were a way to let me add to a list of 'my bugs' without requiring assignment (or editbugs) that would be totally cool. I don't know your specific usecase - maybe the shared saved search named My CC'd Bugs might work (or not) which you could enable on https://bugzilla.wikimedia.org/userprefs.cgi?tab=saved-searches (see http://blogs.gnome.org/aklapper/2013/07/12/bugzillatips-saved-searches/ for general info on saved searches and sharing them with other users). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New Bugzilla users have restricted accounts
On Sat, 2013-11-09 at 10:22 -0400, MZMcBride wrote: I'll just reiterate what I said previously: it would be wonderful to do a full evaluation/audit of the current Bugzilla inputs and figure out which we can eliminate or make smarter (e.g., only display under certain conditions). Just to explain the current situation: *Custom* fields (in Wikimedia Bugzilla: Web Browser and Mobile Platform) can be configured to be only shown under certain conditions (e.g. only for specific products/components), but Bugzilla still does not allow disabling some *default* fields that I consider useless in most cases for us (Hardware and OS, upstream ticket: https://bugzilla.mozilla.org/show_bug.cgi?id=763409 ). * https://www.mediawiki.org/wiki/Requests_for_comment/Overthrow_Bugzilla While some pieces of the criticism on that page are entirely valid, all in all it feels rather non-constructive. Plus the topic most acceptable issue tracking/version control/project management tool is so complex and has enough stakeholders that it requires a well-structured process to neither discuss only the favorite bits and pieces of individuals, nor end up in the biggest bikeshed ever. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Engineering Community team updates
On Mon, 2013-11-11 at 16:01 -0800, Quim Gil wrote: On 11/05/2013 01:52 PM, Quim Gil wrote: Next week we will have our monthly IRC meeting, just like every second Tuesday of the month. You can propose topics to be discussed at https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings#2013-11-12 This is happening tomorrow, Nobember 12, at 15:00 UTC on #wikimedia-meetbot Small typo - Make that a 17:00UTC please, as correctly written on https://www.mediawiki.org/wiki/Engineering_Community_Team/Meetings#2013-11-12 and also in the timeanddate.com link here: http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131112T17ah=1 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikipedia Issue
On Thu, 2013-11-14 at 13:50 -0500, Derric Atzrott wrote: If you report this error to the Wikimedia System Administrators, please include the details below. Request: GET http://en.wikipedia.org/wiki/Johnny_the_Homicidal_Maniac, from 10.64.32.106 via cp1067 cp1067 ([10.64.0.104]:3128), Varnish XID 2127871567 Forwarded for: 162.17.205.153, 208.80.154.76, 10.64.32 Thanks! The Operations team is currently working on it and there likely will be an analysis available at https://wikitech.wikimedia.org/wiki/Incident_documentation afterwards. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] QRCode - QRpedia
Hi Rodrigo, On Wed, 2013-12-04 at 15:00 -0200, Rodrigo Padula wrote: So, there are any way to have access to the source code and to localize the platform for pt.wikipedia users and contributors? There are any API to use it by scripts/external pages/apps? https://meta.wikimedia.org/wiki/QRpedia#Development links to the code repository at https://git.wikimedia.org/summary/qrpedia.git . Git/Gerrit usage is explained here: https://www.mediawiki.org/wiki/Gerrit/Tutorial https://www.mediawiki.org/wiki/Developer_access andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Please use sitenotice when a new version of software is deployed
On Thu, 2013-12-05 at 11:28 +0100, Alex Brollo wrote: Users are very confused and worried any time a new version of wiki software is launched and tested, and some major or minor bug comes invariably out. So a constant Be confused and worried, every Thursday! site notice on Wikipedias (Tuesday for other production sites [1]) would help? ;) andre [1] https://www.mediawiki.org/wiki/MediaWiki_1.23/Roadmap -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki 1.22.0 released
On Fri, 2013-12-06 at 23:02 +, Markus Glaser wrote: I am happy to announce the availability of the first stable release of the new MediaWiki 1.22 release series. Congratulations! I'm wondering which older versions are still supported. https://www.mediawiki.org/wiki/Template:DownloadMediaWiki lists 1.20.8 as legacy but not 1.21.3, but now also states that 1.20.x [...] was discontinued. If the latter is correct, does https://www.mediawiki.org/wiki/Template:MW_legacy_release_number need to be changed from 1.20.8 to 1.21.3? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Draft for Bugzilla etiquette guidelines
Heya everybody, based on a discussion on the teampractices@ mailing list ([1],[2]) I have published an initial draft for potential Bugzilla etiquette guidelines. It tries to explain workflows and helpful behavior in Bugzilla, as things work slightly different than on wikipages (not only on a technical level): https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette I welcome your comments on the Talk/Discussion page! Cheers, andre [1] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000112.html [2] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000158.html -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Draft for Bugzilla etiquette guidelines
Hi, On Mon, 2013-12-09 at 10:17 -0800, Jon Robson wrote: Would we be able to link to such a thing from within the Bugzilla interface to give it more visibility? Yes, in the footer, next to Privacy policy. I've filed https://bugzilla.wikimedia.org/show_bug.cgi?id=58332 so I don't forget. andre -- Andre Klapper | ak...@gmx.net http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Spamming in mailing lists
On Sat, 2013-12-14 at 10:28 +0330, Amir Ladsgroup wrote: public mailing lists (even sometimes private ones) are target of non-stop spamming. As Nemo already wrote, there are some (technical) comments in https://bugzilla.wikimedia.org/show_bug.cgi?id=56525 available. Another thing: GNU mailman has introduced a spam-filtering system In which version? , but I think we haven't updated to that version and our version is 2.1.13 which is released in 2009-12-22 [2] and last stable version of GNU mailman has been released in 23-Nov-2013 [3]. Is there any reason for not updating? See https://bugzilla.wikimedia.org/show_bug.cgi?id=50864#c5 on a related note. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Draft for Bugzilla etiquette guidelines
Last call to provide feedback on the Talk/Discussion page before finalizing this soon. (Thanks everybody for the feedback so far!) andre On Mon, 2013-12-09 at 18:13 +0100, Andre Klapper wrote: based on a discussion on the teampractices@ mailing list ([1],[2]) I have published an initial draft for potential Bugzilla etiquette guidelines. It tries to explain workflows and helpful behavior in Bugzilla, as things work slightly different than on wikipages (not only on a technical level): https://www.mediawiki.org/wiki/Bug_management/Bugzilla_Etiquette I welcome your comments on the Talk/Discussion page! Cheers, andre [1] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000112.html [2] http://lists.wikimedia.org/pipermail/teampractices/2013-November/000158.html -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailing list etiquette and trolling [Bugzilla etiquette]
On Sun, 2013-12-22 at 20:18 +, Marcin Cieslak wrote: Chad innocentkil...@gmail.com wrote: On Wed, Dec 11, 2013 at 3:50 PM, Isarra Yos zhoris...@gmail.com wrote: On 11/12/13 23:28, Petr Bena wrote: I think we need to use less rules and more common sense. This. Rules are silly. Common sense for all :) Yeah, and at this very moment we are getting a Bugzilla etiquette[1] instead of improving a plain text explanation to bug submitters how our process works. The instead of in that sentence confuses me - you can work on both. Where is the current plain text explanation that we should improve? Do you refer to https://www.mediawiki.org/wiki/How_to_report_a_bug ? Which areas for improvement do you see? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] I'm back from Hacker School
On Fri, 2014-01-03 at 22:48 -0500, Sumana Harihareswara wrote: Hi! As of yesterday, I'm back after my three-month sabbatical at Hacker School. Welcome back in the team! :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
On Mon, 2014-01-06 at 03:00 +, reporter wrote: Reports created this week: 594 Resolutions for the week: Reports marked FIXED : 410 For the records, these two numbers are higher because valhallasw was so awesome to write a script that imports Toolserver tools tickets from JIRA to Bugzilla, and applied it on some projects. See [1] for details. Created reports per product Tool Labs tools 347 Top 5 bug report closers wmf.bugconverter [AT] gmail.co317 andre [1] https://bugzilla.wikimedia.org/show_bug.cgi?id=58821 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugzilla Etiquette
Today I removed the This page is currently a draft banner on https://www.mediawiki.org/wiki/Bug_management/Bugzilla_etiquette as the comment rate on its Discussion page has been very low recently, hence I assume consensus has been found. The page is the outcome of lots of discussion among numerous community members (as a Bugzilla etiquette guideline drafted: help complete it banner was shown for several weeks on mediawiki.org). I would like to thank everybody who participated and helped in creating this document! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] English Wikipedia Issues
On Thu, 2014-02-06 at 11:41 -0500, Derric Atzrott wrote: Not sure if anyone else noticed or not yet, but at least the English Wikipedia appears to be having some intermittent issues. This is being worked on currently on IRC in #wikimedia-operations currently, plus was reported to https://bugzilla.wikimedia.org/show_bug.cgi?id=60970 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugzilla downtime: Wed Feb12 22:00 UTC - 01:00 UTC
Hi, bugzilla.wikimedia.org will be unavailable due to maintenance work on Wednesday, February 12th from 22:00 UTC until max. Thursday, February 13th 01:00 UTC. Plans include: * upgrading Bugzilla to newer version * moving Bugzilla to new server * depending on how smooth things go, doing admin maintenance work while bugmail is switched off for a moment, like ** merging the numerous 1.20.x version field entries into one ** mass-removing wikibugs-l@ from CC lists of reports (see bug 47013) as it's set as a globalwatcher anyway ** maybe restructuring the taxonomy of Mobile components (currently still discussed in the Mobile team) Crossing fingers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Wikimedia Bugzilla upgraded to 4.4.1
Hi, bugzilla.wikimedia.org has been upgraded from version 4.2.7 to 4.4.1. [For the technical audience: Bugzilla was also moved to a different server in the new datacenter and Bugzilla is puppetized now.] I would really like to thank Daniel Zahn and Sean Pringle for their wonderful work, help and support! For fixed problems in Bugzilla by this upgrade, see: https://bugzilla.wikimedia.org/buglist.cgi?bug_id=47013,42850,32504,49250,56183,53199,61280,60727 For new functionality, please see the list at https://bugzilla.wikimedia.org/show_bug.cgi?id=49597#c12 If you run into problems with the Bugzilla software itself after this upgrade, please file a bug report under https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wikimediacomponent=Bugzilla We have one small regression so far: Saved Searches in the sidebar look a bit ugly: https://bugzilla.wikimedia.org/show_bug.cgi?id=61288 It is a temporary trade-off for being able to see your Saved Reports (tables and graphs) listed there, similar to Saved Searches. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Reporting a bug with the creation of pdf Files with equations
Hi Daniel, sorry for the late reply. On Thu, 2014-02-13 at 01:59 +0100, Daniel wrote: I just wanted to report a bug, and info...@wikipedia.org referred me here. Sadly, upon trying to create a pdf (using the otherwise genius Print/export feature) of a page that involves lines above letters (e.g. http://en.wikipedia.org/wiki/List_of_mesons) the lines above letters (here essential to indicate the difference between Particle and Antiparticle) just disappear. In the linked Article that can be seen in the caption under the first Image where the pdf then contains the text The strange antiquark (s) despite there being a line above the s in the online Article. Confirming. I cannot quickly find an existing bug report in https://bugzilla.wikimedia.org/buglist.cgi?component=Collectionresolution=--- Could you please create a bug report at https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensionscomponent=Collection Note that there are also rumors of a new PDF Renderer being worked on, so it can only get better. :) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoC '14 Query
Hi, On Wed, 2014-02-26 at 18:41 +0530, Narendra Nath Joshi wrote: Hi all, This is a query regarding GSoC '14. I'm proficient in Hindi and English. I also am a hobbyist web developer and am quite familiar with HTML/CSS/JavaScript. I wanted to know about the projects I can do as a part of translation for GSoC 2014. Where do I start? Thanks for your interest! Please take a look at https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014 Don't hesitate to ask if something is unclear. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Eure Teilnahme wird bezahlt
Hi, just for your interest, you sent this to wikitech-l@lists.wikimedia.org which is an English language mailing list. andre On Fri, 2014-02-28 at 14:26 +0100, Leonie Ehrl wrote: Liebe Community Ich heisse Leonie, bin 26 Jahre und Studentin der Medien- und Kommunikationswissenschaft an der Université de Fribourg (Schweiz). In meiner Masterarbeit beschäftige ich mich mit EUCH, den deutschsprachigen Wikipedianerinnen und Wikipedianern aus Deutschland, Liechtenstein, Österreich und der Deutschschweiz. Mein wissenschaftliches Interesse besteht darin, die Zusammensetzung der deutschsprachigen Community besser zu verstehen. Aus diesem Grund bin ich auf eure Mithilfe angewiesen und wäre dankbar für eine rege Beteiligung bis Freitag, 28. März 2014. Der folgende Link zum Online-Fragebogen führt euch direkt zur Umfrage: https://student.unifr.ch/survey/go/index.php/341639/lang-de-informal Die Beantwortung dauert rund 10 Minuten. Deine Anonymität ist selbstverständlich gewährleistet. Ganz im Sinne der unbeschränkten Zugänglichkeit von Informationen stelle ich meine Arbeit im Juli 2014 unter eine freie Lizenz. Als Dankeschön für eure Zeit und Unterstützung spende ich ausserdem für jeden auswertbaren Fragebogen einen Euro bzw. einen Schweizerfranken an das jeweilige Wikimedia-Chapter. Gerne könnt ihr euch bei Fragen an mich wenden: leonie.e...@outlook.com Viele GrüsseLeonie ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSOC-2014 aspirant
On Sun, 2014-03-02 at 20:33 +0530, Karan Dev wrote: hi, I am B.Tech. (CS) 3rd year student from India. I have 4 years of programming experience. I am comfortable with c/c++ , Php, Javascript, HTML, MySql. I was going through idea page and found interest in Catalogue for MediaWiki extensions. Please someone guide me where to start ? Hi Karan, thanks for your interest in Wikimedia! Have you read https://www.mediawiki.org/wiki/Google_Summer_of_Code_2014 already? It has a section called Where to start which hopefully covers the next recommended steps. If it does not answer your question, please tell which information you're missing so we could improve that page. Cheers, andre PS: Whenever I see where to start? I'm also tempted to point to http://sindhus.bitbucket.org/common-pitfalls-of-newcomers-in-foss.html -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tutorial to edit Help Pages
Hi, On Thu, 2014-03-06 at 09:24 +, Anjali Sharma wrote: I wish to edit the documentation of Wikidata help pages. For that need to learn some advanced editing options like creating anchors for topics in a page. Where can I find a possible help ??? https://www.mediawiki.org/wiki/Help:Links covers how to use anchors. If that's not what you asked for, please be more specific and provide an example. :) Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Multimedia team architecture update
On Fri, 2014-03-07 at 11:50 +0100, Gerard Meijssen wrote: On the Wikidata roadmap it says that Commons will be targeted for inclusion in the second half of 2014. This will have a big impact on Commons. Consequently it will have a big impact on the things that you are discussing. Chances are that much of what you come up with now will be obsolete in a few months time or even worse make the development of the inclusion of Wikidata into Commons even harder. I find it odd that Wikidata is not mentioned at all in this overview. Please elaborate where / in which specific areas you would have expected to see Wikidata being mentioned in Gergo's overview, as I cannot interpret the consequently in your statement yet. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OutreachProgramForWomen Aspirant
Hi Nikita, thanks for your interest! On Fri, 2014-03-07 at 11:11 +0400, Nitika Verma wrote: This is Nitika from India. I am comfortable with c/c++ , Php, Javascript,HTML and MySql. In the projects listed on https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8 I am very interested in the project Book Management in Wikibooks/WikiSource (mentor : https://www.mediawiki.org/wiki/User:Raylton_P._Sousa) Can please someone guide me how to go about this project? Have you taken already a look at https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women/Round_8#Where_to_start and contacted the mentor(s)? The page provides info how to set up your development environment, so you can play with MediaWiki and the BookManagerv2 extension, try to understand its code better, and maybe give an easier bug report a first shot at fixing it. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GSoc Project related assistance
Hi Rohit, On Wed, 2014-03-12 at 19:46 +0530, Rohit Dua wrote: It would be great if we could get the community's valuable *suggestions/ feedback* for the proposal/project. Do you have specific question(s) when you ask for feedback? Specific questions normally help me a lot to provide *helpful* feedback... andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Fwd: REMINDER: Project management tools review: Help shorten the list of candidates
Heja, forwarding another reminder from the teampractices@ list about the Project management tools review. If you're interested in this topic, we welcome your help and are happy answer your questions! Thanks! Forwarded Message From: Andre Klapper aklap...@wikimedia.org To: A mailing list to discuss team practices in Wikimedia organizations teampracti...@lists.wikimedia.org Subject: Re: [teampractices] REMINDER: Project management tools review: Help shorten the list of candidates Date: Fri, 14 Mar 2014 19:13:40 +0100 Heja, Thanks to everybody who has already provided input and feedback on our Project management tools options, so the upcoming RFC can focus on candidates that we really want to further investigate. If you have not taken a look or commented on the candidates: Please take a few minutes to review the options and give your opinion! Engage in the discussion and make sure your voice is heard: https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options This is crucial in order to hopefully finding broad consensus and wide acceptance across teams at the very end of this evaluation. I'd especially like to encourage teams which have not provided input yet. Furthermore, while the focus is clearly on software development, commenting is not restricted to _development_ teams - Input from any teams in the Wikimedia sphere who use workflow or ticket systems can be helpful. Again, thank you for your help! Guillaume and Andre On Tue, 2014-03-04 at 09:35 +0100, Guillaume Paumier wrote: Hi all, Thanks again for providing so much input during the consultation period ( https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review ). It's been extremely useful to understand your respective needs and workflows. We've summarized all this input into consolidated requirements. The goal was to group similar needs to make it easier to identify the features we need across teams and individuals: https://www.mediawiki.org/wiki/Project_management_tools/Review/Requirements Some requirements are conflicting with each other and will require further discussion later, but overall we're pretty much in agreement regarding what we want (even if that's a five-legged unicorn). We've been diligent in including everything that was provided during the consultation. Nonetheless, please take a look at the list of requirements if you have a moment, to make sure we haven't missed anything important. We've also assembled a list of options, i.e. the possible outcomes of this review process. The options go from keeping the status quo to changing a single tool, to consolidating most tools into one. It's still very much a draft and nothing's final. If we've missed anything in that table, please be bold and edit it: https://www.mediawiki.org/wiki/Project_management_tools/Review/Options We've tried to keep the list inclusive, but now we'd like to shorten the list of options, so that the upcoming RFC can focus on the options that actually have a shot. If you're interested in helping with this, please take a look at the list of options and discuss them on the talk page: https://www.mediawiki.org/wiki/Talk:Project_management_tools/Review/Options#Discuss_options Basically, we want to move items from the Options under consideration section to the Unlikely options one. Ideally, we should keep no more than 2 or 3 candidates, to make the RFC easier. If you think an option is unavoidable (e.g. We absolutely must discuss replacing Trello by Pivotal Tracker), then say so on the talk page in the relevant section. Conversely, if you think there's no way we're using iceScrum, leave a comment on the talk page. We'll assess consensus collaboratively and hopefully get rid of unlikely options. This is a collaborative process: we need your help so others don't make decisions on your behalf. Please take a few minutes to review the options and give your opinion. It's Notavote; think of it as a sane version of RfD (you must be new around here?). Let us know if you have any questions and we'll do our best to answer :) Andre and Guillaume -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] IRC Office Hour on Project Management Tools Review: Friday 28th, 17:00UTC
Hi, Guillaume and I will be hosting an IRC office hour on March 28, 2014 (Friday) at 17:00 UTC / 10:00 PDT in #wikimedia-office on irc.freenode.net. We will quickly present the progress and status of the ongoing Project management tools review [1] and after that we are happy to answer your questions! See you at the IRC office hour! Thanks, andre [1] https://www.mediawiki.org/wiki/Project_management_tools/Review -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Forget mailing lists and on-wiki discussions; Twitter's the place!
On Sun, 2014-04-06 at 18:52 +0200, Tomasz W. Kozlowski wrote: Hi! I was surprised to see that Twitter is now the preferred method of contacting the Wikimedia Foundation, and that it is much more effective than long disputes and discussions on mailing lists, Bugzilla and wiki pages. The related ticket (see last comments explaining some stuff) is https://bugzilla.wikimedia.org/show_bug.cgi?id=63512 . Can't judge the effectiveness though. :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Free fonts and Windows users; final plea!
On Fri, 2014-04-11 at 09:42 -0700, Jon Robson wrote: I keep hearing about ALLL THE BUGS but I've not seen anything on Bugzilla. https://bugzilla.wikimedia.org/show_bug.cgi?id=63549 dependency list plus likely stuff on https://www.mediawiki.org/wiki/Talk:Typography_refresh that I'd expect the developers to read and convert into bug reports, when necessary. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] RfC on Product Management Tools and Development Toolchain
Hi, as previously announced [1], we've been facilitating a collective review of Wikimedia's current product management tools and development toolchain. The most popular idea at the moment is to consolidate Wikimedia's product management and infrastructure tools (such as Bugzilla, Gerrit, RT, Mingle, Trello) into all-in-one Phabricator. We have therefore put together a Request for comment to bring this up for wider discussion. This discussion affects anyone who deals with bug reports, feature requests and code changes in Wikimedia, so it's critical that you test Phabricator for your own use and make your voice heard in the RFC: https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator We're compiling a list of Frequently asked questions at https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/FAQ ; You're welcome to add more and help answer them :) We'll host a few IRC discussions while the RFC is running to help answer questions, etc. Our tentative times and dates are at https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Phabricator#IRC_discussions Thank you for your input! Guillaume and Andre [1] http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/074896.html -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [teampractices] RfC on Product Management Tools and Development Toolchain
Hi Dan, On Tue, 2014-04-15 at 12:19 -0400, Dan Andreescu wrote: It's my understanding that the current Phabricator instance is temporary. Indeed, it includes mostly jokes and throw-away testing tasks, comments, boards, etc. Could we stand up an instance to which we would potentially migrate to? We would have to reserve task ids 1-10 to allow us to port from Bugzilla, but do we have any other blockers? We'd preferably reserve some numbers in Phabricator for Bugzilla and RT tickets in order to redirect; and maybe other tools. I don't see us setting up a production instance yet and filing it up with real data, as long as we don't know how we'll actually migrate the real data. I won't stop you from setting up a project in the testing Labs instance (looks like you've done that already) or setting up a separate Phabricator Labs instance though. :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Tuesday 22nd, 03:30UTC: Another IRC Office Hour on Project Management Tools Review / Phabricator
After last Thursday's IRC office hour [1] we are going to have another office hour on April 22, 2014 (Tuesday) at 03:30 UTC (09:00 India; Monday 20:30 California) in #wikimedia-office on irc.freenode.net about the ongoing Project management tools review and the proposal to move to Phabricator: https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator We will quickly present the progress and status and we are happy to answer your questions! See you at the IRC office hour! andre [1] https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2014-04-17 -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugday on General MediaWiki bugs on Tue, April 29 2014, 14:30UTC
Hi, you are invited to join us on the next Bugday: Tuesday, April 29, 2014, 14:30 to 16:30UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging Bugzilla tickets under the product MediaWiki and the component General/Unknown [3]. Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved or to give something back. We encourage everybody to record your activity on the etherpad [4]. This information and more can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140429 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there! andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat [3] https://bugzilla.wikimedia.org/buglist.cgi?component=General%2FUnknownresolution=---product=MediaWiki [4] http://etherpad.wmflabs.org/pad/p/BugTriage -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] need help for downloadin Urdu data from Wikipedia
On Thu, 2014-04-24 at 12:00 +0530, Imran Rasheed wrote: I need to download Urdu text data from Wikipedia for my research work. this is the following link *http://ur.wikipedia.org/wiki/ http://ur.wikipedia.org/wiki/* . Can you please help me, how to download Urdu text data from Wikipedia?? or Give me a suitable link for downloading this Urdu data. See https://en.wikipedia.org/wiki/Wikipedia:Database_download and specifically http://dumps.wikimedia.org/urwiki/20140418/ Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] bugs in #mediawiki
On Fri, 2014-04-25 at 21:51 -0700, Legoktm wrote: The new wikibugs is now in #wikimedia-dev, and also in a few other channels. This entertaining mailing list thread includes statements which miss references, so I'll add those Bugzilla tickets that I am aware of: https://bugzilla.wikimedia.org/show_bug.cgi?id=46322 https://bugzilla.wikimedia.org/show_bug.cgi?id=46144 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New wikibugs bot
On Tue, 2014-04-22 at 22:45 +0200, Merlijn van Deen wrote: As the original wikibugs bot did not come back online today, the tasks of wikibugs have now fully been taken over by a python re-implementation of the same bot, running on Tool Labs. A few improvements over the old bot: - running on Tool Labs instead of the WMF mail server, so community-maintainable, - messages to multiple channels based on bug properties (e.g. product and component) - several minor improvements: - shows changes instead of the new situation - adds first line-or-so of a comment, - shows product and component for each message, - better URLs (with anchor to the specific comment), - real names are now *always* used (they are retrieved from BZ if the mail does not list them). This is lovely and fixes a lot of issues in the old wikibugs. Thanks so much! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] need to download wikipedia data
Hi, On Tue, 2014-04-29 at 10:58 +0530, Imran Rasheed wrote: I need to download wikipedia data for some text retrieval and evaluation for my academic research. So I need to know how to download the content of the following wikipedia link. *http://ur.wikipedia.org/wiki/ http://ur.wikipedia.org/wiki/* I need data in the form of '*text*' files. I already tried KIVIX software but it's not fulfill my conditions. Could you please explain why you repost this question after having received numerous answers already a few days ago and after acknowledging that in http://lists.wikimedia.org/pipermail/wikitech-l/2014-April/076190.html ? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Text-to-speech extension?
On Tue, 2014-04-29 at 08:17 +0200, Gerard Meijssen wrote: Hoi, Are screen readers supported ? But do they understand what is the cruft that is on a page, the kind of cruft that you do not want to get read out to you? Depends on how you define supported. :) For things that don't work, there is https://bugzilla.wikimedia.org and the keyword accessibility. Open tickets: https://bugzilla.wikimedia.org/buglist.cgi?keywords=accessibilityresolution=--- andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugday on General MediaWiki bugs on Tue, April 29 2014, 14:30UTC
Reminder: This will start in about 25 minutes. On Thu, 2014-04-24 at 00:21 +0530, Andre Klapper wrote: you are invited to join us on the next Bugday: Tuesday, April 29, 2014, 14:30 to 16:30UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging Bugzilla tickets under the product MediaWiki and the component General/Unknown [3]. Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved or to give something back. We encourage everybody to record your activity on the etherpad [4]. This information and more can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140429 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there! andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat [3] https://bugzilla.wikimedia.org/buglist.cgi?component=General%2FUnknownresolution=---product=MediaWiki [4] http://etherpad.wmflabs.org/pad/p/BugTriage -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Feedback on 1.23 RC 0
On Tue, 2014-04-29 at 10:50 -0400, Mark A. Hershberger wrote: Are there any other issues that people have run into that we should know about before we do attempt to make a final release of 1.23? There are 13 tickets with a 1.23 target milestone in Bugzilla, and some have patches (are in PATCH_TO_REVIEW status): https://bugzilla.wikimedia.org/buglist.cgi?target_milestone=1.23.0%20releaseresolution=---product=MediaWiki And there are numerous FIXED tickets where backporting the fix to stable releases has been requested: https://bugzilla.wikimedia.org/buglist.cgi?cmdtype=runnamednamedcmd=Backport_Stable%3F Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugday on General MediaWiki bugs on Tue, April 29 2014, 14:30UTC
Thank you to everybody who participated in this bugday! We managed to update about 50 tickets and moved 29 tickets out of the General/Unknown bucket. More details on https://www.mediawiki.org/wiki/Bug_management/Triage/20140429 andre On Thu, 2014-04-24 at 00:21 +0530, Andre Klapper wrote: you are invited to join us on the next Bugday: Tuesday, April 29, 2014, 14:30 to 16:30UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging Bugzilla tickets under the product MediaWiki and the component General/Unknown [3]. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Shifting from PHP mailer to Swift Mailer
Hi Tony, could you clarify your intention for this email? Are you seeking for more input whether it's a good idea, or if this actually needed? Or are you searching for agreement as you plan to work on a patch yourself? Or are you looking for somebody to work on this? It's not entirely clear to me from your email. Thanks, andre On Tue, 2014-04-29 at 21:28 +0530, Tony Thomas wrote: Hi, Looks like there isn't any more reply about this proposal on shifting from UserMailer to Swift-Mailer. Since, we have already started with implementing VERP, it's high time this enhancement needs to be applied, if it needs to be. If Swift-Mailer is to be done, VERP needs to be implemented as a plugin to it, or else as an additional script in the UserMailer code. Bugzilla ticket:- https://bugzilla.wikimedia.org/show_bug.cgi?id=63483 Thanks, Tony Thomas http://tttwrites.in FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi,there is a way* On Fri, Apr 4, 2014 at 10:45 PM, Tony Thomas 01tonytho...@gmail.com wrote: Hi, While working on implementing VERP for Mediawiki[1], Nemo pointed to me, Tyler' recommendation[2] on shifting from PHP mailer to Swift Mailer[3]. Quoting Tyler's words : PHPMailer has everything packed into a few classes, whereas Swift_Mailer actually has a separation of concerns, with classes for attachments, transport types, etc. A result of this is that PHPMailer has two different functions for embedding multimedia: addEmbeddedImage() for files and addStringEmbeddedImage() for strings. Another example is that PHPMailer supports only two bodies for multipart messages, whereas Swift_Mailer will add in as many bodies as you tell it to since a body is wrapped in its own object. In addition, PHPMailer only really supports SMTP, whereas Swift_Mailer has an extensible transport architecture, and multiple transport providers. (And there's also plugins, and monolog integration, etc. My mentors too think about it to be a nice idea, and Nemo recommended adding it to my GSoC project deliverable here ( https://www.mediawiki.org/wiki/VERP#Deliverables ). But, we need more community-consensus on the same as this needs to be done first, and VERP as a plugin to it, if Swift mailer needs to be done. I have opened a BZ ticket for the same ( https://bugzilla.wikimedia.org/show_bug.cgi?id=63483 ). Please comment to this thread or in the BZ regarding the shift as it needs to be done for a start. The discussions we had on this till date is here: https://www.mediawiki.org/wiki/Talk:VERP#Swift_Mailer_and_VERP__40928. [1]: https://www.mediawiki.org/wiki/VERP [2]: https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Third-party_components [3]: http://swiftmailer.org/ Thanks, Tony Thomas http://tttwrites.in FOSS@Amrita http://foss.amrita.ac.in *where there is a wifi,there is a way* ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Help! Phabricator and our code review process
On Mon, 2014-05-05 at 12:18 -0400, Tyler Romeo wrote: Phabricator still does not work directly with Git, right? This topic is covered in http://fab.wmflabs.org/T207 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Phabricator RFC Closed Next Steps
Hi, == Closing the Phabricator RFC == As previously announced [1], we've been facilitating an RFC proposing to replace Wikimedia's current product management tools and development toolchain by a tool called Phabricator: https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator We'd like to thank everybody for discussing and testing Phabricator and providing very helpful feedback for the last three weeks! In order to move forward and avoid letting the RFC be forgotten in a dusty corner of the wiki, it's now time to close and summarize it. The goal of the RFC was to gauge interest in simplifying our development toolchain and consolidating our tools (gitblit, Gerrit, Jenkins, Bugzilla, RT, Trello, and Mingle) into Phabricator. At first glance, it seems that there is support for this proposal. The consensus is also that there are blockers that must be addressed before any migration is considered, and that any migration must be carefully planned and as carefully executed. To be clear: It's not yet been decided to move to Phabricator. The RFC has shown that there is interest and enthusiasm about Phabricator, and this means resources could now be devoted to work more specifically on the blockers and the migration plan. We expect that there will be another (shorter) discussion down the road to serve as a reality check. Its format will be lighter than that of the RFC, since its goal will mostly to check that blockers have been resolved and the migration plan makes sense. == Plan for blockers and migration == A first phase of the migration would focus on migrating all the Bugzilla data to Phabricator, and merging the project management work being done in Trello and Mingle. A second phase —that could be worked in parallel— would focus on substituting Gerrit for code review, and RT. There is also a possibility to deprecate Jenkins as a continuous integration tool, but this option is out of scope for now. A few blockers have been identified in these areas, and we will collaborate with the Phabricator community to fix them. The schedule for this migration depends on resolving those issues which are blockers for Wikimedia moving to Phabricator. The Engineering Platform team at the Wikimedia Foundation would lead this project allocating the resources necessary to define a detailed plan, proceed with the migration, and maintain the new infrastructure. A longer version, requirements to still sort out first, and concerns raised have been summarized by Quim at https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/Plan == Join the next discussions == There will be a session about Phabricator at the Wikimedia hackathon in Zürich this week-end (see [2]), as well as another IRC discussion next week (in #wikimedia-office on Wednesday, May 14, at 18:00 UTC: http://www.timeanddate.com/worldclock/fixedtime.html?msg=Phabricator+migration+planning+IRC+discussioniso=20140514T20p1=329ah=1 ) Cheers, Guillaume and Andre (and Quim) [1] http://lists.wikimedia.org/pipermail/wikitech-l/2014-April/075993.html [2] https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Topics#Future_of_version_control.2C_bug_reporting_and_other_developer_tools -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Login to Wikimedia Phabricator with a GitHub/Google/etc account?
On Thu, 2014-05-15 at 21:34 +, Jeremy Baron wrote: On Thu, May 15, 2014 at 9:20 PM, Quim Gil q...@wikimedia.org wrote: There are good reasons to plan for Wikimedia SUL only (consistency with the rest of Wikimedia projects), and there are good reasons to plan for other providers as well (the easiest path for most first-time contributors). If there's a problem with SUL/centralauth and you can't log in either to the wikis or to phabricator then how do we report/track that issue? We can still make noise on mailing lists and IRC (which sometimes is the case for reporting issues already). Right now people complain that e.g. Bugzilla has a separate login so they don't report issues there. It's hard to judge what's the bigger problem because being concerned about our tools having the same auth mechanism has only come up since having the same auth mechanism is being considered, of course. :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] enwiki display issues
Hi John, thanks for bringing this up. On Fri, 2014-05-16 at 16:07 -0400, John wrote: Looks like Javascript/CSS is intermittently failing. http://en.wikipedia.org/wiki/Wikipedia:Village_pump_%28technical%29#Something_is_broken This was discussed also in #wikimedia-tech on IRC and as a first step. If I got it correctly it's not clear yet what the culprit is, but trying to first bypass your browser cache is recommended to check if the problem(s) still happen: https://en.wikipedia.org/wiki/Wikipedia:BYPASS andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Status of the new PDF Renderer
Hi, On 01/18/2014 03:42 AM, Matthew Walker wrote: We've just finished our second sprint on the new PDF renderer. A significant chunk of renderer development time this cycle was on non latin script support, as well as puppetization and packaging for deployment. We have a work in progress pipeline up and running in labs which I encourage everyone to go try and break. Seeing breakage of PDF downloads on pl.wikisource reported in https://bugzilla.wikimedia.org/show_bug.cgi?id=65298 I got curious what the status of the new PDF renderer is. https://www.mediawiki.org/wiki/PDF_rendering#Status only links to the quoted email from January 2014. Has anything happened in the last four months that is worth to be added as a status update? For the records, Nemo asked on the Talk page for a test instance and I support the idea of having a bugday on PDF rendering once public testing infrastructure for the new PDF renderer is available. Open tickets to potentially re-test: https://bugzilla.wikimedia.org/buglist.cgi?resolution=---component=Collection andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] That you to anonymous users
On Tue, 2014-05-20 at 17:35 +0300, Strainu wrote: I've recently noticed the Thank you feature is only available for signed-in users, while anons cannot receive thank yous. The anonymous users are often the ones that would need encouraging the most, so it would make sense to me to have this feature available to them too. Are there significant technical problems against such a change? https://bugzilla.wikimedia.org/show_bug.cgi?id=61022 (if arguments are missing, adding them in a comment is welcome). andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Status of the new PDF Renderer
Hi, On Mon, 2014-05-19 at 11:57 -0700, C. Scott Ananian wrote: That's a good question! I'm in SFO this week, so it's probably worth setting aside a day to resync and figure out what the next steps for the new PDF renderer are. Any news (or a public test instance available)? As I wrote, I'd be interested in having a bugday on testing the new PDF renderer by going through / retesting https://bugzilla.wikimedia.org/buglist.cgi?resolution=---component=Collection Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Process change: New contributors getting editbugs on Bugzilla
On Thu, 2014-05-29 at 11:57 -0700, Mark Holmquist wrote: We've made every editbugs user able to add editbugs to an account. Thank you Mark (and Chad) for going ahead! I'm crossing fingers that advantages will outweigh the potential problems which made me indecisive about how to solve this problem. Time will tell, but right now I'm just happy there is progress. Thanks! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] enwiki display issues
On Sat, 2014-05-31 at 07:52 -0300, Helder . wrote: Shouldn't we have an incident report[1] about this? https://wikitech.wikimedia.org/wiki/Incident_documentation/20140529-appservers (as mentioned in the other thread) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Page view stats
Hi, On Mon, 2014-06-02 at 11:36 +0900, ikuyamada wrote: It seems that the page view stats have not been uploaded for several days. http://dumps.wikimedia.org/other/pagecounts-raw/2014/ Are there any plans to fix this? See https://bugzilla.wikimedia.org/show_bug.cgi?id=65978 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Search results on English Wikipedia not updating
On Tue, 2014-06-03 at 00:59 -0700, ENWP Pine wrote: It appears that suggested search results are not being updated on English Wikipedia. See https://bugzilla.wikimedia.org/show_bug.cgi?id=66011 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Help: Needed in OAuth
Hi, On Thu, 2014-06-05 at 20:13 +0530, Amanpreet Singh wrote: I need some help regarding my GSoC project in which I need to implement an OAuth login system for a browser based plugin, so we can identify users. But I am stuck and not able to get anything here https://github.com/apsdehal/Mediawiki-login-api/blob/master/lib/OAuth/MWOAuthClient.php#L77 . Kindly help me, and tell me if further information is needed. What is the problem you're facing, what have you tried already, what's the output you get, etc.? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Tuesday 17th, 17:30UTC: IRC Office Hour on Phabricator
Hi, we are going to have another IRC office hour about the migration to Phabricator: https://www.mediawiki.org/wiki/Phabricator in #wikimedia-office on irc.freenode.net on June 17, 2014 (Tuesday) at 17:30 UTC We will quickly present the status, progress, open issues. And we are happy to answer your questions! See you at the IRC office hour! andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Which mailer should we use? (was: Making a plain MW core git clone not be installable)
On Thu, 2014-06-12 at 09:23 +0200, Thomas Gries wrote: The present notification systems works fine - why do you want to change it? http://lists.wikimedia.org/pipermail/wikitech-l/2014-April/075653.html andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bugday on older MediaWiki bugs with high priority set on Tue, June 24 2014, 17:00UTC
Hi everybody, you are invited to join us on the next Bugday: Tuesday, June 24, 2014, 17:00 to 18:30UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging open Bugzilla tickets under the product MediaWiki which have high priority set for more than one year. Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved or to give something back. All information can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140624 For more information on triaging in general and what that means, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there? andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugday on older MediaWiki bugs with high priority set on Tue, June 24 2014, 17:00UTC
Reminder: The triage starts in 60 minutes. andre On Tue, 2014-06-17 at 16:42 +0200, Andre Klapper wrote: Hi everybody, you are invited to join us on the next Bugday: Tuesday, June 24, 2014, 17:00 to 18:30UTC [1] in #wikimedia-office on Freenode IRC [2] We will be triaging open Bugzilla tickets under the product MediaWiki which have high priority set for more than one year. Everyone is welcome to join, and no technical knowledge needed! It's an easy way to get involved or to give something back. All information can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140624 For more information on triaging in general and what that means, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there? andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC chat -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] bugzilla: keyword for every language
On Wed, 2014-06-25 at 10:44 +0200, Petr Bena wrote: Can we have that? so that people can filter out bugs that are require skills for certain languages only? For example if I needed to fix something that is C++ I would just tag it so, same for PHP, JS, etc... So that C++ devs could filter out only all bugs that require C++ knowledge and see all bugs across all of wikimedia that can be fixed in that language. Developers could then simply filter out only bugs that they are interested in or able to fix. Well, before developers can simply filter out bugs, somebody would have to go through ~14000 open tickets, understand which language(s) a bug report is about, and set the language(s) on all of these tickets. Would you like to volunteer? :) More seriously, doesn't the Bugzilla product or component that a bug report belongs to already pretty much define the programming language(s) in that area? That's the level where I'd expect such information to be located. (Or in a programming-language tag of a project's DOAP file in its code repository.) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] bugzilla: keyword for every language
On Wed, 2014-06-25 at 13:51 +0200, Petr Bena wrote: it maybe works for large ones, but for example when I create a bug for huggle or wm-bot where PHP, python, or JS guy is needed, nobody ever notice that. BTW mozilla is already doing this and it seems to be pretty effective What do you refer to? http://www.joshmatthews.net/bugsahoy/ where you can query Mozilla Bugzilla tickets by programming language? Or the [lang=php] tags in the Status Whiteboard of Mozilla Bugzilla? If the latter, anybody can edit the whiteboard of tickets in Wikimedia Bugzilla, so you can just do it. :) andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] bugzilla: keyword for every language
On Wed, 2014-06-25 at 17:11 +0200, Petr Bena wrote: ok that seems to be good enough for me. What is actually difference between these keywords and white-board if it can serve the same purpose? See https://www.mediawiki.org/wiki/Bugzilla/Fields andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Bug Bounty Program
A general and boring explanation on how access restrictions are handled/configured in Bugzilla currently. No opinions involved. On Wed, 2014-06-25 at 21:18 -0700, Chris Steipp wrote: There are a few cases where there may be legitimate private data in a security bug (look, sql injection, and here are some rows from the user table!, Hey, this was supposed to be suppressed, and I can see it, This user circumvented the block on this IP). But there might be ways to flag or categorize a report as also including private data? Someone with more bugzilla experience would need to comment. I'm not aware of any standardized way to do this. Current practice is described in item 2 below. In general, Bugzilla offers two things: 1) Access restriction to all tickets in a certain product by default (like all tickets under Security). Only Bugzilla admins, members of the security group, the bug reporter, and people explicitly CC'ed on such a ticket can access such a ticket in such a product. 2) Separate from that, marking both attachments and specific comments in a ticket as private. It's configured that it can be set and seen by Bugzilla admins and members of the security group. There is a practice (tradition?) to set the 'private' flag if somebody finds or notifies about private data exposed (IPs, passwords, SSIDs), insults / personal attacks, or spam. We don't have an explicit policy defined for setting that flag. A while ago I was told that people who by default have access to Security tickets in Bugzlla need to have an NDA [1] in place. andre [1] https://en.wikipedia.org/wiki/Non-disclosure_agreement -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Bug Bounty Program
On Thu, 2014-06-26 at 16:17 +0200, Bartosz Dziewoński wrote: I feel like this would result in a ton of reports that say YOU CAN DEFACE THE MAIN PAGE!!! which is editable, if not protected, because it's a wiki. This. I have seen several 'bug reports' in Mozilla Bugzilla by 'security researchers' about source code of projects being exposed on Mozilla's servers. Clearly a security breach. What does FOSS stand for? So it boils down to how to keep clueless people out, to be rough. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Bug Bounty Program
On Fri, 2014-06-27 at 15:06 +0200, Antoine Musso wrote: I would like us to have our own instance of Google Code-in to list tasks that could be fulfilled by volunteers. Kind of the +easy bugs we have in Bugzilla but with a nicer interface that only has those tasks. https://openhatch.org/search/?q=project=MediaWiki sounds close. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Discontinue internet explorer 6 and 7 support
Hi, On Sun, 2014-06-29 at 16:56 +0100, Thomas Mulhall wrote: Hi could we discontinue support for internet explorer 6 and 7 because jquery ui 1.11.0 drops support for internet explorer 6 and 7. Could you elaborate how decisions made by Jquery UI developers are relevant for us, and who the we is here? MediaWiki? Windows xp support internet explorer 8. Could you elaborate why you think this is relevant? (My computer might support software that can manage a nuclear power plant, still I might not have that software installed because I don't have a nuclear power plant handy.) In any case, absolute browser numbers for Wikimedia can be found on http://stats.wikimedia.org/wikimedia/squids/SquidReportClients.htm andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Winter, v. 0.6
On Mon, 2014-07-14 at 09:26 +0100, Magnus Manske wrote: Have you considered a maximum column width to make text more readable on wide screens? Quick'n'ugly mockup: https://dl.dropboxusercontent.com/u/23027995/Screen%20Shot%202014-07-14%20at%2009.24.21.png VectorBeta had this for a short time. See https://bugzilla.wikimedia.org/show_bug.cgi?id=59815 for records, links, complaints. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Phabricator migration update
Hi, this is a quick status update on the planned migration of our development planning tools to Phabricator. See https://www.mediawiki.org/wiki/Phabricator for general info. Several things have been worked on and achieved in the meantime: * WMF SUL Authentication has been implemented for Phabricator. * A separate server legalpad.wikimedia.org was deployed (a tool to manage trusted users - workflow to be further defined with Legal. * A data backup system for Phabricator in place. * Code to restrict access to tasks in a certain project is in place (same as Bugzilla's Security project) * The dedicated Phabricator server was upgraded to Ubuntu Trusty. * Packaging for Debian using pkg-php-tools/dh_php5 The identified tasks are listed on the planning board at http://fab.wmflabs.org/project/board/31/ Bugzilla: When it comes to the planning of how to convert data in Bugzilla tickets to Phabricator, we are mostly done. The elements that a Bugzilla report includes are listed in http://fab.wmflabs.org/T423 with links to subtasks. Obviously, Phabricator has a different UI and different workflow concepts than Bugzilla. While it's not the goal to have complete feature parity in every possible way, I'm pretty confident that we are close enough. As people are likely more interested in what Bugzilla functionality will be different, I'll try to summarize what I'm aware of: * Bugzilla's products, components and keywords will be turned into projects / tags in Phabricator. * Bugzilla votes will be turned into tokens. * Bugzilla's Severity field itself should get dropped - for example, if there is a real need to be able to search for critical severity (which translates to crash), it can become a crash project in Phabricator (think of keywords in terms of Bugzilla here). * For those ~50 users who have used Bugzilla's private Tags feature so far (introduced in February), this feature will be dropped, but you will get warned before. Similar, some Whiteboard data will likely also get dropped (or moved into the first comment if really considered relevant). Apart from that I am not aware of any other data we might drop or lose, or any other important functionality that would not be available in Phabricator. If you are passionate about a specific topic of task management / development workflows if you think after reading existing comments in the discussion of the related task that an important aspect has not been considered yet, please feel free to provide your input. To follow the progress of our Phabricator migration and to help, please see the planning board at http://fab.wmflabs.org/project/board/31/ Regular status updates are published at https://www.mediawiki.org/wiki/Phabricator/Migration#Status As usual, big thanks to Chase and Mukunda for their work, and to many others for providing input, feedback and help. Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Phabricator migration update
Hi, On Fri, 2014-07-18 at 15:29 -0700, Steven Walling wrote: When we've migrated from Bugzilla, are you looking for teams to be guinea pigs and try out Phabricator? Overall, I feel like we're not going to get the real benefit until we migrate from Gerrit and the entire toolset is on Phabricator. That said, I think Growth would be interested in provisionally giving Phabricator a try as a Trello/Bugzilla replacement. Note that mail notifications can sometimes be delayed due (bug 65861). If you are aware that fab.wmflabs.org is an unstable service until migrated to production, and if you could deal with potential data loss (which has never happened so far), teams are definitely welcome to try out the Labs instance with a small project and provide more feedback. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] News about stolen Internet credentials; reducing Wikimedia reliance on usernames and passwords
On Tue, 2014-08-05 at 22:05 -0700, Pine W wrote: After reading this [1] I am wondering if Wikimedia should start taking steps to reduce reliance on usernames and passwords. What steps do you refer to, or is this intentionally vague? Disallowing usernames and logins? Two-step authentication/verification? Something else? andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikimedia-l] let's elect people to serve on the wikimedia engineering community team! (brainstorming)
Hi, On Wed, 2014-08-06 at 12:01 +1000, svetlana wrote: On Wed, 6 Aug 2014, at 06:58, Quim Gil wrote: - encourage feedback by absolutely /anyone/ about the next features they'd like, Betas and Bugzilla today. Phabricator should make it easier to provide feedback in a wider range of topics, not only bugs. 99% of users of Wikimedia projects don't /know/ about these tools. That's the problem, and your response is not reflecting it. I've seen people on Village Pumps etc. complaining about certain software changes introduced. After I provided links to five [sic!] previous announcements, their reply was basically I didn't see them! Wrong place, you should have put them $here and $there instead. What is your proposal to _successfully_ make more people aware of such tools, if that's the problem? There are also enough (note to myself: [citation needed]) Wikipedia readers who don't know that you can edit an article yourself. Everybody has the personal freedom to not be interested in $stuff. Personally I'm fine with driving a car while having no clue why and how a car works. Cheers, andre PS: Obviously this is all my personal opinion. -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Engineers in residence
On Sun, 2014-08-10 at 00:23 +1000, svetlana wrote: utter and complete rubbish as it excludes the community and leaves all development within corporate hands; All against free software philosophy and/or community involvement I don't appreciate the language you used. Assume that people mean well, please? programming should be a hobby, like editing articles Free Software definitions don't imply that you shall not take money for your work, or eventually even make a living on it. It's part of the personal freedom that everybody has. However, nobody stops you from living your ideals of keeping programming a hobby only. :) Cheers, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] PHPUnit tests in MediaWiki
On Fri, 2014-08-15 at 10:48 -0700, Jon Robson wrote: Suddenly I cannot run PHPUnit tests on vagrant cd /vagrant/mediawiki/tests/phpunit /usr/bin/php5 phpunit.php --configuration /vagrant/mediawiki/extensions/Echo/tests/echo.suite.xml --group=Echo No MWMultiVersion instance initialized! MWScript.php wrapper not used? Only MWMultiVersion related ticket I'm aware of: https://bugzilla.wikimedia.org/show_bug.cgi?id=69419 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Preparser: Comments after === became a part of a header in xml representation
Hi, On Mon, 2014-08-18 at 14:11 +0400, Nikolay Shaplov wrote: When I do preparsing of the following text [...] This quite a minor problem, but I think it worth reporting. Feel free to create a minor bug report in https://bugzilla.wikimedia.org under MediaWiki Parser. Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Make port 22 on gerrit.wikimedia.org default for git (same as what 29418 is now)
On Tue, 2014-08-26 at 10:34 +0200, Petr Bena wrote: One of major issues I am now having is, that git needs to be accessed using non-standard port because regular ssh access is still being served on port 22. This is a problem on restricted networks where random ports are prohibited and blocked for various reasons, while standard ports like 21, 22, 80 etc are open. Related ticket: https://bugzilla.wikimedia.org/show_bug.cgi?id=35611 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Simplest UI for creating editing Phabricator tasks
Every new tool has its learning curve, and feedback helps to investigate making it less steep, so thanks for the feedback! :) On Wed, 2014-08-27 at 10:54 +0300, Amir E. Aharoni wrote: == Four == Another thought: I searched for the attachment icon. I found it, but I am not sure that it would be easy to find for all users. I might be subjective, thought, because I upload a lot of screenshots and mileage may vary for other users. Anecdotal comment: Enough users don't find the Add an attachment button/link in Bugzilla tickets either (and either ask how to add a screenshot, or upload to a 3rd party website and paste the link) so I'm not too afraid that things can get much worse... andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Upgrading jQuery UI to 1.11.1
On Fri, 2014-08-29 at 12:48 +0100, Thomas Mulhall wrote: Hi should we upgrade jQuery UI to 1.11.1 See https://bugzilla.wikimedia.org/show_bug.cgi?id=69386#c2 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] UploadWizard bug triage on Sep 09, 17:00UTC
Heja everybody, you are invited to join us on the next Bugday: Tuesday, September 09, 2014, 17:00 to 19:00UTC [1] in #wikimedia-multimedia on Freenode IRC [2] We will take a look at open Bugzilla tickets for UploadWizard. Everyone is welcome to join. No technical knowledge needed! It's an easy way to get involved or to give something back. More information can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140909 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there? andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] UploadWizard bug triage on Sep 09, 17:00UTC
Reminder: This starts in 60 minutes. On Sun, 2014-08-31 at 21:33 +0200, Andre Klapper wrote: you are invited to join us on the next Bugday: Tuesday, September 09, 2014, 17:00 to 19:00UTC [1] in #wikimedia-multimedia on Freenode IRC [2] We will take a look at open Bugzilla tickets for UploadWizard. Everyone is welcome to join. No technical knowledge needed! It's an easy way to get involved or to give something back. More information can be found here: https://www.mediawiki.org/wiki/Bug_management/Triage/20140909 For more information on triaging in general, check out https://www.mediawiki.org/wiki/Bug_management/Triage See you there? andre [1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html [2] See http://meta.wikimedia.org/wiki/IRC for more info on IRC -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Priorities in Bugzilla
On Tue, 2012-11-27 at 22:23 +, Tim Landscheidt wrote: If at the moment the priority field neither necessarily triggers action nor reflects the actual state of affairs, why even bother and not just delete/hide it from view? This would free more time to fix bugs. I don't see how dropping it all together helps planning or how it frees more time. Obviously anybody is free to work on anything but some stuff simply is more important than other stuff. I understand that there are many options and ways to express that importance though, and that severity, priority, target milestones, blocker bugs have some ambiguity to discuss in the long run. Right now I'd like to introduce a clear way to mark issues that should be handled immediately. Not to quote from another video about GitHub (where issues have only title and comment), let's not forget Git: No bug- tracker at all :-). I'm happy if using http://dir.gmane.org/gmane.comp.version-control.git works well for the Git developers and if important issues don't get lost. There are many ways and tools how to do software development, some work well for some, others work well for others, and not every tool is needed by everybody. GitHub itself has a bugtracker (Issues tab) by the way. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Standardizing highest priority in Bugzilla
On Wed, 2012-11-28 at 00:36 +0100, Krinkle wrote: I don't think adding more fields/values is the solution. Perhaps use milestone for immediate? Currently milestones are used in MediaWiki for tarballs (that we don't create for MW 1.21), in VisualEditor for deployments (VE-2012-12-34), and globally in MediaWiki Extensions for branches refering to a MediaWiki version. See my last two lines down there in this email. So both Get man on the moon (tracking) and [Regression] Bike shed should not be on fire have highest priority. But one is a regression milestoned for the current release, and the other is on track for N+2 release or maybe Future release. For the MediaWiki Bugzilla product: The conflict would be wmf deployments vs MW tarballs. We currently use TMs for MW tarballs and we have a 1.20.x, 1.21.0 there. We tag regressions with a code-update-regression keyword. For issue that should block wmf deployments the blocker bug 38865 is used (which is not great but I plan to tackle this later, not now). Besides an immediate bug without a milestone doesn't make sense to start with? If that is possible, there is a missing milestone I guess. It's possible. Immediate means immediate. ;) If it should block wmf deployment, also mark it as blocking bug 38865. If it should block an MW tarball, set the Target Milestone accordingly. We should make more use of being able to combine and query different fields to express clarity instead of adding more options that represent a multiple of values in other fields which then also need to be set separately I agree in the long run, but it might interfere with teams and their use of Bugzilla again. Global workflows vs. this works for my team. Right now I'd like to introduce a clear way to mark issues that should be handled immediately. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bugzilla Weekly Report
On Mon, 2012-11-26 at 03:00 +, reporter wrote: MediaWiki Bugzilla Report for November 19, 2012 - November 26, 2012 Trying to locate the script creating this weekly email, I found wikimedia/bugzilla/modifications/bugzilla-3.6.2/scripts/bugzilla_report.php in Gerrit. We're running Bugzilla 4.0 currently, and wikimedia/bugzilla/modifications/bugzilla-4.0/ does not include such a script. Does any historian know if it was just forgotten to drop the file in SVN (now Gerrit) in the bugzilla-4.0 folder? Mark, maybe? Thanks, andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Standardizing highest priority in Bugzilla: IMMEDIATE priority added
Thanks for all the good and valuable feedback, explaining your workflows, and discussing current flaws potential improvements in the long run. For the short term I have now created a priority called Immediate which should be used to identify issues that need immediate attention. This means that teams don't have to change their use of highest. Please set IMMEDIATE PRIORITY when it is appropriate. The documentation at http://www.mediawiki.org/wiki/Bugzilla/Fields has been updated accordingly: * Immediate priority: Must be fixed immediately (means: Drop any other work). Reports should have an assignee set in the Assigned to field. * Highest priority: Should be fixed next by a team. Teams should only have very few issues (preferably one) with highest priority at the same time. Reports should have an assignee set in the Assigned to field. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Complete (basic) analysis of MediaWiki
On Mon, 2012-12-03 at 19:40 +0100, Federico Leva (Nemo) wrote: Compare e.g. https://www.ohloh.net/p/mediawiki/contributors?query=sort=commits Also, https://bugzilla.wikimedia.org/weekly-bug-summary.cgi?tops=10days=10 proves they're not talking of the whole bugzilla but then they don't say which components. Would be helpful to mention the exact dataset you refer to. Also I'd rather challenge weekly-bug-summary.cgi's results: MediaWiki extensions has 2031 open bugs, and only 1883 have been filed in the last 10 days? = 148 bug reports got opened more than 274 years ago? But maybe I fail to read weekly-bug-summary.cgi correctly. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] the skin change in 1.21wmf5, display breakage, fix retrospective, again
After Sumana's summary of the wmf5 phase2 deployment (last Wednesday) at http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064718.html we ran into similar issues again yesterday night when deploying to English Wikipedia (phase3). According to Ryan in bug 42452 , this time The problem seems to be that ResourceLoader isn't delivering the updated CSS. Some minutes later Ryan touched and synced the startup.js and ext.vector.collapsibleNav.css files. Seems to be working correctly now. Still, we have several users that state that after purging their browser cache they *still* face issues: https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#What_just_happened_to_the_UI.3F Can anyone shed some light on how affected users can track down and help to fix the underlying problems here, if possible? What could users try, and which data could they provide? Obviously I'd love to avoid ending up with the same situation (and lively Village Pump discussions) again tomorrow when deploying wmf5 to all other Wikipedias. andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
