[coc-tf] Code of Conduct Task Force

Jordi,

You owe an apology to Leo and his colleagues in the RIPE Code-of-Conduct 
Task Force,
as your message is utterly inappropriate.

I expect to see your apology later today.

I respectfully suggest that you reflect on your “deep experience in 
many abuse situations”
and consider what consequences usually and normally follow from posting 
messages which are
obstructive, which waste time, and which contain disrespectful and 
threatening language.

I hope I may look forward to your constructive engagement with the RIPE 
Code-of-Conduct
Task Force in response to Leo’s kind invitation to contribute to their 
work by email.

Kind regards,

Niall O’Reilly
RIPE Vice-Chair


On 9 Nov 2020, at 16:51, Jordi Palet Martínez wrote:

> Hi Leo, all,
>
> I'm coping the RIPE Chair and Vice-chair, as this seems to me very 
> strange and extremely ridiculous. Fortunately, I don't know how to say 
> very bad words in English which I've in my mind right now in Spanish, 
> otherwise, you will read all them.
>
> I've tried to find the information about how the Task Force membership 
> is "selected" and why is done by the Chair and Vice-Chair. I was 
> unable to find that information. Can you point me to the relevant 
> documents?
>
> I only was able to found this email:
> https://www.ripe.net/ripe/mail/archives/diversity/2020-September/000526.html
>
> An email from September 8th, that I didn't read before (I've been too 
> busy the last few weeks), asking for volunteers. Yes, the email says 
> "Please contact us before 15 September 2020", but doesn't point to a 
> closure of the Task Force membership, or rules for participating, or 
> anything similar. It even says "please", so this is a clear sign, at 
> least in Spanish, that it is preferred to respond before 15th, but not 
> that the call is "closed" by then.
>
> To add further information, as indicated in my later email on 26 Oct., 
> I was sergeant-at-arms of the IETF for almost 12 years, so I've also a 
> deep experience in many abuse situations to the mailing list, which I 
> guess can be very useful.
>
> So even if there is not (or as said, I was unable to find it) any 
> explicit *community decided* way to select the TF members, clearly 
> this shows that I've something to contribute from practical 
> experience.
>
> I never head that in RIPE community we have closed groups. This is 
> clearly against the full concept of openness and in this concrete 
> case, against the full concept of diversity and inclusivity. How come 
> a TF coming out from the Diversity TF, can be closed?
>
> I can't believe this.
>
> The conclusion is very clear to me. This is just a theater. I think 
> this should be openly exposed to the full RIPE and the other RIRs 
> communities. Very sad situation.
>
> I'm also going to talk to my lawyer about all this, in case it is a 
> case of discrimination or other illegal actions, according to laws.
>
> Regards,
> Jordi
> @jordipalet
>
>
> El 9/11/20 16:13, "Leo Vegoda" <leo at vegoda.org> escribió:
>
>     Dear Jordi,
>
>     You wrote to the coc-tf at ripe.net list on 26 October asking to
>     subscribe so that you could contribute to the work. I promised to
>     place your request on the agenda for the next TF meeting.
>
>     The Code of Conduct TF met on 6 November and we discussed your 
> request.
>
>     We agreed that membership of the Code of Conduct TF had been 
> decided
>     by the RIPE Chair and Vice-Chair following an open call for
>     participation. The Code of Conduct TF is not empowered to expand 
> its
>     own membership.
>
>     We discussed opening the list to new subscribers but agreed that 
> as
>     the majority of the work is done on calls, this adds little 
> benefit.
>     Instead, we agreed to two actions to increase transparency. 
> Firstly,
>     we will make the list archive public. Secondly, we will add a 
> summary
>     of key discussion points and decisions at the top of each set of
>     minutes, to make it easier for people outside the TF to build
>     familiarity with our work.
>
>     The RIPE NCC will be adding the mailing list archive to the TF web
>     page in the next few days.
>
>     We encourage you to write to the coc-tf at ripe.net list if you have 
> a
>     contribution to make.
>
>     As well as listening to the community through our own mailing list 
> and
>     through the ripe-list at ripe.net list, we will actively communicate 
> our
>     progress.
>
>     Kind regards,
>
>     Leo Vegoda
>     On behalf of the Code of Conduct TF
>
>     On Mon, Oct 26, 2020 at 4:53 AM Leo Vegoda <leo at vegoda.org> wrote:
>     >
>     > Hi Jordi,
>     >
>     > I will place your request on the agenda for the TF's next 
> meeting.
>     >
>     > Kind regards,
>     >
>     > Leo
>     >
>     > On Mon, Oct 26, 2020 at 4:51 AM Jordi Palet Martínez
>     > <jordi.palet at theipv6company.com> wrote:
>     > >
>     > > Hi all,
>     > >
>     > > I will like to subscribe to the COC Task Force in order to 
> contribute to the work.
>     > >
>     > > I've been working in other regions in a similar task, by means 
> of a policy proposal, and I think I can contribute with many points.
>     > >
>     > > I looked into the web page and it is not clear how to ...
>     > >
>     > > Regards,
>     > > Jordi
>     > > @jordipalet
>     > >
>     > >
>     > >
>     > >
>     > > **********************************************
>     > > IPv4 is over
>     > > Are you ready for the new Internet ?
>     > > http://www.theipv6company.com
>     > > The IPv6 Company
>     > >
>     > > This electronic message contains information which may be 
> privileged or confidential. The information is intended to be for the 
> exclusive use of the individual(s) named above and further 
> non-explicilty authorized disclosure, copying, distribution or use of 
> the contents of this information, even if partially, including 
> attached files, is strictly prohibited and will be considered a 
> criminal offense. If you are not the intended recipient be aware that 
> any disclosure, copying, distribution or use of the contents of this 
> information, even if partially, including attached files, is strictly 
> prohibited, will be considered a criminal offense, so you must reply 
> to the original sender to inform about this communication and delete 
> it.
>     > >
>     > >
>     > >
>     > >
>     > >
>     > > --
>     > > coc-tf mailing list
>     > > coc-tf at ripe.net
>     > > https://mailman.ripe.net/
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
>
> This electronic message contains information which may be privileged 
> or confidential. The information is intended to be for the exclusive 
> use of the individual(s) named above and further non-explicilty 
> authorized disclosure, copying, distribution or use of the contents of 
> this information, even if partially, including attached files, is 
> strictly prohibited and will be considered a criminal offense. If you 
> are not the intended recipient be aware that any disclosure, copying, 
> distribution or use of the contents of this information, even if 
> partially, including attached files, is strictly prohibited, will be 
> considered a criminal offense, so you must reply to the original 
> sender to inform about this communication and delete it.