Moving the ownership of azure-mask about azure-mask

[clarkio]

Hey @cmaneu, I'm great thanks and hope you are as well.

I'm glad to hear of the expanded usage of this extension and appreciate you reaching out. I'm open to contributions to help address the issues and missing use cases you mention. Would you be open to helping contribute to that?

One of the challenges is definitely time for me to commit to this but also that the Azure UI changes constantly and lacks a standard to label/identify sensitive data in it (either by some sort of class or id attribute). I'm also aware that different internal teams tend to manage their own space in the overall UI which also adds to this moving target of identifying and adding fields to be concealed through the extension.

During my time as an employee there were a few attempts to either provide concealment directly in the portal or standardize labeling of sensitive fields. Unfortunately it didn't quite get the momentum and support we had hoped for at the time. I believe this would be the best solution for the long-term to the problem this extension attempts to address. Maybe you can take charge of that initiative internally to get the discussion going again too?

I'm open to further discussion around all this and wish to keep providing value to folks that find this extension useful. Feel free to continue chatting here or privately over DM if you'd prefer.

[spboyer]

@cmaneu @clarkio - did this move of ownership happen?

cc:/ @charpfritz

[cmaneu]

Hey @spboyer,
I was embarked on a non-Azure related work for quite a time (and still), and didn't get back to this discussion. AFAIK, no ownership changes have happened.

[clarkio]

Did you all get a chance to read my response @cmaneu @spboyer ? Any further comment or thoughts on that?