Re: [Wikitech-l] Lua deployed to test2wiki
On Tuesday, August 14, 2012 at 11:31 PM, Rob Lanphier wrote: One obvious target for converting to Lua would be the Cite template. It would be really great to take an article with a long parse time (e.g. the Barack Obama or The Beatles), import it to test2, and try to get the parse time down to something reasonable simply by converting the Cite+other key templates to Lua. Template:Cite is terrifyingly complex. What are some other key templates? There must be others like me who want the fame and fortune of being an early adopter, without all that the hard work :) -- Ori Livneh o...@wikimedia.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Lua deployed to test2wiki
To answer my own question: http://en.wikipedia.org/wiki/Wikipedia:Database_reports/Templates_transcluded_on_the_most_pages -- Ori Livneh o...@wikimedia.org On Monday, August 20, 2012 at 12:30 AM, Ori Livneh wrote: On Tuesday, August 14, 2012 at 11:31 PM, Rob Lanphier wrote: One obvious target for converting to Lua would be the Cite template. It would be really great to take an article with a long parse time (e.g. the Barack Obama or The Beatles), import it to test2, and try to get the parse time down to something reasonable simply by converting the Cite+other key templates to Lua. Template:Cite is terrifyingly complex. What are some other key templates? There must be others like me who want the fame and fortune of being an early adopter, without all that the hard work :) -- Ori Livneh o...@wikimedia.org (mailto:o...@wikimedia.org) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Lua deployed to test2wiki
I know if I happen to have time to learn Lua, I'd definitely tackle the ArticleHistory template. One of the more complex ones out there. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Mon, Aug 20, 2012 at 3:44 AM, Ori Livneh o...@wikimedia.org wrote: To answer my own question: http://en.wikipedia.org/wiki/Wikipedia:Database_reports/Templates_transcluded_on_the_most_pages -- Ori Livneh o...@wikimedia.org On Monday, August 20, 2012 at 12:30 AM, Ori Livneh wrote: On Tuesday, August 14, 2012 at 11:31 PM, Rob Lanphier wrote: One obvious target for converting to Lua would be the Cite template. It would be really great to take an article with a long parse time (e.g. the Barack Obama or The Beatles), import it to test2, and try to get the parse time down to something reasonable simply by converting the Cite+other key templates to Lua. Template:Cite is terrifyingly complex. What are some other key templates? There must be others like me who want the fame and fortune of being an early adopter, without all that the hard work :) -- Ori Livneh o...@wikimedia.org (mailto:o...@wikimedia.org) ___ 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] [RFC] Abstract table definitions
Makes sense. IMHO most of the stuff I mentioned is just minor qualms. The overall syntax is pretty nice, and I think it'd be a great idea to have something like this. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Sun, Aug 19, 2012 at 7:12 AM, Daniel Friesen dan...@nadir-seen-fire.comwrote: On 12-08-18 10:37 PM, Tyler Romeo wrote: I think this is an awesome idea and I'd be willing to help on this. I have a few questions about the page linked above though: - Why don't we use foreign keys in MySQL? We don't use them now so I didn't use them in the abstract table schema types. PostreSQL and iirc Oracle use them so I added reference(), it also acts as a documentation hint. We could regenerate the table schema documentation based on this. This time around directly extracting what column refers to another out of the code. For MySQL, FKeys actually lower performance, but in any case if you think we should use foreign keys we should have a wikitech-l discussion over it. - The word hack is used three times. That's probably an issue. ;) Heh. Yeah. Though how else do we handle the few spots where a part of our database schema goes and does something complete out of line from the rest of the schema? eg: cl_timestamp uses timestamp instead of our binary(14). - Is there a reason we're changing the default from NULL to NOT NULL? Wouldn't it be better to just use a required keyword? 95% of our column definitions are NOT NULL. In fact not allowing null is practically a default, you don't really allow null unless you make an explicit decision that you want null values. So I made NOT NULL the default and made allowing null an explicit nullable flag. NOT NULL only prevents you from setting a field as null. It doesn't make it required because most other fields will still default to something like 0, '', or some other default that's specified. So required doesn't really fit the meaning - We should probably support MySQL's -- comment syntax, just in case. Yeah I planned to from the start. Just include opening #, --, and // comments inside the parser. Although, when it came to table alters I started contemplating the -- comment vs. -column; parsing and rethought that. Though thinking about it again, the parsing will probably work fine. - What's the [ignore] on the insert call do? (It becomes a little confusing since there is also the [tablename] syntax on global indexes.) That was for INSERT IGNORE. After I noticed that some of our archive/*.sql files use INSERT IGNORE. I dropped the idea of `insert ignore tablename ...` because it would be ambiguous for a table named ignore. So yeah, it would be nice to find a better syntax for insert ignore. I'm also contemplating if I should find a syntax for INSERT..SELECT since we seem to use it in a small number of migrations. - The Alter Table syntax looks really weird (with tildas and whatnot). I started wanting to keep the alter table syntax as close as possible to the table definition/creation syntax. So I started with prefixing with - and + which work beautifully as DROP and ADD column/etc... commands. Then when I thought of MODIFY/CHANGE I didn't want to make that unprefixed and ~ seemed to work best for that. But yeah, here and there it could use some ideas for alternative ways to do the syntax. ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Sat, Aug 18, 2012 at 2:20 PM, Daniel Friesen li...@nadir-seen-fire.com wrote: I see the branch, but I don't see the code: https://svn.wikimedia.org/viewvc/mediawiki/branches/abstract-schema/phase3/ It looks like someone just copied phase3 and then never actually changed any code. I don't even see a syntax idea there. ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] On 12-08-18 11:10 AM, Chad wrote: We tried this before, and I'd love to see it happen. Take a look at the abstract-schema branch in SVN for what we did. -Chad On Aug 18, 2012 1:53 PM, Daniel Friesen li...@nadir-seen-fire.com mailto:li...@nadir-seen-fire.com wrote: We've got a nice abstract query system but our table creation and migrations are horrible. We re-write them for multiple database engines. And as a result extensions need to do the same and often don't. Leading to things being a mess for databases other than MySQL. While I was doing the sites stuff a syntax for defining tables came to mind and I wrote out an RfC for a method of defining our database abstractly. https://www.mediawiki.org/wiki/Requests_for_comment/Abstract_table_definitions -- ~Daniel Friesen (Dantman,
Re: [Wikitech-l] How to create account by API?
Hey Munaf, Can we schedule a quick IRC meet sometime today to discuss this, I can help on incorporating the required changes. Akshay On Fri, Aug 17, 2012 at 10:46 PM, Munaf Assaf mas...@wikimedia.org wrote: This is a long thread that I just caught wind of, but I thought I'd interject with a few notes. The E3 team is going to start doing experiments on the account creation process, starting with the signup page. The front-end is going to be reworked to conform to the design team's new Agora standards, like so: http://www.mediawiki.org/wiki/Account_creation_user_experience As for the API: we are going to make some improvements to it as part of our first experiment. Yes, it is functional now, but we need to do a bit of hacking to support our proposed UX improvements, as well as make it more consistent with WMF JavaScript guidelines. If someone wants to improve the signup template in core, that would be excellent - but since our team needs to move quickly, we're likely going to just going to make our own fork of the extension and display the proposed template for users in a small experimental bucket. Feel free to email me if you have questions. :-) Cheers, Munaf On Fri, Aug 17, 2012 at 8:30 AM, Tyler Romeo tylerro...@gmail.com wrote: With items like SpecialPages and API classes, it is indeed a possibility to first make it an extension and then integrate it, primarily because there is little difference in how a core SpecialPage/APIBase is implemented and how an extension is implemented. However, this workflow is not required. The problem is that the LoginForm class is old and run-down, and we shouldn't really be basing code off of it. A better way to go about it would be to make use of the newer MW infrastructures like FormSpecialPage and Status to make a cleaner implementation. The account creation API currently in Gerrit is actually a bit of a hack (as is the Login API and many other similar modules) because of the fact that there is not a good separation between application logic and UI in many core features of MW. It would be much preferred to fix this then to pile on top of the current way things are implemented. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com | tylerro...@gmail.com On Fri, Aug 17, 2012 at 11:09 AM, Akshay Agarwal akshay.leadin...@gmail.com wrote: I am not sure how stuff works now but at the time I was working on this project, any features missing in the MediaWiki codebase were first developed as an extension, reviewed, tested and then integrated in the core. The current version of the SpecialPage looks similar to LoginForm because it was indeed derived from there one of the main goals for this project was to remove the account creation code from SpecialUserLogin put it inside its own SpecialPage. I do realize that some refactoring might still be needed but I definitely can say that the efforts to do that would be much lesser than rewriting the entire module because the new module would again have to go through similar iterations through which SignupAPI already went. Tyler, I really appreciate your efforts in developing a new API I would encourage you to contribute with all the learning that you have had in this project to getting SignupAPI deployed because the project involves many more things than just an additional API, many of which I have conveyed in my previous mail. On Fri, Aug 17, 2012 at 8:27 PM, Derric Atzrott datzr...@alizeepathology.com wrote: User account creation is something that is pretty critical to the MediaWiki infrastructure. If we're going to be completely revamping the signup page, it should not be done in an extension. Furthermore, looking at the extension's code now, there are numerous design problems that would need to be fixed if this were to be deployed (primarily the fact that the entire special page looks pretty much like a copy of LoginForm's account creation interface). Not to mention that an account creation API is something that the core needs and site admins should not have to rely on an extension to install it. I'm welcome to a rewrite and refactoring of the LoginForm, if that's a goal we want to aim towards. Still we should take note of the lessons he learned when he made his extension and apply them to development of a API in the core, should we go that route. I agree that this should be a core feature and not an extension. This seems like the sort of thing that many Wikis will need and I'm somewhat surprised the request for someone to make it doesn't come up more often. Thank you, Derric Atzrott ___
Re: [Wikitech-l] Is the current system too difficult for volunteer developers?
On 07/29/2012 09:17 AM, Niklas Laxström wrote: Have you wondered how GiGeGat [1] works for volunteer developers if even paid developers have difficulties with it? We have already seen cases where it works, but we don't know much about the cases where volunteers decide to give up. Here, however, is one example [2] of the latter which I want to highlight. The developer finds it too slow and complicated and wants to move to GitHub and as consequence we cannot provide translation services for his extensions at translatewiki.net. Anyone willing to dig deeper what problems there are and try to resolve them? -Niklas [1] My favorite abbreviation for Git, Gerrit and Gated trunk [2] http://translatewiki.net/wiki/Thread:Support/Add_MediaWiki_Extensions_from_github_to_translation Thanks for the heads-up, Niklas. I think other people in the thread have provided the current stats around commits and number of committers, but to return to the original point: it looks like the TWN thread there has stopped without a resolution. Niklas, is there any outcome, or is the developer still awaiting a solution? -- 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] How to create account by API?
Ashkay, I'm actually the designer on it, not the developers (Ori Livneh and S Page). We're still in the midst of planning the experiment, so it's not all ready to go yet. We'll email you with questions/etc. soon! Thanks, Munaf Assaf On Monday, August 20, 2012 at 7:52 AM, Akshay Agarwal wrote: Hey Munaf, Can we schedule a quick IRC meet sometime today to discuss this, I can help on incorporating the required changes. Akshay On Fri, Aug 17, 2012 at 10:46 PM, Munaf Assaf mas...@wikimedia.org (mailto:mas...@wikimedia.org) wrote: This is a long thread that I just caught wind of, but I thought I'd interject with a few notes. The E3 team is going to start doing experiments on the account creation process, starting with the signup page. The front-end is going to be reworked to conform to the design team's new Agora standards, like so: http://www.mediawiki.org/wiki/Account_creation_user_experience As for the API: we are going to make some improvements to it as part of our first experiment. Yes, it is functional now, but we need to do a bit of hacking to support our proposed UX improvements, as well as make it more consistent with WMF JavaScript guidelines. If someone wants to improve the signup template in core, that would be excellent - but since our team needs to move quickly, we're likely going to just going to make our own fork of the extension and display the proposed template for users in a small experimental bucket. Feel free to email me if you have questions. :-) Cheers, Munaf On Fri, Aug 17, 2012 at 8:30 AM, Tyler Romeo tylerro...@gmail.com (mailto:tylerro...@gmail.com) wrote: With items like SpecialPages and API classes, it is indeed a possibility to first make it an extension and then integrate it, primarily because there is little difference in how a core SpecialPage/APIBase is implemented and how an extension is implemented. However, this workflow is not required. The problem is that the LoginForm class is old and run-down, and we shouldn't really be basing code off of it. A better way to go about it would be to make use of the newer MW infrastructures like FormSpecialPage and Status to make a cleaner implementation. The account creation API currently in Gerrit is actually a bit of a hack (as is the Login API and many other similar modules) because of the fact that there is not a good separation between application logic and UI in many core features of MW. It would be much preferred to fix this then to pile on top of the current way things are implemented. *--* *Tyler Romeo* Stevens Institute of Technology, Class of 2015 Major in Computer Science www.whizkidztech.com (http://www.whizkidztech.com) | tylerro...@gmail.com (mailto:tylerro...@gmail.com) On Fri, Aug 17, 2012 at 11:09 AM, Akshay Agarwal akshay.leadin...@gmail.com (mailto:akshay.leadin...@gmail.com) wrote: I am not sure how stuff works now but at the time I was working on this project, any features missing in the MediaWiki codebase were first developed as an extension, reviewed, tested and then integrated in the core. The current version of the SpecialPage looks similar to LoginForm because it was indeed derived from there one of the main goals for this project was to remove the account creation code from SpecialUserLogin put it inside its own SpecialPage. I do realize that some refactoring might still be needed but I definitely can say that the efforts to do that would be much lesser than rewriting the entire module because the new module would again have to go through similar iterations through which SignupAPI already went. Tyler, I really appreciate your efforts in developing a new API I would encourage you to contribute with all the learning that you have had in this project to getting SignupAPI deployed because the project involves many more things than just an additional API, many of which I have conveyed in my previous mail. On Fri, Aug 17, 2012 at 8:27 PM, Derric Atzrott datzr...@alizeepathology.com (mailto:datzr...@alizeepathology.com) wrote: User account creation is something that is pretty critical to the MediaWiki infrastructure. If we're going to be completely revamping the signup page, it should not be done in an extension. Furthermore, looking at the extension's code now, there are numerous design problems that would need to be fixed if this were to be deployed (primarily the fact that the entire special page looks pretty much like a copy of LoginForm's account creation interface). Not to mention that an account creation API is
[Wikitech-l] Invitation for Localisation team development demonstration 2012-08-21 15:00 UTC
You are invited to the Localisation team development demo on Tuesday 21 August 2012 at 15:00 UTC (other time zones: 08:00 PDT, 17:00 CEST, 20:30 IST). This meeting will take 40 minutes at most. In this meeting the Localisation team will present its deliverables from sprint 22[1]. After about 20 minutes of presentation, the remainder of the meeting is for discussion. We hope you can attend, and please invite any other colleagues or friends you think are interested! This meeting will be held using WebEx. Please ensure that you log in a few minutes before the meeting starts, so that you have time to install any required plug-ins or software. Connection details and a quick link to add this meeting to your calendar can be found below the signature. Slides of our previous sprint demo are also available[2]. [1] https://mingle.corp.wikimedia.org/projects/internationalization/cards/1071 [2] https://commons.wikimedia.org/wiki/File:Wikimedia_Localisation_team_Sprint_21_demo.pdf -- Siebrand Mazeland Product Manager Localisation Wikimedia Foundation M: +31 6 50 69 1239 Skype: siebrand Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate --- To join the online meeting (Now from mobile devices!) --- 1. Go to https://wikimedia.webex.com/wikimedia/j.php?ED=183453277UID=1297933382RT=MiMyMg%3D%3D 2. If requested, enter your name and email address. 3. No password is required 4. Click Join. To view in other time zones, please click the link: https://wikimedia.webex.com/wikimedia/j.php?ED=183453277UID=1297933382ORT=MiMyMg%3D%3D To add this meeting to your calendar program, click this link: https://wikimedia.webex.com/wikimedia/j.php?ED=183453277UID=1297933382ICS=MILD=1RD=2ST=1SHA2=kNl8D6AcQ4btV9qDHhL-oDcEv-g0qy803klHuaaLpfo=RT=MiMyMg%3D%3D ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Is the current system too difficult for volunteer developers?
On Mon, 20 Aug 2012 09:15:00 -0700, Sumana Harihareswara suma...@wikimedia.org wrote: On 07/29/2012 09:17 AM, Niklas Laxström wrote: Have you wondered how GiGeGat [1] works for volunteer developers if even paid developers have difficulties with it? We have already seen cases where it works, but we don't know much about the cases where volunteers decide to give up. Here, however, is one example [2] of the latter which I want to highlight. The developer finds it too slow and complicated and wants to move to GitHub and as consequence we cannot provide translation services for his extensions at translatewiki.net. Anyone willing to dig deeper what problems there are and try to resolve them? -Niklas [1] My favorite abbreviation for Git, Gerrit and Gated trunk [2] http://translatewiki.net/wiki/Thread:Support/Add_MediaWiki_Extensions_from_github_to_translation Thanks for the heads-up, Niklas. I think other people in the thread have provided the current stats around commits and number of committers, but to return to the original point: it looks like the TWN thread there has stopped without a resolution. Niklas, is there any outcome, or is the developer still awaiting a solution? It also looks like it didn't even go on for long. I'd like to know what kind of issues he had, rather than just the fact that he had issues, and we know there are issues which may or may not be the ones he had trouble with. He's using GitHub so it looks like he's fine with the Git part. Is it Gerrit he had trouble with or the fundamental idea of Gated repos where he waits for review? Or is his issue more with the current trouble trying to create new repos and get into development? If he has Gated repo issues, would Gerrit's direct push permission work? If Gerrit is really the issue and he doesn't actually have an issue with the idea of a Gated repo, then would another gated workflow work? eg: Would Phabricator's work? Or would mine work? -- ~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://daniel.friesen.name] ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Wiki Loves Monuments Android App v1.1beta2
Very sorry for the confusion. We scaled back this beta release because it was not yet at a point where a public beta release on Google Play made sense. The project page will be updated to say the next release, which is intended to be this Friday, will be put on Google Play. Phil On Sun, Aug 19, 2012 at 11:45 AM, Cristian Consonni kikkocrist...@gmail.com wrote: 2012/8/18 Philip Chang pch...@wikimedia.org: Greetings WLM testers, Below you'll find a new beta of our android app that's very close to being feature complete. As before, make sure to have Unknown sources in Settings = Applications turned on. Uploads will go to test wiki so feel free to upload whatever you like. Download: http://dumps.wikimedia.org/android/WLM-v1.1beta2.apk Feedback: http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/Feedback Just one question: reading the app development timeline[*], it says that the beta version would be downloadable from the Play store as a beta app. I tried to search it with no success, both from the play store[+] and from the phone (the results I obtain are the same, btw) . When will be the app available on the store? (or it's just me which can't find it?) Cristian [*] http://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application#Project_timeline [+] https://play.google.com/store/search?q=wiki+loves+monumentsc=appsprice=0sort=1 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Phil Inje Chang Product Manager, Mobile Wikimedia Foundation 415-812-0854 m 415-882-7982 x 6810 ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
First of all, thank you Ryan, Faidon, Brandon and others for the related thread. Indeed it feels like a rough environment sometimes, especially on lists, sometimes also on IRC and I really appreciated seeing colleagues step in for me in that way. On Fri, Aug 17, 2012 at 1:59 PM, MZMcBride z...@mzmcbride.com wrote: I've always found you to be incredibly helpful on IRC, on the mailing lists, and elsewhere and I've always appreciated having you around. I apologize if my initial message suggested otherwise. That said, also thank you for that, MZ. apology gladly accepted. I read your reply to Guillom's post as shit happens. And it most certainly does. But you said that the archives were last rebuilt two weeks ago, which is where the timeline kind of fell apart in my head. That's understandable. To me it sounded like he just walked away when most of the messages had been sent during the night in PST and i had just arrived at the office. Until Guillaume brought it up on the list I thought of it as a drawback of removing mails, which i had mentioned before and which makes us do as little removals as possible but we would have to live with as it had happened before. There was no communication to the list and its members and the archive being rebuilt two weeks ago and the consequences of doing so. One of the reasons for not sending any announcement for this to the list was that it was about removing private data, so i did not want to go Look, here is this private data i am now going to delete. Of course i could have still pointed out that archives are being rebuilt without giving the details. Ok, back to the technical issue: On Sat, Aug 18, 2012 at 1:19 AM, Guillaume Paumier gpaum...@wikimedia.org wrote: After April 2012: The link http://lists.wikimedia.org/pipermail/wikitech-l/2012-July/061691.html was posted on meta to reference a message of mine from July 2012. That ID (061691) had to be changed to 061614 after the rebuild from 2 weeks ago (i.e. a translation of -77). After yesterday's rebuild, it's now at ID 061621 (a translation of +7 consistent with the 7 empty messages you've reinserted). :( This is really unfortunate, but sorry, i don't have an explanation for the difference of -77 unless there has been another rebuild that i am not aware of or it actually was broken before my latest change...or it's a mailman bug..:/ So, it appears that the archives have been corrupted inconsistently besides the simple translations of -77 or -7. Someone can probably verify that with other links (e.g. from the Signpost pages). Is it really random or at least consistent -77 since after April 2012? Well, but as Ryan pointed out this whole issue has happened several times in the past, so i expect you could always find broken links somewhere depending on the time they have been created. the August 2012 archive page contains several No subject messages I don't know where these come from. Are they really new since this incident? I would really prefer to not delete anything at this point and break links once again. On Sat, Aug 18, 2012 at 11:35 AM, Platonides platoni...@gmail.com wrote: If I remember right, the issue of deleting old mails was not just that the ids moved the number of deleted mails, but that when rebuilding the archive, new versions rebuilt it differently. Thus the changed numeration. That would indeed explain inconsistencies in old links before April. I think though that we have rebuilt archives more than once with this current mailman version. Still would explain corruption from the past though. Can we restore the old files from backups? Again, really unfortunate, but we can't at this point. Backups are going back one week. I'm afraid the best i can do now is to help fixing external links. If somebody wants to point me to WP pages with broken links to mailman archives, i would gladly help to fix them in an edit sprint. Daniel Zahn dz...@wikimedia.org Operations Engineer ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
I don't know where these come from. Are they really new since this incident? I would really prefer to not delete anything at this point and break links once again. Those emails are definitely new. I didn't see them in the archive earlier this month when I was going through it. Backups are going back one week. Usually not one to complain about gramatically improper sentences, as I write them regularly, but you lost me on this sentence. Do our backups only go back a week? Or are backups only taken once a week? Thank you, Derric Atzrott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Invitation for Localisation team development demonstration 2012-08-21 15:00 UTC
This meeting will be held using WebEx. Please ensure that you log in a few minutes before the meeting starts, so that you have time to install any required plug-ins or software. Connection details and a quick link to add this meeting to your calendar can be found below the signature. Funny question, is there any chance of holding this (and/or future) meetings without relying on non-free software? Especially 'round these parts, there are bound to be people who prefer not to use Flash/Quicktime/WMP/WebEx. bias disclosure: I am one of them. -- Mark Holmquist Contractor, Wikimedia Foundation mtrac...@member.fsf.org http://marktraceur.info ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Meta: Inproper Line Breaks
This may help: http://www.fix-outlook-line-breaks.com/ Not quite my issue as I don't have HTML emails turned on. You seem to be writing the messages for cutting at 80 characters per line, but be actually sent cutting at 74 or so. The first are treated as hard breaks, so there are two breaks, one at 74 characters and another one at what would have been 80, thus producing lonely words. I also suspect of Outlook for causing hthis, but know little on how to fix. See if you have some option to reduce the line length. I agree that this seems to be an Outlook issue. If I don't hand break my lines, Outlook does it for me it seems (see the last message I posted for an example). I'll count how many characters it breaks at and break there by hand in the future so that I continue to get at the beginning of all quoted lines. Hopefully that works. Thank you all for your help in diagnosing this rather annoying issue. Thank you, Derric Atzrott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Mailman archives broken?
On Mon, Aug 20, 2012 at 11:29 AM, Derric Atzrott datzr...@alizeepathology.com wrote: Do our backups only go back a week? Or are backups only taken once a week? They are taken daily and go back one week. To be exact 6 Daily-slots exist in Amanda backup. -- Daniel Zahn dz...@wikimedia.org Operations Engineer ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Invitation for Localisation team development demonstration 2012-08-21 15:00 UTC
Hi Mark, We use WMF's infrastructure which is WebEx. It is unfortunately not free software but I would love to have another alternative that scales for remote / distributed folks joining in and scaling for video, audio and screen sharing. Suggestions are always welcome :-) Alolita On Mon, Aug 20, 2012 at 11:32 AM, Mark Holmquist mtrac...@member.fsf.org wrote: This meeting will be held using WebEx. Please ensure that you log in a few minutes before the meeting starts, so that you have time to install any required plug-ins or software. Connection details and a quick link to add this meeting to your calendar can be found below the signature. Funny question, is there any chance of holding this (and/or future) meetings without relying on non-free software? Especially 'round these parts, there are bound to be people who prefer not to use Flash/Quicktime/WMP/WebEx. bias disclosure: I am one of them. -- Mark Holmquist Contractor, Wikimedia Foundation mtrac...@member.fsf.org http://marktraceur.info ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Alolita Sharma Director of Engineering Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Invitation for Localisation team development demonstration 2012-08-21 15:00 UTC
This meeting will be held using WebEx. Please ensure that you log in a few minutes before the meeting starts, so that you have time to install any required plug-ins or software. Connection details and a quick link to add this meeting to your calendar can be found below the signature. Funny question, is there any chance of holding this (and/or future) meetings without relying on non-free software? Especially 'round these parts, there are bound to be people who prefer not to use Flash/Quicktime/WMP/WebEx. bias disclosure: I am one of them. +1 this. I didn't participate and wasn't planning on it, but I think, given the nature of the community, that using free software as much as possible can't be a bad thing. Thank you, Derric Atzrott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Meta: Inproper Line Breaks
On Mon, Aug 20, 2012 at 2:36 PM, Derric Atzrott datzr...@alizeepathology.com wrote: This may help: http://www.fix-outlook-line-breaks.com/ Not quite my issue as I don't have HTML emails turned on. You seem to be writing the messages for cutting at 80 characters per line, but be actually sent cutting at 74 or so. The first are treated as hard breaks, so there are two breaks, one at 74 characters and another one at what would have been 80, thus producing lonely words. I also suspect of Outlook for causing hthis, but know little on how to fix. See if you have some option to reduce the line length. I agree that this seems to be an Outlook issue. If I don't hand break my lines, Outlook does it for me it seems (see the last message I posted for an example). I'll count how many characters it breaks at and break there by hand in the future so that I continue to get at the beginning of all quoted lines. Or install vim, copy from outlook to vim, :set tw=70, use `gqq` as needed, copy back. -Jeremy ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Invitation for Localisation team development demonstration 2012-08-21 15:00 UTC
On Mon, Aug 20, 2012 at 11:35 AM, Alolita Sharma asha...@wikimedia.org wrote: We use WMF's infrastructure which is WebEx. It is unfortunately not free software but I would love to have another alternative that scales for remote / distributed folks joining in and scaling for video, audio and screen sharing. Suggestions are always welcome :-) fwiw: http://www.webriti.com/index.php/open-source/apache-open-meeting-an-open-source-alternative-to-webex/ http://incubator.apache.org/openmeetings/ -- Daniel Zahn dz...@wikimedia.org Operations Engineer ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Announcing Signpost for Android app 1.0 RC1!
Assuming wikitech-l also has some people interested in this. -- Forwarded message -- From: Yuvi Panda yuvipa...@gmail.com Date: Mon, Aug 20, 2012 at 11:38 PM Subject: Announcing Signpost for Android app 1.0 RC1! To: mobile-l mobil...@lists.wikimedia.org Me and a friend ([[User:Notnarayan]])) have been working on a Signpost app in our spare time for a while. This lets you access Wikipedia Signpost from a mobile device in a nice and (hopefully) beautiful way. More information at https://www.mediawiki.org/wiki/Signpost_Mobile_App Today, I'm putting out RC1 of the version 1 of this app. You can download it at https://github.com/yuvipanda/WPSignpost/WPSignpost-1.0RC1.apk/qr_code and file issues at https://github.com/yuvipanda/WPSignpost/issues?state=open. You can find screenshots of the current version of the app at https://commons.wikimedia.org/wiki/Category:Wikipedia_Signpost_Android_App_screenshots For this version, features so far are: 1. Load current issue of the Signpost 2. Browse through and load any previous issue of the Signpost 3. Beautiful Image based display of each signpost issue 4. Articles are formatted easily for viewing on your mobile device 5. Sharing of articles from the app All of them have been implemented, and provided no major new issues are found, I'll push this version to the Google Play store in a week. Please do test it out on your device, and report issues either at the github url specified above or by replying to this email. -- Yuvi Panda T http://yuvi.in/blog ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Announcing Signpost for Android app 1.0 RC1!
Awesome Yuvi :-) Good stuff. On Mon, Aug 20, 2012 at 12:45 PM, Yuvi Panda yuvipa...@gmail.com wrote: Assuming wikitech-l also has some people interested in this. -- Forwarded message -- From: Yuvi Panda yuvipa...@gmail.com Date: Mon, Aug 20, 2012 at 11:38 PM Subject: Announcing Signpost for Android app 1.0 RC1! To: mobile-l mobil...@lists.wikimedia.org Me and a friend ([[User:Notnarayan]])) have been working on a Signpost app in our spare time for a while. This lets you access Wikipedia Signpost from a mobile device in a nice and (hopefully) beautiful way. More information at https://www.mediawiki.org/wiki/Signpost_Mobile_App Today, I'm putting out RC1 of the version 1 of this app. You can download it at https://github.com/yuvipanda/WPSignpost/WPSignpost-1.0RC1.apk/qr_code and file issues at https://github.com/yuvipanda/WPSignpost/issues?state=open. You can find screenshots of the current version of the app at https://commons.wikimedia.org/wiki/Category:Wikipedia_Signpost_Android_App_screenshots For this version, features so far are: 1. Load current issue of the Signpost 2. Browse through and load any previous issue of the Signpost 3. Beautiful Image based display of each signpost issue 4. Articles are formatted easily for viewing on your mobile device 5. Sharing of articles from the app All of them have been implemented, and provided no major new issues are found, I'll push this version to the Google Play store in a week. Please do test it out on your device, and report issues either at the github url specified above or by replying to this email. -- Yuvi Panda T http://yuvi.in/blog ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l -- Alolita Sharma Director of Engineering Wikimedia Foundation ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Bots create page views
This regular bi-weekly pattern of reported page views http://stats.grok.se/sv.s/latest90/Wikisource:Projekt_Bibel%C3%B6vers%C3%A4ttningar/Fjellstedt is created by a bot job. Note that this is a WikiProject page. Are the reported number of page views inflated by bots? Is there no way to filter out bot visits? In other news, this page has a weekly pattern of real, human visitors, since it is a radio quiz where lots of listeners are known to use google searches, http://stats.grok.se/sv/latest90/Melodikrysset -- Lars Aronsson (l...@aronsson.se) Aronsson Datateknik - http://aronsson.se ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Lua deployed to test2wiki
Ori Livneh wrote: On Monday, August 20, 2012 at 12:30 AM, Ori Livneh wrote: On Tuesday, August 14, 2012 at 11:31 PM, Rob Lanphier wrote: One obvious target for converting to Lua would be the Cite template. It would be really great to take an article with a long parse time (e.g. the Barack Obama or The Beatles), import it to test2, and try to get the parse time down to something reasonable simply by converting the Cite+other key templates to Lua. Template:Cite is terrifyingly complex. What are some other key templates? There must be others like me who want the fame and fortune of being an early adopter, without all that the hard work :) To answer my own question: https://en.wikipedia.org/wiki/Wikipedia:Database_reports/Templates_transcluded _on_the_most_pages Templates that are transcluded a lot usually are not the most complex or the most interesting. As I understand it, brace substitution and recursion depth were/are the big performance killers with ParserFunctions. I could swear that you used to be able to profile Parser::BraceSubstitution or something similar directly with a ?forceprofile=true or ?forcetrace=true URL parameter, but it doesn't seem to be working now. (?forceprofile=true still outputs an HTML comment with some profiling information; ?forcetrace=true seems to do nothing.) I believe Tim has created or plans to create better profiling tools for templates. I have no idea what the status of that is. If you're looking for other nerdy/fun templates to convert, the chess templates come to mind. MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
