Nov 15 2018
Hi, sorry everyone. I was busy organizing hackathon and also preparing for a MediaWiki workshop. @Charlie_WMDE thanks a lot for sharing the mockup. I will work on it and change the UI accordingly.
Sep 26 2018
Hi, did anyone test the latest patch? :)
HacktoberFest is arriving. Potential opportunity to bring newcomers to Wikimedia Tech. :)
Sep 23 2018
Hi @Lea_WMDE. Thank you for your feedback. Based on your suggestions, I have amended my current patch and updated it taking into account different parameters (days, months etc). You can check the patch 2 here: Patch 2.
Sep 20 2018
So, I thought of a different approach for this task which creates a better UI
Aug 30 2018
Sure! @Charlie_WMDE. However, you can download the patch and test it locally and let me know how can we make it better.
Aug 29 2018
Hi @Charlie_WMDE, I tried but the tooltip doesn't automatically show on render. I will upload a [WIP] patch to show a basic structure.
Aug 17 2018
This tooltip will not be triggered on hover. It will be shown as a "tooltip" permanently. It will not be triggered on an event such as hover etc.
Instead of showing the text above the marker, what if we show it as a tooltip?
Aug 15 2018
Aug 13 2018
Aug 9 2018
Proposed solution that I have think of: Keep the height intact (same) for all changes having < 100 bytes (both positive and negative). Let the logarithmic algorithm calculate the height if it's equal or greater than 100 bytes.
I am interested in working on this task.
I was reading and understanding the problem statement. I have a question. Are we showing the labels on the basis of a pre-defined time frame (say, a month) or is it based on the number of contributions? From what I understand, it is based on the number of contributions within a particular time frame. Well, this will make it a much wider problem because there are articles that have more than 30 changes in a particular day. Check this for example: Revision History of Helicopter 66
So, we need to take into account the number of contributions within a time frame and that time frame can be anything. It can be a day, a couple of days, a week, a month, few months, an year.
Is there something that I am missing?
Please correct me if I am wrong somewhere.
Jul 20 2018
I realize where I was wrong. Thank you! I think this ticket can be closed.
Okay, so now a simple query like this:
Jul 8 2018
Jul 7 2018
Can't reproduce it on Firefox 60 and Chrome 67.
May 13 2018
Interesting thought! I have seen many newcomers coming from platforms like you mentioned above and stay and contribute for a long time. Many newcomers visit these sites in order to kickstart their open-source development. If few of the beginner bugs get posted on these websites, we can get a lot of new contributors. The bugs that we usually provide to Google Code-In students, would be a decent way to start, in my opinion. :)
Sep 23 2017
Sorry for the delay. But here is the link to my blog post: https://mywikieducation.blogspot.in/2017/09/wikimania-hackathon-2017.html
Aug 17 2017
Alright, you were correct. It was my bad. I just opened the same link twice. Apologies for the same.
Well, this ::after pseudo-element is causing the trouble. The ::after pseudo-element is not used here.
I will take care of it in future. Thank you, @Aklapper :)
Alright, @D3r1ck01 I need to dig too for the information. :)
I think this has to do something with https://gerrit.wikimedia.org/r/#/c/363264/ if it has happened all of a sudden. Can you please tell me your ISP and country from where you tried to access the image?
Can't reproduce it on Firefox 54 and Chrome 59.
@Volker_E Yes, I mean vertically. Here is the screenshot:
I get the 200 status on Chrome and Firefox. Can you provide some more information?
Aug 12 2017
Aug 11 2017
Jul 12 2017
Issue reproduced on Opera 46.
Jul 7 2017
It is specifically mentioned here (https://github.com/wikimedia/mediawiki-extensions-PageAssessments/blob/68c5a3f7921abe9f923b85d8129bd3709dbd76ac/api/ApiQueryPageAssessments.php#L29) that projects will be displayed always one more than the limit. Should we change it?
Jun 22 2017
May 18 2017
I found the deprecated MySQL extension functions here as well: GitHub
May 10 2017
I tried on my Android version 6.0 running Amigo OS 3.2.0 using Google Chrome 58.0.3029.83 and wasn't able to reproduce either. Please mention the version of Android and browser.
Apr 30 2017
I'd like to volunteer.
Mar 18 2017
Patch set 3 uploaded. Link: https://gerrit.wikimedia.org/r/#/c/343024
Mar 17 2017
Patch set 2 uploaded. Link: https://gerrit.wikimedia.org/r/#/c/343024
Mar 16 2017
I have been noticing it from my last two tasks. I have to explicitly mention the gerrit link here even after tagging the correct Phab ticket in the commit message.
@phuedx: I am is to blame. I wrote the comment mentioning the gerrit link and forgot to submit it. I just checked it now. I apologize for it.
Mar 15 2017
I would like to do the task. :)
Aug 21 2016
So, if we add a code that handles this exception, would it solve the problem? Or is there any other way to do it?
Aug 20 2016
at the top and setting the $_SESSION variable should solve this problem.
Aug 7 2016
Jul 29 2016
Dec 22 2015
POSSIBLE CHANGES IN "BetaFeatures" EXTENSION
• Probably, we will have to make a new module or modify an existing module for enabling the features in mobile and have to define the 'targets'.
• 'targets' must be set to mobile.
• MobileFrontend's "Minerva" skin might prove handy.