Thanks Russ, I assumed as much, having read https://www.djangoproject.com/conduct/changes/.
------------------------------------------------------------------------------------------ Perhaps Daniele's keynote talk at Djangocon this year, combined with the already very good Django code of conduct, caused me to assume too much of this community's progression towards appreciating both the need of diversity in tech and the actual conditions required to bring that about. Benjamin, you asked if there is an actual problem that needs solving. Yes. Absolutely. It is a systemic one within the world of software development and I am excited to be a part of a particular software development community that is taking proactive steps towards the goal of a safe, supportive environment for *everyone *who is working towards that same goal. The quality of our software will reflect the quality of our community. Here is just a tiny sample of reading for any who are interested in learning why these kinds of policies are so important: 1. See the recent case of Anita Sarkeesian, which is one sort of situation I have in mind when writing down a policy such as this: https://twitter.com/femfreq/status/504718160902492160/photo/1 http://www.washingtonpost.com/news/morning-mix/wp/2014/08/29/gaming-vlogger-anita-sarkeesian-is-forced-from-home-after-receiving-harrowing-death-threats/ 2. http://modelviewculture.com/pieces/abuse-as-ddos, including this bit: "Just like with computer security, you should have plans in place to identify and address attacks. At conferences, user groups, and other events, this can take the form of a code of conduct along with a policy for enforcement. In workplaces, this often takes the form of an employee handbook. These types of policies help mitigate attacks when they happen, so that decisions don’t have to be made on the fly when something goes wrong. These policies are far from perfect fixes for everything, but they’re better than doing nothing." 3. http://modelviewculture.com/pieces/the-open-source-identity-crisis. By the way, I'm proud that the one time this author links to something django-related, it's this situation <http://geekfeminism.wikia.com/wiki/Django_primary-replica_terminology_patch_dispute> in which the core devs wisely and quickly made the right choice. On Monday, September 8, 2014 9:37:16 PM UTC-4, Russell Keith-Magee wrote: > > Hi Kevin, > > Thanks for these suggestions. > > By way of settings expectations - a patch of this nature has a little more > procedural overhead than a normal patch, because it requires a change to > our community policies. Regardless of the merit (or otherwise) of a > specific proposal, a change to these policies needs to be ratified by the > core team and the DSF membership before it goes into effect. > > Discussions on the ticket itself from people outside those groups is > definitely welcome - the broader opinion and attitudes of the community > will be considered as part of the ratification process. But it's not > something that a small group of people can quickly agree on and commit. > > Russ %-) > > > On Sun, Sep 7, 2014 at 9:10 AM, Kevin Daum <kevin...@gmail.com > <javascript:>> wrote: > >> I have submitted two pull requests for the code of conduct: >> >> - #84 <https://github.com/django/djangoproject.com/pull/84>, to let >> folks who belong to a wide variety of social identities know that yes, >> even >> they are welcome here, and >> - #86 <https://github.com/django/djangoproject.com/pull/86>, to make >> explicit the currently implicit policy that someone's abusive behavior >> outside the django community *may* have an adverse effect on their >> ability to participate within the django community. >> >> I welcome your feedback. >> >> Thanks, >> Kevin Daum >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/0633ea6c-c973-4cb0-bf94-60d045c608ea%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/0633ea6c-c973-4cb0-bf94-60d045c608ea%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/8511aebc-fef2-462c-90f4-92d6ad3337f0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
