On 07/27/2014 09:08 PM, Majken Connor wrote:
On Sun, Jul 27, 2014 at 2:58 PM, Benjamin Kerensa <[email protected]>
wrote:
Yeah it seems just changing job descriptions does not really go to the
extent of getting new hires to agree to participate with community and
meet other expectations. If modifying a job description was all it
took to get new hires to meet certain expectations surely their would
not be a need for the other documents and agreements new hires already
sign.
I think having new hires enter into an agreement with the project is a
great step forward in trying to change some of the status quo.
No, but emphasizing it earlier on in the process will signal that we take
it seriously. Which is why I think having a formal doc is important as
well. That sends the signal that we find it important enough to highlight
it on its own, not just reference it across different processes. If we put
it out there early then it may help applicants self-select out of a culture
they're not interested in.
You can always do both.
However, unless someone at Mozilla is amused enough to do something about
it, I expect Mozilla to do neither. (I am not at Mozilla nor in HR, so,
sorry, but I won't be able to help here. I can only make snarky comments
from the sidelines on m.governance. :)
~fantasai
_______________________________________________
governance mailing list
[email protected]
https://lists.mozilla.org/listinfo/governance
