[diversity] [Ext] Draft CoC and response guide
- Previous message (by thread): [diversity] [Ext] Draft CoC and response guide
- Next message (by thread): [diversity] [Ext] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Amanda Gowland
agowland at ripe.net
Thu Apr 11 11:45:24 CEST 2019
In principle, yes...but it's a grey area in terms of the RIPE Chair's scope...technically, SEE and ENOG and MENOG are not governed by RIPE. I think once we have the RIPE CoC up and running, we can then push the respective PCs to adopt or amend to their needs while keeping the spirit/key points as close to ours as possible. On 10/04/2019 14:59, Brian Nisbet wrote: > First off, Sasha, this is great, thank you so much! > > Secondly, I think any CoC has to apply to all RIPE Community events > and online interactions. I don't think restricting it to just RIPE > meetings would be a good idea. > > Now, maybe there has to be something iterative here, but certainly the > aim should be to have the same, or as close to the same, bearing in > mind the diversity of the service region, CoC across anything RIPE is > running. > > Even if we started with the main meeting and the mailing lists, that > would be a good thing, but I'd really like to see it spread further > than that. > > Thanks, > > 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 > > ------------------------------------------------------------------------ > *From:* diversity <diversity-bounces at ripe.net> on behalf of Amanda > Gowland <agowland at ripe.net> > *Sent:* Tuesday 9 April 2019 09:36 > *To:* diversity at ripe.net > *Subject:* Re: [diversity] [Ext] Draft CoC and response guide > Hi Gergana, Benno, > > Benno has it right. > > We talked about this in the last TF meeting - the minutes were > circulated a few weeks ago or so. If we follow the typical TF protocol > for work output, it's basically: > > - Present to the community > - Ask for feedback from community > - TF reiterates if needed > - RIPE Chair declares consensus > > But since there isn't the equivalent of HPH in the other regional > communities, I would imagine this would fall to the respective > PCs...well, I'm not sure but I think that sounds right? > > thx, > > Amanda > > On 08/04/2019 18:20, Benno Overeinder wrote: > > Hi Gergana and all, > > > > I think you are correct. > > > > Speaking now for myself, not the PC collective, a suggestion might > be to ask the RIPE chair, PC and the WG chairs collective for a first > reading and approval (not sure this is the right wording), and next > for community consensus of the CoC on the RIPE mailing list (not the > TF mailing list). > > > > But for sure, our RIPE chair knows how to proceed in the proper way. > > > > Best, > > > > — Benno > > > > — > > Benno J. Overeinder > > NLnet Labs > > https://www.nlnetlabs.nl/ > > > >> Op 8 apr. 2019 om 17:18 heeft Gergana Petrova <gpetrova at ripe.net> > het volgende geschreven: > >> > >> Thanks Amanda! I can certainly bring this up with the relevant PCs > for the regional meetings. > >> > >> But, just for my info - is the RIPE PC going to be approving the > CoC? I wasn't aware they have to. They are responsible for the plenary > program, but not the meeting itself. So for example all day Wednesday > and Thursday have nothing to do with them. Here is their Charter for > more info: https://www.ripe.net/publications/docs/ripe-600 > <https://www.ripe.net/publications/docs/ripe-600>). > >> > >> I thought the CoC is more a question of the RIPE community's > agreement/concensus (basically this taskforce's mailing list, which > include the people from the RIPE Community interested on this topic). > Similar to the way WGs work. > >> > >> Anybody from RIPE PC can shed light on this? Brian? I hope I'm not > creating a mess. > >> > >> Cheers, > >> Gergana > >> > >>> On 08/04/2019 16:35, Amanda Gowland wrote: > >>> Hi Gergana, > >>> It's a good question. But seeing as the ENOG and MENOG and SEE > Meetings have their own PCs, I think it's probably something that they > would need to adopt on their own accord. Certainly, it would be simple > to just adapt one for the RIPE Meeting but it's not within the scope > of the TF to do that. > >>> thx, > >>> Amanda > >>>> On 08/04/2019 16:30, Gergana Petrova wrote: > >>>> Hi Sasha, hi all, > >>>> > >>>> Just want to join in with thanking you for this excellent CoC draft! > >>>> > >>>> Just a general question, as I am not sure if the mandate of the > Transforce covers this. The CoC mentions "Where does the Code of > Conduct apply?" - RIPE meetings. I was wondering if we can include > "RIPE meetings and other events organised by the RIPE NCC such as > ENOG, MENOG, SEE and other regional meetings." > >>>> > >>>> What do you think? > >>>> > >>>> Cheers, > >>>> Gergana > >>>> > >>>>> On 08/04/2019 10:48, Amanda Gowland wrote: > >>>>> Sasha, > >>>>> > >>>>> THANK YOU for contributing such a stellar draft! I've gone > through and made some edits, some more British spelling-isms + putting > some of the goals in active tense. I also made the scope (in terms of > who it applies to) a bit more explicit. > >>>>> > >>>>> Warm regards, > >>>>> > >>>>> Amanda > >>>>> > >>>>> > >>>>> > >>>>>> On 08/04/2019 10:36, John Springer wrote: > >>>>>> I agree, excellent work! > >>>>>> > >>>>>> I have suggest some minor edits of the Response guide. > >>>>>> > >>>>>> John Springer > >>>>>> acting solely on my own behalf > >>>>>> > >>>>>> On Sat, Apr 6, 2019 at 5:10 AM David Huberman > <david.huberman at icann.org <mailto:david.huberman at icann.org>> wrote: > >>>>>> > >>>>>> Sasha, > >>>>>> > >>>>>> The draft CoC is quite excellent. Nice work! I have > completed a > >>>>>> copyediting pass in "suggesting" mode: > >>>>>> > >>>>>> - normalized words to British English spellings (3 > instances of > >>>>>> behavior were changed to behaviour) > >>>>>> - removed contractions > >>>>>> - fixed a few typos > >>>>>> - enforced consistent paragraph spacing > >>>>>> - enforced the Oxford comma > >>>>>> > >>>>>> /david > >>>>>> writing solely on his personal behalf > >>>>>> > >>>>>> On 4/5/19, 7:32 AM, "diversity on behalf of Sasha Romijn" > >>>>>> <diversity-bounces at ripe.net <mailto:diversity-bounces at ripe.net> on > >>>>>> behalf of sasha at mxsasha.eu <mailto:sasha at mxsasha.eu>> wrote: > >>>>>> > >>>>>> Hello all, > >>>>>> > >>>>>> Closely based on the work I did for Write the Docs, > with some > >>>>>> adjustments to fit the RIPE community, I put together a > draft for > >>>>>> a CoC and for a response guide. > >>>>>> > >>>>>> CoC: > >>>>>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1IAJj9UjW2zroz5v6XQYgYEYotfZlV4Trk2vRdaoPaP4_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=sy8t_T8v902B5ESqiOxzVnu6ezEWJaYUIsfScYJuvyY&e= > >>>>>> > >>>>>> Response guide: > >>>>>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1gaLo4axYDRTpQnhUJyG92EHBmEIkxSDN8Urmy-2Dzn9nQ_edit&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=tLYhKXwOC4CmhGYH2JhF4h-Qy6XZgbV4ujIJt5XPyus&e= > >>>>>> > >>>>>> I went with Google docs for now, as it’s quite > accessible. You > >>>>>> can leave comments and suggest changes, and we can discuss > broader > >>>>>> topics on the mailing list. There are a few parts about > structure > >>>>>> still to be filled in, but let’s start here. > >>>>>> We haven’t really spoken about any of the details, > other than > >>>>>> a general “this can be a starting point”, so I don’t know what > >>>>>> kind of discussions other people would like to bring up. > >>>>>> > >>>>>> Sasha > >>>>>> _______________________________________________ > >>>>>> diversity mailing list > >>>>>> diversity at ripe.net <mailto:diversity at ripe.net> > >>>>>> > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.ripe.net_mailman_listinfo_diversity&d=DwIGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=iTOW7nSt3tBCc5xNiHfQNhFilU9Ki9_nVAHGfa3QG5w&m=ag_h5GXVGbSsDgGW59YleMXVaOJnV4ga6CJcCIfZ38A&s=BARWpiMNfao6C_dqEoTNumUx0AVYtnpFY2CTnE4YmwA&e= > >>>>>> > >>>>>> _______________________________________________ > >>>>>> diversity mailing list > >>>>>> diversity at ripe.net <mailto:diversity at ripe.net> > >>>>>> https://lists.ripe.net/mailman/listinfo/diversity > >>>>>> > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> diversity mailing list > >>>>>> diversity at ripe.net > >>>>>> https://lists.ripe.net/mailman/listinfo/diversity > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> diversity mailing list > >>>>> diversity at ripe.net > >>>>> https://lists.ripe.net/mailman/listinfo/diversity > >>>>> > >>>> _______________________________________________ > >>>> diversity mailing list > >>>> diversity at ripe.net > >>>> https://lists.ripe.net/mailman/listinfo/diversity > >> _______________________________________________ > >> diversity mailing list > >> diversity at ripe.net > >> https://lists.ripe.net/mailman/listinfo/diversity > > > > _______________________________________________ > > diversity mailing list > > diversity at ripe.net > > https://lists.ripe.net/mailman/listinfo/diversity > > > > _______________________________________________ > diversity mailing list > diversity at ripe.net > https://lists.ripe.net/mailman/listinfo/diversity -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/diversity/attachments/20190411/5874f2b6/attachment.html>
- Previous message (by thread): [diversity] [Ext] Draft CoC and response guide
- Next message (by thread): [diversity] [Ext] Draft CoC and response guide
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]