You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
I wasn't aware of the related discussion in the certbot project. I'm sure the EFF will want to use the same code of conduct across all of their projects.
Sorry for the delay, this is still caught in internal process. As much as I'd like this today, it is something that we'd like to do right the first time instead of rush through.
Hi @jeremyn -- I got to speak with someone who's working on the Code of Conduct effort at EFF and it's still in internal process there. I'm sorry for the wait (and I personally helped introduce a code of conduct in a previous community so I'm also looking forward to the CoC when it's ready). Thanks for checking.
@dannyob It's not clear to me from your comment, but is there going to be a window where we can give feedback and hope to have that feedback taken into account? For example if you release a draft CoC for comments at the end of March, and someone has serious concerns, will you realistically be able to modify the draft CoC based on those concerns before April 26th?
@epicminecrafting oh so many lawyers @jeremyn yep there will, though I anticipate that will center more around comments and instructions about how best to put the code into practice. If it all becomes greatly hectic, I'll just let that process take as much time as it takes, and concentrate on finishing a separate event process instead.
I mentioned the Aprl date to reassure the very patient watchers of this issue that I do have some kind of internal deadline now. I also anticipate things moving a lot more quickly, but you may have heard that from me before...
Update! We've got a small bit of wording to craft, and should have something more to offer in a couple of weeks. Thank you for your fantastically high levels of patience and tolerance.
Okay folks, here's our the preliminary text of the code, as filtered through many internal discussions, wrangling, and probably not quite enough proof-reading.
I'm putting this here so that all of you who have been following this issue for so long can have a chance to see and comment on a preview. As I said, oh so many comments ago, it is at heart same as the Rust CoC. I'm happy to answer questions, but because this has taken so long, and because there were sometimes fairly intricate and context-dependent reasons for any alterations we made, please be tolerant of me if I have to dive back into my notes or am imperfect in explaining fully those intricacies the first time around.
I think one thing I'll note off the bat is that despite being filtered through lawyers, this is not a very legalistic document. This is deliberate: EFF, more than most I hope, understands the limits and challenges to spelling out every possible "if" and "but" for good or bad conduct in a single document; and how much how communities are built on understanding and acting on the spirit of the unwritten rules that bind us, not by consulting an external definitive text.
Also: if you're hoping to run this code through an emulator, and then throw at it some edge cases ("What happens if I post an insult so long that it buffer overwrites this code of conduct's stack and personally attacks someone in the next github repo but one?"), you're probably better off thinking "what is the common sense answer to this question?", and assume we'll do that. It's really about giving people a feel for what's okay and what's not, not being a perfect guide to edge-cases. That's what humans (or human-level AIs) are for.
Thanks @Bisaloo -- the markdown was autogenerated by Pandoc, whose defaults seems to be pretty enthusiastic when it comes to escaping characters. I'll make sure the final version is a bit more readable.
@dannyob, maybe you're already planning to do this but I think it would be good to have some information about the Code of Conduct team. In particular, I think it would be important for users to know that the person they might be reporting is not in the Code of Conduct team. Or at least, it would provide them with a way to contact someone else from the team (if email addresses of the individual team members are provided).
If you already planned to do this, good job! If not, I definitely think it would be a worthwhile addition.
@Bisaloo yep, that's the plan. We'll put this info on the contact web page.
@pipboy96 hey! so as you can probably guess from the dates on this issue, we've had this in draft form for quite a while now, and it's not something that's really amenable to the line-by-line patching of a github repo. We're more at the stage of putting it out to explain why some things are worded the way they are, rather than re-writing and then sucking it back into EFF vortex for more endless process.
Activity
jeremyn commentedon Jun 27, 2017
I'm not @Hainish but I agree with having a code of conduct. The Contributor Covenant looks pretty good and has traction in major projects.
jeremyn commentedon Jun 27, 2017
I wasn't aware of the related discussion in the certbot project. I'm sure the EFF will want to use the same code of conduct across all of their projects.
Hainish commentedon Jun 27, 2017
This is going through internal process at EFF currently.
jeremyn commentedon Oct 28, 2017
@Hainish What's the status of this at the EFF?
Hainish commentedon Oct 31, 2017
Sorry for the delay, this is still caught in internal process. As much as I'd like this today, it is something that we'd like to do right the first time instead of rush through.
jeremyn commentedon Nov 1, 2017
@Hainish Does this mean that there is a draft version of a code of conduct being actively discussed internally at the EFF?
Hainish commentedon Nov 1, 2017
I'm not sure, @andresbase might know
andresbase commentedon Nov 1, 2017
Yes there is, and we hope to publish it soon. We'll update you when we do.
jeremyn commentedon Nov 1, 2017
@Hainish and @andresbase: great, thanks for the information.
jeremyn commentedon Nov 19, 2017
@Hainish , @andresbase Just checking in, what's the status here?
brainwane commentedon Nov 28, 2017
Hi @jeremyn -- I got to speak with someone who's working on the Code of Conduct effort at EFF and it's still in internal process there. I'm sorry for the wait (and I personally helped introduce a code of conduct in a previous community so I'm also looking forward to the CoC when it's ready). Thanks for checking.
14 remaining items
jeremyn commentedon Mar 9, 2018
@dannyob It's not clear to me from your comment, but is there going to be a window where we can give feedback and hope to have that feedback taken into account? For example if you release a draft CoC for comments at the end of March, and someone has serious concerns, will you realistically be able to modify the draft CoC based on those concerns before April 26th?
dannyob commentedon Mar 9, 2018
@epicminecrafting oh so many lawyers
@jeremyn yep there will, though I anticipate that will center more around comments and instructions about how best to put the code into practice. If it all becomes greatly hectic, I'll just let that process take as much time as it takes, and concentrate on finishing a separate event process instead.
I mentioned the Aprl date to reassure the very patient watchers of this issue that I do have some kind of internal deadline now. I also anticipate things moving a lot more quickly, but you may have heard that from me before...
dannyob commentedon Mar 31, 2018
(Status update: currently with lawyers, really still looking like Rust's CoC, so take a look at that if you'd like to get ahead of the curve)
jeremyn commentedon Aug 11, 2018
@dannyob What is the current status of having a Code of Conduct, please?
Bisaloo commentedon Sep 17, 2018
Echoing @jeremyn's question: is this still on the roadmap? Could we get an update please?
dannyob commentedon Sep 25, 2018
Update! We've got a small bit of wording to craft, and should have something more to offer in a couple of weeks. Thank you for your fantastically high levels of patience and tolerance.
dannyob commentedon Dec 4, 2018
Okay folks, here's our the preliminary text of the code, as filtered through many internal discussions, wrangling, and probably not quite enough proof-reading.
I'm putting this here so that all of you who have been following this issue for so long can have a chance to see and comment on a preview. As I said, oh so many comments ago, it is at heart same as the Rust CoC. I'm happy to answer questions, but because this has taken so long, and because there were sometimes fairly intricate and context-dependent reasons for any alterations we made, please be tolerant of me if I have to dive back into my notes or am imperfect in explaining fully those intricacies the first time around.
I think one thing I'll note off the bat is that despite being filtered through lawyers, this is not a very legalistic document. This is deliberate: EFF, more than most I hope, understands the limits and challenges to spelling out every possible "if" and "but" for good or bad conduct in a single document; and how much how communities are built on understanding and acting on the spirit of the unwritten rules that bind us, not by consulting an external definitive text.
Also: if you're hoping to run this code through an emulator, and then throw at it some edge cases ("What happens if I post an insult so long that it buffer overwrites this code of conduct's stack and personally attacks someone in the next github repo but one?"), you're probably better off thinking "what is the common sense answer to this question?", and assume we'll do that. It's really about giving people a feel for what's okay and what's not, not being a perfect guide to edge-cases. That's what humans (or human-level AIs) are for.
preamble
code
reporting guidelines
Bisaloo commentedon Dec 4, 2018
Thank you for the update @dannyob!
A very technical (and very minor) issue: URLs in markdown should be enclosed in
<url>(source). So I would write:**Contact**: *<email@eff>*<https://www.bolderadvocacy.org/wp-content/uploads/2018/06/Election_Checklist_for_501c3_Public_Charities.pdf>*<email@eff>*<https://github.com/EFForg>(I've redacted the email address just in case)
My text editor gets confused by backslash escaped characters in the current version.
dannyob commentedon Dec 4, 2018
Thanks @Bisaloo -- the markdown was autogenerated by Pandoc, whose defaults seems to be pretty enthusiastic when it comes to escaping characters. I'll make sure the final version is a bit more readable.
Bisaloo commentedon Mar 4, 2019
@dannyob, maybe you're already planning to do this but I think it would be good to have some information about the Code of Conduct team. In particular, I think it would be important for users to know that the person they might be reporting is not in the Code of Conduct team. Or at least, it would provide them with a way to contact someone else from the team (if email addresses of the individual team members are provided).
If you already planned to do this, good job! If not, I definitely think it would be a worthwhile addition.
pipboy96 commentedon Mar 17, 2019
@dannyob Can you publish this draft in a GitHub repo so it can be publicly discussed for some time before being enforced for all EFF projects?
dannyob commentedon Apr 3, 2019
@Bisaloo yep, that's the plan. We'll put this info on the contact web page.
@pipboy96 hey! so as you can probably guess from the dates on this issue, we've had this in draft form for quite a while now, and it's not something that's really amenable to the line-by-line patching of a github repo. We're more at the stage of putting it out to explain why some things are worded the way they are, rather than re-writing and then sucking it back into EFF vortex for more endless process.
pipboy96 commentedon May 9, 2019
🎉