Page MenuHomePhabricator

Update Fileimporter-Configs: Remove GFDL from list of 'good templates'
Closed, DeclinedPublic


Due to changes of Commons-Policy most GFDL-only works will not be allowed anymore in the future.

Make sure GFDL is removed from the list of 'good templates' on all FileImporter-Configs.

Event Timeline

Restricted Application added a project: TCB-Team. · View Herald TranscriptSep 19 2018, 10:48 AM
Pikne added a subscriber: Pikne.EditedSep 19 2018, 4:56 PM

Per Commons licensing policy GFDL-only works are still allowed if they were licensed before 15 October 2018. Also, on local projects there are quite some GFDL-only files left that can be dual licensed per relicensing criteria. Having have to change these older GFDL works to use some different 'good template' before moving to Commons and then change back to GFDL on Commons would seem as an unnecessary inconvenience to me. It's also possible to tag new GFDL-only uploads with an additional 'bad template'. Perhaps rather we can let every project decide which way they will configure it if losing files after moving to Commons actually becomes a problem.

@Pikne The communities are free to set up the configs as they want! This ticket is to make sure the new change is reflected in the configurations where the community has not yet started taking care of the configs.
The idea is also to remove GFDL from the list of "good"-templates, but not add it to the "bad"-templates. This way they can be still moved to commons if they are marked with any other "good"-template – so one could also have a template "Suitable for commons" (several wikis have this already) that if present allows to move the file but will be automatically removed from the wikitext by the fileimporter.

WMDE-Fisch closed this task as Declined.Wed, Feb 12, 1:44 PM
WMDE-Fisch added a subscriber: MichaelSchoenitzer.

It's currently not clear what should be done with this ticket from the TCB-Team side. We believe that action is required by the communities to adapt their configs and we will not interfere.

@MichaelSchoenitzer maybe this has already been done even? If not, then this should rather be communicated outside of Phabricator to the communities directly