Meta talk:Deletion policy/Archives/2024

Please do not post any new comments on this page. This is a discussion archive first created in 2024, although the comments contained were likely posted before and after this date. See current discussion or the archives index.

Proposed amendment to WM:CSD

Latest comment: 8 months ago10 comments4 people in discussion

@Billinghurst, Pppery, TenWhile6, 1234qwer1234qwer4, and Hide on Rosé: This is a follow on of Special:PermaLink/26234292#Special:PrefixIndex/Translations:Access_to_nonpublic_personal_data_policy-summary

Good day all. Recently, many of our local translation pages are moved to Foundation wiki and their local pages are removed from the translation system. Their respective content in Translations is left orphaned and there is no apparent need to keep them as their history are moved wholesale. As such, I'd like to propose adding a new CSD criteria to nuke such pages in Translations. There is a similar CSD criteria for articles but not for translation units.

And just to clarify this proposal also includes deleting the main translation page. e.g. PAGE will be left with a soft redirect and PAGE/translationlanguage will be deleted. --Min☠︎rax^«¦talk¦» 06:13, 24 February 2024 (UTC)

@Minorax I seem to recall that the history of these pages are not actually done being dealt with yet? Example page: HERE contrasted with foundationwiki. Seems that the imports are not maintaining attribution necessary. Am I missing something? — xaosflux ^Talk 12:02, 24 February 2024 (UTC)

Eh, seems to be a problem with importing/exporting translations. Will look into it. --Min☠︎rax^«¦talk¦» 13:09, 24 February 2024 (UTC)

Seems to be a limitation of the extension where the history of the pages won't be imported/exported. --Min☠︎rax^«¦talk¦» 13:50, 26 February 2024 (UTC)

Comment: For reference, there is a related Phabricator ticket - although it will not help with content already migrated. However, it may be ready before the next mass migration of translations of duplicated content (this time Board resolutions) is conducted (Phabricator ticket related to that process). --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 00:34, 27 February 2024 (UTC)

Can the transfer be put on hold until this feature to the extension is pushed through? --Min☠︎rax^«¦talk¦» 08:02, 8 March 2024 (UTC)

I believe the plan is to do the transfer once that feature is completed (they are currently working on it). I suspect any change to that plan would be result of discovering a new hurdle that will delay the feature longer than expected. But at this point, I am not aware of any hurdles or delays.

Also, note the discussion at Template_talk:Languages#Fix? with some other ideas on how to handle these language subpages - specifically putting them back into translation system. I will go with what community decides, but wanted to point out there seems to be some different ideas. --Gregory Varnum (Wikimedia Foundation) [he/him] (talk) 18:55, 12 March 2024 (UTC)

Think that the conversation was about adding a new reason, not the process, nor the history. We are just looking at how we manage the deletion, and the remaindered translations: when the parent page has been deleted. — billinghurst sDrewth 21:07, 12 March 2024 (UTC)

Comment If the works are migrated, I would think that we can simply say that it is "Redundant content". I don't think that we need to create a new reason. — billinghurst sDrewth 11:23, 25 February 2024 (UTC)