Page MenuHomePhabricator

Show new versions of files (and possibly separately description changes) made on WikimediaCommons on the Watchlist
Open, Stalled, LowPublic

Tokens
"Like" token, awarded by Liuxinyu970226."Like" token, awarded by D3r1ck01."Like" token, awarded by Poyekhali."Like" token, awarded by Checkingfax."Like" token, awarded by Fae."Like" token, awarded by Steinsplitter."Like" token, awarded by Ricordisamoa.
Assigned To
None
Authored By
Steinsplitter, Mar 1 2015

Description

Currently, an edit made on Wikidata is visible to users on other Wikis as well. To understand what this means, visit the RecentChanges page on meta-wiki. Observe the edits shown on this page with the letter "D"; it indicates that these edits were made on Wikidata. Now on every wiki, there is an option for the user to add pages to a watchlist that they can use to see changes made to wiki pages they have chosen to track. If you are on meta-wiki, you can see your watchlist here https://meta.wikimedia.org/wiki/Special:Watchlist. On MediaWiki replace [https://meta.wikimedia.org] in the previous URL with [http://mediawiki.org], on Wikipedia with [http://wikipedia.org], etc.

The goal of this project is to show new versions of files (and possibly also file description changes, with a separate rc_source and filtered separately) made on Wikimedia Commons on the Watchlist in a similar way it is currently possible for Wikidata as explained above. 

New versions of files (e.g. a crop, rotation, other change to the actual image/video) are much more relevant to Wikipedia than description edits (since they affect the content of the article). Thus, either it should only cover new versions, or new versions and file description changes should be separate, so you can opt into neither, one, or both. (However, a file description change could be relevant in allowing a better caption.)

See sample image below and try on all other wikis;

Steps;

  1. To view changes on any wiki, go to the Wiki and navigate to “Recent changes” then uncheck the “Wikidata” box so that changes on Wikidata related to that wiki will not be hidden. A sample link can be found here: https://meta.wikimedia.org/w/index.php?title=Special:RecentChanges&hideWikibase=0 (when hideWikibase=0, Wikidata edits will show but then hideWikibase=1, Wikidata edits will be hidden. Actually, it's hidden by default).
  1. Select any Wikidata entry for the recent change (after step 1) and add the entry to your watchlist. Then edit the item and check your watchlist on that wiki, you should see the change available on your watch list or if someone else edits the Wikidata entry, it will show on your watchlist as well.

Above are the two steps to reproduce the task (for Wikidata use case) and understand what is to be done for this project. The project will be to show edits made on Wikimedia Commons on the Watchlist (globally). For example: edits on transcluded files, etc.

T171027: "Read timeout is reached" DBQueryError when trying to load specific users' watchlists (with +1000 articles) on several wikis should be resolved before this is enabled in production.

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

As previously mentioned, this task is moved to 'Recheck in February 2016' as it doesn't have two mentors assigned to it as of today, October 23 - 2015. The project will be included in the discussion of next iteration of GSoC/Outreachy, and is excluded from #Outreachy-11. Potential candidates are discouraged from submitting proposals to this task for #Outreachy-11 as it lacks mentors in this round.

Restricted Application added a subscriber: JEumerus. · View Herald TranscriptFeb 11 2016, 11:45 AM
Sumit added a subscriber: Sumit.Feb 18 2016, 1:33 PM
NOTE: This task is a proposed project for Google-Summer-of-Code (2016) and Outreachy-Round-12 : GSoC 2016 and Outreachy round 12 is around the corner, and this task is listed as a Possible-Tech-Projects for the same. Projects listed for the internship programs should have a well-defined scope within the timeline of the event, minimum of two mentors, and should take about 2 weeks for a senior developer to complete. Interested in mentoring? Please add your details to the task description, if not done yet. Prospective interns should go through Life of a successful project doc to find out how to come up with a strong proposal for the same.
Legoktm updated the task description. (Show Details)Feb 18 2016, 5:29 PM
Fae awarded a token.Feb 27 2016, 1:26 PM
Fae added a subscriber: Fae.
Checkingfax added a subscriber: Checkingfax.
Poyekhali added a subscriber: Poyekhali.
Saylikarnik added a subscriber: Saylikarnik.EditedFeb 28 2016, 10:53 AM

Is this task eligible for Outreachy round 12? If yes, should I start working on my proposal? @Legoktm

I think we'll probably be able to find another mentor, so yeah. But in my opinion, having experience with the MediaWiki codebase and understanding the product that you will be implementing (and demonstrating that with patches) will be significantly more important than writing a nice proposal.

Saylikarnik added a comment.EditedFeb 29 2016, 2:40 AM

