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]/
[diversity] RIPE Code of Conduct 2.0
- Previous message (by thread): [diversity] RIPE Code of Conduct 2.0
- Next message (by thread): [diversity] RIPE Code of Conduct 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Amanda Gowland
agowland at ripe.net
Mon Jul 29 10:24:25 CEST 2019
Fully agree with Brian, I think, the idea of having 'enforcement' in our community is a trigger in general and the instinct is to push against it. And there is definitely the very real fear that if there's an implicit expectation that 'we'll all do our best to make sure bad actors are stopped', then we could get into a situation where no one acts because they assume someone else must have already done. Would it help if I went over the documentation that Sasha has sent through and draft a proposal/call for volunteers/scope for a CoC Team to review now? a On 29/07/2019 10:12, Brian Nisbet wrote: > So, I've been looking at this again, and reading the various comments and it's my impression that the sticking point is the enforcement, because we seem to agree on everything else? > > I mean, text that says "please call things out, don't be a bystander" is easy and fine, I think? But it also does not solve the problem. > > I think the core point here is that change is made and that asking everyone to do something will not be that change. So I fully agree we need some sort of group, as other communities have put in place, and I don't think spending a long time trying to gather data is the right way to go. Mostly because I think we have that data already. > > We are engineers, we can iterate, we can put this group together and if it fails, we can take it away again. I think we fool ourselves, as humans, into thinking that someone once there must always be there. Working Groups have changed, have gone away, lots of other structures and pieces of the RIPE Community have changed and will continue to change. > > So rather than continuing to try to see what's happening and then act, I very strongly suggest we act and then see what happens. We are a very strong community, we can take a little risk, so to speak. > > 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 > >> -----Original Message----- >> From: diversity <diversity-bounces at ripe.net> On Behalf Of Sasha Romijn >> Sent: Friday 19 July 2019 13:38 >> To: diversity at ripe.net >> Subject: Re: [diversity] RIPE Code of Conduct 2.0 >> >> Hello all, >> >> This thread has been quiet for a month now. How do we move forward with >> this? >> >> Sasha >> >> _______________________________________________ >> diversity mailing list >> diversity at ripe.net >> https://mailman.ripe.net/ > _______________________________________________ > diversity mailing list > diversity at ripe.net > https://mailman.ripe.net/ >
- Previous message (by thread): [diversity] RIPE Code of Conduct 2.0
- Next message (by thread): [diversity] RIPE Code of Conduct 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]