Add Nominate for Speedy Deletion option for images

[gopalakrishnaa]

What is the user problem or growth opportunity you want to see solved?

We have two options for deletion on Wikimedia Commons.

1. Speedy Deletion on Commons

• Used for cases where deletion is obviously necessary, such as blatant copyright violation, vandalism, nonsense pages, corrupted files, user-requested deletions, empty or obsolete categories, and unused redirects.
• To tag for speedy deletion, use the {{speedydelete|Reason}} template at the top of the file or page, providing a clear reason for deletion.
• Specific speedy deletion templates like {{Copyvio}} (for copyright issues) are often used.
• Speedy deletion should only be used in cases specified by the speedy deletion criteria, and not for anything controversial or debatable.
• Always notify the original uploader or page author when tagging for speedy deletion.

2. Nominate for Deletion (Commons:Deletion requests)

• Used for less clear-cut cases, disputed media, or files/pages that require community input before deletion.
• To nominate, go to the media description page and click "Nominate for deletion" in the Tools menu, or list files manually at Commons:Deletion requests.
• Mass nominations are possible for entire categories or groups of files.
• Provide as much detail as possible: reasons, evidence, duplicate links, and context for the nomination so the closing administrator has all relevant information.
• Use this method if the content does not qualify for speedy deletion, or if there are significant questions about copyright status, scope, or notability.

We use whenever in doubt or when the file/page does not clearly meet speedy deletion criteria, use nomination for deletion to allow community review.

How do you know that this problem exists today? Why is this important?

When I spoke to community members and admins, there were mentions about this problem. Because the Criteria for Speedy Deletion uploads might be larger, which are uploaded from a mobile phone. Now we have only a mark for the deletion option, which will take a week to delete any copyright image,s etc.
In general Speedy Deletion process can have pre-existing reasons and then Nominate for Deletion will have a dialogue box where the user can provide a appropriate reason to write.
For Speedy Deletion we can have these major reasons.

1. Copyright violations - (https://commons.wikimedia.org/wiki/Category:Copyright_violations)
2. Duplicate - (https://commons.wikimedia.org/wiki/Category:Duplicate)
3. Advertisements for speedy deletion - (https://commons.wikimedia.org/wiki/Category:Advertisements_for_speedy_deletion)
4. Personal files for speedy deletion - (https://commons.wikimedia.org/wiki/Category:Personal_files_for_speedy_deletion)
5. Other speedy deletions - (https://commons.wikimedia.org/wiki/Category:Other_speedy_deletions)

Who will benefit from it?

Commons community and Users with extended rights

Anything else you would like to add?

@RitikaPahwa4444 and @nicolas-raoul, please assign this to @devjadiya, or if anyone would like to help or mentor Dev, please add a comment in this thread.

[nicolas-raoul]

One of the main complaints, from the Wikimedia Commons community, against our app, is that our users send too many frivolous deletion nominations.

In other words, users regularly nominate for deletion pictures that are actually good.

So, before adding speedy deletion nomination, #2852 must be implemented or any other solution to address the problem.

So, how about implementing #2852 instead? :-)

The present issue can be kept as it is a good idea for the future, thanks for filing it!

[RitikaPahwa4444]

@RitikaPahwa4444 and @nicolas-raoul, please assign this to @devjadiya, or if anyone would like to help or mentor Dev, please add a comment in this thread.

It might be a bit off-topic but I would still like to share my take on this. As I suggested before, getting more involved in the community on GitHub is the best way to learn and get help instead of working in isolation. Most of the folks here willingly help the contributors out without even being asked for mentorship :)

As far as the complexity of the code base is concerned (something that you mentioned before), there is specific reason why we recommend picking up bugs/good-first issues over enhancements (some of them are now tagged as features). It helps new contributors onboard quickly and understand the nuances of the code base at the same time. I would highly recommend anyone new here to go through our contributing guidelines and explore a bit before picking up features.

Moreover, features require discussions over feasibility as well before anyone could go and implement them, so it's always better to discuss before asking to get them assigned and code them out right away. Our community is quite active and many seasoned members and contributors have valuable insights to share 🙂