Re: [Register] Allyship workshop for open source communities

[Aizhamal Nurmamat kyzy]

The Allyship workshop for open source communities is scheduled for next
week Thursday Sep 16th!

If interested, sign up via
https://docs.google.com/forms/d/1DM7KNyd7QQKiCRrepQTIDAChvtC6QERCt1JUNO5R3Fc/edit

Feel free to forward to other communities that might be interested. Thanks
a lot!

On Sun, Aug 22, 2021 at 11:38 AM Michael Sokolov  wrote:

> Thanks for the invitation. I'm interested, but will be unavailable on
> that day. Please do let us know if another opportunity comes around
>
> -Mike
>
> On Fri, Aug 20, 2021 at 1:03 PM Aizhamal Nurmamat kyzy
>  wrote:
> >
> > Hi everyone,
> >
> > I am helping to organize an allyship training for open source
> contributors
> > sponsored by Google's OSPO. Few folks have expressed interest in this
> > workshop, so I am extending the invite to all of you.
> >
> > Workshop date: Thursday, September 16th, 2021 at 8:30am PST or 5:30 PM
> > CEST.
> > Please register by filling out the form linked below[1]
> >
> > Here are more details:
> >
> > The training led by Dr. Kim Tran (https://www.kimtranphd.com/) aims to
> > position people of color and those in solidarity with us to develop the
> > necessary skills to build bridges across race, ability, gender, sexuality
> > and class.
> >
> > Participants will leave:
> > - With the capacity to identify marginalization in real time in the open
> > source community
> > - Knowing how to address and respond to marginalization at individual and
> > systemic levels
> > - With a strong, critical understanding of the allyship framework
> > - Intersectional lenses, examining dynamics around gender, class, ability
> > and race
> > - A toolkit for recognizing and combating marginalization in real time
> >
> > Format:
> > - Large groups will engage in a *90 minute*, remote learning session.
> > - Participants will be capped at 45 to enable engaging interactive
> > participation and responsiveness to participant questions and concerns.
> > - Session will include webinar style portion as well as breakouts for
> > hypothetical scenarios.
> >
> >
> > [1]
> >
> https://docs.google.com/forms/d/1DM7KNyd7QQKiCRrepQTIDAChvtC6QERCt1JUNO5R3Fc/edit
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [DISCUSSION] Do we have any ideas, initiatives or tools to help non English speakers contribute to ASF projects?

[Phillip Tröller]

Hey, i dont even know if im doing this right but here is my story. Or actually 
the missing story is the interesting part. Ill make it short, because im not 
prepared for this message.


I "worked" the last 2 weeks (and 5 years before that) on a topic that HUGELY 
involves language AI and ... me.

Long story short:
Based on my EXPERIENCE which is neither written down nor scientific i would 
maybe start to think out of the box/scope/policies and start working on 
!unifying, all that bad worded but heighly valuable contant! In a (new) 
language that everybody understands, if he just stays a while and listens.

Holen Sie sich Outlook für Android

From: Sharan Foga 
Sent: Thursday, September 9, 2021 8:17:18 PM
To: dev@community.apache.org 
Subject: Re: [DISCUSSION] Do we have any ideas, initiatives or tools to help 
non English speakers contribute to ASF projects?

Hi Willem

Sorry for the delayed response - and thanks very much for the feedback.

The ALC have been an excellent way to reach out the different communities 
around the world in their local language, and I think this will always be a 
very strong way to attract new people. Unfortunately the pandemic has stopped 
in person events and meetups, but keeping the communication active via Podcasts 
etc as you are doing will definitely help.

Thanks for the ideas and suggestions, and it is also good to see how you are 
working to mix the languages to reach even more people. It is great to see how 
people are trying different steps to improve the experience for others :-)

I think the online format of ApacheCon has given us more flexibility and 
options for having sessions in other languages - and (Rich please correct me if 
I am wrong:-) my understanding is that the HopIn platform used for ApacheCon 
could be made available to projects who want to hold a project specific online 
event.  That means that projects with communities that have multiple languages 
could possibly look at staging smaller targeted multi language events.

Thanks again for sharing!
Sharan


