Sun, Nov 19
There's a column on the Google-Code-in-2017 board (Imported in GCI site). However, the communication for task/implementation related stuff should be done within phabricator (so anyone can follow it), and only GCI related things should be done on the GCI site (it's possible to do all of the communication in the GCI site, though). So, I wouldn't close the task once it is imported into GCI, but it's up to you :)
@Petrb Was it intentional that you closed this task as resolved? It could be confusing for a GCI student to click on the "external URL" link in the GCI platform and then seeing an already resolved task :/
Sat, Nov 18
For GCI students: What is the acceptance criteria, when does a student now, when the task is finished? :) Is there any material which could help them to solve this task?
Was already imported as: https://codein.withgoogle.com/dashboard/tasks/4880480144982016/
Thu, Nov 16
Thanks for the info @Nikerabbit! :)
I also updated the GCI task :)
Wed, Nov 15
@D3r1ck01 That looks ok to me, thanks for eacting so fast! :) Do you think that this is doable by one student or should one student convert, let's say, 5 strings to finish the task and another student can do the same to finish the task, two (so having multiple instances of the task)?
@Sanjay311999 You need to give me the address of your Google account so I can invite you to be a mentor for Wikimedia in the GCI platform. You can either give me a link where your address is already publicly visible, or simply sent it to my gerrit e-mail-address: email@example.com
Tue, Nov 14
I'll mentor this task :)
Imported as: https://codein.withgoogle.com/dashboard/tasks/5720874852286464/
@D3r1ck01 Do you've an answer for @Nemo_bis' comment? And could you please add some info to the task description to give a possible student some more info about what they need to do and how they can find that out themself (e.g. some links for getting help in 18n topics, documentation and so on)?
@D3r1ck01 It might be reasonable to have a bit more informative description for the task: What does the student need to change and how? Is there any information material they can use to find that out? Where do they get help or documentation on making things translateable? :)
I'll mentor this task! :)
Imported as: https://codein.withgoogle.com/dashboard/tasks/5655660068864000/
I'll mentor this task :)
Imported as: https://codein.withgoogle.com/dashboard/tasks/6254785994948608/
Hmm, screenshots for a console application where the (copyable) console output seems to be pasted as text already? Is this really reasonable? :)
First three set of tasks imported as:
@Dbrant: For GCI it would be good to know, what the acceptance criteria for this task is? When do you think, a student fulfilled the task? Where should the layouts, found by the student, should be documented? Here in the task as a comment? Can you provide an abstract "How to" for the students to find out, how they know, if a layout "look andbehave identically to the old layout"? Thanks for your added information! :)
@Prtksxna The question is, if this task is doable for a GCI student, which means, that it shouldn't take longer than 2-3 hours for an experienced developer and 2-3 days for a beginner (I don't expect this task to be a beginner task, right?)?
If it's ok with you, @srishakatux, I would like to co-mentor this task :)
Imported into GCI: https://codein.withgoogle.com/dashboard/tasks/5649160172732416/
@Prtksxna I think this is quite a big task on it's own. What do you think on creating some subtasks for specific elements of inputbox and using that subtasks for creating GCI tasks out of it? That could be easier to overlook for a student (which should not be overwhelmed by to big tasks)? :)
Mon, Nov 13
Sat, Nov 4
Thu, Nov 2
Sun, Oct 29
*wohoo* :) Added you as a mentor to this task!
Sat, Oct 28
@rosalieper I sent the invitation to the second e-mail mentioned on your MediaWiki user profile again :)
@BBlack Nevertheless: Thanks for your time and work you put into this! :)
Just from my experience: The npm team clearly states (in their documentation) that the file "is intended to be committed into source repositories". However, for a customer I worked for, commiting the package-lock.json file to git created several problems with their CI infrastructure (which had no direct internet access, though, just through a proxy). This could be a very specific problem, which does not apply to Wikimedia infrastructure, however, I really don't see a benefit for us when commiting the file (like I do not see a benefit with composer's lock), as the CI should always use the newest compatible version as specified in package.json when testing a commit. Package-lock.json prevents it (that's the purpose).
The pro argument is (like you said already): all the exclusions can be found in one file (as long as it integrates with grunt). That would mean, that it would be easier to see, what files will be checked with the tool (you do not need to open Gruntfile.js to see what is _included_ and then look for a specialized file in the projects root to see what is _excluded_).
@Nikerabbit Great, thanks for explanation and for the missing add, makes much more sense now :)
Thu, Oct 26
I changed some things, added a description (it would be great if someone could add a note _why_ we want to do that :)) and added some links. One thing I don't get (probably there's omething missing?) is the first task, especially what do you mean with that part:
and keyAlgorithm: legacy if it is not specified
@Ladsgroup Can you elaborate on what the task for a possible GCI student would be? What should they create/change exactly, what do you want to see to accept this task :)
That could be a good GCI task, added as:
https://codein.withgoogle.com/dashboard/tasks/4847880890220544/ (7 days)
Oct 19 2017
That sounds like a really good idea, thanks for bringing this up, @Tgr. Without looking into it deeper, I'll create some subtasks to split the work down and prevent "massive" changes in gerrit. I'll also start working on that :)
ähm, I think so, thanks for bringing this back to me, haven't seen, that it is still open :)
Oct 13 2017
Oct 8 2017
Oct 4 2017
Sep 26 2017
Sep 21 2017
Sep 19 2017
Sep 17 2017
:D I'll change them to read-only again.
https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/WikidataEntitySuggester is not listed above (in the Gerrit project list) :P Re-activated it. I also re-activated all others in gerrit.
Ah damn :D Sorry, just saw my change merged, and I thought I uploaded one to change NewPages, too (as I saw my example image) :P Thanks for pointing to this @Ladsgroup :D
To be honest: My vision is, that there's an on-wiki way to configure MediaWiki ("configure" -> change configuration options), like a special page providing that functionality (where extension and core settings can be viewed and changed by recognized groups (read: groups with a special permission).
@MarcoAurelio I changed the repos back to "Active", so you can add changes to them now (I'm not doing it, as I don't have time now, and I don't see a reason doing it :]). Please give me a hint, when you're finished, so I can mark them as read-only again :)
See also: https://gerrit.wikimedia.org/r/#/c/18201/ (removed from WMF wikis)