Apache HTTP Server

We're down to the final weeks of the year, and the Apache community continues to march forward. Here's what we've been up to: Support Apache – help the ASF continue to provide $20B+ worth of software for ... [More] the public good –at 100% no cost. - Companies such as Bloomberg Philanthropies, IBM, Microsoft, and Wells Fargo's matching gift programs offer tax benefits, and provide their employees the ability to boost their support of a diverse set of nonprofit organizations. Thank you for your tax-deductible, year-end charitable gift to the ASF https://s.apache.org/fxyz1  ASF Board – management and oversight of the business affairs of the corporation in accordance with the Foundation's bylaws. - The Apache Software Foundation Operations Summary: Q2 FY2020 (August - October 2019) https://s.apache.org/2kv2n - Next Board Meeting: 15 January 2020. Board calendar and minutes http://apache.org/foundation/board/calendar.html Apache Diversity & Inclusion – newly-formed committee supports initiatives that promote diversity, equity, and inclusion across the greater Apache community. - The 2020 ASF Community Survey closes on 4 January: we'd love your insight! https://s.apache.org/pzol5 ApacheCon™ – the ASF's official global conference series, bringing Tomorrow's Technology Today since 1998 - CFP and Registration OPEN for Apache Roadshow/DC https://www.apachecon.com/usroadshowdc20/index.html - ApacheCon 2019's interviews, presentations, and photos are available at https://www.apachecon.com/history.html ASF Infrastructure – our distributed team on three continents keeps the ASF's infrastructure running around the clock. - 7M+ weekly checks yield uptime at 99.93%. Performance checks across 50 different service components spread over more than 250 machines in data centers around the world. http://www.apache.org/uptime/ Apache Code Snapshot – this week, 919 Apache contributors changed 1,473,033 lines of code over 4,069 commits. Top 5 contributors, in order, are: Tilman Hausherr, Tellier Benoit, Andrea Cosentino, Bruce Schuchardt, and Andi Huber.     Apache Project Announcements – the latest updates by category. Big Data -- - Apache Kafka 2.4.0 released http://kafka.apache.org/ Content -- - Apache PDFBox JBIG2 ImageIO 3.0.3 released http://pdfbox.apache.org/ Identity Management -- - Apache Fortress 2.0.4 released http://directory.apache.org/fortress/ IoT -- - Apache IoTDB (Incubating) 0.8.2 released http://iotdb.apache.org/ Libraries --  - Apache Log4j 2.13.0 released http://logging.apache.org/ - Apache DeltaSpike 1.9.2 released http://deltaspike.apache.org/ Machine Learning -- - Apache Hivemall (Incubating) 0.6.0 released http://hivemall.incubator.apache.org/ Messaging -- - Apache Qpid Proton 0.30.0 released http://qpid.apache.org Servers -- - Apache Tomcat 7.0.99 and 8.5.50 released http://tomcat.apache.org/Web Conferencing -- - Apache OpenMeetings 4.0.10 and 5.0.0-M3 released http://openmeetings.apache.org Did You Know?  - Did you know that Apache SkyWalking is used at enterprises, universities and research centers such as Alibaba Cloud, China Mobile, DiDi, InBev, Lenovo, Peking University, and WeBank? http://skywalking.apache.org/  - Did you know that Apache IoTDB (incubating) received a "Most Popular Open Source Project From China in 2019" award? http://iotdb.apache.org/  - Did you know that the Apache Syncope admin console is now available in French Canadian? http://syncope.apache.org/ Apache Community Notices:  - The Apache Way to Sustainable Open Source Success https://s.apache.org/GhnI  - ASF Operations Summary: Q2 FY2020 (August - October 2019) https://s.apache.org/2kv2n  - Celebrating 20 Years Community-led Development "The Apache Way" https://s.apache.org/ASF20thAnniversary  - ASF Founders look back on 20 Years of the ASF https://blogs.apache.org/foundation/entry/our-founders-look-back-on  - Foundation Reports and Statements http://www.apache.org/foundation/reports.html  - ApacheCon: Tomorrow's Technology Today since 1998 http://s.apache.org/ApacheCon  - ASF Annual Report for FY2019 https://s.apache.org/FY2019AnnualReport  - The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3  - Foundation Statement –Apache Is Open. https://s.apache.org/PIRA  - "Success at Apache" focuses on the people and processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache  - Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter (https://twitter.com/TheASF) and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation  - Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/ and Twitter account https://twitter.com/ApacheCommunity  - The list of Apache project-related MeetUps can be found at http://events.apache.org/event/meetups.html  - Find out how you can participate with Apache community/projects/activities --opportunities open with Apache Camel, Apache HTTP Server, and more! https://helpwanted.apache.org/  - Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby = = = For real-time updates, sign up for Apache-related news by sending mail to [email protected] and follow @TheASF on Twitter. For a broader spectrum from the Apache community, https://twitter.com/PlanetApache provides an aggregate of Project activities as well as the personal blogs and tweets of select ASF Committers. [Less]

The Apache Maven team is pleased to announce the release of the Apache Maven Release, version 3.0.0-M1. This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: ... [More] prepare and perform. You should specify the version in your project’s plugin configuration: 1 2 3 4 5 org.apache.maven.plugins maven-release-plugin 3.0.0-M1 You can download the appropriate sources etc. from the download page: https://maven.apache.org/maven-release/download.cgi Release Notes – Apache Maven Release Plugin – Version 3.0.0-M1 Bugs: MRELEASE-229 – release:rollback is missing remove tag implementation MRELEASE-601 – The Maven 2 release plugin modifies CDATA elements in pom.xml files. MRELEASE-694 – -SNAPSHOT is unexpectedly appended to version in branched pom.xml MRELEASE-908 – Git HTTP authentication failing if there are spaces in the password MRELEASE-928 – exposing the password for SCM URL if build failed to commit files to SCM MRELEASE-947 – Wiki page URL for maven-release-plugin is wrong – post Codehaus termination MRELEASE-964 – Error injecting: org.apache.maven.shared.release.phase.RewritePomsForReleasePhase MRELEASE-966 – release plugin does not respect “mvn -f” MRELEASE-968 – Maven release plugin missing plexus-cipher dependency MRELEASE-975 – NPE when using an unknown project versionpolicy id MRELEASE-997 – Unable to release:perform on windows if a file name contains spaces on windows MRELEASE-1009 – Compilation failure when using Java 10 MRELEASE-1034 – Remove SCM tag blocks rollback in some situations New Features: MRELEASE-956 – Release Strategy Interface MRELEASE-980 – Provide the ability to control commit messages MRELEASE-985 – Override SNAPSHOT dependencies from command line MRELEASE-998 – Add ability to create custom phases MRELEASE-1029 – update project.build.outputTimestamp property on prepare MRELEASE-1031 – display release phases to give insight on what’s going on during release Improvements: MRELEASE-703 – [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata MRELEASE-873 – Remove possibly confusing non-standard goals from example MRELEASE-896 – Disable by default and deprecate useReleaseProfile parameter MRELEASE-909 – Add workItem/task support for scm deliver MRELEASE-958 – Using three digit version number (semver) MRELEASE-976 – release:branch should also support project version policies MRELEASE-977 – release:branch should prompt for branch name if none is given MRELEASE-979 – Support NamingPolicies to manage Branch and Tag names MRELEASE-992 – Deprecated maven flag —no-plugin-updates shows warnings in the console output MRELEASE-993 – Use shallow checkout per default (git scm) MRELEASE-994 – Drop Maven2 support MRELEASE-1005 – Extract ResourceGenerator from ReleasePhase MRELEASE-1007 – Rework usage workingDirectory and commonBasedir MRELEASE-1023 – Minor code cleanups MRELEASE-1032 – add https://m.a.o/xsd/maven-4.0.0.xsd schema instead of http://m.a.o/maven-v4_0_0.xsd Tasks: MRELEASE-356 – Deprecate the automated release profile MRELEASE-990 – switch to Git MRELEASE-1027 – New Release MRELEASE-1033 – Site: Dead link to wiki Dependency upgrades: MRELEASE-952 – Replace JDom as XML transformer MRELEASE-1010 – Upgrade maven-plugins parent to version 32 MRELEASE-1024 – Upgrade to SCM 1.11.2 Enjoy, -The Apache Maven team [Less]

