Confluence and Jira are slow regardless of the distance between you and the
data center. They’re bloated.
On Tue, May 14, 2019 at 18:59, Justin Mclean
wrote:
> Hi,
>
> What has seem to worked on some of the non-English background projects
> I’ve mentored:
> - Encourage to PPMC to ask people
Hi,
What has seem to worked on some of the non-English background projects I’ve
mentored:
- Encourage to PPMC to ask people to communicate in English if they can
- Encourage to PPMC to ask people to provide a translation along with their
original email either by someone else or a machine
F%2Fwiki.debian.org%2FAntiHarassmentdata=02%7C01%7Caharui%40adobe.com%7Cdc1f83c5db3244143ce408d6d8a7fb19%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636934613329848952sdata=oCyzofhBdkgB0G1vPwYvya7ErMDEiSuyG38ex2m3zWs%3Dreserved=0
>
> ________________
> From:
so sharing some resources from Debian's Anti-Harrassment team Wiki page
[1]
[1] https://wiki.debian.org/AntiHarassment
From: Alex Harui
Sent: Tuesday, May 14, 2019 9:46 AM
To: diversity@apache.org
Subject: Re: [FAQ] Proto-FAQ question 1
IMO, we can come
On 14/05/2019 17:46, Alex Harui wrote:
> When I see a post in non-English on the lists of the projects I participate
> in, I shove it into Google Translate. It works well enough to give me an
> idea of what the post is about. If I thought it was important, I would copy
> the English
m Debian's Anti-Harrassment team Wiki page
[1]
[1] https://wiki.debian.org/AntiHarassment
From: Alex Harui
Sent: Tuesday, May 14, 2019 9:46 AM
To: diversity@apache.org
Subject: Re: [FAQ] Proto-FAQ question 1
IMO, we can come up with a way to support n
IMO, we can come up with a way to support non-English official communication
channels. We have to try to make it clear to as many people as possible that
it is ok to write an email in your native language on dev@ and users@. We
could decide that private@ is the air-traffic-controller channel
This is something that's been on my mind a lot recently.
We can't come up with a way to support non-English official
communication channels for the Foundation as Bertrand mentions, but if
we don't allow non-official channels in other languages, as the saying
goes, "the Internet will route
It has been interesting to me how important words are in these discussions. In
this case, the word "fix". We may not be able to "fix" as in "eliminate" the
requirement to communicate in English, but I believe we can and should
encourage communities to choose their words more carefully so that
Patricia Shanahan wrote on 5/13/19 4:13 PM:
> The first and most important question is something along the lines of:
>
> --
>
> Q: Apache does everything by e-mail. I do not know or care about the
> race, ethnicity, gender, age, weight,
On Tue, May 14, 2019 at 3:09 PM Daniel Gruno wrote:
> ...It's like democracy - while not perfect, it is (I would say) the least
> sucky way of ensuring fairness, openness and proper governance, as it is
> the most universal (and de facto standard) language we have..
+1
> I do not see the need
On 14/05/2019 08.59, Bertrand Delacretaz wrote:
On Tue, May 14, 2019 at 2:49 PM Justin Mclean wrote:
...we’ve asked them to speak English on the mailing lists, so we could ask them
what that experience
was like and if anyone felt excluded...
I'm sure the requirement to use English does turn
On Tue, May 14, 2019 at 2:49 PM Justin Mclean wrote:
> ...we’ve asked them to speak English on the mailing lists, so we could ask
> them what that experience
> was like and if anyone felt excluded...
I'm sure the requirement to use English does turn some people away.
If that's not your native
Hi,
> Active contributors to Apache software have to be fluent, reading and
> writing, in written English.
Over the last couple of years we had a number of projects (about a dozen)
donated from China and we’ve asked them to speak English on the mailing lists,
so we could ask them what that
From this point of view, we have a really strong exclusion that is more
likely to be relevant to software use than e.g. gender.
Active contributors to Apache software have to be fluent, reading and
writing, in written English.
On 5/13/2019 9:41 PM, Kenneth Knowles wrote:
I alluded to this
Answer N: the numbers show that our community is overwhelmingly male. This
implies that we are somehow, perhaps unintentionally, excluding half of the
planet. We would like to find out why and fix it. This doesn't mean that we
can fix the whole industry but we can make our corner of it a little
Most of the points in my draft were about inclusion, making sure
everyone feels welcome. This is directly about diversity as a benefit in
its own right.
On 5/13/2019 9:41 PM, Kenneth Knowles wrote:
I alluded to this elsewhere, but I would welcome feedback on whether this
perspective is
I alluded to this elsewhere, but I would welcome feedback on whether this
perspective is relevant. It hinges on whether the ASF's mission is to
provide software *that is a public good* in the technical economics sense
(non-excludable non-rivalrous) or software *for the public good* (aka the
I think the point was not that the FAQ needed those things, but the ASF
at large :D and that the different way of phrasing it was intended to
draw attention to all of those things.
-Joan
On 2019-05-13 6:45 p.m., Patricia Shanahan wrote:
I would love truly elegant documentation. However, I am
The "Open Source Diversity" site[1] that Shane mentioned elsethread led me
to the "Contributor Covenant" site[2] which also has a FAQ[3] which, in my
limited experience, seems pretty good and is "CC BY 4.0 License" [4]
Niall
[1] https://opensourcediversity.org/
[2]
I would love truly elegant documentation. However, I am neither a
Confluence expert nor a graphic designer. As you say, it needs a community.
Perhaps people who are good at graphic design could create frameworks
for the FAQ and Resources? Should each of them, long term, be Wiki pages
or pages
On 13/05/2019 18.03, Matt Sicker wrote:
This might be slightly inflammatory, but how about this: do you want
non-shitty documentation? How about graphics and logos? Maybe a nice
website? Or some helpful users for support? Hard to do without community!
I'd add non-shitty code to that as well
This might be slightly inflammatory, but how about this: do you want
non-shitty documentation? How about graphics and logos? Maybe a nice
website? Or some helpful users for support? Hard to do without community!
On Mon, May 13, 2019 at 15:14, Patricia Shanahan wrote:
> The first and most
The first and most important question is something along the lines of:
--
Q: Apache does everything by e-mail. I do not know or care about the
race, ethnicity, gender, age, weight, or any other personal
characteristics of other
24 matches
Mail list logo
