Jun 29 2018
Apr 25 2018
Thank you so much for this opportunity! I'm very excited to work on this tool :).
Mar 27 2018
Oh wait, we do store the results, right? Not everything that comes back from PetScan, but the query returns articles which we'd be putting in our database so we can track their statuses etc. We probably also want to do that because of how slow PetScan can be -- we don't want people waiting 1min to open a worklist while we run a query in the server.
Ah yes, we're storing the results. I went a bit wrong in the explanation. The process of updating the results has been added to the proposal.
Mar 26 2018
Cool, this looks great and is just about ready for final submission. I've made a few more comments below but none are blocking to the proposal -- I'm convinced you understand the problem and have a plan to solve it :)
Thanks a lot! :)
Mar 25 2018
I'd like to see a bit more detail on how you'd design and implement some of the things you've mentioned. Do let me know if you have any questions of course.
I've added more detail in the proposal itself. Kindly look through it. If it still lacks some detail, let me know.
Mar 23 2018
Hi @Surlycyborg ,
I've made my project proposal , containing timeline, detailed solution to the problem and the database schema for my solution .
Link to proposal : Project Proposal
Your reviews on this would be very helpful.
Mar 22 2018
I am Megha Sharma, a final year undergraduate student studying Computer Science in PEC University of Technology, India.
I'm interested in this project and want to contribute in it. I know I am very late but I just finished my Outreachy Round 15 internship with Wikimedia. As my project was challenging and big, so it got a bit extended.
But since I did my Outreachy internship with Wikimedia only, I am quite well versed with Toolforge, MediaWiki APIs, OAuth, Database and Git. So, I can quickly get started.
Also, this is the link of the tool (which is in its final stages) and, this for the git repository for the work that I did for Wikimedia in Outreachy Round-15.
Mar 6 2018
Feb 18 2018
Feb 9 2018
Feb 8 2018
Feb 4 2018
Feb 3 2018
Jan 28 2018
Jan 17 2018
Jan 5 2018
Dec 23 2017
Dec 11 2017
Oct 31 2017
I've made changes to the code of Task-4 according to your comments.
Oct 30 2017
Thanks for the feedback. I got the point and agree with it too. Hence, I’ve made this tool which shows the contributions of a user in terms of no. of pages edited and created in the present year similar to Github’s contribution timeline.
Oct 25 2017
Since I have some time left, I thought to pick up some module from my timeline. It'll help me if I'll get selected. I've decided to start with the graphs component. For now, I am aiming to represent the pages created and pages edited by a user over time. This will act as POC for the graphs that I had shown in the mockups in MicroTask-3.
I wanted your feedback on the same.
Also, review for the 1st revision of microtask 2 is pending. Can you please go through it so that I can close it in time?
Oct 23 2017
I don't think it's useful to that before working on the frontend. An MVP doesn't necessarily have to look pretty, but it shouldn't look like a debug >dump either - how well something looks will influence users' opinions of it, even if they are asked to disregard it. Lack of design makes it hard to >quickly understand the shape of the information presented, etc.
If you want to release the MVP by the mid-term evaluation point, you should pull some features from it (e.g. badges).
Oct 20 2017
I've completed my project proposal.
Oct 18 2017
Oct 14 2017
Oct 9 2017
Oct 7 2017
Oct 4 2017
Oct 2 2017
Sep 28 2017
I am final year undergraduate student studying in PEC University of Technology, India.
A week back I came to know about Outreachy and found the concept very interesting. Since then, I've been searching for some interesting projects and found this one the best out of the lot.
I've a knack for development but I am relatively new to Open Source, hence I hope it will be a great learning experience.