On behalf of the Apache Kafka® community, it is my pleasure to announce the release of Apache Kafka 2.4.0. This release includes a number of key new features and improvements that we will highlight in this blog post. For the full list, please see the ... [More] release notes. What’s new with the Kafka broker, producer, and consumer KIP-392: Allow consumers to fetch from closest replica Historically, consumers were only allowed to fetch from leaders. In multi-datacenter deployments, this often means that consumers are forced to incur expensive cross-datacenter network costs in order to fetch from the leader. With KIP-392, Kafka now supports reading from follower replicas. This gives the broker the ability to redirect consumers to nearby replicas in order to save costs. See KIP-392 and this blog post for more details. KIP-429: Kafka Consumer Incremental Rebalance Protocol KIP-429 adds Incremental Cooperative Rebalancing to the consumer rebalance protocol in addition to the original eager rebalance protocol. Unlike the eager protocol, which always revokes all assigned partitions prior to a rebalance and then tries to reassign them altogether, the incremental protocol tries to minimize the partition migration between members of a consumer group by letting consumers retain their partitions during a rebalance event. As a result, end-to-end rebalance times triggered by scaling out/down operations as well as rolling bounces are shorter, benefitting heavy, stateful consumers, such as Kafka Streams applications.  See KIP-429 and this blog post for more details. KIP-455: Create an Administrative API for Replica Reassignment As a replacement for the existing ZooKeeper-based API, the new API supports incremental replica reassignments and cancellation of ongoing reassignments. This also addresses the current limitations in the ZooKeeper-based API like security enforcement and auditability. The new API is exposed via the AdminClient. See KIP-455 for more details. KIP-480: Sticky Partitioner Currently, in the case where no partition and key are specified, a producer's default partitioner partitions records in a round-robin fashion. This results in more batches that are smaller in size and leads to more requests and queuing as well as higher latency.  KIP-480 implements a new partitioner, which chooses the sticky partition that changes when the batch is full if no partition or key is present. Using the sticky partitioner helps improve message batching, decrease latency, and reduce the load for the broker. Some of the benchmarks which Justine Olshan discusses on the KIP show up to a 50% reduction in latency and 5–15% reduction in CPU utilization. See KIP-480 for more details. KIP-482: The Kafka Protocol should Support Optional Tagged Fields The Kafka remote procedure call (RPC) protocol has its own serialization format for binary data. The Kafka protocol currently does not support optional fields, nor does it support attaching an extra field to a message in a manner that is orthogonal to the versioning scheme.  In order to support these scenarios, KIP-482 adds optional tagged fields to the Kafka serialization format. Tagged fields are always optional. KIP-482 also implements more efficient serialization for variable-length objects. See KIP-482 for more details. KIP-504: Add new Java Authorizer Interface This KIP defines a Java authorizer API that is consistent with other pluggable interfaces in the broker. Several limitations in the current Scala authorizer API that could not be fixed without breaking compatibility have been addressed in the new API. Additional request context is now provided to authorizers to support authorization based on the security protocol or listener.  The API also supports asynchronous ACL updates with batching. The new pluggable authorizer API only requires a dependency on the client’s JAR. A new out-of-the-box authorizer has been added, leveraging features supported by the new API. The additional context provided to the authorizer has been used to improve audit logging. Batched updates enhance the efficiency of ACL updates using the new authorizer when multiple ACLs are added for a resource. An asynchronous startup and updated APIs will enable Kafka to be used as the storage backend for ACLs once ZooKeeper is removed under KIP-500. In addition, authorizer implementations can now enable dynamic reconfiguration without broker restarts. See KIP-504 for more details. KIP-525: Return topic metadata and configs in CreateTopics response Before, the CreateTopics API response only returned a success or failure status along with any errors. With KIP-525, the API response returns additional metadata, including the actual configuration of the topic that was created. This removes the need for additional requests to obtain topic configuration after creating the topic.  Furthermore, this KIP enables users to obtain default broker configs for topic creation using CreateTopics with validateOnly=true. This is useful for displaying default configs in management tools used to create topics. See KIP-525 for more details. KAFKA-7548: KafkaConsumer should not throw away already fetched data for paused partitions. When a partition is paused by the user in the consumer, the partition is considered "unfetchable." When the consumer has already fetched data for a partition and the partition is paused, then in the next consumer poll all data from "unfetchable" partitions will be discarded. In use cases where pausing and resuming partitions are common during regular operation of the consumer, this can result in discarding pre-fetched data when it's not necessary.  Once the partition is resumed, new fetch requests will be generated and sent to the broker to get the same partition data again. Depending on the frequency of pausing and resuming of partitions, this can impact different aspects of consumer polling, including broker/consumer throughput, number of consumer fetch requests, and NIO-related garbage collection (GC) concerns for regularly dereferenced byte buffers of partition data. This issue is now resolved by retaining completed fetch data for partitions that are paused so that it may be returned in a future consumer poll once the partition is resumed by the user. See KAFKA-7548 for more details. What’s new in Kafka Connect KIP-382: MirrorMaker 2.0 KIP-382 implements MirrorMaker 2.0 (MM2), a new multi-cluster, cross-datacenter replication engine based on the Connect framework. This tool includes several features designed for disaster recovery, including cross-cluster consumer checkpoints and offset syncs. Automatic topic renaming and cycle detection enable bidirectional active-active replication and other complex topologies.  A new RemoteClusterUtils class enables clients to interpret checkpoints, heartbeats, and "remote topics" from other clusters. See KIP-382 for more details. KIP-440: Extend Connect Converter to support headers KIP-440 adds header support to Kafka Connect. This enables the use of Kafka Connect together with Kafka producers and consumers that rely on headers for serialization/deserialization. See KIP-440 for more details. KIP-507: Securing Internal Connect REST Endpoints KIP-507 brings out-of-the-box authentication and authorization to an internal REST endpoint used by Connect workers to relay task configurations to the leader. If left unsecured, this endpoint could be used to write arbitrary task configurations to a Connect cluster.  However, after KIP-507, the endpoint automatically secures as long as the other attack surfaces of a Connect cluster (such as its public REST API and the underlying Kafka cluster used to host internal topics and perform group coordination) are also secure. See KIP-507 for more details. KIP-481: SerDe Improvements for Connect Decimal type in JSON KIP-481 adds to the JSON converter decimal.format for serializing Connect’s DECIMAL logical type values as number literals rather than base64 string literals. This new option defaults to base64 to maintain the previous behavior, but it can be changed to number to serialize decimal values as normal JSON numbers. The JSON converter automatically deserializes using either format, so make sure to upgrade consumer applications and sink connectors before changing source connector converters to use the number format. See KIP-481 for more details. What’s New in Kafka Streams KIP-213: Support non-key joining in KTable Previously, the Streams domain-specific language (DSL) only allowed table-table joins based on the primary key of the joining KTables. Now, for a KTable (left input) to join with another KTable (right input) based on a specified foreign key as part of its value fields, the join result is a new KTable keyed on the left KTable’s original key. This supports updates from both sides of the join. See KIP-213 for more details. KIP-307: Allow to define custom processor names with KStreams DSL Prior to this release, while building a new topology through the Kafka Streams DSL, the processors were automatically named. A complex topology with dozens of operations can be hard to understand if the processor names are not relevant. This KIP allows users to set more meaningful processor names. See KIP-307 for more details. KIP-470: TopologyTestDriver test input and output usability improvements The TopologyTestDriver allows you to test Kafka Streams logic. This is a lot faster than utilizing actual producers and consumers and makes it possible to simulate different timing scenarios. Kafka 2.4.0 introduces TestInputTopic and TestOutputTopic classes to simplify the test interface.  See KIP-470 for more details. Metrics, monitoring, and operational improvements KIP-412 adds support to dynamically alter a broker's log levels using the Admin API.  KIP-495 allows users to dynamically alter log levels in the Connect framework. KIP-521 changes Connect to also send log messages to a file and rolls that file every day. KIP-460 modifies the PreferredLeaderElection RPC to support unclean leader election in addition to preferred leader election. KIP-464 allows you to leverage num.partitions and default.replication.factor from the AdminClient#createTopics API. KIP-492 supports the security provider config, which can be used to configure custom security algorithms. KIP-496 adds an API to delete consumer offsets and expose it via the AdminClient. KIP-503 adds metrics to monitor the number of topics/replicas marked for deletion. KIP-475 adds metrics to measure the number of tasks on a connector. KIP-471 exposes a subset of RocksDB's statistics in Kafka Streams metrics, which enables users to find bottlenecks and tune RocksDB accordingly. KIP-484 adds new metrics for the group and transaction metadata loading duration. KIP-444 adds a few new metrics at the Streams instance level such as static version/commit-id as well as dynamic state. ZooKeeper upgrade to 3.5.x ZooKeeper has been upgraded to 3.5.x. support for TLS encryption added in ZooKeeper 3.5.x. This enables us to configure TLS encryption between Kafka brokers and ZooKeeper. Scala 2.13 support Apache Kafka 2.4.0 now supports Scala 2.13 while also remaining compatible with Scala 2.12 and 2.11. Conclusion We want to take this opportunity to thank everyone who has contributed to this release! To learn more about what’s new in Apache Kafka 2.4, be sure to check out the release notes and highlights video. [Less]

