This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
- Previous message (by thread): [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
- Next message (by thread): [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gergana Petrova
gpetrova at ripe.net
Wed Apr 21 11:23:43 CEST 2021
Hi all, I should have made it clearer: I was responding to Niall's email. @Randy: 100% agree Cheers, Gergana On 21/04/2021 03:39, Randy Bush wrote: > hi gergana, > > [ top posting reversed ] > >>> my naïve view is that, if the ncc is an organiser, then the coc MUST >>> apply. >>> >>> if i am asked to be on (or chair) a panel which has no under-represented >>> folk, i decline, making the reason very clear. >> >> I don't think of the SEE, MENOG and ENOG communities as "distinct from >> RIPE", rather than sub-communities of RIPE. > > i might phrase is as comminities *within* ripe; i.e. not subordinate to. > but that is likely my over-sensitivity. > >> These communities don't have a separate Chair or Working Groups and >> their members participate in and are subject to the >> RIPE-community-developed policies, which is why to me they are an >> integral part of the RIPE community. > > so are these communities then relevant? > > my point was intended more to the ripe community or the ncc providing > meeting coordination with an external group, e.g. Euro IoT Regulatory > Wannabes. imiho, the coc virus would be more beneficial than the gpl > virus. :) you hang out with us, you behave civily. > > randy > > --- > randy at psg.com > `gpg --locate-external-keys --auto-key-locate wkd randy at psg.com` > signatures are back, thanks to dmarc header butchery >
- Previous message (by thread): [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
- Next message (by thread): [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]