Looks like this is set at https://gerrit.wikimedia.org/g/mediawiki/extensions/UploadWizard/+/d0572ccc8f27d024d012f5a94051ef6eebe9c1d6/UploadWizard.config.php#568

Yeah I'll support it. But consider that newbies are probably not aware of the complexities, deformities, counterintuitiveness and peculiarities behind copyright rules.

[EDIT] I replied on Commons.

Noting the discussion was done on Commons; this was the consensus:

Add PD-textlogo, but only autopatrollers can see it.

@Matrix @Sdkb Would it be possible to revisit this? Adding an auto-patroller-only restriction seems like it will be a fair bit more work. (In particular, I'm wondering how this would interact with the campaign system?)

In T376522#11199598, @Soda wrote:

@Matrix @Sdkb Would it be possible to revisit this? Adding an auto-patroller-only restriction seems like it will be a fair bit more work. (In particular, I'm wondering how this would interact with the campaign system?)

As I argued in the RfC, I'd much prefer that it just be shown to everyone. But it took quite a lot of effort to get even this consensus, and as a consensus it should be respected. I think that, after a while of having this enabled for autopatrollers and seeing that it's not the end of the world, editors might be more willing to revisit the restriction. But I don't anticipate that revisiting the discussion immediately would lead to a substantially different result (there are just too many editors on Commons willing to sacrifice usability for newcomers so that they have less to patrol).

On a technical level, I'm not sure I follow the concern about interaction with the campaign system. (And on a broader level, ugh, I really wish that the WMF team had consulted with the community when initially putting together this list. It would have been so much easier than trying to change it after the fact. cc @Sannita )

@Soda Unfortunately, per my close this would be against the community consensus. There were valid points raised in opposition, and we can't ignore that. I apologise for the extra work this is going to cause, but I doubt the community consensus will change in the near future. Perhaps also clarifying that the file must also be below TOO in the country of origin is also helpful.

In T376522#11199685, @Sdkb wrote:

On a technical level, I'm not sure I follow the concern about interaction with the campaign system.

So, on a technical level, the way this is implemented is that UploadWizard has a list of hardcoded licenses and a default campaign. When a user goes to UploadWizard, the default campaign is provided, and when the user applies a specific campaign (by navigating to (say) this link) the specific campaign that is being specified by the ?campaign=<stuff> URL parameter is used. Now, these specific campaigns can pick and choose particular licenses to display; they can choose to omit specific licenses or show ones that are not shown in the default flow. Within this context, there is no existing mechanism to gate by user rights

Now, assuming there is an implementation of a "gated" PD-textlogo (where you need to be autopatrolled), what would happen in the case where a different campaign also decided to add PD-textlogo to their list of allowed copyright license templates ? Do we gate it for autopatrollers as well, or do we allow folks to bypass the AP restriction by choosing the particular campaign?

My assumption here is that we want "we allow folks to bypass AP restrictions for specific campaigns" (since there is already a pre-existing PD-textlogo license, which I assume is being used by some campaigns and we do not want to break the workflow here), in that case, we would need to build code that allows campaigns to set user-rights restrictions for each specific campaign. If not, we need to add code that makes sure that for any campaign.

(In contrast if we could just add PD-textlogo or PD-textlogo-to-be-reviewed it would be a much simpler few-line config change of adding a new license and then adding it to the flow)

(And on a broader level, ugh, I really wish that the WMF team had consulted with the community when initially putting together this list. It would have been so much easier than trying to change it after the fact. cc @Sannita )

I can throw the list for the default campaign here from the current source code. This should be pretty comprehensive with regard to the current state of the code, feel free to suggest more stuff that should be added (or have the community take a look)

• If the work is your own
  • CC0
  • CC BY 4.0
  • CC BY-SA 4.0
  • Custom (put your own)
• If the work is from a third party:
  • Freely licensed
    • CC0
    • CC BY 4.0
    • CC BY 3.0
    • CC BY 2.5
    • CC-BY-SA 4.0
    • CC BY-SA 3.0
    • CC-BY-SA 2.5
    • Custom (put your own)
    • Unknown (scary warning about not uploading the file)
  • Public domain works
    • PD-US
    • PD-old-70
    • PD-USGov
    • PD-USGov-NASA
    • Custom-PD (put your own)
    • Unsure (scary warning about not uploading the file
  • VRT (show the release generator and a checkbox that the user understands that if they do not secure a release, file will be deleted)
  • None (scary warning to not upload)