[16:56:10] Language Engineering office hour starts in another 5 mins [17:00:59] #startmeeting Language Engineering monthly office hour [17:00:59] Meeting started Wed Mar 12 17:00:59 2014 UTC and is due to finish in 60 minutes. The chair is arrbee. Information about MeetBot at http://wiki.debian.org/MeetBot. [17:00:59] Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. [17:00:59] The meeting name has been set to 'language_engineering_monthly_office_hour' [17:01:15] Hello, Welcome to the monthly office hour of the Wikimedia Language Engineering team [17:01:26] good evening [17:01:44] My name is Runa and I am am the Outreach coordinator for our team [17:01:52] Moin [17:02:30] My team mates around are: aharoni divec kart_ Nikerabbit pginer santhosh [17:02:58] Our last office hour was held on February 12, 2014. The logs are at: [17:03:08] #link https://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2014-02-12 [17:03:09] Mirëmbrëma. [17:03:41] IMPORTANT: The chat today will be logged and publicly posted. This has also been mentioned in the channel topic. [17:04:02] For those who are here for the first time, [17:04:18] We are the Language Engineering team of the Wikimedia Foundation [17:04:36] and our mission is to build language features and tools to support our wiki communities across the world [17:05:02] aharoni: what is the appropriate response to that greeting? [17:05:28] Our team hosts office hours once every month on the 2nd Wednesday of the month [17:05:31] * aharoni checks his recently-purchased Albanian textbook [17:05:56] This office hour is intended as an open house for our community and us to interact about our work and projects [17:06:18] We look forward to learning more about how the tools are being used, and how we can make them better [17:07:23] Today's session is particularly interesting for us because we also wanted to connect with the students who have been looking at the language engineering projects for this year's Google Summer of Code and OPW [17:08:03] Before that discussion I'd like to introduce you to a new tool that has been keeping us quite engaged since the past few weeks [17:08:28] #info This new extension called ContentTranslation is designed to be used for translating wiki pages [17:08:51] #link https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/ContentTranslation [17:09:13] This would include editing features and translation tools to assist in translations [17:09:50] or https://www.mediawiki.org/wiki/Extension:ContentTranslation [17:10:02] This includes (among others) Translation Memory backed by an ever increasing corpus of parallel text, Machine Translation engines, dictionaries, glossaries [17:10:11] Thanks santhosh [17:10:14] #link https://www.mediawiki.org/wiki/Extension:ContentTranslation [17:10:28] We also intend to tap into the resources at wikidata for links and other data [17:11:22] We are at an early stage of developing this system and are focusing both at the backend servers and frontend user interfaces simultaneously. [17:11:58] Presently, we are collaborating with Bangor University to leverage the language technology solutions for the content translation backend server. [17:12:28] The full announcement is at: [17:12:35] #link http://www.bangor.ac.uk/news/full.php.en?nid=17792&tnid=17792 [17:13:07] this is for translations on multilingual wikis, or from one monolingual wiki to another? [17:13:12] Several features are being designed for this tool [17:14:06] YairRand: the latter [17:14:42] The translation editor is intended to make the translation workflow more fluent (avoiding the constant tab-switching and copy&pasting usually involved in the translation process) [17:15:26] In the translation view the user can see the source article next to your translation, and tools such as automatic translation and dictionary info will be at hand [17:16:51] The extension can also be set up locally, but with limited capability. The instructions are included in the source [17:17:34] We are in the process of documenting our work and you can read more at: [17:17:41] #link https://www.mediawiki.org/wiki/Content_translation/Documentation/Introduction [17:17:58] Meanwhile you can view a video that shows how the editor is shaping up: [17:18:06] #link https://www.youtube.com/watch?v=2QqlhgOTf-A [17:19:25] santhosh and divec_ over to you for some more inputs [17:20:52] That is pretty much about the ContentTranslation project, we will have more updates as the development progress [17:21:29] Thanks santhosh [17:21:39] (All: Watch that video on awesome work santhosh and divec_ has put!) [17:21:52] aharoni: anything to add here? [17:21:55] The translation memory feature allows recall of previously translated segments which are similar; in some cases this can be useful across similar languages [17:22:35] Not much, except that we are very excited. [17:22:42] :) [17:22:46] This may not say much, [17:22:54] but we really want to do it Right. [17:23:24] [Which doesn't mean that it will be developed very slowly :) ] [17:23:44] also pginer is the leading on the design front [17:24:08] * purodha looking forward to reading more from the links mentioned :-) [17:24:35] We're lucky to have experience across many different types of use cases for content translation; this will hopefully allow us to avoid falling into some of the potential pitfalls of a workflow that works for certain common language pairs but not other situations. [17:25:04] divec_: +1 [17:25:34] purodha: you may want to bookmark this link [17:25:38] #link https://www.mediawiki.org/wiki/Content_translation/Documentation [17:25:51] is it online only tool or desktop version is also available? [17:25:54] * purodha did that already  [17:26:11] purodha: But I have to warn you, its going under heavy editing for the next few days [17:26:44] Pavanaja: it is online only. [17:27:02] Pavanaja: it's an online tool optimised specifically for wiki article translation [17:27:26] Oops. Is the meeting over? Am I late? [17:27:29] As such, there are certain differences from other tools designed to translate documents or software strings [17:27:34] Hey Niharika :) [17:27:42] We are about half way through [17:27:45] Hey arrbee. [17:27:47] Okay. [17:29:17] Thats possibly all we had for now about the Content Translation tool. We will be providing more frequent updates once we go into the next phases of development. [17:29:41] Please do ping us at any time if you have questions or suggestions. [17:30:07] I'll move to the next segment [17:30:34] Summer of Code and OPW open house which I had announced yesterday at the meeting hosted by qgil [17:31:41] Before we begin can we know who all are here particularly for the GSoC and OPW program discussion [17:32:31] * arrbee looks around for the mentors too [17:32:41] o/ [17:33:03] Hi all, I am BPositive from Pune, India. I am a GSoC aspirant. [17:33:11] Hello kondi BPositive [17:33:41] hey I'm Rohit (8ohit.dua). GSoC aspirant [17:33:50] Hi rohit-dua [17:34:06] The full list of the language engineering projects can be found here: [17:34:12] #link https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Internationalization_and_localization [17:34:21] You may have already seen the list [17:34:40] (Do note that all listed mentors may not be available right now) [17:35:02] I'm here, but in another meeting :( [17:35:05] We have been receiving proposals and queries for quite a few of these projects [17:35:10] Nikerabbit: no worries [17:35:34] Unless unavoidable, we would like not to discuss about specific proposals [17:35:47] These are better handled through the mediawiki pages that you are creating :) [17:36:35] is this meeting for language engineering GSoC projects aspirants ? because I'm on a different project [17:36:38] In today's session we would like to address your questions about our work, and what you can expect from these projects [17:37:35] rohit-dua: This is the Language Engineering office hour and we are using some time from it to take questions from the students about our projects [17:38:08] rohit-dua: you are most welcome to stick around and share your thoughts [17:40:02] kondi: BPositive We would love to have some feedback on the projects we listed and what you found interesting [17:41:11] arrbee, I found the project "Tools for mass migration of legacy translated wiki content" interesting [17:41:48] BPositive: I believe you also have a proposal for it [17:42:15] arrbee, Yes. Here is the link to the proposal: https://www.mediawiki.org/wiki/Extension:Translate/Mass_migration_tools [17:42:40] arrbee, Nikerabbit: FYI, someone (User:Mep62) interested in participating with OPW for the wiki page translation project sent me an e-mail, I replied but didn't hear anything back [17:42:59] BPositive: Did you find enough information from the project description? (We would like to know if we could make it more informative) [17:43:23] kondi: hi [17:43:31] SPQRobin: ahh ok. Its hard to follow up unless a proposal is in place. [17:44:11] I chose to work on the LUv2 idea since it seems like a project, if accomplished, will be quite useful for all the projects using translatewiki.net as a localisation platform [17:44:16] kart_: hey [17:44:23] The project description was a bit short, but I could understand what the project is all about once I migrated a wiki page manually [17:45:07] kondi: good choice! We will love to see LU2 up and running. Will be quite useful. [17:45:11] And Nikerabbit, and Nemo_bis have been of great help in doing so [17:45:29] BPositive: yay for Nemo and Nike! :) [17:45:57] ugaga :) [17:46:49] kart_: :) I need a proper proposal though. All I have is notes scattered on my desk and disk. [17:47:06] kondi: do that soon! [17:47:07] I first did that assignment, and then fixed a couple of bugs related to the Translate extension to get familiar with the code. I have been reading the code in parallel as well :) [17:47:39] BPositive: really nice. Loved your commits! [17:47:44] We saw aalekh saying yesterday that he could not get through to the mentors. If that happens, which is not unlikely given the timezone differences, direct emails would be very very helpful. [17:48:27] Thanks kart_ . Looking forward to contribute even more :) [17:48:30] BPositive: thanks for your patches ;) [17:48:49] kondi: yes, do that soon and get started with the page on mediawiki.org. Its easy for the mentors too once they know the one place where to go and look. [17:49:03] BPositive: Thats a good start :) [17:49:12] arrbee: sure, will do. [17:49:19] Nikerabbit, thanks for been a fab reviewer ;) Your detailed and long comments still leave me amazed ;) [17:49:24] *being [17:50:13] We have 10 more minutes [17:50:35] BPositive: ask Niharika ;) [17:50:49] Niharika: Did you want to share anything from your OPW experience? [17:50:58] I know the number - 32 or so [17:50:59] arrbee: Yep! [17:51:18] Niharika: please :) [17:51:40] It was an awesome learning experience. I´d like to thank everyone who helped me complete the project. [17:51:41] Now I want to ask a question if I may :) [17:51:56] Also, please do try out the Beta Feature and file as many bugs as possible. [17:52:09] Dear guest students, what makes you curious about internationalization? [17:52:10] I´ll work on every one of them after this week. [17:52:11] bugs.are.important [17:52:41] Special thanks to pginer, santhosh, Nikerabbit. :) [17:52:50] Niharika: we have loved your blog posts! [17:53:00] Thank you! [17:53:16] yes, Niharika - no blog post is too simple. [17:53:27] everything is worth to be written and you did it very well. [17:53:47] :) I am so glad you all liked it. [17:53:57] aharoni, The very fact that language does not become a barrier for people to get information :) [17:54:23] For everyone, here is Niharika's document on her OPW work on compact interlanguage links [17:54:27] #link http://niharika29.roon.io/ [17:54:49] Thanks arrbee. [17:55:25] I'm also really happy to see the good work from Niharika [17:55:42] BPositive: Thats a good thought. :) [17:56:42] We have just under 4 minutes more on this channel [17:57:09] You can also try the beta feature at beta-wiki. One good page to do so is: http://en.wikipedia.beta.wmflabs.org/wiki/Francisco_Goya [17:57:30] (you need to enable the feature from the top-right beta link once you log-in) [17:57:46] A bit off topic but the Languages team here is looking for someone to join the fun: http://hire.jobvite.com/CompanyJobs/Careers.aspx?c=qSa9VfwQ&cs=9UL9Vfwt&page=Job%20Description&j=oH3gXfwH [17:57:52] * arrbee realises she has been neglecting the #info tag today *sigh* [17:58:13] Thanks circeberman :) [17:58:15] And you can drop your comments here: https://www.mediawiki.org/wiki/Talk:Universal_Language_Selector/Design/Interlanguage_links [17:58:18] #link http://hire.jobvite.com/CompanyJobs/Careers.aspx?c=qSa9VfwQ&cs=9UL9Vfwt&page=Job%20Description&j=oH3gXfwH [17:58:41] Thanks Niharika [17:59:15] I would like all the team members to go through my proposal and provide some feedback on the discussion page [17:59:49] BPositive: kondi : and if there are more people lurking here today and are planning to look at the internationalization projects for GSoC or OPW: We are on #mediawiki-i18n (Freenode) most of the time [18:00:09] and you can also reach us through the mediawiki-i18n mailing list [18:00:47] our team is spread out all over the world and we may not always be looking at IRC messags, but we will surely reply your mails. So do write to us if you have questions. [18:01:06] We will have to wrap up now. [18:01:15] Thanks everyone who came by today [18:01:29] and for the lively discussions [18:01:45] #info Our next office hour would be on 9 April 2014 [18:01:46] Bye [18:01:58] Our mailing list is mediawiki-i18n@lists.wikimedia.org and IRC channel is #mediawiki-i18n [18:02:02] bye [18:02:10] Language Engineering office hours are held every 2nd Wednesday at 1700 UTC [18:02:16] Thanks everyone [18:02:22] thanks Runa [18:02:22] #endmeeting [18:02:22] Meeting ended Wed Mar 12 18:02:22 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [18:02:22] Minutes: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-17.00.html [18:02:22] Minutes (text): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-17.00.txt [18:02:22] Minutes (wiki): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-17.00.wiki [18:02:23] Log: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-17.00.log.html [18:54:09] who is the best person to talk to about office.m.wikimedia.org - seems to be a config problem there on mobile site [18:54:51] ^ James_F any ideas? [18:56:23] jdlrobson: Ask in -operations? [18:56:43] oh wait it's all public [18:56:44] sweet [20:11:36] https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12 here in about 50 minutes [20:51:21] hi [20:51:36] Hi Newyorkadam [20:51:47] sup [20:51:47] In about 10 minutes in here we'll be discussing some RFCs https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12 [20:57:42] 3 mins [20:59:02] brb coffee [21:00:26] OK! [21:00:27] #startmeeting RFC review 12 March 2014 Channel is logged and publicly posted (DO NOT REMOVE THIS NOTE). https://meta.wikimedia.org/wiki/IRC_office_hours [21:00:27] Meeting started Wed Mar 12 21:00:27 2014 UTC and is due to finish in 60 minutes. The chair is sumanah. Information about MeetBot at http://wiki.debian.org/MeetBot. [21:00:28] Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. [21:00:28] The meeting name has been set to 'rfc_review_12_march_2014_channel_is_logged_and_publicly_posted__do_not_remove_this_note___https___meta_wikimedia_org_wiki_irc_office_hours' [21:00:38] #chair sumanah brion TimStarling [21:00:38] Current chairs: TimStarling brion sumanah [21:00:44] #link: https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12 [21:00:49] #link https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12 [21:01:01] #info Today we're covering four RfCs in 30 minutes because the discussions can be pretty quick: [21:01:08] Configuration (database) RfCs: original, RFC 2, and JSON onwiki. Shall we ask authors to consolidate by a certain date? [21:01:08] URL shortener (and URL Shortener Service, probably to be consolidated). Do we have the implementation details Tim wanted? [21:01:08] Assert. Any particular enthusiasm or next steps here? [21:01:08] Linker refactor. Any initial comments? [21:01:42] #topic Configuration (database) RfCs | Channel is logged and publicly posted (DO NOT REMOVE THIS NOTE). https://meta.wikimedia.org/wiki/IRC_office_hours [21:01:49] ok, that's overkill :-) [21:02:00] #link https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database The 2010 proposal, by Brion Vibber and Chad Horohoe, which we sort of decided to abandon in November [21:02:00] #link https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database_2 The 2013 proposal, by Kunal Mehta and Ryan Schmidt [21:02:17] We have talked about these topics in several past discussions: [21:02:22] #link https://www.mediawiki.org/wiki/Architecture_meetings/Wikimania_2013#Configuration_database summer 2013 [21:02:28] #link https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-11-06/Log#Configuration_database November 6, 2013 "current RFC probably abandoned, legoktm to file new RFC" [21:02:37] #link https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-11-06/Notes#Configuration_database summary of Nov 6 discussion [21:02:37] #link https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2013-11-20 "ACTION: legoktm and other interested devs to develop requirements list on wiki" from Nov 20 2013 [21:02:50] #link https://www.mediawiki.org/wiki/Talk:Architecture_Summit_2014/Configuration January Architecture Summit discussion - "Basic hygiene of taking what's already being used (JSON configuration like EventLogging, Zero, and UploadWizard campaigns) and separating into separate extension or integrating into Core." agreed [21:02:50] #link https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-02-05 Feb 5 discussion - decided "maybe consolidate the 3 potential RFCs into 1, maybe with 3 sections -- interface, backend, frontend" [21:02:50] #link https://gerrit.wikimedia.org/r/#/c/109850/ now needs review [21:02:54] i like the assert proposal; it's simple, straightforward, and has clear use benefits and not much downside [21:03:11] brion: cool, I'll ask you to repeat that in a few minutes :-) [21:03:27] :D [21:03:40] ok, so brion & TimStarling I sort of want you to #agree on a few things or tell me if it's a bad idea [21:03:48] It seems the Config RFCs are primarily stuck on https://gerrit.wikimedia.org/r/109850 [21:03:50] #idea Per https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Configuration_database_2#Title_.28currently:_.22RFC.2FConfiguration_database_2.22.29 rename the second proposal to be more specific and less confusing - are we agreed to do this? [21:04:11] yes +1 [21:04:30] yes [21:04:43] * hexmode looks at the commit [21:05:40] Unfortunately the Config class interface is far from being fully thought out, as Daniel Kinzler has pointed out [21:05:54] yeah, it looks like Daniel Kinzler has an open question on https://gerrit.wikimedia.org/r/#/c/109850/ - legoktm do you have any particular thoughts you wanna share? [21:06:11] I don't think you really need my approval to rename an RFC, but ok [21:06:28] The problem is that there needs to be some sort of routing, i.e., a way to fetch some config variables from one backend and others from another. [21:06:34] TimStarling: approval no, but if you thought it was a bad idea I'd want to know. ok :) [21:06:46] sumanah: legoktm might be unavailable writing exams atm (he mentioned midterms 'in a few hours' about an hour or so ago) [21:06:47] But in the current interface the Config class *is* the backend [21:06:55] #agreed Per https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Configuration_database_2#Title_.28currently:_.22RFC.2FConfiguration_database_2.22.29 rename the second proposal to be more specific and less confusing [21:07:18] #idea from the Feb 5 meeting: "maybe consolidate the 3 potential RFCs into 1, maybe with 3 sections -- interface, backend, frontend" - do we still think this is a good idea? [21:07:29] +1 [21:07:35] #link https://www.mediawiki.org/wiki/Requests_for_comment/Json_Config_pages_in_wiki I think - I'm not clear on what the "three RFCs" are otherwise [21:08:16] Yes, IIRC from the architecture summit that was the third option [21:09:02] OK. Should we assign that as an action to somebody? [21:10:25] it sounds like once we do that we can mark https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database as abandoned -- unless we want to mark it abandoned anyway right away [21:11:23] I'll mark it as abandoned [21:11:46] #action TimStarling will mark the 2010 proposal https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database as abandoned [21:12:31] it sounds like we don't have particular "yes we ought to do this soooon" on the tripartite thing right now, so I suggest we move on to the next topic [21:13:06] (we only have 30 min total today) [21:13:26] #topic URL shortener | Channel is logged and publicly posted (DO NOT REMOVE THIS NOTE). https://meta.wikimedia.org/wiki/IRC_office_hours [21:13:26] #link https://www.mediawiki.org/wiki/Talk:Requests_for_comment/URL_shortener [21:13:26] #link https://www.mediawiki.org/wiki/Talk:Requests_for_comment/URL_shortener#IRC_meeting_2013-09-24 Our RFC meeting from a few months ago [21:13:26] #info In September we had an IRC meeting about this where we agreed that Tim would update the RFC with his implementation suggestion https://www.mediawiki.org/wiki/Talk:Requests_for_comment/URL_shortener#Tim.27s_implementation_suggestion and then we'd ask the mailing list for more discussion. Tim, would you like to do that, or delegate it maybe to someone? [21:14:19] #link https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener_service_for_Wikimedia One more logistical detail: Are we agreed to consolidate this proposal into the "URL shortener" one? [21:14:44] YuviPanda: you might have opinions on this :-) [21:15:14] sumanah: :) I think we definitely should merge them. [21:15:43] cool, YuviPanda are you willing to take that on? [21:16:16] sumanah: sadly not atm :( I can help with discussion and maybe final implementation, though. Can't promise to lead it right now [21:16:55] YuviPanda: If I give it a go, can I show you a draft of the merged proposal so you can tell me what I got wrong? :-) [21:17:08] sumanah: yes, that I can do! :) [21:17:11] OK! [21:17:36] #action sumanah to consolidate https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener_service_for_Wikimedia into https://www.mediawiki.org/wiki/Talk:Requests_for_comment/URL_shortener by March 26 - asking Yuvi for review help [21:17:52] sumanah: ty! [21:18:22] TimStarling: if you want, you can delegate the "incorporate Tim's implementation suggestions into the RfC" task to me as well, as long as you're willing to review my work & give me feedback [21:18:31] I think it's a question for the proposer (white cat) [21:18:43] (or whatever he calls himself in english now) [21:18:59] ok [21:18:59] i.e. are his requirements satisfied by the other proposal? [21:19:29] #action sumanah to contact とある白い猫 to check whether proposer's requirements are satisfied by other proposal [21:20:35] TimStarling: ok, that's about the merger of the 2 proposals together. What about the followup from the last meeting, about putting your implementation suggestions into https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener itself? [21:21:28] sure, you can do that if you like [21:21:59] #action In September we had an IRC meeting about this where we agreed that Tim would update the RFC with his implementation suggestion https://www.mediawiki.org/wiki/Talk:Requests_for_comment/URL_shortener#Tim.27s_implementation_suggestion and then we'd ask the mailing list for more discussion. sumanah to do this in March [21:22:05] ok, next topic [21:22:06] #topic Assert | Channel is logged and publicly posted (DO NOT REMOVE THIS NOTE). https://meta.wikimedia.org/wiki/IRC_office_hours [21:22:06] #link https://www.mediawiki.org/wiki/Requests_for_comment/Assert Daniel Kinzler's proposal, last modified in January [21:22:20] #info i like the assert proposal; it's simple, straightforward, and has clear use benefits and not much downside [21:22:30] Are other people eager for this? [21:22:50] I mean, it looks like it just needs to be pasted into Gerrit [21:23:11] Looks pretty good as a contract programming implementation for PHP [21:23:13] basically, this is kind of a "yay" that I will paste into the RfC talk page :-) to get Daniel to do so [21:23:36] :D [21:23:47] Is the RFC owner around? (Duesentrieb) [21:23:51] we can continue discussion at the RfC talk page; I just thought people might have missed this one since it isn't as huge [21:24:01] parent5446: no, I don't see him in channel right now - it's late in Berlin [21:24:06] ok, next thing [21:24:09] #topic Linker refactor | Channel is logged and publicly posted (DO NOT REMOVE THIS NOTE). https://meta.wikimedia.org/wiki/IRC_office_hours [21:24:10] #link https://www.mediawiki.org/wiki/Requests_for_comment/Linker_refactor Katie Filbert's proposal, last updated in December [21:24:10] Are people eager for this? [21:24:18] i am :D [21:24:36] it has ZERO comments on the talk page! A little "go for it" would be nice :-) [21:24:38] oh wait lemme read that one first [21:24:40] hahahahha [21:24:56] This is very closely related to TitleValue [21:25:08] Since TitleValue proposes deprecating linker in favor of a service [21:25:28] yeah, should be on top of TitleValue [21:25:30] oh god yes, Linker needs re-refactoring [21:25:54] Actually, reading this RFC, it sounds less Linker-specific and more "get rid of static classes" in general [21:25:55] this predates the TitleValue implementation, right? [21:26:10] well, that's part of what TitleValue is doing [21:26:42] i'm broadly in favor, would have to dive in and do some poking at it to comment more in detail since Linker's last refactor i don't recall what's what [21:26:58] aude: ^ [21:27:21] i.e. TitleValue is getting rid of static methods [21:28:09] e.g. Title::newFromText() -> $titleParser->parseTitle() [21:28:29] Should the RfC author maybe revise this to clarify the dependency chain with the TitleValue RfC? [21:28:54] Linker::link() -> $renderer->renderHtmlLink() [21:29:25] yes, or she can collaborate with Daniel generally [21:29:29] fair [21:29:42] flow time [21:29:44] #action aude to collaborate with Daniel, figure out Linker refactor thing [21:29:46] #topic next meetings [21:29:46] #link https://www.mediawiki.org/wiki/Architecture_meetings Upcoming meetings [21:29:46] RFC review 2014-03-19 (IRC) - MVC Framework and structured logging [21:29:46] RFC review 2014-03-26 (also IRC) - allow styling in templates, + 1 more, you can suggest one to cover [21:29:51] #endmeeting [21:29:51] Meeting ended Wed Mar 12 21:29:51 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) [21:29:51] Minutes: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-21.00.html [21:29:51] Minutes (text): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-21.00.txt [21:29:51] Minutes (wiki): https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-21.00.wiki [21:29:52] Log: https://tools.wmflabs.org/meetbot/wikimedia-office/2014/wikimedia-office.2014-03-12-21.00.log.html [21:29:57] whee! [21:30:01] Thanks folks [21:30:05] hope that was useful to y'all [21:30:15] * parent5446 goes back to code review. [21:30:15] yes thanks :D [21:38:46] https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12 now has notes + log.