On 2021/08/29 23:52:53, Willem Jiang  wrote:
> Hi Sharan,
>
> Thanks for bring this top up. It's a common case that we are facing
> for the Apache projects from China.
> In the yesterday's ALC Beijing Podcast[1] recording, we have the
> similar disussion when talking about build up the community in ASF.
> The solution could be leveraging the free translation services[2][3]
> to compose the questions or check the answers, and we are also try to
> build the local community by encouraging voluteers to translate the
> policy documentations[4].
>
> Using English in the Open Source world could help us get touch with
> more audices, we are try our best to encourage the contributor to use
> English when they are writing emails, have public discussion in github
> issues.
>
> When we hold the local meetup we prefer to use Chinese, but when we
> talk about the issue and PRs we perfer to use English.
> In ApacheCon Asia 2021[5]，we got 50% Chinese sessions and 50% English
> sessions and we have the Chinese version of website to open up the
> local market,  I think this is banlance we choose now.
>
> [1]https://www.ximalaya.com/keji/37853515/
> [2]https://www.deepl.com/
> [3]https://translate.google.com
> [4]https://github.com/alc-beijing/translation
> [5]https://www.apachecon.com/acasia2021/
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Aug 30, 2021 at 1:13 AM Sharan Foga  wrote:
> >
> > Hi All
> >
> > Recently I heard about an incident where a potential contributor wanted to 
> > contribute something to an ASF project but had found it difficult to 
> > interact because of the language barrier. They had very limited English 
> > skills.
> >
> > I'd like to start a discussion to get some ideas around what we could do in 
> > general to encourage or help people who may find it hard to become involved 
> > at the ASF because of language.
> >
> > I seem to remember that the latest ASF D&I Survey had some findings around 
> > language confidence and that it had sometimes acted as a barrier for new 
> > contributors. Do we have any plans, initiatives or existing tools that 
> > could help with this?. It would be great to get some feedback from anyone 
> > that has experienced this language barrier and discuss what could be done 
> > to improve the situation and help others.
> >
> > Does anyone have any comments, suggestions or ideas? I'd like to hear them. 
> > Please join the conversation and let's see what can be done.
> >
> > Thanks
> > Sharan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@co

[jira] [Created] (COMDEV-425) Reporter tool's "Busiest GitHub topics" is missing "lucene" for Lucene project

[Michael McCandless (Jira)]

Michael McCandless created COMDEV-425:
-

 Summary: Reporter tool's "Busiest GitHub topics" is missing 
"lucene" for Lucene project
 Key: COMDEV-425
 URL: https://issues.apache.org/jira/browse/COMDEV-425
 Project: Community Development
  Issue Type: Bug
  Components: Reporter Tool
Reporter: Michael McCandless
 Attachments: Screen Shot 2021-09-09 at 5.34.16 PM.png

I am working on the quarterly board report for Apache Lucene, and noticed under 
the "Community Health" section that the "Busiest GitHub topics" seems to be 
missing the "lucene" GitHub repository.

It seems to contain only {{lucene-solr}}, {{lucenenet}}, {{lucene-site}}.

Likely something needs to be updated because Solr split out of Lucene, and 
Lucene's main (to be 9.0 release soon) branch is on a new(-ish) {{lucene}} 
repository: [https://github.com/apache/lucene]

!Screen Shot 2021-09-09 at 5.34.16 PM.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Conscious Language Checker Tool Being Developed

[Sharan Foga]

Hi All

I'm posting this here as it is sort of related to my thread around tools that 
could help with language.

A new tool is currently being developed under our  D&I project that is called 
the Conscious Language Checker that can scan Apache projects repos, code and 
highlight potential words that could be potentially inappropriate or may cause 
offence. Like any ASF project the tool is under development and the first 
version of it is getting a range of feedback. 

If you want to learn a bit more about the tool, help to develop it or simply 
want to join the conversation - the discussion is happening over the 
d...@diversity.apache.org and here is a link to the discussion thread 
https://s.apache.org/r57ba

If you are interested in taking a look at the tool dashboard - here is the 
link: https://clc.diversity.apache.org/ 

My understanding is that projects can opt in if they want their results to be 
included so please feel free to join the conversation.

Thanks
Sharan

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [DISCUSSION] Do we have any ideas, initiatives or tools to help non English speakers contribute to ASF projects?

[Sharan Foga]

Hi Willem

Sorry for the delayed response - and thanks very much for the feedback.

The ALC have been an excellent way to reach out the different communities 
around the world in their local language, and I think this will always be a 
very strong way to attract new people. Unfortunately the pandemic has stopped 
in person events and meetups, but keeping the communication active via Podcasts 
etc as you are doing will definitely help. 

Thanks for the ideas and suggestions, and it is also good to see how you are 
working to mix the languages to reach even more people. It is great to see how 
people are trying different steps to improve the experience for others :-)

I think the online format of ApacheCon has given us more flexibility and 
options for having sessions in other languages - and (Rich please correct me if 
I am wrong:-) my understanding is that the HopIn platform used for ApacheCon 
could be made available to projects who want to hold a project specific online 
event.  That means that projects with communities that have multiple languages 
could possibly look at staging smaller targeted multi language events. 

