[08:24:28] Niharika: For contributing to slimapp, do I need to clone the gerrit repository and submit patches using Gerrit from Vagrant VM? [08:25:20] Neha16: Let me check. [08:26:21] Neha16: Yeah, you'd need to do that. [08:26:42] Neha16: Let me know if there's some confusion about using vagrant. I can probably help with that. [08:27:12] Niharika: Ok, Thanks a lot. The patch D894 still has problems? [08:27:13] D894: Updating iegreview codebase to use wikimedia slimapp library - https://phabricator.wikimedia.org/D894 [08:28:07] Neha16: Nope, I'm gonna test it now. Diffusion doesn't let one see individual diffs unlike Gerrit so I was confused about that for a bit. [08:28:49] Niharika: Great. Let me know if there are any other corrections :) [08:29:04] Will do. [08:37:45] andre__: Around? I have a GCI task idea and wanted to run it by you. We don't seem to have a catalog of MediaWiki extensions anywhere. Wikiapiary has them but that website is very frequently down and not maintained. I think it'd be a good idea to just have a big table on mw.org (or elsewhere) that contains the URL, name, description, maintenance status for extensions. That'd make those extensions searchable which is currently [08:37:45] very lacking. [08:39:24] It's not a very good way to browse extensions but better than nothing. [11:28:17] Niharika: Hej! I like the idea but I don't think that would be a GCI task at this stage... [11:28:25] Because we'd create yet another place where we have a list to manually update, and that specific aspect bothers me :-/ [11:28:50] there's already the infoboxes on each mw:Extension:Foo page, and pages like mw:Developers/Maintainers [11:30:19] andre__: Yeah but there's no definite way to search for extensions. I have to resort to doing a google search when looking for extensions (so do other people). I'm not sure what's a better way. [11:30:51] I didn't mean for this to be a single GCI task either. It'd involve multiple students adding 10-15 extensions to the list each. [11:30:56] Category:Extensions or such on mw.org? :-/ Though there are already billions of them [11:31:43] andre__: No, like, I want an extension to do with captcha or to do with security or search. So I'd like to search the extension descriptions rather than titles. [11:31:45] My take is that we would create yet another manual list, which might get outdated at some point. So I'd doubt that having this manually would be helpful in the long run [11:31:52] I agree. [11:32:05] I just wish there was *something*. [11:32:05] in theory that's what the Categories on mw.org are for. In theory... [11:32:14] Yeah, I strongly agree with that :( [11:32:33] There is a big problem. I just don't know yet how to solve it. [11:33:13] There have been a couple of GSoC projects about this in the past, I think. I don't know what came out of them. [11:33:49] Been even wondering once if I can / should somehow (API? but Infoboxes...? web scraping?) get a list of pages under mw:Extension:* and somehow extract status, categories, etc. [11:34:09] IMHO what's in the infobox should be in some JSON format or such, but that's just me dreaming aloud [11:35:09] Yeah. If the infoboxes could be scraped, that would get us halfway to the solution. [11:36:39] 'xactly [11:37:19] I think we need to brainstorm a bit more :-/ but not the first time I'm also thinking about this problem [11:37:21] A fancy toolforge tool for this could work nicely. [11:37:30] Yeah. [12:54:48] IMO the problem is best solved by supporting / yelling at WikiApairy [12:55:25] iirc, and my mind is a bit hazy about this, there was a gsoc project about it last year [13:00:47] Hi guys [13:01:46] can someone help me with an error I am getting while trying to install an extension into my vagrant environment... [13:02:39] himanshuc3, unlikely... please try #wikimedia-dev [13:02:48] ok [13:02:56] that's where more developers are [13:03:04] himanshuc3, thanks. and please don't ask to ask. :) [20:09:45] andre__: have we published any l10n tasks? https://codein.withgoogle.com/dashboard/tasks/6066959961554944/ is a huggle l10n which wasnt published because it was assumed they were ineligible again, and is the only l10n task I could find. [20:11:26] jayvdb, we have not. I talked with Petr about "Translate Huggle to French" but that one would not be suitable because it could be done by using machines [20:11:55] if we find L10N tasks that aren't about throwing strings into Google Translate I'd very much welcome them :) [20:13:25] ya, maybe add "language not supported by Google Translate" to the task ? ;-) [20:14:04] + Yandex, etc [20:14:43] or provide a shortlist of languages we know are not in any MT engine [20:16:13] Heh... that still won't solve the problem that I could commit rubberish strings that noone can verify? [20:16:53] indeed; we need mentors from obscure languages :/ [20:18:22] really bizarre that Wikimedia has difficulty getting mentors from our smaller communities who would benefit the most from having a bunch of students doing all sorts of lovely stuff for them [20:20:16] (as much as I hate them...) do we have a massmessage about Google Code-in ? if not, maybe we could create one for next year, with example tasks that are 'fix my wiki' type tasks, i.e. improving templates, lua, etc. [21:03:28] jayvdb, I spammed a bunch of on-wiki pages, see https://phabricator.wikimedia.org/T178288 , but the response rate has always been about one person per year. [21:03:44] Hmm, mass message... I've never tried that. Worth a line in https://www.mediawiki.org/wiki/Google_Code-in/Admins ? [21:49:08] andre__: it didnt help that tech ambassadors program kinda redesigned how they did stuff right around when the call of mentors initally occoured [21:52:05] oh, didnt know [21:54:18] Yeah, thats when they decided to cleanup, and make it so they had a true list of active tech ambassadors (I am a enwiki tech ambassador), and for what project they other things i cant remember off the top of my head but it was a pretty decent and needed redesign [23:21:47] andre__: translators-l would be the obvious place to write to [23:22:01] Hmm, thanks. Noted. [23:22:31] and don't mention GCI, that just scares people away, ask them instead if they are willing to review translations done by students :) [23:23:15] heh