I have some experience with the MediaWiki codebase ,
https://phabricator.wikimedia.org/T121332 (Added screenshots for the monaco and example skins, involves use of wikimedia commons so maybe a bit related :P)
https://phabricator.wikimedia.org/T126530 (Reported the bug)
https://phabricator.wikimedia.org/T121281 (Working on this currently)

I'll start working on microtask T38859 as mentioned in the description..If there are any other microtasks that I need to do please let me know! @Legoktm

Qgil removed a subscriber: Qgil.Feb 29 2016, 8:48 AM
Sumit added a comment.Feb 29 2016, 4:09 PM

@Bawolff , this looks like a well scoped project, would you be willing to mentor it this year for GSoC/Outreachy ?

01tonythomas updated the task description. (Show Details)Mar 2 2016, 3:49 PM
Niharika removed a subscriber: Niharika.Mar 2 2016, 6:34 PM
Sumit added a comment.Mar 4 2016, 2:21 AM

It'd be great if we could have a co-mentor soon for this project :) @Legoktm lets us know if you know someone who could co-mentor. Moving to "Missing-mentors" for now.

@Legoktm I would like to work on this as my GSoC project if that's possible.

@Legoktm I am working on microtask T38859 and uploaded a patch.
Let me know if there are any other microtasks that I can do to get familiar with the codebase.

This comment was removed by Harjotsingh.
Sumit added a comment.Sep 11 2016, 4:58 PM

@Legoktm this looks like a well described project but one that didn't get through because of lack of a co-mentor. Would you be willing to mentor this if we have this one for the current round of Outreachy-13 internship?

Yes, however due to my time constraints this quarter, the intern must absolutely be already familiar with the relevant MediaWiki subsystems as I will have less time this quarter to do basic bootstrapping that I'm normally happy to do. And we can find such a person, I'll commit to finding a second mentor.

Sumit added a comment.Sep 11 2016, 9:45 PM

Yes, however due to my time constraints this quarter, the intern must absolutely be already familiar with the relevant MediaWiki subsystems as I will have less time this quarter to do basic bootstrapping that I'm normally happy to do. And we can find such a person, I'll commit to finding a second mentor.

Thanks for that ! :) Also, the requirement is perfectly fine. As I see only one outstanding microtask left, could you add one or two more, depending on the skill level you'd want to assess. That would be a good metric to see if the candidate satisfies the above requirements.
Featuring for Outreachy.

Legoktm updated the task description. (Show Details)Sep 14 2016, 10:32 PM

Is this project still missing a mentor?
Is there a common place you all meet periodically? I am interested in mentoring, and would love to introduce myself on the mail-list/IRC.

Sumit added a comment.Sep 19 2016, 3:57 PM

Is this project still missing a mentor?
Is there a common place you all meet periodically? I am interested in mentoring, and would love to introduce myself on the mail-list/IRC.

@Shubhpatel108 thanks for your interest, the project needs a co-mentor but in order to be a mentor, one needs to have prior experience with contributing to MediaWiki or related experience.

You can introduce yourself on Wikitech-l or MediaWiki-General irc channel.

Would there be any interest in mentoring this project for Outreachy Round 15? Application period opens in two days. See a few other ideas for projects that we are promoting for the upcoming round https://www.mediawiki.org/wiki/Outreachy/Round_15

I would like to co-mentor this project for Outreachy program Round 15. @Legoktm, could we do this for?

Yes, I think so. However what I said earlier still applies:

Yes, however due to my time constraints this quarter, the intern must absolutely be already familiar with the relevant MediaWiki subsystems as I will have less time this quarter to do basic bootstrapping that I'm normally happy to do. And we can find such a person, I'll commit to finding a second mentor.

Okay! Great to hear @Legoktm, if this is okay, you can add my name and we start showcasing while seeing if some students are interested.

@D3r1ck01 If you are willing to help a potential candidate get started with the project and assist them in resolving smaller issues along the way, while @Legoktm chimes in to help with bigger pieces of the project, I will be happy to showcase this project in https://www.mediawiki.org/wiki/Outreachy/Round_15

@D3r1ck01 If you are willing to help a potential candidate get started with the project and assist them in resolving smaller issues along the way, while @Legoktm chimes in to help with bigger pieces of the project, I will be happy to showcase this project in https://www.mediawiki.org/wiki/Outreachy/Round_15

Okay @srishakatux. Great!

D3r1ck01 updated the task description. (Show Details)Sep 20 2017, 11:39 AM

@D3r1ck01 , @Legoktm I am interested in this project for Outreach/R_15 and have started working on a micro task. will let you know when I submit a patch and/or have a question. Thanks

D3r1ck01 added a comment.EditedSep 21 2017, 11:27 AM

@D3r1ck01 , @Legoktm I am interested in this project for Outreach/R_15 and have started working on a micro task. will let you know when I submit a patch and/or have a question. Thanks

Great @Noella94, will be looking forward to see your PS. Below is a link to take note of;

