code-of-conduct icon indicating copy to clipboard operation
code-of-conduct copied to clipboard

Published 20 hours ago • verified publisher icon rubyberlin

Change process

Open PragTob opened this issue 10 years ago • 3 comments

We need a change process for our code of conduct.

When we want to add something, remove or hugely reformulate there are a couple of steps that need to be taken, this is an idea (can be improved) of what that probably entails:

  • Formulate a change idea and probably a first version in English as a pull request
  • Inform all involved parties (I guess most of all other meetups who signed this CoC) of the incoming addition and invite them to collaborate and discuss
  • We need some method of finding an agreement or a point where we say, nah we do this and bump the version
  • Afterwards we need to contact translators to add translations in our supported languages

What do we need to accomplish this?

  • [ ] Versioning, see #7 we need to have all versions accessible
  • [ ] List/contact information of translators (right now I know most of them personally, so it's not THAT important)
  • [ ] A change process/idea for one (see above)
  • [ ] easier accessible list of the emails of meetup organizers (just need to extract them from the json, we have that)

Input highly welcome.

From the community, for the community. For an open, welcoming, inclusive and steadily improving tech community.

Cheers, Tobi

PragTob avatar Feb 05 '15 23:02 PragTob

For the list of authors, thanks to git we have a blame list :dancers:

I really like the idea of involving the other meetups and finding a point in between. It might also happen that most people agree on something, but others don't, which I guess is fine too.

eljojo avatar Feb 06 '15 08:02 eljojo

How can YOU help here?

  • Give feedback on the change process
  • implement a mechanism for versioning (e.g. orgs may support different versions of the coc) as well as different versions of the coc available and then PR :) Also just part of that.
  • create files with contact information so we can contact relevant people

Thanks :heart:

PragTob avatar Mar 25 '15 22:03 PragTob

the other day I thought that having a TRANSLATORS.md, COLLABORATORS.mdor RESPONSIBLES.md (or something like that) file with contact information for the translators would help with the second point.

I guess some text file would do the job, or maybe a json file so it could be parsed automatically. oh and maybe some raketask that sends them an email whenever there's a change to the official (I guess) english version. :dancers:

eljojo avatar Mar 29 '15 21:03 eljojo