Can be removed from the UW config/code, if not yet removed.
"Consensus" is a strong word for a discussion between three people, of whom two "voted" for the change. This would not just remove the template transclusion on new files, but stop any user from using a custom license on any upload, greatly reducing the usefulness of the tool (as evidenced by the 500k+ files that use this template) - I'm not convinced this is the way to go, but I'm not the only voice in this discussion anyway.
Would it be acceptable to simply remove the 'templates' entry for the template in question, rather than turning off custom licenses entirely? I'm still not certain there is consensus even to support that move, but I'm asking if that's what you *meant* to do.
@Ramsey-WMF, I'd like your thoughts on this when you get a chance. (assigned)
@CKoerner_WMF you might want to chime in as well.
With upcoming changes involved with Structured Data on Commons, retaining this template is actually potentially useful for purposes of helping to identify custom template files that will need to be changed to fit into the new (still undecided) structured licenses format.
In short, in the future we'll need to migrate everything to a different system and every little bit that helps us identify what goes where is welcome (including templates like this).
We would like to have *some* sort of standard way to programatically look for these kinds of files that use custom licenses. If it's not Custom_license_marker, we're open to suggestions for items that work equally well or better. Otherwise, we should keep/revert the old functionality.
All template usage has been removed yet & the template has been deleted:
(change visibility) 12:04, 4 October 2017 Steinsplitter (talk | contribs | block) deleted page Template:Custom license marker (unused & deprecated) (view/restore)
Please pull such data from the databases using a mysql query.
Disclaimer: We won't turn off custom licenses (there are hundreds of custom licenses on commons) but just the redundant and incomplete tracking template. Up to date/non incomplete data can be pulled from the database if needed. This is just some really old tracking stuff.
Edit: I think we can close this task then as locally handled, as no configuration change in the code itself is necessary.