Email sent to mentors regarding the above tasks, waiting for a reply.
May 7 2020
May 6 2020
Thanks a lot.
May 5 2020
May 1 2020
@Aklapper Ahhh, missed that, looks good then, sorry and thanks a lot.
Apr 29 2020
Seems like they don't close tasks till the patch(s) is/are deployed.
Apr 28 2020
I'm new here ^^
You can find more help here: https://www.mediawiki.org/wiki/Phabricator/Project_management#Assigning_tasks.
Apr 27 2020
Apr 26 2020
A possible addition to the list of topics are some small stuff (not as complex as making a bot or even a tool) / task like T251050. In this particular case, it's hard to expect small (to medium) size wikis have someone who's comfortable with gerrit or even code in general.
Apr 21 2020
You're supposed to use the action wbgetentities to get structured data.
For example: https://commons.wikimedia.org/wiki/Special:ApiSandbox#action=wbgetentities&format=json&sites=commonswiki&titles=File%3ACommons_logo.svg
Apr 16 2020
Apr 5 2020
Apr 1 2020
Mar 31 2020
Mar 30 2020
Mar 29 2020
Mar 26 2020
- Does a user need to be authorised to perform the above verification?
Mar 25 2020
Mar 24 2020
@Gabrielchl My suggestion would be to think out a descriptive name which could be used for the tool and explain why you think this name could be used. Also, it would be nice to explain more the features which you think would be nice to have.
Mar 20 2020
I came across this solution before I post this comment but for some reason, it did not work for me.
If possible, tell us what exactly did you try to fix it, if it still doesn't work 2nd try.
@AdhamKhatean, if you search on Google, you'll get answers, such as: https://www.mediawiki.org/wiki/Topic:Veh8l4gmryp07fzh
Mar 19 2020
Mar 18 2020
Mar 17 2020
Mar 16 2020
@Eugene233 would that be fine if I've got another idea, for example, looking for images with structure data from recent edits.
Because imagining what new user would prefer, I don't think most of them would use the tool with a specific category already in mind.
Mar 15 2020
Mar 14 2020
A problem with the above patch is that it doesn't work for Wiki Love campaigns, as they require specific category information of the images.
I've considered fetching the info for each image and store them to the database, however it would take a lot of time. @NavinoEvans, any suggestions?
Fixing the current issues in the above patch:
- # of images got is far less than what's expected
(Update: fixed, had to handle continue argument with api call)
- API query max number of pageids to provide at a time is 50, figuring out what's the best way to avoid hitting the max.
(Update: fixed, instead of translating all pageids to image name at once, we'll have participation manager do it when the image is loaded)
Mar 13 2020
@Gabrielchl Hi! Thanks for your proposal. I hope that you are already in touch with potential mentors of this project as it would be nice if you could get early feedback from them. If for some reason you are not able to reach out to them, please let me know!
With the above patch, the tool now:
- Uses images in db to calculate # of images
- Uses images in db to show in participation page
- Allow image id specification in participation page
- Can new test cases for new route and util functions
(I'll work on them after the above patch gets approved :) )
@Sanyam.wikime, please also include instructions on how to reproduce the bug.
Mar 12 2020
For point two what I meant is that The reviewer should have some special permissions or not ?
What do you mean by "The reviewer", reviewer of what? Do you mean gerrit patch reviewer? Or the task's owner? This GSoC task's mentor?
I am trying to run the Isa app but I get [Errno 2] No such file or directory: '/~Isa/isa/config.yaml'
That's definitely possible, will do. :)
The campaign page is far less enticing than the participation page.
Never thought about that, sorry about that.
Mar 11 2020
The above patch allows multilingual campaign name, if it's fine, i'll then extend it to cover short and long description.
The multilingual campaign name is stored as a json string. Older version of campaign names will still be supported (a.k.a. doesn't break the script).
It'll try to show the campaign name as the user's language, if not available, it'll try to show 'en', if also not available, it'll show it as the first possible language.