On behalf of the Apache Kafka® community, it is my pleasure to announce the release of Apache Kafka 2.4.0. This release includes a number of key new features and improvements that we will highlight in this blog post. For the full list, please see the ... [More] release notes. What’s new with the Kafka broker, producer, and consumer KIP-392: Allow consumers to fetch from closest replica Historically, consumers were only allowed to fetch from leaders. In multi-datacenter deployments, this often means that consumers are forced to incur expensive cross-datacenter network costs in order to fetch from the leader. With KIP-392, Kafka now supports reading from follower replicas. This gives the broker the ability to redirect consumers to nearby replicas in order to save costs. See KIP-392 and this blog post for more details. KIP-429: Kafka Consumer Incremental Rebalance Protocol KIP-429 adds Incremental Cooperative Rebalancing to the consumer rebalance protocol in addition to the original eager rebalance protocol. Unlike the eager protocol, which always revokes all assigned partitions prior to a rebalance and then tries to reassign them altogether, the incremental protocol tries to minimize the partition migration between members of a consumer group by letting consumers retain their partitions during a rebalance event. As a result, end-to-end rebalance times triggered by scaling out/down operations as well as rolling bounces are shorter, benefitting heavy, stateful consumers, such as Kafka Streams applications.  See KIP-429 and this blog post for more details. KIP-455: Create an Administrative API for Replica Reassignment As a replacement for the existing ZooKeeper-based API, the new API supports incremental replica reassignments and cancellation of ongoing reassignments. This also addresses the current limitations in the ZooKeeper-based API like security enforcement and auditability. The new API is exposed via the AdminClient. See KIP-455 for more details. KIP-480: Sticky Partitioner Currently, in the case where no partition and key are specified, a producer's default partitioner partitions records in a round-robin fashion. This results in more batches that are smaller in size and leads to more requests and queuing as well as higher latency.  KIP-480 implements a new partitioner, which chooses the sticky partition that changes when the batch is full if no partition or key is present. Using the sticky partitioner helps improve message batching, decrease latency, and reduce the load for the broker. Some of the benchmarks which Justine Olshan discusses on the KIP show up to a 50% reduction in latency and 5–15% reduction in CPU utilization. See KIP-480 and this blog post for more details. KIP-482: The Kafka Protocol should Support Optional Tagged Fields The Kafka remote procedure call (RPC) protocol has its own serialization format for binary data. The Kafka protocol currently does not support optional fields, nor does it support attaching an extra field to a message in a manner that is orthogonal to the versioning scheme.  In order to support these scenarios, KIP-482 adds optional tagged fields to the Kafka serialization format. Tagged fields are always optional. KIP-482 also implements more efficient serialization for variable-length objects. See KIP-482 for more details. KIP-504: Add new Java Authorizer Interface This KIP defines a Java authorizer API that is consistent with other pluggable interfaces in the broker. Several limitations in the current Scala authorizer API that could not be fixed without breaking compatibility have been addressed in the new API. Additional request context is now provided to authorizers to support authorization based on the security protocol or listener.  The API also supports asynchronous ACL updates with batching. The new pluggable authorizer API only requires a dependency on the client’s JAR. A new out-of-the-box authorizer has been added, leveraging features supported by the new API. The additional context provided to the authorizer has been used to improve audit logging. Batched updates enhance the efficiency of ACL updates using the new authorizer when multiple ACLs are added for a resource. An asynchronous startup and updated APIs will enable Kafka to be used as the storage backend for ACLs once ZooKeeper is removed under KIP-500. In addition, authorizer implementations can now enable dynamic reconfiguration without broker restarts. See KIP-504 for more details. KIP-525: Return topic metadata and configs in CreateTopics response Before, the CreateTopics API response only returned a success or failure status along with any errors. With KIP-525, the API response returns additional metadata, including the actual configuration of the topic that was created. This removes the need for additional requests to obtain topic configuration after creating the topic.  Furthermore, this KIP enables users to obtain default broker configs for topic creation using CreateTopics with validateOnly=true. This is useful for displaying default configs in management tools used to create topics. See KIP-525 for more details. KAFKA-7548: KafkaConsumer should not throw away already fetched data for paused partitions. When a partition is paused by the user in the consumer, the partition is considered "unfetchable." When the consumer has already fetched data for a partition and the partition is paused, then in the next consumer poll all data from "unfetchable" partitions will be discarded. In use cases where pausing and resuming partitions are common during regular operation of the consumer, this can result in discarding pre-fetched data when it's not necessary.  Once the partition is resumed, new fetch requests will be generated and sent to the broker to get the same partition data again. Depending on the frequency of pausing and resuming of partitions, this can impact different aspects of consumer polling, including broker/consumer throughput, number of consumer fetch requests, and NIO-related garbage collection (GC) concerns for regularly dereferenced byte buffers of partition data. This issue is now resolved by retaining completed fetch data for partitions that are paused so that it may be returned in a future consumer poll once the partition is resumed by the user. See KAFKA-7548 for more details. What’s new in Kafka Connect KIP-382: MirrorMaker 2.0 KIP-382 implements MirrorMaker 2.0 (MM2), a new multi-cluster, cross-datacenter replication engine based on the Connect framework. This tool includes several features designed for disaster recovery, including cross-cluster consumer checkpoints and offset syncs. Automatic topic renaming and cycle detection enable bidirectional active-active replication and other complex topologies.  A new RemoteClusterUtils class enables clients to interpret checkpoints, heartbeats, and "remote topics" from other clusters. See KIP-382 for more details. KIP-440: Extend Connect Converter to support headers KIP-440 adds header support to Kafka Connect. This enables the use of Kafka Connect together with Kafka producers and consumers that rely on headers for serialization/deserialization. See KIP-440 for more details. KIP-507: Securing Internal Connect REST Endpoints KIP-507 brings out-of-the-box authentication and authorization to an internal REST endpoint used by Connect workers to relay task configurations to the leader. If left unsecured, this endpoint could be used to write arbitrary task configurations to a Connect cluster.  However, after KIP-507, the endpoint automatically secures as long as the other attack surfaces of a Connect cluster (such as its public REST API and the underlying Kafka cluster used to host internal topics and perform group coordination) are also secure. See KIP-507 for more details. KIP-481: SerDe Improvements for Connect Decimal type in JSON KIP-481 adds to the JSON converter decimal.format for serializing Connect’s DECIMAL logical type values as number literals rather than base64 string literals. This new option defaults to base64 to maintain the previous behavior, but it can be changed to number to serialize decimal values as normal JSON numbers. The JSON converter automatically deserializes using either format, so make sure to upgrade consumer applications and sink connectors before changing source connector converters to use the number format. See KIP-481 for more details. What’s New in Kafka Streams KIP-213: Support non-key joining in KTable Previously, the Streams domain-specific language (DSL) only allowed table-table joins based on the primary key of the joining KTables. Now, for a KTable (left input) to join with another KTable (right input) based on a specified foreign key as part of its value fields, the join result is a new KTable keyed on the left KTable’s original key. This supports updates from both sides of the join. See KIP-213 for more details. KIP-307: Allow to define custom processor names with KStreams DSL Prior to this release, while building a new topology through the Kafka Streams DSL, the processors were automatically named. A complex topology with dozens of operations can be hard to understand if the processor names are not relevant. This KIP allows users to set more meaningful processor names. See KIP-307 for more details. KIP-470: TopologyTestDriver test input and output usability improvements The TopologyTestDriver allows you to test Kafka Streams logic. This is a lot faster than utilizing actual producers and consumers and makes it possible to simulate different timing scenarios. Kafka 2.4.0 introduces TestInputTopic and TestOutputTopic classes to simplify the test interface.  See KIP-470 and this blog post for more details. Metrics, monitoring, and operational improvements KIP-412 adds support to dynamically alter a broker's log levels using the Admin API.  KIP-495 allows users to dynamically alter log levels in the Connect framework. KIP-521 changes Connect to also send log messages to a file and rolls that file every day. KIP-460 modifies the PreferredLeaderElection RPC to support unclean leader election in addition to preferred leader election. KIP-464 allows you to leverage num.partitions and default.replication.factor from the AdminClient#createTopics API. KIP-492 supports the security provider config, which can be used to configure custom security algorithms. KIP-496 adds an API to delete consumer offsets and expose it via the AdminClient. KIP-503 adds metrics to monitor the number of topics/replicas marked for deletion. KIP-475 adds metrics to measure the number of tasks on a connector. KIP-471 exposes a subset of RocksDB's statistics in Kafka Streams metrics, which enables users to find bottlenecks and tune RocksDB accordingly. KIP-484 adds new metrics for the group and transaction metadata loading duration. KIP-444 adds a few new metrics at the Streams instance level such as static version/commit-id as well as dynamic state. ZooKeeper upgrade to 3.5.x ZooKeeper has been upgraded to 3.5.x. support for TLS encryption added in ZooKeeper 3.5.x. This enables us to configure TLS encryption between Kafka brokers and ZooKeeper. Scala 2.13 support Apache Kafka 2.4.0 now supports Scala 2.13 while also remaining compatible with Scala 2.12 and 2.11. Conclusion We want to take this opportunity to thank everyone who has contributed to this release! To learn more about what’s new in Apache Kafka 2.4, be sure to check out the release notes and highlights video. [Less]

