Re: [Wikitech-l] [WikimediaMobile] [Wiki Loves Monuments] WLM app: create account?
hi, yuvi said he is not able to add account creation to the wlm mobile app because the mw api is not usable. there is a bug filed in march, now approaching 6 months age: https://bugzilla.wikimedia.org/show_bug.cgi?id=46072 with priority high, which means according to andre klapper: https://www.mediawiki.org/wiki/Bugzilla/Fields#Priority Not the next task, but should be fixed soon. Depending on teams manpower this can take between one and six months. who needs to do what to get this fixed? (sorry for crossposting to wikitech, as i understood this is not a mobile problem ...) rupert. On Sun, Sep 2, 2012 at 2:57 AM, Tomasz Finc tf...@wikimedia.org wrote: Sadly not for this contest. The API to create accounts never reached enough maturity while this app was in development. Background info here : http://www.mediawiki.org/wiki/User:Akshay.agarwal Thats why we dont require it to save images for later upload. I agree that this would be great to have in the future. --tomasz On Sat, Sep 1, 2012 at 1:41 PM, Cristian Consonni kikkocrist...@gmail.com wrote: 2012/9/1 rupert THURNER rupert.thur...@gmail.com: hi philip, would it be possible to add an account creation screen to the wlm mobile app? I posted the same request here: http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feedback#Registration a couple of days ago. Cristian ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
On 27/08/13 03:12, C. Scott Ananian wrote: Stated more precisely: a non-GPL-compatible license for an extension means that the extension can never be distributed with core. That is incorrect, the GPL does not say that. The GPL allows verbatim copies of source code, with no restrictions on the license of any bundled or dynamically linked code. Only non-source forms (or binaries in v2) have more restrictive conditions. Since the MediaWiki core and extensions are distributed solely in source form, the non-source (binary) conditions do not apply. -- Tim Starling ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] [Language Engineering] Reminder: Bug triage for RTL bugs today August 28, 2013 at 1700 UTC/1000 PDT
Hello, This is a reminder that the Language Engineering team will be hosting an hour long bug triage for R-T-L bugs later today, i.e. August 28, 2013 at 1700 UTC/1000 PDT on the IRC channel #mediawiki-i18n (Freenode). etherpad link: https://etherpad.wikimedia.org/p/BugTriage-i18n-2013-08 Thanks Runa -- Forwarded message -- From: Runa Bhattacharjee rbhattachar...@wikimedia.org Date: Fri, Aug 23, 2013 at 11:56 AM Subject: Language Engineering bug triage session for RTL language bugs - Aug 28th 2013, Wednesday 1700 UTC/1000PDT To: Wikimedia developers wikitech-l@lists.wikimedia.org, Wikimedia Mailing List wikimedi...@lists.wikimedia.org, MediaWiki internationalisation mediawiki-i...@lists.wikimedia.org Hello, The Wikimedia Language Engineering team will be hosting a bug triage session on Wednesday, August 28th 2013 at 17:00 UTC (10:00 PDT) for some of the bugs that exist in languages written from Right-to-Left (RTL). During this 1 hour session we will be using the etherpad linked below to collaborate. We have already listed some bugs, but please feel free to add more bugs (or file new ones!), and comments about what you’d like to see addressed during the session. You can send questions directly to me on email or IRC (nick: arrbee). Please see below for the event details. Thank you. regards Runa === Event Details === # What: Bug triage session for RTL language bugs # Date: August 28, 2013 (Wednesday) # Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://www.timeanddate.com/worldclock/fixedtime.html?iso=20130828T1700 ) # IRC Channel: #mediawiki-i18n (Freenode) # Etherpad: https://etherpad.wikimedia.org/p/BugTriage-i18n-2013-08 Questions can be sent to: runa at wikimedia dot org -- Language Engineering - Outreach and QA Coordinator Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] CodeEditor deployment (was [Wikitech-ambassadors] Deployment highlights for the week of August 26th)
On Tue, Aug 27, 2013 at 10:01 PM, MZMcBride z...@mzmcbride.com wrote: Helder . wrote: On Fri, Aug 23, 2013 at 6:39 PM, Greg Grossmeier g...@wikimedia.org wrote: == Thursday == * CodeEditor support will be enabled for all JS and CSS on all wikis Without fixing the bug which makes it use spaces instead of tabs? Seriously? https://bugzilla.wikimedia.org/show_bug.cgi?id=39616 This bug is now resolved/fixed. :-) Thanks to Alex M. and Ori L. for working on this. That reminds me. The patch adds a JS hook so individual users can select spaces vs tabs for their newly-added lines. Is this going to cause complaints that pages wind up with a mixture of lines indented with spaces and lines indented with tabs? Also, how is indenting with tabs going to interact with people who use the plain-text editor rather than CodeEditor, since it's somewhat difficult to use tabs there because the tab key moves to the next form field? -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
Tim, thanks, I found this a very interesting aspect that I have not considered before. 2013/8/28 Tim Starling tstarl...@wikimedia.org On 27/08/13 03:12, C. Scott Ananian wrote: Stated more precisely: a non-GPL-compatible license for an extension means that the extension can never be distributed with core. That is incorrect, the GPL does not say that. The GPL allows verbatim copies of source code, with no restrictions on the license of any bundled or dynamically linked code. Only non-source forms (or binaries in v2) have more restrictive conditions. Since the MediaWiki core and extensions are distributed solely in source form, the non-source (binary) conditions do not apply. -- Tim Starling ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Project director Wikidata Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin Tel. +49-30-219 158 26-0 | http://wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Advance notice: I'm taking a sabbatical October-December
I've been accepted to Hacker School https://www.hackerschool.com, a writers' retreat for programmers in New York City. I will therefore be taking an unpaid personal leave of absence from the Wikimedia Foundation via our sabbatical program. My last workday before my leave will be Friday, September 27. I plan to be on leave all of October, November, and December, returning to WMF in January. During my absence, Quim Gil will be the temporary head of the Engineering Community Team. Thank you, Quim! I'll spend much of September turning over responsibilities to him. Over the next month I'll be saying no to a lot of requests so I can ensure I take care of all my commitments by September 27th, when I'll be turning off my wikimedia.org email. If there's anything else I can do to minimize inconvenience, please let me know. And -- I have to say this -- oh my gosh I'm so excited to be going to Hacker School in just a month! Going from advanced beginner to confident programmer! Learning face-to-face with other coders, 30-45% of them women, all teaching each other! Thank you, WMF, for the sabbatical program, and thanks to my team for supporting me on this. I couldn't do this without you. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Advance notice: I'm taking a sabbatical October-December
Hi! On 08/28/2013 07:24 AM, Sumana Harihareswara wrote: I've been accepted to Hacker School https://www.hackerschool.com Congratulations! You have worked a lot to achieve this (and it is only the beginning). During my absence, Quim Gil will be the temporary head of the Engineering Community Team. ... which I don't expect to bring much change to the quite horizontal and distributed way of working of our team. But in any case: happy to Be Useful. PS: if we get bored here we will start collecting bugs to test you when you're back. ;) -- 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] CodeEditor deployment (was [Wikitech-ambassadors] Deployment highlights for the week of August 26th)
On Wed, Aug 28, 2013 at 6:29 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: That reminds me. The patch adds a JS hook so individual users can select spaces vs tabs for their newly-added lines. Is this going to cause complaints that pages wind up with a mixture of lines indented with spaces and lines indented with tabs? Also, how is indenting with tabs going to interact with people who use the plain-text editor rather than CodeEditor, since it's somewhat difficult to use tabs there because the tab key moves to the next form field? IMO we should phase out use of the literal tab character, which is very. teletype-centric. I would recommend normalizing tabs on input into four-spaces. But keeping existing behavior when cut-n-pasting text with tabs isn't awful for now, I suppose. This doesn't add *new* tabs when typing code does it? -- brion ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [WikimediaMobile] [Wiki Loves Monuments] WLM app: create account?
Basically, nobody seemed to like my approach of adapting the existing hacky captcha interface for action=edit to action=createaccount. I would recommend totally rewriting the captcha plugin system in ConfirmEdit to not be awful, and devise a more sustainable and extensible API for creating accounts and displaying confirmation screens. It'd be way faster to tidy up and merge the existing patch and use that 'for now', but as they say temporary solutions often end up becoming permanent -- brion On Tue, Aug 27, 2013 at 11:33 PM, rupert THURNER rupert.thur...@gmail.comwrote: hi, yuvi said he is not able to add account creation to the wlm mobile app because the mw api is not usable. there is a bug filed in march, now approaching 6 months age: https://bugzilla.wikimedia.org/show_bug.cgi?id=46072 with priority high, which means according to andre klapper: https://www.mediawiki.org/wiki/Bugzilla/Fields#Priority Not the next task, but should be fixed soon. Depending on teams manpower this can take between one and six months. who needs to do what to get this fixed? (sorry for crossposting to wikitech, as i understood this is not a mobile problem ...) rupert. On Sun, Sep 2, 2012 at 2:57 AM, Tomasz Finc tf...@wikimedia.org wrote: Sadly not for this contest. The API to create accounts never reached enough maturity while this app was in development. Background info here : http://www.mediawiki.org/wiki/User:Akshay.agarwal Thats why we dont require it to save images for later upload. I agree that this would be great to have in the future. --tomasz On Sat, Sep 1, 2012 at 1:41 PM, Cristian Consonni kikkocrist...@gmail.com wrote: 2012/9/1 rupert THURNER rupert.thur...@gmail.com: hi philip, would it be possible to add an account creation screen to the wlm mobile app? I posted the same request here: http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feedback#Registration a couple of days ago. Cristian ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Mobile-l mailing list mobil...@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mobile-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Advance notice: I'm taking a sabbatical October-December
Sumana Harihareswara sumanah at wikimedia.org writes: I've been accepted to Hacker School https://www.hackerschool.com, a writers' retreat for programmers in New York City. I will therefore be taking an unpaid personal leave of absence from the Wikimedia Foundation via our sabbatical program. My last workday before my leave will be Friday, September 27. I plan to be on leave all of October, November, and December, returning to WMF in January. During my absence, Quim Gil will be the temporary head of the Engineering Community Team. Thank you, Quim! I'll spend much of September turning over responsibilities to him. Over the next month I'll be saying no to a lot of requests so I can ensure I take care of all my commitments by September 27th, when I'll be turning off my wikimedia.org email. If there's anything else I can do to minimize inconvenience, please let me know. And -- I have to say this -- oh my gosh I'm so excited to be going to Hacker School in just a month! Going from advanced beginner to confident programmer! Learning face-to-face with other coders, 30-45% of them women, all teaching each other! Thank you, WMF, for the sabbatical program, and thanks to my team for supporting me on this. I couldn't do this without you. Congratulations, Sumana! This sounds like a great opportunity for you. It is so great that programs like Hacker School and OPW are springing up these days to help people that are out of school get experience becoming better programmers. I'm looking forward to hearing about your experiences there. --Rachel *Gnome FOSS Outreach Program for Women Intern Browser Test Automation, Wikimedia Foundation* ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
On Wed, Aug 28, 2013 at 5:52 AM, Tim Starling tstarl...@wikimedia.orgwrote: On 27/08/13 03:12, C. Scott Ananian wrote: Stated more precisely: a non-GPL-compatible license for an extension means that the extension can never be distributed with core. That is incorrect, the GPL does not say that. The GPL allows verbatim copies of source code, with no restrictions on the license of any bundled or dynamically linked code. Only non-source forms (or binaries in v2) have more restrictive conditions. Since the MediaWiki core and extensions are distributed solely in source form, the non-source (binary) conditions do not apply. Yup. In retrospect, an odd oversight for GPL v3; perhaps more understandable for v2. Luis -- Luis Villa Deputy General Counsel Wikimedia Foundation 415.839.6885 ext. 6810 NOTICE: *This message may be confidential or legally privileged. If you have received it by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity.* ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] New search backend live on mediawiki.org
Today we threw the big lever and turned on our new search backend at mediawiki.org. It isn't the default yet but it is just about ready for you to try. Here is what is we think we've improved: 1. Templates are now expanded during search so: 1a. You can search for text included in templates 1b. You can search for categories included in templates 2. The search engine is updated very quickly after articles change. 3. A few funky things around intitle and incategory: 3a. You can combine them with a regular query (incategory:kings peaceful) 3b. You can use prefix searches with them (incategory:norma*) 3c. You can use them everywhere in the query (roger incategory:normans) What we think we've made worse and we're working on fixing: 1. Because we're expanding templates some things that probably shouldn't be searched are being searched. We've fixed a few of these issues but I wouldn't be surprised if more come up. We opened Bug 53426 regarding audio tags. 2. The relative weighting of matches is going to be different. We're still fine tuning this and we'd appreciate any anecdotes describing search results that seem out of order. 3. We don't currently index headings beyond the article title in any special way. We'll be fixing that soon. (Bug 53481) 4. Searching for file names or clusters of punctuation characters doesn't work as well as it used to. It still works reasonably well if you surround your query in quotes but it isn't as good as it was. (Bugs 53013 and 52948) 5. Did you mean suggestions currently aren't highlighted at all and sometimes we'll suggest things that aren't actually better. (Bugs 52286 and 52860) 6. incategory:category with spaces isn't working. (Bug 53415) What we've changed that you probably don't care about: 1. Updating search in bulk is much more slow then before. This is the cost of expanding templates. 2. Search is now backed by a horizontally scalable search backend that is being actively developed (Elasticsearch) so we're in a much better place to expand on the new solution as time goes on. Neat stuff if you run your own MediaWiki: CirrusSearch is much easier to install than our current search infrastructure. So what will you notice? Nothing! That is because while the new search backend (CirrusSearch) is indexing we've left the current search infrastructure as the default while we work on our list of bugs. You can see the results from CirrusSearch by performing your search as normal and adding srbackend=CirrusSearch to the url parameters. If you notice any problems with CirrusSearch please file bugs directly for it: https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensionscomponent=CirrusSearch Nik Everett ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] GitHub replication: tags not getting pushed?
Hey, Two days ago I created a tag for Diff [0]. While I'm writing this mail, the tag has yet to appear on the GitHub mirror [1]. I made a commit after I first noticed the tag did not appear to see if replicating that would also sync the tags, which turned out not to be the case, as the commit made it onto GitHub, while the tag did not show up. We do not appear to have an appropriate component on bugzilla for this piece of our infrastructure, so reporting the issue here. [0] tag 0.8 https://git.wikimedia.org/tags/mediawiki%2Fextensions%2FDiff.git [1] https://github.com/wikimedia/mediawiki-extensions-Diff/releases Cheers -- Jeroen De Dauw http://www.bn2vs.com Don't panic. Don't be evil. ~=[,,_,,]:3 -- ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] GitHub replication: tags not getting pushed?
On Wed, Aug 28, 2013 at 11:28 AM, Jeroen De Dauw jeroended...@gmail.comwrote: Hey, Two days ago I created a tag for Diff [0]. While I'm writing this mail, the tag has yet to appear on the GitHub mirror [1]. I made a commit after I first noticed the tag did not appear to see if replicating that would also sync the tags, which turned out not to be the case, as the commit made it onto GitHub, while the tag did not show up. We do not appear to have an appropriate component on bugzilla for this piece of our infrastructure, so reporting the issue here. Wikimedia - Git/Gerrit? -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
Will it be set as the search backend further on Wikimedia projects? Is there source code available for Elasticsearch on Gerrit? I couldn't find it. Stemming doesn't work for some languages at all, thus searching exact matches only. On Wed, Aug 28, 2013 at 9:20 PM, Nikolas Everett never...@wikimedia.org wrote: Today we threw the big lever and turned on our new search backend at mediawiki.org. It isn't the default yet but it is just about ready for you to try. Here is what is we think we've improved: 1. Templates are now expanded during search so: 1a. You can search for text included in templates 1b. You can search for categories included in templates 2. The search engine is updated very quickly after articles change. 3. A few funky things around intitle and incategory: 3a. You can combine them with a regular query (incategory:kings peaceful) 3b. You can use prefix searches with them (incategory:norma*) 3c. You can use them everywhere in the query (roger incategory:normans) What we think we've made worse and we're working on fixing: 1. Because we're expanding templates some things that probably shouldn't be searched are being searched. We've fixed a few of these issues but I wouldn't be surprised if more come up. We opened Bug 53426 regarding audio tags. 2. The relative weighting of matches is going to be different. We're still fine tuning this and we'd appreciate any anecdotes describing search results that seem out of order. 3. We don't currently index headings beyond the article title in any special way. We'll be fixing that soon. (Bug 53481) 4. Searching for file names or clusters of punctuation characters doesn't work as well as it used to. It still works reasonably well if you surround your query in quotes but it isn't as good as it was. (Bugs 53013 and 52948) 5. Did you mean suggestions currently aren't highlighted at all and sometimes we'll suggest things that aren't actually better. (Bugs 52286 and 52860) 6. incategory:category with spaces isn't working. (Bug 53415) What we've changed that you probably don't care about: 1. Updating search in bulk is much more slow then before. This is the cost of expanding templates. 2. Search is now backed by a horizontally scalable search backend that is being actively developed (Elasticsearch) so we're in a much better place to expand on the new solution as time goes on. Neat stuff if you run your own MediaWiki: CirrusSearch is much easier to install than our current search infrastructure. So what will you notice? Nothing! That is because while the new search backend (CirrusSearch) is indexing we've left the current search infrastructure as the default while we work on our list of bugs. You can see the results from CirrusSearch by performing your search as normal and adding srbackend=CirrusSearch to the url parameters. If you notice any problems with CirrusSearch please file bugs directly for it: https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensionscomponent=CirrusSearch Nik Everett ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- З павагай, Павел Селіцкас/Pavel Selitskas Wizardist @ Wikimedia projects ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
On Wed, Aug 28, 2013 at 3:37 PM, Paul Selitskas p.selits...@gmail.comwrote: Will it be set as the search backend further on Wikimedia projects? Yes. I'm not sure when though. Is there source code available for Elasticsearch on Gerrit? Our plugin that interacts with Elasticsearch is called CirrusSearch and lives in gerrit here: https://gerrit.wikimedia.org/r/#/projects/mediawiki/extensions/CirrusSearch,dashboards/default https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/CirrusSearch Elasticsearch lives in github here: https://github.com/elasticsearch/elasticsearch Stemming doesn't work for some languages at all, thus searching exact matches only. Stemming is done based on the language of the wiki. I expect only English stemming to work on mediawiki.org. Right now we use the default language analysers for all the languages that Elasticsearch supports out of the box ( http://www.elasticsearch.org/guide/reference/index-modules/analysis/lang-analyzer/) with some customizations for English. Languages that aren't better supported get a default analyser that doesn't do any stemming and splits on spaces. I expect we'll have to add build some more analysers in the future. Nik ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
On Wed, Aug 28, 2013 at 12:37 PM, Paul Selitskas p.selits...@gmail.comwrote: Will it be set as the search backend further on Wikimedia projects? That's the plan eventually :) Is there source code available for Elasticsearch on Gerrit? I couldn't find it. Stemming doesn't work for some languages at all, thus searching exact matches only. No, ES is not in Gerrit. It's an upstream project, their website is elasticsearch.org The CirrusSearch extension (our part of the project) is in Gerrit though. -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
Just for fun, I added some license-parsing logic to Template:Extension on mediawiki.org. I think the job queue is still updating the categories, but so far we have: Extensions with no license specified: 596 Extensions with an unknown license: 779 GPL licensed extensions: 667 MIT licensed extensions: 44 BSD licensed extensions: 23 AGPL licensed extensions: 10 MPL licensed extensions: 1 I was actually surprised to see how few MIT and BSD extensions we have considering how much animosity there is towards the GPL, but I suppose most people just want to match the licensing of MediaWiki. If you haven't specified the license of your extension, now would be a good time to do so :) Ryan Kaldari On Wed, Aug 28, 2013 at 9:10 AM, Luis Villa lvi...@wikimedia.org wrote: On Wed, Aug 28, 2013 at 5:52 AM, Tim Starling tstarl...@wikimedia.org wrote: On 27/08/13 03:12, C. Scott Ananian wrote: Stated more precisely: a non-GPL-compatible license for an extension means that the extension can never be distributed with core. That is incorrect, the GPL does not say that. The GPL allows verbatim copies of source code, with no restrictions on the license of any bundled or dynamically linked code. Only non-source forms (or binaries in v2) have more restrictive conditions. Since the MediaWiki core and extensions are distributed solely in source form, the non-source (binary) conditions do not apply. Yup. In retrospect, an odd oversight for GPL v3; perhaps more understandable for v2. Luis -- Luis Villa Deputy General Counsel Wikimedia Foundation 415.839.6885 ext. 6810 NOTICE: *This message may be confidential or legally privileged. If you have received it by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity.* ___ 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] WMFs stance on non-GPL code
Just out of curiosity, what code are you using to do license parsing? If you want seriously robust parsing, you might take a peek at https://github.com/dmgerman/ninka Luis On Wed, Aug 28, 2013 at 1:36 PM, Ryan Kaldari rkald...@wikimedia.orgwrote: Just for fun, I added some license-parsing logic to Template:Extension on mediawiki.org. I think the job queue is still updating the categories, but so far we have: Extensions with no license specified: 596 Extensions with an unknown license: 779 GPL licensed extensions: 667 MIT licensed extensions: 44 BSD licensed extensions: 23 AGPL licensed extensions: 10 MPL licensed extensions: 1 I was actually surprised to see how few MIT and BSD extensions we have considering how much animosity there is towards the GPL, but I suppose most people just want to match the licensing of MediaWiki. If you haven't specified the license of your extension, now would be a good time to do so :) Ryan Kaldari On Wed, Aug 28, 2013 at 9:10 AM, Luis Villa lvi...@wikimedia.org wrote: On Wed, Aug 28, 2013 at 5:52 AM, Tim Starling tstarl...@wikimedia.org wrote: On 27/08/13 03:12, C. Scott Ananian wrote: Stated more precisely: a non-GPL-compatible license for an extension means that the extension can never be distributed with core. That is incorrect, the GPL does not say that. The GPL allows verbatim copies of source code, with no restrictions on the license of any bundled or dynamically linked code. Only non-source forms (or binaries in v2) have more restrictive conditions. Since the MediaWiki core and extensions are distributed solely in source form, the non-source (binary) conditions do not apply. Yup. In retrospect, an odd oversight for GPL v3; perhaps more understandable for v2. Luis -- Luis Villa Deputy General Counsel Wikimedia Foundation 415.839.6885 ext. 6810 NOTICE: *This message may be confidential or legally privileged. If you have received it by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity.* ___ 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 -- Luis Villa Deputy General Counsel Wikimedia Foundation 415.839.6885 ext. 6810 NOTICE: *This message may be confidential or legally privileged. If you have received it by accident, please delete it and let us know about the mistake. As an attorney for the Wikimedia Foundation, for legal/ethical reasons I cannot give legal advice to, or serve as a lawyer for, community members, volunteers, or staff members in their personal capacity.* ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
On Thu, Aug 29, 2013 at 6:41 AM, Luis Villa lvi...@wikimedia.org wrote:
Just out of curiosity, what code are you using to do license parsing? If
you want seriously robust parsing, you might take a peek at
https://github.com/dmgerman/ninka
Luis
standard parser functions via the template
{{lc:{{{license|}}} }}
|gpl|gplv2|gplv2 or later|gpl v2|gpl v2 or later|gplv2+|gplv3|gpl v3 = GPL
licensed extensions
|agpl|agplv2|agplv3 = AGPL licensed extensions
|mit|expat|expat (mit)|x11 = MIT licensed extensions
|bsd|new bsd|revised bsd|modified bsd|freebsd = BSD licensed extensions
|mpl|mplv2|mpl v2 = MPL licensed extensions
|#default = Extensions with unknown license
}}]]
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] WMFs stance on non-GPL code
On Wed, Aug 28, 2013 at 5:40 PM, K. Peachey p858sn...@gmail.com wrote:
On Thu, Aug 29, 2013 at 6:41 AM, Luis Villa lvi...@wikimedia.org wrote:
Just out of curiosity, what code are you using to do license parsing? If
you want seriously robust parsing, you might take a peek at
https://github.com/dmgerman/ninka
Luis
standard parser functions via the template
{{lc:{{{license|}}} }}
|gpl|gplv2|gplv2 or later|gpl v2|gpl v2 or later|gplv2+|gplv3|gpl v3 = GPL
licensed extensions
|agpl|agplv2|agplv3 = AGPL licensed extensions
|mit|expat|expat (mit)|x11 = MIT licensed extensions
|bsd|new bsd|revised bsd|modified bsd|freebsd = BSD licensed extensions
|mpl|mplv2|mpl v2 = MPL licensed extensions
|#default = Extensions with unknown license
}}]]
Oh, the template, not the code itself. Makes sense; ignore lil 'ol me ;)
Luis
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
--
Luis Villa
Deputy General Counsel
Wikimedia Foundation
415.839.6885 ext. 6810
NOTICE: *This message may be confidential or legally privileged. If you
have received it by accident, please delete it and let us know about the
mistake. As an attorney for the Wikimedia Foundation, for legal/ethical
reasons I cannot give legal advice to, or serve as a lawyer for, community
members, volunteers, or staff members in their personal capacity.*
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] HTTPS enabled for all logged-in users
== HTTPS enabled by default for logged-in users on Wikimedia sites == Today, August 28, the Wikimedia Foundation is making a change to the software that powers the Wikimedia projects: By default, all logged-in users will now be using HTTPS to access Wikimedia sites. What this does is encrypt the connection between the Wikimedia servers and the user's browser so that the information sent between the two is not readable by anyone else. This is in response to the recent concerns over the privacy and security of our user community, and we explained the rationale for this change in our post about the future of HTTPS at Wikimedia[0]. ===What this means for you === How this works is simple: If a user wants to log in, they will be redirected to use HTTPS for the login, thus keeping their username and password secure. After they are logged in, they stay on the HTTPS version of the Wikimedia site they are using. === Excluded Countries === Some users live in areas where HTTPS is not an easy option, most times because of explicit blocking by a government. At the request of these communities, we have made an explicit exclusion for users from those affected countries. Simply put, users from China and Iran will not be required to use HTTPS for logging in, nor for viewing any Wikimedia project site ===Disabling=== Are you having a slow or unreliable experience while browsing Wikimedia sites over HTTPS? Then you can turn HTTPS off in your user preferences, under the User profile tab: Uncheck Always use a secure connection when logged in. You will need to log out and log in again for the preference to take effect. But remember, you will still need to log in using the secure HTTPS process. ===HELP!=== For further details, please see the HTTPS[1] page on Meta-Wiki, which is available in several languages. Are you unable to log in and edit a Wikimedia wiki after this change? Please contact the Wikimedia Foundation Operations team via any means you find comfortable, including this blog post's comments section, on IRC in the #wikimedia-operations channel, or via the ht...@wikimedia.org email address. Greg Grossmeier [0] http://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ [1] http://meta.wikimedia.org/wiki/HTTPS -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Extension OpenID: new version 3.40 published
Today, I published a new version of the extension OpenID. - adds the long-wanted option for Admins to pin logins to a single (fixed, or forced) OpenID Provider. - defines parameters of OpenID provider/s in an array. Parameters are no longer hard-coded on several places like in the CSS. - fixes other minor problems. The extension has been tested with mediawiki core and PHP 5.5.+ (previous PHP versions 5.3.+ and 5.4.+ do also work). Homepage https://www.mediawiki.org/wiki/Extension:OpenID Commit message of https://gerrit.wikimedia.org/r/#/c/55287/73 CHANGES https://git.wikimedia.org/raw/mediawiki%2Fextensions%2FOpenID/ea5677c252c739c49c4eff2c6760e0d10adb2281/CHANGES README https://git.wikimedia.org/raw/mediawiki%2Fextensions%2FOpenID/ea5677c252c739c49c4eff2c6760e0d10adb2281/README If you have to report bugs: https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensionscomponent=OpenID signature.asc Description: OpenPGP digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] HTTPS enabled for all logged-in users
After many months of struggle, WMF takes one big step towards a more secure Wikipedia. Good job everybody! *-- * *Tyler Romeo* Stevens Institute of Technology, Class of 2016 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Wed, Aug 28, 2013 at 6:11 PM, Greg Grossmeier g...@wikimedia.org wrote: == HTTPS enabled by default for logged-in users on Wikimedia sites == Today, August 28, the Wikimedia Foundation is making a change to the software that powers the Wikimedia projects: By default, all logged-in users will now be using HTTPS to access Wikimedia sites. What this does is encrypt the connection between the Wikimedia servers and the user's browser so that the information sent between the two is not readable by anyone else. This is in response to the recent concerns over the privacy and security of our user community, and we explained the rationale for this change in our post about the future of HTTPS at Wikimedia[0]. ===What this means for you === How this works is simple: If a user wants to log in, they will be redirected to use HTTPS for the login, thus keeping their username and password secure. After they are logged in, they stay on the HTTPS version of the Wikimedia site they are using. === Excluded Countries === Some users live in areas where HTTPS is not an easy option, most times because of explicit blocking by a government. At the request of these communities, we have made an explicit exclusion for users from those affected countries. Simply put, users from China and Iran will not be required to use HTTPS for logging in, nor for viewing any Wikimedia project site ===Disabling=== Are you having a slow or unreliable experience while browsing Wikimedia sites over HTTPS? Then you can turn HTTPS off in your user preferences, under the User profile tab: Uncheck Always use a secure connection when logged in. You will need to log out and log in again for the preference to take effect. But remember, you will still need to log in using the secure HTTPS process. ===HELP!=== For further details, please see the HTTPS[1] page on Meta-Wiki, which is available in several languages. Are you unable to log in and edit a Wikimedia wiki after this change? Please contact the Wikimedia Foundation Operations team via any means you find comfortable, including this blog post's comments section, on IRC in the #wikimedia-operations channel, or via the ht...@wikimedia.org email address. Greg Grossmeier [0] http://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/ [1] http://meta.wikimedia.org/wiki/HTTPS -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | ___ 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] WMFs stance on non-GPL code
On Sun, Aug 25, 2013 at 5:15 PM, Jeroen De Dauw jeroended...@gmail.comwrote: Hey, I'm curious what the stance of WMF is on BSD, MIT and MPL licensed code. In particular, could such code be deployed on WMF servers? Was this just grenade lobbing? You still haven't clarified your question, though a number of folks asked for clarification. Can you let us know why you're asking this? - Ryan ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] HTTPS enabled for all logged-in users
On Wed, Aug 28, 2013 at 3:19 PM, Tyler Romeo tylerro...@gmail.com wrote: After many months of struggle, WMF takes one big step towards a more secure Wikipedia. Good job everybody! Agreed - fantastic to see this out the door :-). Thanks to everyone who made it happen. Erik -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
On 08/28/2013 02:20 PM, Nikolas Everett wrote: Today we threw the big lever and turned on our new search backend at mediawiki.org. It isn't the default yet but it is just about ready for you to try. Here is what is we think we've improved: 1. Templates are now expanded during search so: 1a. You can search for text included in templates 1b. You can search for categories included in templates 2. The search engine is updated very quickly after articles change. 3. A few funky things around intitle and incategory: 3a. You can combine them with a regular query (incategory:kings peaceful) 3b. You can use prefix searches with them (incategory:norma*) 3c. You can use them everywhere in the query (roger incategory:normans) Template expansion and category intersection search - so exciting! Thank you, Nik and Chad, for working on this. -- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] HTTPS enabled for all logged-in users
Thanks a lot to everybody who make it possible! I find the GeoIP solution quite elegant. I wrote a script this morning to let anonymous users opt-in for being redirected to HTTPS with the same forceHTTPS cookie [1]; such a script could be used to increase the proportion of HTTPS visitors (probably this script should be not used now before the server load is better known). [1] https://www.mediawiki.org/wiki/Snippets/forceHTTPS_cookie Sébastien Le Thu, 29 Aug 2013 00:25:50 +0200, Erik Moeller e...@wikimedia.org a écrit: On Wed, Aug 28, 2013 at 3:19 PM, Tyler Romeo tylerro...@gmail.com wrote: After many months of struggle, WMF takes one big step towards a more secure Wikipedia. Good job everybody! Agreed - fantastic to see this out the door :-). Thanks to everyone who made it happen. Erik ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
Chad wrote: No, ES is not in Gerrit. It's an upstream project, their website is elasticsearch.org The CirrusSearch extension (our part of the project) is in Gerrit though. https://www.mediawiki.org/wiki/Elasticsearch https://wikitech.wikimedia.org/wiki/Elasticsearch I'm not sure what should be at either title (perhaps redirects), but this is where I went to find answers. When you get a chance. :-) MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] New search backend live on mediawiki.org
On Wed, Aug 28, 2013 at 5:08 PM, MZMcBride z...@mzmcbride.com wrote: Chad wrote: No, ES is not in Gerrit. It's an upstream project, their website is elasticsearch.org The CirrusSearch extension (our part of the project) is in Gerrit though. https://www.mediawiki.org/wiki/Elasticsearch https://wikitech.wikimedia.org/wiki/Elasticsearch I'm not sure what should be at either title (perhaps redirects), but this is where I went to find answers. When you get a chance. :-) Those now redirect to real places. Thanks for the reminder :) -Chad ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
