I will quickly ask the UX designer who originally helped with the mocks last quarter, while I also think about these other implications and who to loop in.

@Prototyperspective points out that checking for CCBY should be possible with yt-dlp command parameters like:

Ah yes sorry, I forgot! Thank you for adding.

This revised list of 2k or so files from @Prototyperspective (thanks again!) may have better quality at source for half of the files:

Thank you @Amdrel !

Adding the relevant patch: https://github.com/toolforge/video2commons/pull/263

I think this can be closed now, too, right?

Seems this has been resolved. If this is regularly reproducible, we can look into what else to do.

There's some ongoing work that might solve this: https://phabricator.wikimedia.org/T401638

Maybe we can revisit this if a significant portion are modified? This would be a new feature.

Were you folks able to sit down and talk about this?

Now we have filter by tags, so we don't think we need to filter by components or stewards. Maybe we revisit this in the future.

Now we have filter by tags, so we don't think we need to filter by components or stewards. Maybe we revisit this in the future.

Now we have filter by tags, so we don't think we need to filter by components or stewards. Maybe we revisit this in the future.

Now we have filter by tags, so we don't think we need to filter by components or stewards. Maybe we revisit this in the future.

Now we have filter by tags, so we don't think we need to filter by components or stewards. Maybe we revisit this in the future.

Apologies for not filing a ticket earlier to track the work done so far here! The second part to fix videos imported with low quality remains open and @Amdrel is having a hard time reproducing, but @Prototyperspective has provided some pointers in this discussion thread: https://meta.wikimedia.org/wiki/Talk:Community_Wishlist/W447 (thank you!)

Does anyone have alternative solutions?
Or do you @Don-vip also agree with the solution and feedback from @Amdrel and @bd808 ?

It is beginning to sound like this is out of scope for v2c, but rather something for MediaWiki - is there someone cc'd here who might be able to assign to the right owner?

@Amdrel thanks for filing respective issues in GitHub!
@Pppery thanks for fixing the typo!

I think I need to create a new GitHub account before I filed this in GitHub for more transparency. However, if someone else would like to, that would be great as I'm short on time and need to see what the recommended company policy is for my new GitHub account.

@Amdrel - is this something you can look into after @Don-vip grants you maintainer rights to investigate?

@Sdkb were you able to look into the possibility that the tool you're using to check metadata is not recognizing the GPS coordinates when stored under those keys as suggested by @Amdrel ? This will help prioritize fixing the issue or we can close this if it's not reproducible.

In T406670#11293120, @dmaza wrote:

When a wish is created, make a request to action=wishlistvote on behalf of the user. Leave the comment blank – they'll be able to change it later if they want to.

To be clear, the comment can only be changed by editing the /Votes page or after the status is changed to one that allows voting.

Also, the default wording for under-review is not fitting anymore This wish is currently under review. Once accepted, you will be able to support it.. Looping @JSengupta-WMF @Meztuinaga-ctr

@Don-vip thank you for providing context - I was unaware since I'm new at WMF. We appreciate the merge and time will tell! We had contracted Simone to help out here, but maybe he can still take a look and provide feedback or just move onto the other v2c issues

Just because I'm new and unaware of who's who - are you folks working with Simone on this?