The Apache Log4j 2 team is pleased to announce the Log4j 2.13.0 release! Apache Log4j is a well known framework for logging application behavior. Log4j 2 is an upgrade to Log4j that provides significant improvements over its predecessor, Log4j 1.x ... [More] , and provides many other modern features such as support for Markers, lambda expressions for lazy logging, property substitution using Lookups, multiple patterns on a PatternLayout and asynchronous Loggers. Another notable Log4j 2 feature is the ability to be "garbage-free" (avoid allocating temporary objects) while logging. In addition, Log4j 2 will not lose events while reconfiguring. The artifacts may be downloaded from https://logging.apache.org/log4j/2.x/download.html. This release contains bugfixes and minor enhancements. Some of the new features in this release are: Log4j 2 now requires Java 8 or higher to build and run. Experimental support for Log4j 1 configuration files. See Log4j 2 Compatiblity with Log4j 1. The Logger API has been enhanced to support a builder pattern. This can dramatically improve the overhead of capturing location information. See Log Builder. Better integration with Spring Boot by providing access to Spring variables in Log4j 2 configuration files and allowing Log4j 2 system properties to be defined in the Spring configuration. See Logging in the Cloud. Support for accessing Kubernetes information via a Log4j 2 Lookup. The Gelf Layout now allows the message to be formatted using a PatternLayout pattern. Logging in the Cloud provides an example of this, as well as the use of the Spring and Kubernetes Lookups. Due to a break in compatibility in the SLF4J binding, Log4j now ships with two versions of the SLF4J to Log4j adapters. log4j-slf4j-impl should be used with SLF4J 1.7.x and earlier and log4j-slf4j18-impl should be used with SLF4J 1.8.x and later. Note that the XML, JSON and YAML formats changed in the 2.11.0 release: they no longer have the "timeMillis" attribute and instead have an "Instant" element with "epochSecond" and "nanoOfSecond" attributes. The Log4j 2.13.0 API, as well as many core components, maintains binary compatibility with previous releases. GA Release 2.13.0 Changes in this version include: New Features LOG4J2-2732: Add ThreadContext.putIfNotNull method. Thanks to Matt Pavlovich. LOG4J2-2731: Add a Level Patttern Selector. LOG4J2-63: Add experimental support for Log4j 1 configuration files. LOG4J2-2716: Add the ability to lookup Kubernetes attributes in the Log4j configuration. Allow Log4j properties to be retrieved from the Spring environment if it is available. LOG4J2-2710: Allow Spring Boot application properties to be accessed in the Log4j 2 configuration. Add lower and upper case Lookups. LOG4J2-2639: Add builder pattern to Logger interface. Fixed Bugs LOG4J2-2058: Prevent recursive calls to java.util.LogManager.getLogger(). LOG4J2-2725: LOG4J2-2725 - Added try/finally around event.execute() for RingBufferLogEventHandler to clear memory correctly in case of exception/error Thanks to Dzmitry Anikechanka. LOG4J2-2635: Wrong java version check in ThreadNameCachingStrategy. Thanks to Filipp Gunbin. LOG4J2-2674: Use a less confusing name for the CompositeConfiguration source. Thanks to Anton Korenkov. LOG4J2-2727: Add setKey method to Kafka Appender Builder. Thanks to Clément Mathieu. LOG4J2-2707: ArrayIndexOutOfBoundsException could occur with MAC address longer than 6 bytes. Thanks to Christian Frank. LOG4J2-2712: The rolling file appenders would fail to compress the file after rollover if the file name matched the file pattern. LOG4J2-2693: @PluginValue does not support attribute names besides "value". LOG4J2-2647: Validation blocks definition of script in properties configuration. LOG4J2-2680: Set result of rename action to true if file was copied. Thanks to Guillermo Xavier Hurtado Garcia. LOG4J-2672: Add automatic module names where missing. Thanks to Stephen Colebourne. LOG4J2-2673: OutputStreamAppender.Builder ignores setFilter(). Thanks to Yuichi Sugimura. LOG4J2-2725: Prevent a memory leak when async loggers throw errors. Thanks to Dzmitry Anikechanka. Changes LOG4J2-2701: Update Jackson to 2.9.10. LOG4J2-2709: Allow message portion of GELF layout to be formatted using a PatternLayout. Allow ThreadContext attributes to be explicitly included or excluded in the GelfLayout. Apache Log4j 2.13.0 requires a minimum of Java 8 to build and run. Log4j 2.3 was the last release that supported Java 6 and Log4j 2.11.2 is the last release to support Java 7. For complete information on Apache Log4j 2, including instructions on how to submit bug reports, patches, or suggestions for improvement, see the Apache Apache Log4j 2 website: https://logging.apache.org/log4j/2.x/ [Less]

FOUNDATION OPERATIONS SUMMARY Second Quarter, Fiscal Year 2020 (August - October 2019) "...a preeminent organization in the world of open source software... The ASF has always distinguished itself by maintaining a consistent mode ... [More] of project governance and evolution, known as "The Apache Way"."—Brian Proffitt, Senior Principal Community Architect, Red Hat Open Source Program Office (ASF Silver Sponsor) > Conferences and Events: During this period we held two major Apache events. In September we held ApacheCon North America in Las Vegas, Nevada, and celebrated the 20th anniversary of the ASF. We had around 725 attendees at the Flamingo Hotel. Event details may be found at https://www.apachecon.com/acna19/   Videos of the plenary sessions and other selected content may be found at https://www.youtube.com/watch?v=0CLDVMcyo1s&list=PLU2OcwpQkYCzWULP5C-C9eTF4DcbnYa2l and audio from selected other presentations is at http://feathercast.apache.org/   Photos from the event are at https://photos.apachecon.com/?/category/2 In October we held ApacheCon Europe in Berlin, Germany. We had around 300 in attendance at the Kulturbrauerei Berlin. Event details may be found at https://aceu19.apachecon.com/  Session videos may be found at https://www.youtube.com/watch?v=2EvCF4XKLso&list=PLU2OcwpQkYCxVGCGWtMxb9d27Z-pcoN9a  Photos from the event are at https://photos.apachecon.com/?/category/1 At the end of this period, we were in planning for our 2020 schedule of events. This will include: Apache Roadshow Chicago (Proposed) - 2020-05-27 to 2020-05-30 Chicago, IL, USA Apache Roadshow, Seattle - 2020-06-10 to 2020-06-13 Seattle, WA, USA ApacheCon North America, New Orleans - 2020-09-28 to 2020-10-03 New Orleans, LA, USA Apache Roadshow China (Proposed) - 2020-10-24 to 2020-10-26, (Location TBD) (Please note that some of these events are still tentative.) For sponsorship opportunities, please contact [email protected] Upcoming events are listed at http://events.apache.org/ and may change as planning progresses. > Community Development: During this quarter a key theme was event participation. In August our main focus was dealing with the requests for ordering project stickers for ApacheCon. For this special anniversary event we wanted to ensure that any many projects as possible would have stickers available on the ASF booth. The main focus in September was to help provide support for Apachecon NA in Las Vegas. As usual we co-ordinated the Apache booth which was staffed by our community volunteers from various projects. They had the chance to speak to attendees, promote their project and hand out a range of giveaways. The ASF booth was also the central place where the Apache feather was on display for all attendees to sign.  In October the feather was also taken to Berlin for ApacheCon EU and attendees were also invited to sign the feather. Once again we had a central and dynamic booth which became a meeting hub for attendees. As part of bringing the Apache Way to new audiences, an Apache Day event was held in Indore, India during September. The aim was to give people an overview of the ASF, the Apache Way and also give some practical help in becoming a contributor. Also this quarter we participated at CCOSS 19 in Guadalajara, Mexico. There was an Apache track with talks ranging from Getting Started to Governance and Open Source Licences. This was a great opportunity to connect with potential new contributors to open source. We are still receiving requests to participate at events so need to put a plan in place for 2020. > Committers and Contributions: Over the past quarter, 1,581 contributors committed 42,338 changes that amount to 14,073,594 lines of code across Apache projects. The top 5 contributors, in order, were: Tilman Hausherr (1,010 commits), Andrea Cosentino (788 commits), Mark Robert Miller (771 commits), Mark Thomas (681 commits), and Jean-Baptiste Onofré (616 commits). All individuals who are granted write access to the Apache repositories must submit an Individual Contributor License Agreement (ICLA). Corporations that have assigned employees to work on Apache projects as part of an employment agreement may sign a Corporate CLA (CCLA) for contributing intellectual property via the corporation. Individuals or corporations donating a body of existing software or documentation to one of the Apache projects need to execute a formal Software Grant Agreement (SGA) with the ASF. During Q2 FY2020, the ASF Secretary processed 210 ICLAs, 7 CCLAs, and 14 Software Grants. History of Apache committer growth can be seen at https://projects.apache.org/timelines.html > Brand Management: Operations — The work of the Brand Management team falls broadly into one of three categories: trademark transfers and registrations granting permission to use our marks addressing potential infringements of our marks The volume of work this quarter has been roughly double that of the previous quarter. The increase has been mostly in the areas of requests to use our marks and queries regarding potential infringements. The increase in volme has been manageable, largely due to the tracking system we have put in place. This quarter has seen requests to use Apache marks for user groups, events, merchandise, publications and training courses with nearly all requests being granted, subject to our Trademark Usage Policy. There have been a few cases this quarter of requests being made for marks that the ASF does not own which we have redirected to the correct owners. Registrations — A number of registrations came up for renewal this quarter. We review each renewal as it comes up and, as a result, opted not to renew some of those registrations. The remaining renewals are in now progress. Some registrations, particularly those outside the US, tend to be more complex. This quarter some of our registrations in China have continued to require additional work to help them progress. Infringements — Potential infringements are brought to our attention from both internal and external sources. The majority of infringements we see are accidental and our project communities are able to resolve these quickly and informally with occasional input from the Brand Management team. A small number of issues take longer to resolve. We made progress on some of these this quarter and hope that that progress will continue next quarter. We received multiple reports of a significant infringement this quarter and are in contact with the company concerned to remedy the situation. We hope to have this resolved in the next quarter. And finally… The Brand Management team  welcomes your comments and suggestions as well as any questions you might have. Please see https://www.apache.org/foundation/marks/contact for our contact details. > Infrastructure: The datacenter fast-exit mentioned last quarter was completed, as an all-hands shift. That went very well, and our services have been relocated. That sudden move really helped us to double-check our configuration management (Puppet-based) and to reallocate services to better-cost providers, to stretch our Infrastructure dollar. For a short while in August, we experienced some email issues that created a perfect storm with one of our primary providers. That has been resolved, with a new mail queue monitoring system and alerting, helping to improve our ongoing level of uptime and service. September was our 20th Anniversary ApacheCon North America, held in Las Vegas, Nevada. The entire team traveled to Vegas to meet with each other and with the community. It was a great opportunity to put faces to new names, to see some old faces, and to get a bit of work and team bonding accomplished. We also launched our new ".asf.yaml" service for out projects to self-service many aspects of their GitHub presence, and workflow for publishing project websites. More features for the projects, and less tickets for the team. This has been working well, and we continue to improve upon its capabilities. One of the Apache community members provided several features through some Pull Requests -- it is always great to see someone in the community helping out the thousands of others who form Apache. One of our final initiatives in the quarter, was a revamp of how we map projects' Apache Subversion repositories over to GitHub. We upgraded the server, improved the mapping system, and pruned out numerous unused projects (eg. they had switched to git). We also improved the resiliency of our GitHub-based webhooks by using message queues for repeatability, and to hold messages while we upgrade the primary server. We've seen improvements in stability and ordering, already. > Financial Statement: > Fundraising: Fundraising work continues smoothly with very few non-BAU/business-as-usual details to share. "No news is good news", as they say! We are pleased to report that the online form and digital agreement signature procedures announced last quarter are working well and keeping busywork to a minimum. We once again thank all of our wonderful ApacheCon sponsors that showed up in force at ApacheCon NA and ApacheCon EU and were glad to enjoy some in-person time with both Event and Foundation sponsors. A targeted sponsorship for D&I was received and processed per our BAU procedure. This was the first exercise of the procedure and worked well. We also continued conversations with a targeted sponsor for a project as well as explored the possibility of a crypto token donation. = = = Thank you to all our Sponsors -- PLATINUM: Amazon Web Services, Cloudera, Comcast, Facebook, Google, LeaseWeb, Microsoft, Pineapple Fund, Verizon Media, Tencent GOLD: Anonymous, ARM, Bloomberg, Handshake, Huawei, IBM, Indeed, Union Investment, Workday SILVER: Aetna, Alibaba Cloud Computing, Baidu, Budget Direct, Capital One, Cerner, Inspur, ODPi, Private Internet Access, Red Hat, Target BRONZE: Airport Rentals, The Blog Starter, Bookmakers, Cash Store, Bestecasinobonussen.nl, CarGurus, Casino2k, Cloudsoft, The Economic Secretariat, Emerio, Footprints Recruiting, Gundry MD, HostChecka.com, Host Advice, HostingAdvice.com, Journal Review, LeoVegas Indian Online Casino,  Mutuo Kredit AG, Online Holland Casino, ProPrivacy, PureVPN, RX-M, SCAMS.info, Site Builder Report, Start a Blog by Ryan Robinson, Talend, The Best VPN, Top10VPN, Twitter, Web Hosting Secret Revealed TARGETED PLATINUM: CloudBees, DLA Piper, JetBrains, Microsoft, OSU Open Source Labs, Sonatype, Verizon Media TARGETED GOLD: Atlassian, The CrytpoFund, Datadog, PhoenixNAP, Quenda TARGETED SILVER: Amazon Web Services, HotWax Systems, Rackspace TARGETED BRONZE: Bintray, Education Networks of America, Google, Hopsie, No-IP, PagerDuty, Peregrine Computer Consultants Corporation, Sonic.net, SURFnet, Virtru To sponsor The Apache Software Foundation, visit http://apache.org/foundation/sponsorship.html . To make a one-time or monthly recurring donation, please visit https://donate.apache.org/ # # # Report prepared by Sally Khudairi, Vice President Marketing & Publicity, with contributions by Rich Bowen, Vice President Conferences; Sharan Foga, Vice President Community Development; Mark Thomas, Vice President Brand Management; David Nalley, Vice President Infrastructure; Greg Stein, ASF Infrastructure Administrator; Tom Pappas, Vice President Finance; and Daniel Ruggeri, Vice President Fundraising. For more information, subscribe to the [email protected] mailing list and visit http://www.apache.org/, the ASF Blog at http://blogs.apache.org/, the @TheASF on Twitter, and https://www.linkedin.com/company/the-apache-software-foundation. (c) The Apache Software Foundation 2019. [Less]

Happy Friday, everyone. We've had a productive week --let's review: Support Apache – help the ASF continue to provide $20B+ worth of software –at 100% no cost– for the public good. - As a US 501(c)(3) ... [More] not-for-profit charitable organization, we do not pay for code development or contributions by our Board of Directors, Executive Officers, 765 Individual ASF Members, 205 Apache Project Management Committees, 7,500+ Committers and countless contributors. Less than 10% of the funds we raise is spent on overhead. Thank you for your individual or corporate tax-deductible, year-end charitable gift to the ASF https://s.apache.org/fxyz1 ASF Board – management and oversight of the business affairs of the corporation in accordance with the Foundation's bylaws.   - Next Board Meeting: 18 December 2019. Board calendar and minutes http://apache.org/foundation/board/calendar.html Apache Diversity & Inclusion – newly-formed committee supports initiatives that promote diversity, equity, and inclusion across the greater Apache community. - Have you taken the 2020 ASF Community Survey yet? https://s.apache.org/pzol5 ApacheCon™ – the ASF's official global conference series, bringing Tomorrow's Technology Today since 1998 - CFP and Registration OPEN for Apache Roadshow/DC https://www.apachecon.com/usroadshowdc20/index.html - ApacheCon 2019's interviews, presentations, and photos are available at https://www.apachecon.com/history.html ASF Infrastructure – our distributed team on three continents keeps the ASF's infrastructure running around the clock. - 7M+ weekly checks yield uptime at 99.86%. Performance checks across 50 different service components spread over more than 250 machines in data centers around the world. http://www.apache.org/uptime/Apache Code Snapshot – this week, 389 Apache contributors changed 726,972 lines of code over 2,315 commits. Top 5 contributors, in order, are: Claus Ibsen, Alex Herbert, Jarek Potiuk, Tilman Hausherr, and Rene Cordier.   Apache Project Announcements – the latest updates by category. Big Data -- - Apache Druid (incubating) 0.16.1 released http://druid.apache.org/ - Apache HBase 2.1.8 released http://hbase.apache.org/ Cloud -- - Apache Libcloud 2.7.0 released http://libcloud.apache.org/ Content -- - Apache Jackrabbit 2.19.6 and Jackrabbit Oak 1.10.7 released http://jackrabbit.apache.org/ - Apache Tika 1.23 released http://tika.apache.org/ Libraries -- - Apache Commons Pool 2.8.0 released http://commons.apache.org/ - Apache Juneau 8.1.2 released http://juneau.apache.org/ Mail -- - Apache SpamAssassin 3.4.3 released https://spamassassin.apache.org/ Messaging -- - Apache Qpid Broker-J 7.1.6, Qpid Proton-J 0.33.3, and Qpid JMS 0.48.0 released http://qpid.apache.org Programming Language -- - Apache Groovy 3.0.0-rc-2 released http://groovy.apache.org/ Servers -- - Apache Tomcat 9.0.30 released http://tomcat.apache.org/ Did You Know?  - Did you know that the following Apache projects are celebrating anniversaries this month? Apache Portable Runtime (APR; 19 years); Logging Services (16 years); Cayenne and OFBiz (13 years); Synapse (12 years); Camel (11 years); Axis,  OpenWebBeans, and Pivot (10 years); Aries (9 years); Flex (7 years); Helix (6 years); Flink (5 years); Beam and Eagle (3 years); Trafodion (2 years); Airflow (1 year) --many happy returns! https://projects.apache.org/  - Did you know that the European Commission’s Directorate-General for Informatics (DIGIT) is powered by Apache HTTP Server, Apache Lucene, and Apache Tomcat? https://aceu19.apachecon.com/session/open-source-software-european-commissions-informatics-directorate  - Did you know that Kirjastot Bibliotek Library uses Apache Wicket? https://wicket.apache.org/ Apache Community Notices:  - The Apache Way to Sustainable Open Source Success https://s.apache.org/GhnI  - Celebrating 20 Years Community-led Development "The Apache Way" https://s.apache.org/ASF20thAnniversary  - ASF Founders look back on 20 Years of the ASF https://blogs.apache.org/foundation/entry/our-founders-look-back-on  - Foundation Reports and Statements http://www.apache.org/foundation/reports.html  - ApacheCon: Tomorrow's Technology Today since 1998 http://s.apache.org/ApacheCon  - ASF Annual Report for FY2019 https://s.apache.org/FY2019AnnualReport  - The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3  - Foundation Statement –Apache Is Open. https://s.apache.org/PIRA  - "Success at Apache" focuses on the people and processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache  - Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter (https://twitter.com/TheASF) and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation  - Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/ and Twitter account https://twitter.com/ApacheCommunity  - The list of Apache project-related MeetUps can be found at http://events.apache.org/event/meetups.html  - Find out how you can participate with Apache community/projects/activities --opportunities open with Apache Camel, Apache HTTP Server, and more! https://helpwanted.apache.org/  - Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby = = = For real-time updates, sign up for Apache-related news by sending mail to [email protected] and follow @TheASF on Twitter. For a broader spectrum from the Apache community, https://twitter.com/PlanetApache provides an aggregate of Project activities as well as the personal blogs and tweets of select ASF Committers. [Less]

