It would be awesome to consider the functions in the Taxonomy Role module to move into core. It exposes some permissions per role per vocabulary to give granular access to adding taxonomy terms to nodes. Does a great job, operates on a pretty parallel model as other modules (for example, adding permissions per content type when new types are created) so the learning curve is pretty short.

This would keep users from needing an additional module, and add a great level of value to core.

If I had the chops then I would try to add the access control permissions to both the permissions page as well as the individual vocabulary edit pages. A little help text would go a long way too.

That's my pitch.

Comments

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented

I think taxonomy role is a typical example of a module that belongs in contrib, not in core. The use case is just too specific.

"would keep users from needing an additional module" is not a good motivation to move something into core, because it would mean that everything should be core. If you're concerned that installing modules is too complicated, we'd rather fix that.

marcvangend’s picture

marcvangend
he/him
Primary language Dutch
Location Amsterdam
commented
Status: Active » Closed (won't fix)

I forgot to change that status - I'm setting this to won't fix, but if anyone disagrees, please speak up.