On Thu, Sep 11, 2014 at 6:11 AM, Andrew Pinkham wrote:
> Hi,
> I am not qualified enough to express an opinion on the matter of the DCoC.
> However, I have a few questions:
>
> - Have we consulted a psychologist or a specialist on the topics of
> community inclusion and protection? Their knowledg
On Sep 10, 2014, at 4:21 PM, Malte wrote:
> That's a lot of locales to change though. I am still somewhat new to Git. How
> would you go about it?
I asked about Git recently on the Django Core Mentorship list. Carl Meyer
responded with a really good workflow for creating a PR. I have copied key
Hi,
I am not qualified enough to express an opinion on the matter of the DCoC.
However, I have a few questions:
- Have we consulted a psychologist or a specialist on the topics of community
inclusion and protection? Their knowledge/research could be instrumental in
determining the best way to w
On Wednesday, 10 September 2014 22:21:39 UTC+1, Malte wrote:
>
> That's a lot of locales to change though. I am still somewhat new to Git.
> How would you go about it?
>
Oddly, I came to the same conclusion last night that seconds should be
removed and was just contemplating writing a pull req
Hi Anssi,
My only concern about pushing the DEP and formally numbering it is that we
haven't fully worked out what our DEP process *is* yet. I'm still
recovering from DjangoCon US jet lag, but once that has worn off, I've got
some ideas about how we can use the DEP process and the technical board
Hi Wim,
That's a lot of locales to change though. I am still somewhat new to Git.
How would you go about it?
On Wednesday, September 10, 2014 10:18:04 PM UTC+2, Wim Feijen wrote:
>
> Hi Malte,
>
> Sounds like a good idea to remove the seconds. Aymeric says the same.
>
> Can you open a ticket an
Hi Malte,
Sounds like a good idea to remove the seconds. Aymeric says the same.
Can you open a ticket and if you want create a pull request?
Wim
On Wednesday, 10 September 2014 18:26:11 UTC+2, Malte wrote:
>
> Hi Aymeric,
>
> Yes, I agree. And backwards compatibility is a concern I share. But
On Wednesday, September 10, 2014 10:39:51 AM UTC-4, Josh Smeaton wrote:
>
> Kevin,
>
> > It simply says, in deliberately vague language, that if a member of the
> Django community is treated abusively by another member of the Django
> community _outside_ a Django forum and that abuse is reporte
Benjamin,
1. It's not a zero-tolerance policy, and it never has been. So all of your
arguments based on that idea are null and void.
2. The only instance of "abuse" of the policy relates to behavior that was
inappropriate even given cultural differences. Just because you don't
understand somethin
Hi Josh,
I agree with and understand your sentiments. However, you are basically
arguing that since we cannot count on the common sense of the user
community to behave professionally in professional environments, we must
therefore count on the commonsense of TPTB who will enforce a speech and
Hi Aymeric,
Yes, I agree. And backwards compatibility is a concern I share. But as it
is right now, time output is not very useful if it includes seconds.
Few people will state:
"Posted on 10.9.2014 20:45:29".
--
You received this message because you are subscribed to the Google Groups
"Djang
Hi Aymeric,
Yes, I agree. And backwards compatibility is a concern I share. But as it
is right now, time output is not very useful if it includes seconds.
Few people will state:
"Posted on 10.9.2014 20:45:29".
On Wednesday, September 10, 2014 6:10:44 PM UTC+2, Aymeric Augustin wrote:
>
> While
While there are some backwards compatibility concerns, I believe option 1
is better:
- It provides consistency out-of-the-box for international websites.
- It makes the default behavior more reasonable in general.
--
Aymeric.
2014-09-10 17:56 GMT+02:00 Malte :
> Hi!
>
> I recently contributed
Hi!
I recently contributed the zh_CN, zh_TW, zh_Hans and zh_Hant locale
formats. These locale formats enable dates and times to be formatted
correctly in a given locale. While doing this, I noticed different authors
have very different ideas of how time should be displayed, in particular,
some
On Wed, Sep 10, 2014, Josh Smeaton wrote:
>Perhaps the wording could then be closer to the intent. Something like "if
>a member of the Django community is treated abusively by another member of
>the Django community outside of a Django forum, and is reported, it will
>warrant investigation and
Kevin,
> It simply says, in deliberately vague language, that if a member of the
Django community is treated abusively by another member of the Django
community _outside_ a Django forum and that abuse is reported to the
conduct committee, the committee will not reject the report outright simply
Benjamin (and all others still paying attention),
I love the Django code of conduct. It's not perfect but it's quite good.
How does a person who claims one or even many historically marginalized
identities know that the Django community is a safe place for them without
a published and enforced
Ben,
I know you haven't advocated the removal of the CoC (or #84 for that
matter), but you've questioned speech and behaviour limitations upthread,
so I thought I would include my thougths of a CoC in general.
Just because the code of conduct hasn't been used for intervention
(forgetting the o
(I found I've said "correct me if I'm wrong" in nearly every paragraph I've
written - so please, correct anything below that you don't agree with)
I've been wanting to stay out of this conversation because, as Aymeric put
it, it is a very sensitive topic. But I've got a few things to say.
It se
I plan to push the DEP as draft to the django/deps repository. The DEP
will be DEP number 2.
DEP 2 will need to be accepted or rejected eventually. Before that it
doesn't have any official status.
I am planning to do the push as this way it is easier to work on it
collaboratively. There is a lot
20 matches
Mail list logo