Assuming your local wiki is setup, please do ask questions if you are stuck and I will be ready to help ASAP. You can ask on #wikimedia-dev while pinging me (nick -> d3r1ck). @Legoktm is busy ATM so I will be doing the bootstrapping and all the ground work with you :). But I think he maybe available to do some patch review.

D3r1ck01 updated the task description. (Show Details)Sep 21 2017, 9:41 PM

Thank you @D3r1ck01 for the response and for the detailed description of the task.

srishakatux updated the task description. (Show Details)Sep 23 2017, 12:37 AM

@D3r1ck01 I've tried to simplify the description a bit and added it here too https://www.mediawiki.org/wiki/Outreachy/Round_15#Show_edits_made_on_Wikimedia_Commons_on_the_Watchlist.

I'm wondering if the "Steps" in this task description containing two points are still necessary, is there something that you could add to help explain what is to be done now in the context of Wikimedia Commons?

@srishakatux, the steps are to reproduce the issue so interested students can understand what is needed to be implemented for commons. So at least the steps are necessary for someone new to the project (for him/her to understand what needs to be done). In addition, the project is now well explain and if there is any specific questions, students can ping on IRC or here on the ticket and we will respond to their questions. But, if there are any updates to the ticket, I will ping you. Thanks.

D3r1ck01 updated the task description. (Show Details)Sep 25 2017, 5:26 PM

Yes, probably me :)
I'm also, slightly concerned about the scope being too small, so another component of this could be moving the Wikibase code to do this into core, which would then be used by both Wikibase and GlobalUsage.

@Legoktm does this still apply?

Mattflaschen-WMF renamed this task from Show edits made on WikimediaCommons on the Watchlist to Show new versions of files (and possibly separately description changes) made on WikimediaCommons on the Watchlist.Sep 26 2017, 5:24 AM
Mattflaschen-WMF updated the task description. (Show Details)
Mattflaschen-WMF updated the task description. (Show Details)
  1. There are performance issues due to the Wikidata feature. 95% of the recentchanges rows on some wikis are Wikidata, and some queries do not yet handle that well: T171027: "Read timeout is reached" DBQueryError when trying to load specific users' watchlists (with +1000 articles) on several wikis. This should be blocked on that, or it will make the problem worse.
  2. There are some use cases for doing it for the file description too (e.g. improved description can lead to improved caption, deletion tag), but new file version is much more useful. I think either it should be only file version, or both but with a different rc_source, so they can be filtered separately.

@Mattflaschen-WMF, I agree with you on file versions and description changes and think they should be at the top of the priority queue before other aspects are looked at.

"File versions" on it's own has a lot of properties to take into considerations such as; rotation, new version, deletion etc which has to be looked at, since we are talking about commons, file versions is the most useful of all.

"Description changes" in this case also has very important aspects, for example someone may change the license of a file which may affects how it's been used on Wikipedia and other public wikis or the file summary. So this also counts, making this 2 key aspects to be taken into consideration when carrying out this project.

  • File Versions
  • Description Changes

Both should be implemented, what do you think @Mattflaschen-WMF? Cc @Bawolff, @Legoktm.

srishakatux added a comment.EditedOct 4 2017, 10:19 PM

This message is for candidates considering to apply to the Outreachy program:

Just making sure that you already know:

  • Deadline for submitting applications is October 23rd. It's good to start working on the application 2-3 weeks before the deadline, that way you might be able to get feedback from your mentors.
  • If you have already completed a microtask, communicated with your mentor about the next steps, and now thinking of working on your application then here is what I recommend:
    • Make sure you've checked whether or not you meet the eligibility criteria listed here https://www.outreachy.org/apply/eligibility/
    • When you start working on the application on the Outreachy program website, fill out the eligibility information first, even if you don't know yet what content should go in other parts of the application. That will allow Outreachy organizers to verify (see point 3 under "How to Apply" section https://www.outreachy.org/apply/).
    • As, you might know that Wikimedia requires you to submit your proposal on Phabricator. Make sure you are well aware of the process to do so (point number 9 under "Application Process Steps" here https://www.mediawiki.org/wiki/Outreachy/Participants).

If you have any questions about the application process, please ask! Good luck working on your applications! :)

Legoktm changed the task status from Open to Stalled.Oct 13 2017, 9:38 PM

I'm marking this as stalled as I think it would be unwise to work on an implementation of this until the Wikidata recentchanges explosion situation is resolved.

Removing the Possible-Tech-Projects tag as we are planning to kill it soon! This project does not seem to fit in the Outreach-Programs-Projects category in its current state, so I am not adding that tag right now!

Restricted Application added a project: Growth-Team. · View Herald TranscriptJul 12 2018, 5:45 AM
4nn1l2 added a subscriber: 4nn1l2.Jul 6 2019, 8:55 PM