Re: [Wikitech-l] CSS Regressions
See also: https://bugzilla.wikimedia.org/show_bug.cgi?id=62633 -- Krinkle On 10 Mar 2014, at 22:04, Jon Robson jdlrob...@gmail.com wrote: I just wondered if anyone doing MediaWiki development had any experience in catching CSS regressions? We have had a few issues recently in mobile land where we've made big CSS changes and broken buttons on hidden away special pages - particularly now we have been involved in the development of mediawiki ui and moving mobile towards using them. My vision of how this might work is we have an automated tool that visits a list of given pages on various browsers, take screenshots of how they look and then compares the images with the last known state. The tool checks how similar the images are and complains if they are not the same - this might be a comment on the Gerrit patch or an e-mail saying something user friendly like The Special:Nearby page on Vector looks different from how it used to. Please check everything is okay. This would catch a host of issues and prevent a lot of CSS regression bugs. Any experience in catching this sort of thing? Any ideas on how we could make this happen? ___ 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] OPW applicant introduction
Hello! My name is Frances Hocutt, and I'm applying for the OPW internship program. Specifically, I'm interested in improving the documentation around the available Mediawiki API libraries, writing specifications for what makes a good one, and generally making API:Client Code a more useful page. I've been coordinating my application with Sumana Harihareswara, and my co- mentor will be Tollef Fog Heen. Brad Jorsch and Merlijn van Deen have agreed to offer technical advice as well. Thanks to everyone! You can find my userpage here: https://www.mediawiki.org/wiki/User:Fhocutt. I've been drafting my proposal here: https://www.mediawiki.org/wiki/Evaluating_MediaWiki_web_API_client_libraries (working title). And I've started a page for my microtask here: https://www.mediawiki.org/wiki/API:Client_Code/Access_Library_Comparison. I'll be comparing two of the Python API libraries; right now I'm figuring out what criteria I'll be using. I'm looking at the Google Android, Drive, and Youtube API documentation along with the AWS S3 Ruby API as starting examples. Are there any other API client libraries that you've found exemplary, related to Wikimedia or not? Looking forward to contributing, Frances Hocutt ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] About the bug 46453 - Uzbek: Change date and decimal separators
Thank you. I edited it from gerrit web interface. On Fri, Mar 14, 2014 at 12:19 AM, Jeremy Baron jer...@tuxmachine.comwrote: On Mar 13, 2014 2:37 PM, Maduranga Siriwardena maduranga.siriward...@gmail.com wrote: By mistake I uploaded a patch to a bug to Gerrit having some mistakes in the commit message. If I'm linking a bug to the patch I should add Bug: bugnumber But I added it as Bug:bugnumber (Having no space after the colon) Will it be fine for this time? Or should I do something to correct it? You can send an amended changeset with the same change-id as the original or edit from the gerrit web interface (gerrit will then generate a commit for you) -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Maduranga Siriwardena Undergraduate University of Moratuwa, Faculty of Engineering Department of Computer Science and Engineering ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
On Thursday 13 March 2014 08:38 PM, Niklas Laxström wrote: There have recently been questions whether WMF is able to serve webfonts. Some people think that because of the issues that led to disabling webfonts by default in Universal Language Selector (ULS), WMF is not ready to consider webfonts for typography. I don't think that way. ULS is not a good comparison point because of the following. 1) Universal Language selector is trying to solve a much harder issue than what webfonts are usually used for. It is trying to avoid tofu (missing fonts) which brings a whole list of issues which are not present or are much smaller otherwise: * large fonts for complex scripts, * detecting which fonts are missing, * many fonts per page, * the systems with greatest need of fonts often have bad renderers. 2) WMF has a lot of experience working with web fonts by now. We know how to handle different formats, how to optimally compress fonts and how to check the results in different systems and browsers. In some areas we are even ahead of Google, like non-latin fonts. I wonder why people want to serve webfonts by default, eventhough most Wikipedia users don't need it. Webfonts is a nice option, and it must be an option so as if any user or language need it, they can choose it. Overruling a user's / community's settings without asking their opinion is against any freedom WMF represents. There are various other 'real' issues which are affecting, contribution and rendering of Wikimedia wikis in non-latin languages. Thus, I think that delivering a relative small fonts for simple scripts like latin and cyrillic is something that is possible *if* we are willing to accept that it will take some bandwidth and that page load experience can be affected* if the font is not cached or present locally. -Niklas * The unwanted effects of using webfonts are getting smaller and smaller with modern browsers. And requirement of webfonts is also getting smaller and smaller with modern OSs. Even today's mobile OSs have better language support than that of old desktop OSs. Praveen ___ 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] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
Hi all, I'm Aaron Xiao from Peking University, Beijing, China. I'm interested in the i18n projects for GSoC 2014, especially the UniversalLanguageSelector fonts for Chinese wikis. I'm writing proposal for it currently. It will be finished in 2 or 3 days. I have contacted DChan and Liangent a week ago. Here are some personal information copied from the previous self-introduction mail. Hope to see your feedback, especially when I finish the proposal :) *About me: * 2007~2011 B.S. in Computer Science @ Peking University 2011~2014 M.S. in Information Security @ Peking University See more information on [1]. *Related Experience:* [GSoC] I have participated in GSoC twice, and have contributed code to Wireshark, Blender, OGRE. So I'm familiar with open source culture, and know a bit about how to play well with the community. [I18N] Specially, my work in GSoC 2011 was to build the i18n system for Blender, See [2] for details. We also built the translators' community. I'm still one of the admin currently. See [3]. [PHP, Web frontend] I was the admin of http://zone.pku.edu.cn before, but it cannot be visited outside the campus. Some other web apps I developed: [4] using PHP, [5] using Django. So I know a little about web techs. I can learn new knowledge fast if I need it. [Chinese characters] Of course, my mother tongue :) *About Time:* - For Proposal Actually I just finished the FOSS ASIA conference on 3rd Mar. And now I'm taking a trip around the Southeast Asia. So I don't have much time before 13th. But I'll try my best to discuss the project with you and learn about the information. Then submit the proposal ASAP. - For the Project I'll graduate on early July, and then wait for my H1B visa to come into force in October. So my full-time window is from July to September. According to the GSoC schedule, I can only work as a part-time job before mid-term, and work for full-time before final-term. But I promise to finish the feature on-time, and push it forward to be released finally ( Even after the GSoC event, of course. ) - After the Event I'm interested in I18N projects. I'm always trying to promote great open source projects to Chinese, as well as other non-English users. So maybe I can deal with the other i18n related things after the event, and keep going along with the community :) [1] http://www.linkedin.com/in/xiaoxiangquan [2] http://wiki.blender.org/index.php/User:Xiaoxiangquan/GoogleSummerOfCode/2011/Internationalization [3] https://projects.blender.org/projects/bf-translations [4] http://apps.weibo.com/myfunds [5] http://jipinz.sinaapp.com ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] MediaWiki, Cookies and EU Privacy Policy 95/46/EG
On Tue, Mar 11, 2014 at 10:33 PM, rupert THURNER rupert.thur...@gmail.comwrote: Am 10.03.2014 17:01 schrieb Manuel Schneider manuel.schnei...@wikimedia.ch: Am 10.03.2014 16:54, schrieb Chris Steipp: 1) catch the click on the Login link to show a banner first to ask for the users consent, on acceptance forward the user to the login page 2) modify the login process to set the cookie after the actual login and put an additional text on the login page like by logging in I accept the usage of cookies by this website The cookie on the login page is for the anti-csrf (and captcha if needed) validation, so getting rid of it would be problematic from a technical perspective (or would require a second click on the login page). Thanks Chris for this comment. So that leaves us with option 1) - a javascript banner. I think that shouldn't be too hard to implement. A div which hovers over the Wiki page, the text, two buttons [accept] / [leave]. Accept points to Special:Userlogin, leave just closes the banner. A javascript that shows this div onclick() on the Login link, if no cookie has already been set by the Wiki. Maybe even a LocalSettings.php variable $wgApproveCookies = true; that is true by default and allows admins of internal company wikis etc. to disable that banner. As an option we could even add another setting $wgApproveCookiesAlways, which makes the same div to show up as soon as a user enters the wiki. That way we can support admins that have further extensions installed in their wiki which add cookies right away - like Google Analytics. Is there any technical argument against this proposal? Rupert What's the fallback for users without JavaScript enabled in this scenario? Remco ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
http://wiki.blender.org/index.php/User:Xiaoxiangquan/GoogleSummerOfCode/2011/Internationalization/developing_reports said: Final Report(2011-08-22) To be continued Was it? I don't understand what that project was about in the end, a summary would be nice. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
Hoi, You do not understand what the existing implementation of Webfonts is about. It is about not serving tofu. You know, those pesky boxes that represent a character. When tofu is served, no characters can be seen and consequently no information can be read. Please ask any community if this is what they want. Thanks, GerardM On 14 March 2014 14:36, praveenp me.prav...@gmail.com wrote: On Thursday 13 March 2014 08:38 PM, Niklas Laxström wrote: There have recently been questions whether WMF is able to serve webfonts. Some people think that because of the issues that led to disabling webfonts by default in Universal Language Selector (ULS), WMF is not ready to consider webfonts for typography. I don't think that way. ULS is not a good comparison point because of the following. 1) Universal Language selector is trying to solve a much harder issue than what webfonts are usually used for. It is trying to avoid tofu (missing fonts) which brings a whole list of issues which are not present or are much smaller otherwise: * large fonts for complex scripts, * detecting which fonts are missing, * many fonts per page, * the systems with greatest need of fonts often have bad renderers. 2) WMF has a lot of experience working with web fonts by now. We know how to handle different formats, how to optimally compress fonts and how to check the results in different systems and browsers. In some areas we are even ahead of Google, like non-latin fonts. I wonder why people want to serve webfonts by default, eventhough most Wikipedia users don't need it. Webfonts is a nice option, and it must be an option so as if any user or language need it, they can choose it. Overruling a user's / community's settings without asking their opinion is against any freedom WMF represents. There are various other 'real' issues which are affecting, contribution and rendering of Wikimedia wikis in non-latin languages. Thus, I think that delivering a relative small fonts for simple scripts like latin and cyrillic is something that is possible *if* we are willing to accept that it will take some bandwidth and that page load experience can be affected* if the font is not cached or present locally. -Niklas * The unwanted effects of using webfonts are getting smaller and smaller with modern browsers. And requirement of webfonts is also getting smaller and smaller with modern OSs. Even today's mobile OSs have better language support than that of old desktop OSs. Praveen ___ 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] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
I think it's a kind of Loading Font on Demand. There are thousands of Chinese characters, but we use only 3000 of them in daily life. To a specific wiki page, maybe only 200 are used. So cutting the font file will save a lot of time. Another feature is about glyph-connection. Some rarely-used characters are not included in the database, then we cannot display it. In these cases we can ask the user to contribute glyph. Regards, 2014-03-14 22:17 GMT+08:00 Federico Leva (Nemo) nemow...@gmail.com: http://wiki.blender.org/index.php/User:Xiaoxiangquan/ GoogleSummerOfCode/2011/Internationalization/developing_reports said: Final Report(2011-08-22) To be continued Was it? I don't understand what that project was about in the end, a summary would be nice. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Xiao Xiangquan | 肖祥全 Master Candidate of Computer Science Peking University, Beijing, 100871, PRC. Tel: +86-13810295146 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
I was talking of your 2011 GSoC project, it sounds potentially interesting but your link doesn't bring to any final report so I don't understand what was done. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
On Fri, Mar 14, 2014 at 7:06 PM, praveenp me.prav...@gmail.com wrote:
..
And requirement of webfonts is also getting smaller and smaller with modern
OSs. Even today's mobile OSs have better language support than that of old
desktop OSs.
For example: My Nexus 5 with modern OS, Android Kitkat has no font for
my native language by default.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
ahh, sorry I missed the quoted part... Actually Blender wanted final report in a video format, so I didn't copy it to the dev-report there. You can see How to change between different languages at http://www.youtube.com/watch?v=y3nGUba27y0 The finished features are: - Font loading...done - Handle strings in gerneral C code...done - Handle strings in makesrna code...done - Handle strings in Python code...done - BlenderCN helps translate a full Simplified Chinese version...done - Language selection interface...done - Documents: Screenshots, Implementation Design, Developing Reports...Done And unfinished feature is: - Be able to get input in international languages... (It's really touch) 2014-03-14 23:04 GMT+08:00 Federico Leva (Nemo) nemow...@gmail.com: I was talking of your 2011 GSoC project, it sounds potentially interesting but your link doesn't bring to any final report so I don't understand what was done. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Xiao Xiangquan | 肖祥全 Master Candidate of Computer Science Peking University, Beijing, 100871, PRC. Tel: +86-13810295146 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Interested in UniversalLanguageSelector fonts for Chinese wikis projects
And after the final term, I continued working with the community. Finally the i18n system released along with Blender 2.60 in Oct of that year. 2014-03-14 23:15 GMT+08:00 xiangquan xiao xiaoxiangq...@gmail.com: ahh, sorry I missed the quoted part... Actually Blender wanted final report in a video format, so I didn't copy it to the dev-report there. You can see How to change between different languages at http://www.youtube.com/watch?v=y3nGUba27y0 The finished features are: - Font loading...done - Handle strings in gerneral C code...done - Handle strings in makesrna code...done - Handle strings in Python code...done - BlenderCN helps translate a full Simplified Chinese version...done - Language selection interface...done - Documents: Screenshots, Implementation Design, Developing Reports...Done And unfinished feature is: - Be able to get input in international languages... (It's really touch) 2014-03-14 23:04 GMT+08:00 Federico Leva (Nemo) nemow...@gmail.com: I was talking of your 2011 GSoC project, it sounds potentially interesting but your link doesn't bring to any final report so I don't understand what was done. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Xiao Xiangquan | 肖祥全 Master Candidate of Computer Science Peking University, Beijing, 100871, PRC. Tel: +86-13810295146 -- Xiao Xiangquan | 肖祥全 Master Candidate of Computer Science Peking University, Beijing, 100871, PRC. Tel: +86-13810295146 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
It's really in the tradeoffs, as others have mentioned.
It is obvious that we would love to get rid of tofu at all time. But what
is the effect on readership? As far as I know, a higher delivery speed of a
Website increases readership and the other way around. So if there was any
way to estimate what the trade-off would be -- i.e. how many readers gained
or lost for how much tofu avoided -- that would be great.
Bonus points if we could qualify both sides (e.g. readers who turn into
editors vs the other readers, tofu that prevents you from understanding the
article vs tofu in a language link you don't care anyway).
I don't think that actual bandwidth costs and loading time are interesting
per se for us, but only as secondary indicators.
That's speaking from a fantasy dream world where such metrics are easily
accessible :)
On Fri Mar 14 2014 at 8:08:12 AM, Kartik Mistry kartik.mis...@gmail.com
wrote:
On Fri, Mar 14, 2014 at 7:06 PM, praveenp me.prav...@gmail.com wrote:
..
And requirement of webfonts is also getting smaller and smaller with
modern
OSs. Even today's mobile OSs have better language support than that of
old
desktop OSs.
For example: My Nexus 5 with modern OS, Android Kitkat has no font for
my native language by default.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
___
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] CSS Regressions
Guys thanks so much for all these pointers and ideas. Lots of food for thought here. I find for the MobileFrontend perspective, in a perfect world, all our existing browser tests would visual diff a screenshot at each individual step of our tests against the previously known screenshot and report any oddities. Will sit down and think about this some more but thanks so much - and please don't forget this thread - post any work you do in this area here so we can keep tabs of what the options are! ___ 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
Re: [Wikitech-l] Project Proposal for FOSS OPW Round 8
Hi Jaime, On Thursday, March 13, 2014, Jaime Schatz jaimelynsch...@gmail.com wrote: Here are all three proposals to the OPW application: https://www.mediawiki.org/wiki/Historical_OpenStreetMap#Historical_OpenStreetMap https://www.mediawiki.org/wiki/Hacker%27s_map https://wikitech.wikimedia.org/wiki/Wikimedia_Labs_Toolbox While you can apply with different proposals, we would rather let you focus in the right one. Ideally you should be able to reduce that list after talking to the mentors and making up your mind. Let me know if we can help you deciding. PS: a collateral problem, if the title of your thread is Project Proposal for FOSS OPW Round 8 then your chances of being noticed by the people interested in each of the three projects decrease. -- 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] MediaWiki, Cookies and EU Privacy Policy 95/46/EG
On 14.03.2014, 17:59 Remco wrote: What's the fallback for users without JavaScript enabled in this scenario? Nothing. You can't login without cookies. -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
On Friday 14 March 2014 07:54 PM, Gerard Meijssen wrote: Hoi, You do not understand what the existing implementation of Webfonts is about. It is about not serving tofu. You know, those pesky boxes that represent a character. When tofu is served, no characters can be seen and consequently no information can be read. Please ask any community if this is what they want. Thanks, GerardM Why would every Malayalam Wikimedians suffer webfonts because some language in some other continent has no proper support in OSs. We will not read that language anyhow :-). IMHO, serving webfonts by default only for that language after consulting that community, may be the solution. On Friday 14 March 2014 08:37 PM, Kartik Mistry wrote: On Fri, Mar 14, 2014 at 7:06 PM, praveenp me.prav...@gmail.com wrote: .. And requirement of webfonts is also getting smaller and smaller with modern OSs. Even today's mobile OSs have better language support than that of old desktop OSs. For example: My Nexus 5 with modern OS, Android Kitkat has no font for my native language by default. Sorry to hear that. Even my humble Samsung Galaxy Trend (Android 4.1) has pretty good support for atleast Malayalam, Hindi and Tamil. If I remember correctly there was two different fonts and an input method for Malayalam available in the stock phone. We had to wait untill service pack 2 for a decent Malayalam font while Windows XP released. Praveen ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
I just want to clarify that I was highlighting the possibility of considering webfonts for *typography*. I expect everyone to know by now that tofu issue is not yet solved and people are working on it. -Niklas ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] GSoC'14 Proposal
HighNote - Highlight Making Notes. Yes, as a regular wikipedian, I have been facing a problem. I used to read some article on a topic XYZ. I liked a few keywords or sentences in the article that I wuld like to keep easily accessible. Here is the solution - With HighNote feature activated internally on wikipedia, a user will be able to select(by mouse) the text that he wants to highlight and remember for next time. That text will be saved in the database and everytime that user comes back to that page he will be able to see what he highlighted may be one/ten years ago. Also, he will be able to deselect specific text by selecting(by mouse) again. I have already been working on a prototype of the same by implementing a demo wikipedia page. I want to discuss the feasibility of this project as a GSoC'14 project. Please bring uo some of the challenges that I can face while implementing this so I can consider everything in my final proposal. Thanks. Regards *Sahil Dua* Netaji Subhas Institute of Technology, New Delhi *https://www.facebook.com/picsmashup https://www.facebook.com/picsmashup* Ph: +91-9899740957 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Travel sponsorship requests for the Zürich Hackathon
Just a reminder: On Tuesday, March 4, 2014, Quim Gil q...@wikimedia.org wrote: From the 101 people that has registered to the Wikimedia Hackathon in Zürich, 24 are requesting travel and/or accommodation sponsorship (a few of them apparently by mistake) https://www.mediawiki.org/wiki/Z%C3%BCrich_Hackathon_2014/Scholarships ** The deadline for scholarship application is March 16th. Our goal is to notify applicants by March 17th. Don't miss the deadline! ** Five organizations are contributing sponsorship funds and, to be honest, I still don't know exactly how these five entities will match the budget available with a common list of accepted participants. Still, it is good to see more Wikimedia organizations stepping in to support independent developers, and I have no doubt that we will sort out the process in the next days. In order to help sharing common standards between organizations and also between events, I have started a draft with principles and guidelines at https://www.mediawiki.org/wiki/Volunteer_coordination_and_outreach/Travel_sponsorship Your help is welcome, regardless of how selfish or altruistic your motivations are. A good idea is always a good idea, especially when it comes as an edit to a wiki page. -- 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] GSoC'14 Proposal
There are countless such services already. What you propose is similar to https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Annotation_tool_that_extracts_statements_from_books_and_feed_them_on_Wikidata. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Structured logging RFC discussion on 2014-03-19
The structured logging RFC [0] will be up for discussion again next Wednesday [1]. There is a strawman implementation in gerrit [2] that is likely to be the focus of discussion unless there are other issues that the reviewers find more pressing. At this point the most controversial aspect of my proposed implementation seems to be importing third-party libraries into mw-core and/or the use of composer to manage that activity. I would welcome discussion of alternatives or consensus that this is a reasonable approach for the immediate future that should be revisited if and when a better idea is found for the general problem. [0]: https://www.mediawiki.org/wiki/Requests_for_comment/Structured_logging [1]: https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-19 [2]: https://gerrit.wikimedia.org/r/#/c/112699/ Bryan -- Bryan Davis Wikimedia Foundationbd...@wikimedia.org [[m:User:BDavis_(WMF)]] Sr Software EngineerBoise, ID USA irc: bd808v:415.839.6885 x6855 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Roadmap and deployment highlights - week of March 17th
Welcome to the latest edition of the Roadmap and deployments update! Full schedule for next week at: https://wikitech.wikimedia.org/wiki/Deployments#Week_of_March_17th == Week long things == The end of 'soft-migration' of WMF Labs to the new datacenteron March 21st. After this date, projects will be shutdown and moved by the WMF Labs team. If you haven't yet migrated your WMF Labs tool/bot, please see: http://lists.wikimedia.org/pipermail/labs-l/2014-March/002228.html == Tuesday == MediaWiki deploy window, currently following the 1.23 schedule * group1 to 1.23wmf18: All non-Wikipedia sites (Wiktionary, Wikisource, * Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites) ** https://www.mediawiki.org/wiki/MediaWiki_1.23/wmf18 Flow: Enable Flow on [[meta:Programs_talk:Evaluation_portal/Learning_modules]] == Wednesday == Enabling the Hovercards BetaFeature * https://www.mediawiki.org/wiki/Beta_Features/Hovercards * (exact time tbd) == Thursday == MediaWiki deploy window, currently following the 1.23 schedule) * group2 to 1.23wmf18 (all Wikipedias) ** https://www.mediawiki.org/wiki/MediaWiki_1.23/wmf18 * group0 to 1.23wmf19 (test/test2/testwikidata/mediawiki) ** https://www.mediawiki.org/wiki/MediaWiki_1.23/wmf19 == Potentially of interest == Next week we will begin having SWAT deploy team windows. The difference between these and the previous Lightning Deploy windows is that: A) these are twice a day and an hour long (vs once a day and only 30 minutes) B) they are run by experienced deployers, who will deploy things on behalf of others (who don't have deploy privs/experience) More at: https://wikitech.wikimedia.org/wiki/SWAT_deploys As always, questions welcome, Greg -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | signature.asc Description: Digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Roadmap and deployment highlights - week of March 17th
quote name=Greg Grossmeier date=2014-03-14 time=15:35:18 -0700 == Week long things == The end of 'soft-migration' of WMF Labs to the new datacenteron March 21st. After this date, projects will be shutdown and moved by the WMF Labs team. If you haven't yet migrated your WMF Labs tool/bot, please see: http://lists.wikimedia.org/pipermail/labs-l/2014-March/002228.html I clarified this on wiki, but to close the loop: Tool migration instructions: * http://lists.wikimedia.org/pipermail/labs-l/2014-March/002228.html Project migration instructions: * http://lists.wikimedia.org/pipermail/labs-l/2014-March/002229.html -- | Greg GrossmeierGPG: B2FA 27B1 F7EB D327 6B8E | | identi.ca: @gregA18D 1138 8E47 FAC8 1C7D | signature.asc Description: Digital signature ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Vagrant Cloud
Vagrant Cloud is a new service from Hashicorp that strives to make it easy to share Vagrant boxes and to collaborate on provisioned instances together. It's in very early beta, but I have started poking around a little, and it looks interesting. I don't quite know yet how it will work with our extensive custom plugin architecture, but I suspect that this is not an insurmountable problem. Hashicorp is also committed to a freemium model that makes the software stack free (as in speech) and the basic tier of cloud services free (as in beer), so it may be possible for us to have tighter integration with their service without compromising our values. If your curiosity is piqued and you decide to check it out, please do report back to the list with your findings -- it'd be good to know whether this is something we'd want to watch or not. It does require Vagrant 1.5.1, but I am happy to report that MediaWiki-Vagrant is compatible! :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Webfonts
On Thu, Mar 13, 2014 at 8:08 AM, Niklas Laxström niklas.laxst...@gmail.comwrote: There have recently been questions whether WMF is able to serve webfonts. Some people think that because of the issues that led to disabling webfonts by default in Universal Language Selector (ULS), WMF is not ready to consider webfonts for typography. I don't think that way Me neither; I agree with much of what you are saying. I'm not sure why Odder abandoned https://gerrit.wikimedia.org/r/#/c/115153/ (Odder, I'm sorry if my comments were hurtful for some reason -- and I want to say that I appreciate the fact that you use your technical savvy to help communities make their voices heard in technical forums.) What I was actually going to propose is that the font required by Hebrew Wikisource be loaded unconditionally, for all pages, by being referenced in Common.css. It needs some scrutiny first, but in principle it strikes me as the right way to go. I also think we should consider biting the performance bullet and including a font like Noto https://code.google.com/p/noto/ on all wikis. Again, not a decision to undertake lightly, but something we should definitely consider. It won't solve the problem of individual wikis needing a font for the content language that is suitable for inputing and editing content, but it may be good enough to cover the cases of occasional content in non-primary scripts on most wikis. I filed https://bugzilla.wikimedia.org/show_bug.cgi?id=59983 about that, though to my regret I did so at the height of the ULS drama so my tone was probably not very inviting to future conversation. But if you can stand to ignore it and to think the issue through, please do comment. And finally: I also absolutely agree with Niklas that there remains a large problem that would not be addressed by either approach, and that a platform like ULS, backed by sufficient data and some trial-and-error experience, represents a good approach for solving that. There is one other thing that I think we should be doing: we should strive to offer the very best HOWTO on the internet for obtaining and installing additional fonts for users, so that we empower to use the internet in their language, not just on Wikimedia (and MediaWiki) wikis, but across the web. If something like that already exists and I am simply an ignorant oaf (which is quite possible) than I eat my hat by way of apology :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Vagrant Cloud
quote name=Ori Livneh date=2014-03-14 time=18:22:26 -0700 Vagrant Cloud is a new service from Hashicorp that strives to make it easy to share Vagrant boxes and to collaborate on provisioned instances together. It's in very early beta, but I have started poking around a little, and it looks interesting. I don't quite know yet how it will work with our extensive custom plugin architecture, but I suspect that this is not an insurmountable problem. Hashicorp is also committed to a freemium model that makes the software stack free (as in speech) and the basic tier of cloud services free (as in beer), so it may be possible for us to have tighter integration with their service without compromising our values. There's also a totally libre solution called pagekite https://pagekite.net/ I've used it with vagrant and it Just Works(TM). They have a Free for FOSS tier: https://pagekite.net/signup/?more=bw#fff Just for completeness's sake :) -- | 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
Re: [Wikitech-l] Vagrant Cloud
But, obviously not as well integrated. -- Sent from my phone, please excuse brevity. On Mar 14, 2014 7:38 PM, Greg Grossmeier g...@wikimedia.org wrote: quote name=Ori Livneh date=2014-03-14 time=18:22:26 -0700 Vagrant Cloud is a new service from Hashicorp that strives to make it easy to share Vagrant boxes and to collaborate on provisioned instances together. It's in very early beta, but I have started poking around a little, and it looks interesting. I don't quite know yet how it will work with our extensive custom plugin architecture, but I suspect that this is not an insurmountable problem. Hashicorp is also committed to a freemium model that makes the software stack free (as in speech) and the basic tier of cloud services free (as in beer), so it may be possible for us to have tighter integration with their service without compromising our values. There's also a totally libre solution called pagekite https://pagekite.net/ I've used it with vagrant and it Just Works(TM). They have a Free for FOSS tier: https://pagekite.net/signup/?more=bw#fff Just for completeness's sake :) -- | 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
Re: [Wikitech-l] GSoC'14 Proposal
Nemo, Thanks for bringing this to my notice. But still I think my proposal different than that one in many aspects. 1) I want to help people in making online wikipedia notes., not just one time sharing. 2) My idea is about helping people remember what did they read a few months ago and help them recalling those keywords easily with just a glance over those highlighted words. 3) My idea will help students in revising easily. They won't have to got through the whole wikipedia page. Just look at the previously important highlighted words/sentences and you are done.. Still I would like to know whether the project/idea you pointed out has already been implemented. I highly doubt that. Please throw some light over it. Regards *Sahil Dua* Netaji Subhas Institute of Technology, New Delhi *https://www.facebook.com/picsmashup https://www.facebook.com/picsmashup* Ph: +91-9899740957 On Sat, Mar 15, 2014 at 3:03 AM, Federico Leva (Nemo) nemow...@gmail.comwrote: There are countless such services already. What you propose is similar to https://www.mediawiki.org/wiki/Mentorship_programs/ Possible_projects#Annotation_tool_that_extracts_statements_ from_books_and_feed_them_on_Wikidata. Nemo ___ 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
