Skip to content

doc: Add and modify Offline First code of conduct #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 10 commits into from
Apr 23, 2015
Merged

doc: Add and modify Offline First code of conduct #2

merged 10 commits into from
Apr 23, 2015

Conversation

gee-forr
Copy link
Contributor

OK - here's a first draft. I dunno if you wanna put something in there specifically about recruiters, or if you feel the general harassment points should be sufficient.

My 2c. It's sufficient, as there's a clause around the code of conduct being extended with specific rules for certain channel.s

@gee-forr gee-forr mentioned this pull request Apr 20, 2015
@martincronje
Copy link

Looks cool. Very comprehensive.

Should we tell people where they can get a list of admins to contact if they need to?

It may be worthwhile to mention advertising, recruitment as a separate line-item?

@gee-forr
Copy link
Contributor Author

@martincronje There is a link that tells them where to get the list. Also, what are your suggestions around recruitment?

@kennethkalmer
Copy link
Contributor

This definitely gets my 👍

Thanks @gee-forr for the awesome work! I'll let the channels know, how long should we give for feedback?

@constantm
Copy link

Damn. No more virtual hugs without consent.

@garrensmith
Copy link

This is looking great. We need something about recruitment.

@emilesilvis
Copy link

👍

What are the current thoughts around recruitment and advertising?

Notably the following

 - Included a link to the admins list within the reporting section (as people are likely to scan for a heading and then look for the link).
 - Rearranged order of "we will respond quickly" and "if there's a conflict of interests" to make a bit more sense.
 - Clarified that "in ZA Developers" is "a member of the ZA Developers community"
 - Fixed a logic issue under consequences
 - Added a section allowing for future changes to the code of conduct and suggesting a way to handle making those changes.
@kennethkalmer
Copy link
Contributor

My 2c on the recruitment story is:

  1. Professional recruiters are not welcome, at all
  2. Users don't share the details of others with recruiters without their explicit consent
  3. Advertising an opportunity in brief is acceptable, discussions happen behind the scenes from there
  4. Opportunities should not be blatant referral program links where to poster hopes to earn a commission, this is recruiting.

We should still be able to attract good talent to our teams, and brief messages should allow it. Same goes for new teams, founders should be able to say "We're hiring".

It is a fine line, but definitely (1) & (2) is the most important to me.

@gee-forr
Copy link
Contributor Author

OK - I'll rev the wordsmithing engine up. Stand by for a new commit.

gee-forr and others added 3 commits April 21, 2015 17:03
@kennethkalmer
Copy link
Contributor

#4 is still outstanding, but I don't see that as blocker. Can we get this merged in the meantime?

This is a living document, and I don't want us stuck in this awkward place ;) We need to be in the channels sharing and growing the community.

@kennethkalmer
Copy link
Contributor

Big thanks to @gee-forr & @spartan563 for pouring so much time and effort into this!

@gee-forr
Copy link
Contributor Author

@kennethkalmer no probs. :) Once you're happy with this, merge it back to #2 and I'll add a TL;DR. After that, I think we should publish.

@kennethkalmer
Copy link
Contributor

@gee-forr I added the TL;DR already, have a look :)

@gee-forr
Copy link
Contributor Author

NICE! May I have the honour of merging?

gee-forr added a commit that referenced this pull request Apr 23, 2015
doc: Add and modify Offline First code of conduct.
@gee-forr gee-forr merged commit e53e564 into master Apr 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants