Category: News

The Apache News Round-up: week ending 29 July 2022

Posted on by Michael G

Farewell, July –we’re wrapping
up the month with another great week. Here are the latest updates on
the Apache community’s activities:

ApacheCon™ – the ASF’s official global conference series, bringing Tomorrow’s Technology Today since 1998.

ASF Board – management and oversight of the business affairs of the corporation in accordance with the Foundation’s bylaws.

ASF Infrastructure – our distributed team on three continents keeps the ASF’s infrastructure running around the clock.

  • 7M+
    weekly checks yield uptime at 100.00%. Performance checks across 50
    different service components spread over more than 250 machines in data
    centers around the world. View the     ASF’s Infrastructure Uptime site to see the most recent averages.

Apache Code Snapshot
– Over the past week, 274 Apache Committers and 819 contributors
changed 2,862,825 lines of code over 3,389 commits. Top five
contributors, in order, are: Jean-Baptiste Onofré, Gary Gregory, Claus
Ibsen, Robbie Gemmell, and Dan Haywood.

Apache Project Announcements – the latest updates by category.

Attic – provides process and solutions when an Apache project has reached its end of life.

APIs–

Big Data–

  • Apache Calcite Avatica 1.22.0 released
    • CVE-2022-36364: Avatica JDBC driver httpclient_impl connection property can be used as an RCE vector

Content –

Identity Management –

Libraries–

Network Client –

Programming Languages –

RPC –

Search –

Servers–

Apache Community Notices

Stay updated about The ASF

For real-time updates, sign up for Apache-related news by sending mail to announce-subscribe@apache.org and follow @TheASF on Twitter. For a broader spectrum from the Apache community, Planet Apache provides an aggregate of Project activities as well as the personal blogs and tweets of select ASF Committers.

Have an item? Contact us!

We
try to catch all the major announcements and goings on at The ASF, but
we’re not all-knowing. Have an item you want to see in the weekly
round-up? Send it to press@apache.org.

Riot Games’ head of player community, known as ‘Aureylian’ to game streaming fans, on her favorite corners of the internet

Posted on by Michael G

Here at Mozilla, we are the first to admit the internet isn’t perfect, but we are also quick to point out that the internet is pretty darn magical. The internet opens up doors and opportunities, allows for people to connect with others, and lets everyone find where they belong — their corners of the internet. […]

The post Riot Games’ head of player community, known as ‘Aureylian’ to game streaming fans, on her favorite corners of the internet appeared first on The Mozilla Blog.

Community Working Group posts: Code of Conduct team update: July 27, 2022

Posted on by Michael G

As previously reported, the Community Health Team has started to have regular, bi-weekly meetings in an effort to develop and update the Code of Conduct (CoC) for the Drupal community.

Community Health Team members present at this week’s meeting were

During the meeting, we created milestones leading up to our December 14 goal of having a revised Code of Conduct ready for adoption. This time frame allows us ten 2-week sprints. We settled on a timeline based on one, 2-week public review period and two, 2-week community stakeholder review periods. We created a Trello board with initial tasks for each sprint.

George DeMet will be responsible for managing and prioritizing our backlog of tasks. Donna Bungard will facilitate our meetings and hold us accountable and ensure all team members have tasks for each sprint.

Our main task for the current sprint is to populate a new Miro board with elements of our current Code of Conduct and other Codes of Conduct that we’d like to include in our community’s next Code of Conduct. Jordana Fung will schedule daily Slack reminders to the team to add things to the board.

At our next meeting on August 10, we will discuss and decide which elements will be part of an initial outline to be shared with community stakeholders for feedback. This outline will include what, if anything, we are proposing to keep or discard from our current Code of Conduct as well as any elements that we are considering adopting from other Codes of Conduct.

In previous outreaches to the community related to our current Code of Conduct, the most common request has been that our Code of Conduct be more specific and actionable; this will be an important guiding principle for the team.

If you know of any Code of Conducts from other communities that you feel have elements we should emulate, please let us know at drupal-cwg at drupal dot org or via Twitter @drupalcommunity

A number of Drupal-related groups and individuals have confirmed their willingness to provide feedback to this effort as the process proceeds. If you, or a Drupal-related group, is interested in being part of this process as a community stakeholder, please let us know at drupal-cwg at drupal dot org.