Welcome December! --let's take a look back at what the collective Apache community has been working on over the past week: Support Apache – help the ASF continue to provide $20B+ worth of software –at ... [More] 100% no cost– for the public good - Make a tax-deductible, year-end charitable gift to the ASF https://s.apache.org/fxyz1 - Shop smarter on Amazon: start at https://smile.amazon.com/ , select the ASF as your charitable organization, and 0.5% of the purchase price of eligible products will be donated to the ASF. - The Apache Software Foundation Welcomes CloudBees as its Newest Targeted Sponsor at the Platinum Level https://s.apache.org/buq73 ASF Board – management and oversight of the business affairs of the corporation in accordance with the Foundation's bylaws.   - Next Board Meeting: 18 December 2019. Board calendar and minutes http://apache.org/foundation/board/calendar.html Apache Diversity & Inclusion – newly-formed committee supports initiatives that promote diversity, equity, and inclusion across the greater Apache community. - Launch of the 2020 ASF Community Survey https://s.apache.org/pzol5 ApacheCon™ – the ASF's official global conference series, bringing Tomorrow's Technology Today since 1998 - ApacheCon 2019's interviews, presentations, and photos are available at https://www.apachecon.com/history.html ASF Infrastructure – our distributed team on three continents keeps the ASF's infrastructure running around the clock. - 7M+ weekly checks yield uptime at 99.98%. Performance checks across 50 different service components spread over more than 250 machines in data centers around the world. http://www.apache.org/uptime/Apache Code Snapshot – this week, 809 Apache contributors changed 2,355,719 lines of code over 3,480 commits. Top 5 contributors, in order, are: Dan Haywood, Tilman Hausherr, Jimin Wu, Claus Ibsen, and Sebastian Bazley.   Apache Project Announcements – the latest updates by category. Big Data --  - Apache HBase 1.4.12 released https://hbase.apache.org/  - Apache Kafka 2.2.2 released https://kafka.apache.org/ Content -- - Apache Jackrabbit Oak 1.8.18 released http://jackrabbit.apache.org IoT -- - Apache IoTDB (Incubating) 0.9.0 released http://iotdb.apache.org Libraries --  - Apache Olingo 4.7.0 released https://olingo.apache.org/ Machine Learning -- - Apache TVM (Incubating) 0.6.0 released https://tvm.apache.org/ Search --  - Apache Solr 8.3.1 released http://lucene.apache.org/ Web Frameworks --  - Apache Struts 2.5.22 released https://struts.apache.org/  - Apache MyFaces Core 2.3.6 released http://myfaces.apache.org/ Did You Know?  - Did you know that the ASF does not pay for code development or contributions by its Board of Directors, Executive Officers, 765 Individual ASF Members, 205 Apache Project Management Committees, 7,500+ Committers, and countless contributors? 75% of the ASF's budget supports critical Infrastructure services that 350+ projects and initiatives rely upon each day. We appreciate your generous contributions! https://donate.apache.org  - Did you know that, after 10 years in development, Apache Camel v3 is now available? https://camel.apache.org  - Did you know that the top 5 most active/visited Apache projects over the past year are: Hadoop, Kafka, Lucene, POI, ZooKeeper https://s.apache.org/w7bw1 Apache Community Notices:  - The Apache Way to Sustainable Open Source Success https://s.apache.org/GhnI  - Celebrating 20 Years Community-led Development "The Apache Way" https://s.apache.org/ASF20thAnniversary  - ASF Founders look back on 20 Years of the ASF https://blogs.apache.org/foundation/entry/our-founders-look-back-on  - Foundation Reports and Statements http://www.apache.org/foundation/reports.html  - ApacheCon: Tomorrow's Technology Today since 1998 http://s.apache.org/ApacheCon  - ASF Annual Report for FY2019 https://s.apache.org/FY2019AnnualReport  - The Apache Software Foundation 2018 Vision Statement https://s.apache.org/zqC3  - Foundation Statement –Apache Is Open. https://s.apache.org/PIRA  - "Success at Apache" focuses on the people and processes behind why the ASF "just works". https://blogs.apache.org/foundation/category/SuccessAtApache  - Please follow/like/re-tweet the ASF on social media: @TheASF on Twitter (https://twitter.com/TheASF) and on LinkedIn at https://www.linkedin.com/company/the-apache-software-foundation  - Do friend and follow us on the Apache Community Facebook page https://www.facebook.com/ApacheSoftwareFoundation/ and Twitter account https://twitter.com/ApacheCommunity  - The list of Apache project-related MeetUps can be found at http://events.apache.org/event/meetups.html  - Find out how you can participate with Apache community/projects/activities --opportunities open with Apache Camel, Apache HTTP Server, and more! https://helpwanted.apache.org/  - Are your software solutions Powered by Apache? Download & use our "Powered By" logos http://www.apache.org/foundation/press/kit/#poweredby = = = For real-time updates, sign up for Apache-related news by sending mail to [email protected] and follow @TheASF on Twitter. For a broader spectrum from the Apache community, https://twitter.com/PlanetApache provides an aggregate of Project activities as well as the personal blogs and tweets of select ASF Committers. [Less]

