Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
Reading this thread and thinking about the proposed changes, im getting stuck, and there may be some inconsistencies. The problems identified seem to be 1. Core development is made much harder because of an abundance in local differences in wikis caused by local js and css. 2. Local wikis security may be compromised by lack of formalised structured code review of local js and css. (by staff/core developers?) The former seems to be generally acknowledged, and a large problem, the latter more or less debated, and a smaller problem (is that correct) Fixing 1 pretty much seems unfixable apart from completely banning local js altogether, which is something we don't want to do. Most of the solutions proposed as a compromise focus on fixing 2 by use of code review tools and standards, while still using 1 as a reason, though it actually does nothing to fix it. Is 2 still big enough of a problem to be fixed? If so, what does it need most? A more structured approach? More staffers reviewing gadgets? The use of the same tooling core uses? To me it seems more people doing review is a good thing, but are there enough resources for that? There should be more review more or less implies that that should be done by people who have +2 in core right now. I'm not sure if that is indeed the way to read former posts, but if it is, that is probably a bad idea. Apart from the additional workload that would cause - in this scenario I imagine loads and loads of patches waiting for review - it again moves the responsibility for maintaining a local wiki to a centralized body, which is bad for the local community. Alternatively, if we want other people to do the code review (e.g. local admins), shouldn't we be asking them what tools they need, if any, to effectively review and deploy patches, rather than centrally decide it for them? If we do ask them, I sincerely doubt their answer will be git and gerrit. As far as centralized gadgets go, lets not worry too much about those until the infrastructure for them actually exists. On Dec 12, 2013 8:58 AM, Chad innocentkil...@gmail.com wrote: +1 to everything MZM said. Except the XSS in user/site/gadget JS vs core/extension XSS. Intuition tells me the former is much more common. We just think about core/extension XSS because it gets a security release and tons of attention. -Chad On Dec 11, 2013 8:01 PM, MZMcBride z...@mzmcbride.com wrote: Bartosz Dziewoński wrote: I really liked what Jon said at the beginning, and what has apparently been lost in the discussions already – Keep gadgets for experiment, but ensure global gadgets are held to a higher standard of quality and made more visible to a wider audience.. Proper global gadgets still don't exist, but when they finally happen, experienced coders who do this for a living should take them under their wings (to clean up existing code, to check new contributions – but a post-merge code-review might still be more appropriate); but local gadgets should stay the safe haven of innovation they are now. Yep. We should obviously find ways to improve performance and reduce unnecessary code. Global (Wikimedia-wide) gadgets would be a good approach to take. Converting successful JavaScript gadgets into PHP MediaWiki extensions would be another good approach to take. There are others. The idea being proposed in bug 58236, as it was framed, was a non-starter. It simply riled people up and caused them to become defensive. (Its sibling bugs didn't help.) However, if we re-frame the issue, I think many people would agree that if there's a desire to enable a gadget for _all_ users, whatever functionality that is being provided by that gadget probably ought to be integrated into a MediaWiki extension. Brian Wolff wrote: Submitting patches is not the problem. Getting them reviewed in a timely fashion is a problem. Having power taken out of local wikis hands is a problem. Yep. Brian Wolff also wrote: I also think it would be unenforcable unless one plans to ban personal js in all forms. Quite: if you ban site-wide JavaScript (Common.js, Monobook.js, gadgets, etc.), people will simply revert to using per-user JavaScript (i.e., User:Foo/script.js) and importScript(), as they did for years. Tyler Romeo wrote: I'll be frank. I don't really care. If power is really the issue, then let people from the wikis have +2 on their wiki's Gerrit project. Currently you already have a +1/+2 model on the wiki. Any user can +1 while any local administrator can +2. Tyler Romeo also wrote: If the cost of increasing site-wide security and alleviating developers' pain is a few upset users who will get over it in a month or two, then so be it. With respect, your posts exhibit hints that you have not been a community member of a Wikimedia wiki, though perhaps I'm mistaken. I find it much easier to agree with Bartosz and Brian than with you. It's very
Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
Στις 11-12-2013, ημέρα Τετ, και ώρα 23:01 -0500, ο/η MZMcBride έγραψε: ... The idea being proposed in bug 58236, as it was framed, was a non-starter. It simply riled people up and caused them to become defensive. (Its sibling bugs didn't help.) However, if we re-frame the issue, I think many people would agree that if there's a desire to enable a gadget for _all_ users, whatever functionality that is being provided by that gadget probably ought to be integrated into a MediaWiki extension. I agree that code in MediaWiki:Common.js and in gadgets can cause problems with performance, security or even privacy that code review might prevent. A recent case in point was the Wdsearch code on en wikipedia, invoked on a few other wikis such that every viewed page caused a hit to toollabs, rendering that project inaccessible in short order. Having said that, I think MZMcBride is exactly right; we cannot go in telling folks 'You know all that freedom you had to create and edit your local wiki's javascript/gadgets and get immediate results? We're going to take that away now.' Like it or not, gadgets and js on many wikis is a matter of copy-paste and trying tweaks nearly at random to get the thing to work locally, and that's ok, because that's all the tools some wiki communities have available. Many don't have developers on hand, and they shouldn't have to; just as wikitext was intended to make editing easy for everybody and not just experts, our js/css setup was intended to make editing and adjustment of *that* easy -- or at least approachable -- for everybody and not just experts. And this has been the way of things for over ten years; changing it is a Big Deal. If we start a conversation with the folks who write and/or maintain the js and gadgets on their wikis, setting forth our goals (catching security/privacy/performance issues ahead of time) and asking for collaboration on how we can achieve those goals, rather than coming in with a decision already made for them, we're much more likely to get something constructive out of it. A pool of folks willing to review code in a timely fashion may be one piece of the solution; migration of some gadgets to MW extensions, as has been mentioned, may be another. We can suggest these as possibilities and see what else may be proposed. This list is a fine place to come up with more ideas; it is not a fine place, however, to have the real community discussion. Ariel ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Hi!
Hello, I am new to mediawiki and want to contribute, I have been lurking around the developer docs and articles for about 3 days. I have skills in php, javascript. At the same time I searching for the bugs that I can fix, but I really don't find one, I don't get to think of a starting point to fix the bug. Can somebody provide right direction to fix some bugs or the whole manual of mediawiki (i mean each and everything) should be read carefully before starting. Thanks ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Hi!
You might want to have a look at the Annoying little bugs page [1], I think it's meant exactly for people like you. [1]: https://www.mediawiki.org/wiki/Annoying_little_bugs Petr Onderka [[en:User:Svick]] On Thu, Dec 12, 2013 at 10:27 AM, Amanpreet Singh amanpreet.iitr2...@gmail.com wrote: Hello, I am new to mediawiki and want to contribute, I have been lurking around the developer docs and articles for about 3 days. I have skills in php, javascript. At the same time I searching for the bugs that I can fix, but I really don't find one, I don't get to think of a starting point to fix the bug. Can somebody provide right direction to fix some bugs or the whole manual of mediawiki (i mean each and everything) should be read carefully before starting. Thanks ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Commons Video Uploads waiting (Bug #58155)
On Wed, Dec 11, 2013 at 7:26 PM, Brian Wolff bawo...@gmail.com wrote: The videos are (mostly) over 1 gb, which is our upload limit. Hence maintenance script needed. Ah. Thanks for the clarification. *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Commons Video Uploads waiting (Bug #58155)
Le 11/12/13 23:29, Antoine Musso a écrit : Le 11/12/13 19:15, Manuel Schneider a écrit : Hi, I have a bunch of videos from our last conference waiting for an upload to Commons. For this I have filed a bug several days ago: * https://bugzilla.wikimedia.org/show_bug.cgi?id=58155 Can someone please take care of this in a timely manner? The conference is now three weeks ago and soon nobody will be interested in the videos anymore if we don't provide them near enough to the event. Hello, I have no idea which script should be used to upload those files. If anyone has a link to the step-by-step guide to achieve it, I will be more than happy to execute the commands and proceed with the uploads. I have started a process to download the files from http://lan.80686.net/ It is running on tin.eqiad.wmnet in a screen. Files being written to /home/hashar/bug58155 Whenever that is complete, we can process with the actual import. -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Commons Video Uploads waiting (Bug #58155)
Great, thanks a lot! Please ignore the subfolder. /Manuel Am 12.12.2013 10:43, schrieb Antoine Musso: I have started a process to download the files from http://lan.80686.net/ It is running on tin.eqiad.wmnet in a screen. Files being written to /home/hashar/bug58155 Whenever that is complete, we can process with the actual import. -- Manuel Schneider - Chief Information Officer Wikimedia CH - Verein zur Förderung Freien Wissens Lausanne, +41 (21) 340 66 22 - www.wikimedia.ch ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
I totally agree with Liangent. Having gadgets disabled by default will move a larger number of scripts to Common.js, leading to a whole new class of problems. Strainu 2013/12/9 Liangent liang...@gmail.com: MediaWiki:Common.js can also create disagreement and defaults change without notice. Actually what I did sometimes is to move code from MediaWiki:Common.js to default gadgets, so it can be disabled per user (for example, some users are using a too slow computer or network), and at the same time, this makes maintenance easier for developers, because gadgets can be made modularized, instead of using a big JavaScript and CSS file (Common.js/css). -Liangent On Tue, Dec 10, 2013 at 5:02 AM, K. Peachey p858sn...@gmail.com wrote: For wider discussion --- From: bugzilla-daemon at wikimedia.org Subject: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites http://news.gmane.org/find-root.php?message_id=%3cbug%2d58236%2d3%40https.bugzilla.wikimedia.org%2f%3e Newsgroups: gmane.org.wikimedia.mediawiki.bugs http://news.gmane.org/gmane.org.wikimedia.mediawiki.bugs Date: 2013-12-09 20:41:41 GMT (19 minutes ago) https://bugzilla.wikimedia.org/show_bug.cgi?id=58236 Web browser: --- Bug ID: 58236 Summary: No longer allow gadgets to be turned on by default for all users on Wikimedia sites Product: Wikimedia Version: wmf-deployment Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Site requests Assignee: wikibugs-l at lists.wikimedia.org Reporter: jared.zimmerman at wikimedia.org CC: benapetr at gmail.com, bugzilla+org.wikimedia at tuxmachine.com, dereckson at espace-win.org, greg at wikimedia.org , tomasz at twkozlowski.net, wikimedia.bugs at snowolf.eu Classification: Unclassified Mobile Platform: --- Gadgets being turned on for all site users (including readers) can cause a confusing users experience, especially when there is some disagreement and defaults change without notice (readers are rarely if ever part of these discussions) Move to model where gadgets are per user rather than part of a default experience for users -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l at lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/wikibugs-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
On 12/12/13, Martijn Hoekstra martijnhoeks...@gmail.com wrote: Reading this thread and thinking about the proposed changes, im getting stuck, and there may be some inconsistencies. The problems identified seem to be 1. Core development is made much harder because of an abundance in local differences in wikis caused by local js and css. 2. Local wikis security may be compromised by lack of formalised structured code review of local js and css. (by staff/core developers?) The former seems to be generally acknowledged, and a large problem, the latter more or less debated, and a smaller problem (is that correct) I actually feel the opposite. Point #1 does not make core development much harder. There's the occasional issue with local customization, but in my experience these types of issues are few and far between. Point #2 does scare me a little bit, particularly on the non enwikipedia sites. I agree with Chad that anecdotes in this area probably have more to do with no one looking, than any actual greater security. --Bawolff ___ 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
On Thu, Dec 12, 2013 at 1:50 AM, Nathan Larson nathanlarson3...@gmail.com wrote: From my experience on the Internet, I suspect that most of the times when people are accused of trolling, they are actually serious; and most of the times when people are trolling, they're taken seriously and no one expresses any suspicion that they were trolling. Poe's law?[1] [1]: https://en.wikipedia.org/wiki/Poe%27s_law ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Re-evaluating MediaWiki ResourceLoader's debug mode
Another point to look into if someones wants to refactor the RL debug=true: When loading VE with debug=true hundreds of modules are loaded (with different requests) and it takes long to load it. It would be nice to have an option of debug=0.5 :) in which all the resources (or at least the ve resources) will be loaded as one request, but without minified code and including all the comment. On Wed, Dec 11, 2013 at 8:46 PM, Jon Robson jdlrob...@gmail.com wrote: +1000 to what Max says. It really is kinda obvious to anyone who needs to know how to get into debug mode and if not there are wiki pages and if not it's easy enough to find out if you care enough. That said debug mode could definitely be improved and I'm glad you brought this topic up Max. A few things of the top of my head I'd like to see: * RTL working in debug mode * The code in ResourceLoader really could do with a good refactor - there are far too many different code paths and it would be good if we could simplify this to get them as close as possible. When I've worked with RL in the past to design my own modules which involves files I've had a lot of headaches trying to get things to work in both debug mode and non-debug mode (JavaScript templates [1] being one concrete example) - and even then the result wasn't quite was I was hoping for in that debug mode uses load.php urls to inject JavaScript before the file that needs it. [1] https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FMobileFrontend.git/1f3c57137afae1d0f8ac602b62dccc741893d670/includes%2Fmodules%2FMFResourceLoaderModule.php On 11 Dec 2013 08:33, Max Semenik maxsem.w...@gmail.com wrote: On 11.12.2013, 19:36 Brian wrote: As everybody else already said, less bandwidth is a good thing for most people, obfuscation is OK when the source is available elsewhere, and debug=true is not hard for developers to find. I'd actually disagree with the assertion that debug=true is easy to find, particularly for people who aren't active developers. Some random on the internet who just wants to see what our js looks like (out of curiosity or whatever) is not going to be able to find debug=true. If they look at the URL it will be pretty obvious because all of them have debug=false as first parameter. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] OAuth currently broken on wikis with CirrusSearch
Dear all, OAuth is currently broken on any wiki that has CirrusSearch deployed to it in either primary or secondary mode. We're working on getting this issue fixed as soon as possible. I'll post an update here when we have a timescale for the fix. Thanks, Dan -- Dan Garry Associate Product Manager for Platform Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OAuth currently broken on wikis with CirrusSearch
For reference, the list of wikis which Cirrus is deployed, and therefore where OAuth is broken, is available here: https://www.mediawiki.org/wiki/Search#Wikis Dan On 12 December 2013 16:46, Dan Garry dga...@wikimedia.org wrote: Dear all, OAuth is currently broken on any wiki that has CirrusSearch deployed to it in either primary or secondary mode. We're working on getting this issue fixed as soon as possible. I'll post an update here when we have a timescale for the fix. Thanks, Dan -- Dan Garry Associate Product Manager for Platform Wikimedia Foundation -- Dan Garry Associate Product Manager for Platform Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OAuth currently broken on wikis with CirrusSearch
Note that the wikis that say they were deployed on December 11th but do not have a strike through them have Cirrus running, but their indexes are still being built. I believe OAuth will be broken on those wikis as well. This requires two fixes to actually fix, both of which are in review state pending approval, another test on beta, and eventual deployment. We should have them out sometime in the next few hours. Nik On Thu, Dec 12, 2013 at 11:48 AM, Dan Garry dga...@wikimedia.org wrote: For reference, the list of wikis which Cirrus is deployed, and therefore where OAuth is broken, is available here: https://www.mediawiki.org/wiki/Search#Wikis Dan On 12 December 2013 16:46, Dan Garry dga...@wikimedia.org wrote: Dear all, OAuth is currently broken on any wiki that has CirrusSearch deployed to it in either primary or secondary mode. We're working on getting this issue fixed as soon as possible. I'll post an update here when we have a timescale for the fix. Thanks, Dan -- Dan Garry Associate Product Manager for Platform Wikimedia Foundation -- Dan Garry Associate Product Manager for Platform Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Request for comments: Localisation format changes
Dear list readers, The Wikimedia Foundation teams for VisualEditor and Language Engineering have put together a document that proposes a change in the MediaWiki localisation format. Please provide your input at https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Localisation_format We have also proposed to discuss this RfC in the upcoming RfC review meeting of 2013-12-18[1]. As far as we know, no time has been set for this meeting, yet. Thank you for your insights. Cheers! -- Siebrand Mazeland Product Manager Language Engineering Wikimedia Foundation M: +31 6 50 69 1239 Skype: siebrand Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Commons Video Uploads waiting (Bug #58155)
Le 12/12/13 10:43, Antoine Musso a écrit : I have no idea which script should be used to upload those files. If anyone has a link to the step-by-step guide to achieve it, I will be more than happy to execute the commands and proceed with the uploads. I have started a process to download the files from http://lan.80686.net/ It is running on tin.eqiad.wmnet in a screen. Files being written to /home/hashar/bug58155 Whenever that is complete, we can process with the actual import. All files have been uploaded now! Please contact me if there is any issue :-) Thanks to Ariel Glenn and Nemo bis for the useful commands. -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
On Thu, Dec 12, 2013 at 7:21 AM, Brian Wolff bawo...@gmail.com wrote: I actually feel the opposite. Point #1 does not make core development much harder. There's the occasional issue with local customization, but in my experience these types of issues are few and far between. Point #2 does scare me a little bit, particularly on the non enwikipedia sites. I agree with Chad that anecdotes in this area probably have more to do with no one looking, than any actual greater security. --Bawolff I'll compile hard numbers when I have some free time, but I strongly agree with Bawolff here. Site javascript has a significant percentage of the totally xss'es we've fixed, and almost no one is reviewing them. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wikimedia Commons Video Uploads waiting (Bug #58155)
Thanks a lot to Hashar and those who helped! I am very happy, I just added the videos to the program page of the conference and will send a mail to our community in a minute. They will be very happy as well! https://de.wikipedia.org/wiki/Wikipedia:WikiCon_2013/Programm Regards, /Manuel Am 12.12.2013 18:36, schrieb Antoine Musso: All files have been uploaded now! Please contact me if there is any issue :-) Thanks to Ariel Glenn and Nemo bis for the useful commands. -- Manuel Schneider - Chief Information Officer Wikimedia CH - Verein zur Förderung Freien Wissens Lausanne, +41 (21) 340 66 22 - www.wikimedia.ch ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Request for comments: Localisation format changes
Cool! On Thu, Dec 12, 2013 at 10:34 AM, Siebrand Mazeland (WMF) smazel...@wikimedia.org wrote: We have also proposed to discuss this RfC in the upcoming RfC review meeting of 2013-12-18[1]. As far as we know, no time has been set for this meeting, yet. The WMF Engineering calendar shows the RfC review meeting at 2-3pm PST on 2013-12-18. -- Arthur Richards Software Engineer, Mobile [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] FWD: [Bug 58236] New: No longer allow gadgets to be turned on by default for all users on Wikimedia sites
2013/12/12 Quim Gil q...@wikimedia.org On 12/11/2013 11:21 AM, Chad wrote: Sending wiki edits to Gerrit for review? Absolutely not. I'm totally cool with the idea of code review for Gadgets so forth, just not using Gerrit. We considered it for Scribunto (and heck, I wrote half of a proof of concept) but shot it down because the idea totally sucked. I think I agree with your conclusion, but based on my assumptions. It would be useful to know why you think it sucked. Alright, not on Gerrit. Where? https://www.mediawiki.org/wiki/Gadgets_2.0 ? -- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bug Fixing: #21481
Hi, I am new to wikimedia, I want to start bug fixing for wikimedia so I have started from this annoying little bug https://bugzilla.wikimedia.org/show_bug.cgi?id=21481 Can somebody guide me from where to start and search for fixing this bug, ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki Homepage Redesign
Hi Brena! We have already discussed in person (remotely) but here goes a public reply as well. On 12/02/2013 11:47 AM, Brena Monteiro wrote: Hello everyone, I'm selected to participate of OPW and I will work at MediaWiki Homepage Redesign project in which Quim and Heather are my mentors. Yes! To anybody interested: the goal is to have a proposal to replace the current mediawiki.org homepage by March 10 (end of Brena's OPW internship). Ideally this proposal will consist on a wiki page that can just be copied and pasted. The steps to get there are described at https://www.mediawiki.org/wiki/User:Monteirobrena/OPW#Deliverables Your feedback is welcome. We also want to identify reviewers willing to pay special attention to this project, contributing feedback and helping to reach decisions. If you are interested, please step in. My first activity is identify the main problems at current homepage. I'm watching the page: Requests for comment/MediaWiki.org Main Page tweaks [1] and I would like to emphasise that all collaboration is welcome. After a chat yesterday between Brena, Heather and myself, we agreed that the next step is to agree on a design document. https://www.mediawiki.org/wiki/WMF_Project_Design_Review_Process#Design_Document We need to deal with one wiki page only (an important wiki page, but not as complex as the user interface of a full application), but still this document will be important to define what we want to do, and why. Then mockups. Then wiki implementation. Trying to sign off each phase reaching community consensus. For those willing to get involved now, at https://www.mediawiki.org/wiki/User_talk:Monteirobrena/OPW#Design_document I just created topics to discuss the renaming of https://www.mediawiki.org/wiki/User:Monteirobrena/OPW and set up its right scope... ... and also the actions to close officially https://www.mediawiki.org/wiki/Requests_for_comment/MediaWiki.org_Main_Page_tweaks after integrating the relevant details to the design document. Most of the communication will happen around those wiki pages. Brena will use this list for announcements and wider requests for feedback. You can also find us on #mediawiki IRC. -- Quim Gil Technical Contributor Coordinator @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] OAuth currently broken on wikis with CirrusSearch
On Thu, Dec 12, 2013 at 11:53 AM, Nikolas Everett never...@wikimedia.orgwrote: Note that the wikis that say they were deployed on December 11th but do not have a strike through them have Cirrus running, but their indexes are still being built. I believe OAuth will be broken on those wikis as well. This requires two fixes to actually fix, both of which are in review state pending approval, another test on beta, and eventual deployment. We should have them out sometime in the next few hours. I've just verified the fix in production. Please let me know if any of you are still seeing the error. Thanks, Nik ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Announcement: Kunal Mehta joins Wikimedia as Features Contractor
Hello everyone, It’s with great pleasure that I’m announcing that Kunal Mehta[1] has joined the Wikimedia Foundation as contractor in Features Engineering. Before joining us (and currently), Kunal is a student in college, switching from computer science to business administration for reasons that I’m sure warrant more discussion. Kunal is currently a Wikipedia admin got involved working on the projects 8 years ago. He also helps writing and maintaining bots (legoktm 3’s pywikibot) and working on the nether regions of the volunteer developer community as part of the Volunteer Response Team, which he currently continues to do[2]. I met him at Wikimania through a Wikidata scholarship because apparently we were too cheap to spring for his ticket. Kunal will be working with the Core Features Team since MassMessage[3] and Echo[4] have overlapping concerns, and Flow[5] can use more development support now that it is out. When he isn’t doing that you’ll see him around adding this and that to core or the bots. :-) Kunal lives and goes to school in San Jose. Most importantly, he’s unlocked level 2 in Naan Sense on FourSquare[6]. From his username on the projects, I’d also bet he must like Lego Mindstorms[7]. For the record, Kunal, I, for one, welcome our new robot overlords. As you have guessed from my usual tardiness and my drive to finish my announcements before the calendar year, his first official day was actually October 28th (Only two months ago? Not bad, not bad at all). Please join me in a belated welcome of Kunal Mehta to the Wikimedia Foundation. Take care, Terry [1]: [[User:legoktm]] [2]: https://github.com/legoktm [3]: https://www.mediawiki.org/wiki/Extension:MassMessage [4]: https://www.mediawiki.org/wiki/Echo_(Notifications) [5]: https://www.mediawiki.org/wiki/Flow_Portal [6]: https://foursquare.com/legoktm/badge/51296de6e4b096ae4b48fb8e?ref=tw [7]: https://en.wikipedia.org/wiki/Lego_Mindstorms_NXT terry chay 최태리 Director of Features Engineering Wikimedia Foundation “Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.” p: +1 (415) 839-6885 x6832 m: +1 (408) 480-8902 e: tc...@wikimedia.org i: http://terrychay.com/ w: http://meta.wikimedia.org/wiki/User:Tychay aim: terrychay ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Sherah Smith joins Wikimedia as Fundraising Engineer in Features
Hello everyone, It’s with great pleasure that I’m announcing that Sherah Smith[1] has joined the Wikimedia Foundation as Fundraising Engineer in Features. Before joining us, Sherah was a full stack software engineer at Hackbright Academy[2] helping write a lot of their curriculum development and engineering fellowship software. She also did a brief stint as a front-end developer at yerdle.com on some of their campaigns. She was a referral through Ryan Kaldari, and managed some time during small amounts of her super busy schedule at Hackbright to talk to the FR-tech team and see how truly awesome they are. Long ago (2010), she received her B.S. in computer science at Evergreen State College. Sherah will be working in Fundraising Tech as a front-end engineer. So expect some amazingly cool visualization stuff coming from the annual fundraiser, followed by super less annoying payment processing pages, and such. She also will bug you about opportunities to learn more stuff here. When she isn’t making Fundraising awesome, she can be found writing and performing comedy in various forms, reading excruciatingly depressing novels, and hiking all around the Bay Area. She is also perpetually hacking on things, especially ridiculous apps and games in MeteorJS. Her spirit animal is the pizzacat. Oh, by the way, don’t be an idiot like me and pronounce her name correctly—it’s not sher-a, but she-ra, “just like the princess of power.”[5] As you have guessed from my usual tardiness, her first official day was Monday, December 9. I know you’re thinking, “Only a few days late? What is going on Terry?” Well there is a running pool that Erik has a little spreadsheet in his computer brain of his to pester us Directors to actually announce the staff we hire and I finally figured it’s useless to procrastinate in order to fight the Man. Please join me in a belated welcome of Sherah Smith to the Wikimedia Foundation. :-) Take care, Terry [1]: http://sherahsmith.com/ [2]: http://www.hackbrightacademy.com/ [3]: https://yerdle.com/ [4]: http://sherahsmith.tumblr.com/ [5]: https://en.wikipedia.org/wiki/She-Ra terry chay 최태리 Director of Features Engineering Wikimedia Foundation “Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.” p: +1 (415) 839-6885 x6832 m: +1 (408) 480-8902 e: tc...@wikimedia.org i: http://terrychay.com/ w: http://meta.wikimedia.org/wiki/User:Tychay aim: terrychay ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wmfsf] Announcement: Kunal Mehta joins Wikimedia as Features Contractor
On Thu, Dec 12, 2013 at 5:08 PM, Terry Chay tc...@wikimedia.org wrote: Hello everyone, It’s with great pleasure that I’m announcing that Kunal Mehta[1] has joined the Wikimedia Foundation as contractor in Features Engineering. Sweet! Welcome, Kunal! Roan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Announcement: Kunal Mehta joins Wikimedia as Features Contractor
On 2013-12-12 6:08 PM, Terry Chay tc...@wikimedia.org wrote: Hello everyone, It’s with great pleasure that I’m announcing that Kunal Mehta[1] has joined the Wikimedia Foundation as contractor in Features Engineering. Before joining us (and currently), Kunal is a student in college, switching from computer science to business administration for reasons that I’m sure warrant more discussion. Kunal is currently a Wikipedia admin got involved working on the projects 8 years ago. He also helps writing and maintaining bots (legoktm 3’s pywikibot) and working on the nether regions of the volunteer developer community as part of the Volunteer Response Team, which he currently continues to do[2]. I met him at Wikimania through a Wikidata scholarship because apparently we were too cheap to spring for his ticket. Kunal will be working with the Core Features Team since MassMessage[3] and Echo[4] have overlapping concerns, and Flow[5] can use more development support now that it is out. When he isn’t doing that you’ll see him around adding this and that to core or the bots. :-) Kunal lives and goes to school in San Jose. Most importantly, he’s unlocked level 2 in Naan Sense on FourSquare[6]. From his username on the projects, I’d also bet he must like Lego Mindstorms[7]. For the record, Kunal, I, for one, welcome our new robot overlords. As you have guessed from my usual tardiness and my drive to finish my announcements before the calendar year, his first official day was actually October 28th (Only two months ago? Not bad, not bad at all). Please join me in a belated welcome of Kunal Mehta to the Wikimedia Foundation. Take care, Terry [1]: [[User:legoktm]] [2]: https://github.com/legoktm [3]: https://www.mediawiki.org/wiki/Extension:MassMessage [4]: https://www.mediawiki.org/wiki/Echo_(Notifications) [5]: https://www.mediawiki.org/wiki/Flow_Portal [6]: https://foursquare.com/legoktm/badge/51296de6e4b096ae4b48fb8e?ref=tw [7]: https://en.wikipedia.org/wiki/Lego_Mindstorms_NXT terry chay 최태리 Director of Features Engineering Wikimedia Foundation “Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.” p: +1 (415) 839-6885 x6832 m: +1 (408) 480-8902 e: tc...@wikimedia.org i: http://terrychay.com/ w: http://meta.wikimedia.org/wiki/User:Tychay aim: terrychay ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l Congrats! -bawolff ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Hook for Adding to Empty Search Results
I have an extension using the ArticleFromTitle hook to generate pages for components of a large system we operate. There are approximately 6000 components at the moment with static inventory and config data in a database and live status data in a number of other systems. We are using MediaWiki as a historical maintenance knowledge-base for the staff. With this extension, we can integrate all the data for each device in one place. We can hit MyNS:DeviceName and get a page that describes a device and that page can link to other pages in the main namespace that techs create with vendor details, model info, manuals, etc. We can even keep a talk page for each device. Very handy. Trouble now is I want to be able to find devices using the search feature. SpecialSearchResults looked promising but that only gets called when there is at least one match in normal pages. So, I looked at SpecialSearchNoResults but that doesn't allow me to add to the empty results. Doesn't anyone have a suggestion on how I could go about this? I really want to avoid generating the text of pages externally periodically and loading them into the wiki using the importTextFile maintenance script. The only other thought I had was to extend the SearchMySQL class and change $wgSearchType but I'm hoping to avoid that. Any ideas? --Paul ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Bug Fixing: #21481
Amanpreet Singh wrote: Hi, I am new to wikimedia, Hello and welcome! :-) I want to start bug fixing for wikimedia so I have started from this annoying little bug https://bugzilla.wikimedia.org/show_bug.cgi?id=21481 Can somebody guide me from where to start and search for fixing this bug, Nemo and Bawolff have replied on the bug report. Please feel free to ask any questions there or here on this mailing list. MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
