[coc-tf] RIPE NCC Elections TF Report
- Previous message (by thread): [coc-tf] RIPE NCC Elections TF Report
- Next message (by thread): [coc-tf] Python Community CoC & Procedures
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Leo Vegoda
leo at vegoda.org
Sun Nov 8 19:53:13 CET 2020
I think I agree with Salam. For me, the justification text is the most difficult section. It suggests that the RIPE Trusted Contacts should have the responsibility of checking the records to confirm that candidates for the Executive Board have not violated the Code of Conduct. But the RIPE NCC's Impact Analysis for RIPE Meeting Code of Conduct 3.0 Draft includes this: "If the CoC is accepted, as secretariat we would expect to have a role in establishing or supporting this record-keeping system. Recognising the potentially sensitive nature of any reports, this would need to be handled appropriately within the RIPE NCC (restricted to a small number of staff)." If the actual implementation differs slightly from what is in the justification, and the responsibility falls on one of the small group of RIPE NCC staff responsible for maintaining the records system, the RIPE Trusted Contacts, or successor group, should not need to play a role in RIPE NCC Executive Board elections. That said, I'd appreciate input from the RIPE NCC on this as I might have misunderstood the intent of either or both documents. Kind regards, Leo On Sat, Nov 7, 2020 at 12:18 PM Salam Yamout <salamyamout at gmail.com> wrote: > > Thank you Brian for sharing > To me, this is just another COC abuse case. In this case, somebody (probably an Executive committee member will open a case, and according to the investigation, if the decision is a guilty one, the candidate must withdraw). We just have to make sure that the list of inappropriate behavior includes the type of behaviour we saw on the mailing lists before the elections. > My 2 cents > -salam > > On Fri, Nov 6, 2020 at 5:59 PM Brian Nisbet <brian.nisbet at heanet.ie> wrote: >> >> Folks, >> >> As discussed, the report is here: >> >> https://www.ripe.net/participate/meetings/gm/meetings/october-2020/ripe-ncc-executive-board-election-task-force-report.pdf >> >> The specific amendments are here: >> >> https://www.ripe.net/participate/meetings/gm/meetings/october-2020/proposed-amendments-to-the-ripe-ncc-articles-of-association.pdf >> >> And the resolution passed the GM vote, without any clarity on actual implementation. As Salam very wisely said, we don't have to pick up the ball, but we need to acknowledge the ball exists. >> >> Brian >> >> Brian Nisbet >> >> Service Operations Manager >> >> HEAnet CLG, Ireland's National Education and Research Network >> >> 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland >> >> +35316609040 brian.nisbet at heanet.ie www.heanet.ie >> >> Registered in Ireland, No. 275301. CRA No. 20036270 >> >> -- >> coc-tf mailing list >> coc-tf at ripe.net >> https://mailman.ripe.net/ > > -- > coc-tf mailing list > coc-tf at ripe.net > https://mailman.ripe.net/
- Previous message (by thread): [coc-tf] RIPE NCC Elections TF Report
- Next message (by thread): [coc-tf] Python Community CoC & Procedures
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ coc-tf Archives ]