This week, we are excited to launch the 2020 ASF Community Survey, with which we will gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We ... [More] want to find areas where we can continue to do great work and others where we need to provide more support so that our projects can keep growing healthy and diverse. This joint effort was long overdue: our last survey of this kind was implemented in 2016 [1], which means that all the information we currently have about our communities is outdated. For this new version of the survey, we have hired Bitergia to design it, a company expert in analysing open source communities and other types of software development teams. They have experience in this type of surveys and research in open source communities. Among other studies, their previous work includes an analysis in gender diversity in technical contributions for OpenStack [2]. The 2020 ASF Community Survey is the first part of a two-stage research. The second part consists of interviews with people who have contributed to the ASF, in order to assess their experience. We'll share more on this second part of the project soon. This survey and research are part of the ASF efforts to build a more equitable, inclusive and diverse community. They are run by the Vice Presidency of Diversity and Inclusion, a team formed last May. We'll share a broader update about this group in January. If you have an apache.org email address you will receive an email by Thursday, Dec 5 at 3PM PST, with a link to the survey. Please take 15 minutes to complete it. If you didn't receive the email or you do not have an apache.org email address, please use this link to complete the survey: https://communitysurvey.limequery.org/454363 We are looking to hear from everyone in our community: from users and contributors, to committers and PMCs. Everyone's voice matters. Find more information about the 2020 ASF Community Survey on its page on Confluence [3], including the privacy policy governing this initiative. If you are part of our community, either as a user, contributor, or both, your participation is paramount to the success of this project! Please consider filling out the survey, and share this blog on social media, send it to your fellow Apache contributors. As individuals form the Apache community, your opinion matters: we need to hear your voice. Links [1] https://cwiki.apache.org/confluence/display/COMDEV/ASF+Committer+Diversity+Survey+-+2016 [2] https://blog.bitergia.com/tag/openstack/ [3] https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey # # # [Less]

This week, we are excited to launch the 2020 ASF Community Survey, with which we will gather scientific data that allows us to understand our community better, both in its demographic composition, and also in collaboration styles and preferences. We ... [More] want to find areas where we can continue to do great work and others where we need to provide more support so that our projects can keep growing healthy and diverse. This joint effort was long overdue: our last survey of this kind was implemented in 2016 [1], which means that all the information we currently have about our communities is outdated.  For this new version of the survey, we have hired Bitergia to design it, a company expert in analysing open source communities and other types of software development teams. They have experience in this type of surveys and research in open source communities. Among other studies, their previous work includes an analysis in gender diversity in technical contributions for OpenStack [2]. The 2020 ASF Community Survey is the first part of a two-stage research. The second part consists of interviews with people who have contributed to the ASF, in order to assess their experience. We'll share more on this second part of the project soon.  This survey and research are part of the ASF efforts to build a more equitable, inclusive and diverse community. They are run by the Vice Presidency of Diversity and Inclusion, a team formed last May. We'll share a broader update about this group in January. If you have an apache.org email address you will receive an email by Thursday, Dec 5 at 3PM PST, with a link to the survey. Please take 15 minutes to complete it. If you didn't receive the email or you do not have an apache.org email address, please use this link to complete the survey:  https://communitysurvey.limequery.org/454363 We are looking to hear from everyone in our community: from users and contributors, to committers and PMCs. Everyone's voice matters.  Find more information about the 2020 ASF Community Survey on its page on Confluence [3], including the privacy policy governing this initiative. If you are part of our community, either as a user, contributor, or both, your participation is paramount to the success of this project! Please consider filling out the survey, and share this blog on social media, send it to your fellow Apache contributors. As individuals form the Apache community, your opinion matters: we need to hear your voice. Links [1] https://cwiki.apache.org/confluence/display/COMDEV/ASF+Committer+Diversity+Survey+-+2016[2] https://blog.bitergia.com/tag/openstack/[3] https://cwiki.apache.org/confluence/display/EDI/Launch+Plan+-+The+2020+ASF+Community+Survey # # # [Less]