-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At risk of writing an email by commmittee, below is my first draft of the email for HPH. I just wanna double check I've fully understood all the points we're asking before I hit send. Is the below what people had in mind that we should be asking? - ------ Dear Hans Peiter, I am writing on behalf of the diversity task force regarding the proposed improvements to the Ripe Code Of Conduct. There has been some confusion as to the next steps we need to take, and were hoping you could provide guidance on what should happen next. We have a draft version 3.0 of the CoC, based on feedback from various parties to a version 2.0 that was sent to ripe mailing lists in May. This version is below. https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkc... It has been suggested that perhaps we should have ripe legal do an Impact Analysis on the CoC of conduct before it's fully adopted, but we are unclear the exact process required. Please can you advise. Julia Freeman (On behalf of the Ripe Diversity Task Force) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFdnbL342M0lILkmGIRAkYmAJwN7sL5JJCrgRqn6nMSebwIfacRugCfSakO 5+ZhyefOoVuIdaR6X97Ntlc= =WFrz -----END PGP SIGNATURE-----
Hi Julia, Perhaps you can change the wording so that HPH is requested to request the RIPE NCC legal team for an Impact Analysis. Skip a step so to speak. Kind regards, Job On Wed, Oct 9, 2019 at 19:14 Julia Freeman <ripe-diversity@quixotic.eu> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
At risk of writing an email by commmittee, below is my first draft of the email for HPH. I just wanna double check I've fully understood all the points we're asking before I hit send. Is the below what people had in mind that we should be asking?
- ------
Dear Hans Peiter,
I am writing on behalf of the diversity task force regarding the proposed improvements to the Ripe Code Of Conduct. There has been some confusion as to the next steps we need to take, and were hoping you could provide guidance on what should happen next.
We have a draft version 3.0 of the CoC, based on feedback from various parties to a version 2.0 that was sent to ripe mailing lists in May. This version is below.
https://docs.google.com/document/d/1yqOUPR02SONuSt812cuOBkk_xnhjYzjdk9qmsJkc...
It has been suggested that perhaps we should have ripe legal do an Impact Analysis on the CoC of conduct before it's fully adopted, but we are unclear the exact process required.
Please can you advise.
Julia Freeman (On behalf of the Ripe Diversity Task Force) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFdnbL342M0lILkmGIRAkYmAJwN7sL5JJCrgRqn6nMSebwIfacRugCfSakO 5+ZhyefOoVuIdaR6X97Ntlc= =WFrz -----END PGP SIGNATURE-----
_______________________________________________ diversity mailing list diversity@ripe.net https://lists.ripe.net/mailman/listinfo/diversity
participants (2)
-
Job Snijders -
Julia Freeman