Thanks again for sharing!
Sharan


On 2021/08/29 23:52:53, Willem Jiang  wrote: 
> Hi Sharan,
> 
> Thanks for bring this top up. It's a common case that we are facing
> for the Apache projects from China.
> In the yesterday's ALC Beijing Podcast[1] recording, we have the
> similar disussion when talking about build up the community in ASF.
> The solution could be leveraging the free translation services[2][3]
> to compose the questions or check the answers, and we are also try to
> build the local community by encouraging voluteers to translate the
> policy documentations[4].
> 
> Using English in the Open Source world could help us get touch with
> more audices, we are try our best to encourage the contributor to use
> English when they are writing emails, have public discussion in github
> issues.
> 
> When we hold the local meetup we prefer to use Chinese, but when we
> talk about the issue and PRs we perfer to use English.
> In ApacheCon Asia 2021[5]，we got 50% Chinese sessions and 50% English
> sessions and we have the Chinese version of website to open up the
> local market,  I think this is banlance we choose now.
> 
> [1]https://www.ximalaya.com/keji/37853515/
> [2]https://www.deepl.com/
> [3]https://translate.google.com
> [4]https://github.com/alc-beijing/translation
> [5]https://www.apachecon.com/acasia2021/
> 
> Willem Jiang
> 
> Twitter: willemjiang
> Weibo: 姜宁willem
> 
> On Mon, Aug 30, 2021 at 1:13 AM Sharan Foga  wrote:
> >
> > Hi All
> >
> > Recently I heard about an incident where a potential contributor wanted to 
> > contribute something to an ASF project but had found it difficult to 
> > interact because of the language barrier. They had very limited English 
> > skills.
> >
> > I'd like to start a discussion to get some ideas around what we could do in 
> > general to encourage or help people who may find it hard to become involved 
> > at the ASF because of language.
> >
> > I seem to remember that the latest ASF D&I Survey had some findings around 
> > language confidence and that it had sometimes acted as a barrier for new 
> > contributors. Do we have any plans, initiatives or existing tools that 
> > could help with this?. It would be great to get some feedback from anyone 
> > that has experienced this language barrier and discuss what could be done 
> > to improve the situation and help others.
> >
> > Does anyone have any comments, suggestions or ideas? I'd like to hear them. 
> > Please join the conversation and let's see what can be done.
> >
> > Thanks
> > Sharan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Commented] (COMDEV-424) An open Source Charging Function for 5G-SA - OPENCHF

[Prajith (Jira)]

[ 
https://issues.apache.org/jira/browse/COMDEV-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412519#comment-17412519
 ] 

Prajith  commented on COMDEV-424:
-

Could not load the documents due to internal error.

Linked URL attached for downloading the details

> An  open Source Charging Function for 5G-SA - OPENCHF
> -
>
> Key: COMDEV-424
> URL: https://issues.apache.org/jira/browse/COMDEV-424
> Project: Community Development
>  Issue Type: Project
>  Components: GSoC/Mentoring ideas
>Reporter: Prajith 
>Priority: Major
>   Original Estimate: 8,760h
>  Remaining Estimate: 8,760h
>
> Dear Team,
> Requesting all community members  to help to together to build a OPEN SOURCE 
> Charging System (CHF) for 5G -SA Space for TELCOs. 
> This is one of the key futures for upcoming 5G-ERA for Telcos as well as new 
> business innovations and disruptions.
> Details are  attached and below link
> [LinkedIn|https://www.linkedin.com/feed/update/urn%3Ali%3Aactivity%3A6825386990473674752/]
>  
> we have to start with Open CHF first.
> comments and suggestions are welcome.
> Regards
> Prajith



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

[jira] [Created] (COMDEV-424) An open Source Charging Function for 5G-SA - OPENCHF

[Prajith (Jira)]

Prajith  created COMDEV-424:
---

 Summary: An  open Source Charging Function for 5G-SA - OPENCHF
 Key: COMDEV-424
 URL: https://issues.apache.org/jira/browse/COMDEV-424
 Project: Community Development
  Issue Type: Project
  Components: GSoC/Mentoring ideas
Reporter: Prajith 


Dear Team,

Requesting all community members  to help to together to build a OPEN SOURCE 
Charging System (CHF) for 5G -SA Space for TELCOs. 

This is one of the key futures for upcoming 5G-ERA for Telcos as well as new 
business innovations and disruptions.

Details are  attached and below link

[LinkedIn|https://www.linkedin.com/feed/update/urn%3Ali%3Aactivity%3A6825386990473674752/]

 

we have to start with Open CHF first.

comments and suggestions are welcome.

Regards

Prajith



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org