In apparent disagreement with the direction of 8.x-2.x, I think Masquerade needs to be able to run as a production module. Currently, it's assigned to the "Development" package on the Extend page of modules. This is major not just in the re-naming, but in the concept of how to treat the access controls provided by the module.

It's a legitimate thing for customer service reps to be able to masquerade as users in certain roles, which isn't a development activity - it's a production one.

CommentFileSizeAuthor
#1 masquerade_development_module_list.jpg57.39 KBdeekayen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

deekayen’s picture

Adding a screenshot of what I'm talking about.

andypost’s picture

Agree, 'development' is not a right place for module.
About approach I think we should introduce toolbar button to make module more friendly with none-devs

deekayen’s picture

Status: Active » Fixed

I just removed the Development package until some other modules are updated and we can have the opportunity to talk about a better fit under a different heading.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.