You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context and description of the issue Context: Pravega is a tiered storage system for data streams. It offers a storage-oriented approach for managing stream data compared to other systems like Apache Kafka. Moreover, Pravega streams are elastic (i.e., the number of stream partitions can dynamically change without the applications noticing), which no other event streaming system offers today. Pravega has a good ecosystem of client bindings (e.g., Java, Rust, Python), connectors with stream processing engines (e.g., Flink, Spark), and Kubernetes operators not only for Pravega itself, but also for required components (Apache Bookkeeper, Apache Zookeeper). Pravega has been developed enforcing high technical standards and following strict open source guidelines. Pravega and its ecosystem (connectors, Kubernetes operators) are valuable and can be directly exploitable, as we are demonstrating with use cases in the context of European Research projects (https://neardata.eu/, https://cloudskin.eu/).
Problem description: Due to a shift in priorities of the main supporting company, the project is lacking traction in terms of contributions in the last months. We need a plan to open the maintainer group and grow the community of committers, so the project can continue its development in this new scenario.
The text was updated successfully, but these errors were encountered:
Project Name
Pravega
Project Website
https://pravega.io/
Contact Details
@tkaitchuck @RaulGracia @crazyzhou @fpj
Links to communication channels
https://join.slack.com/t/pravega-io/shared_invite/zt-245sgpw47-vbLBLiLfBdW9TlKemXkUnw
cncf-pravega-dev@lists.cncf.io
Context and description of the issue
Context: Pravega is a tiered storage system for data streams. It offers a storage-oriented approach for managing stream data compared to other systems like Apache Kafka. Moreover, Pravega streams are elastic (i.e., the number of stream partitions can dynamically change without the applications noticing), which no other event streaming system offers today. Pravega has a good ecosystem of client bindings (e.g., Java, Rust, Python), connectors with stream processing engines (e.g., Flink, Spark), and Kubernetes operators not only for Pravega itself, but also for required components (Apache Bookkeeper, Apache Zookeeper). Pravega has been developed enforcing high technical standards and following strict open source guidelines. Pravega and its ecosystem (connectors, Kubernetes operators) are valuable and can be directly exploitable, as we are demonstrating with use cases in the context of European Research projects (https://neardata.eu/, https://cloudskin.eu/).
Problem description: Due to a shift in priorities of the main supporting company, the project is lacking traction in terms of contributions in the last months. We need a plan to open the maintainer group and grow the community of committers, so the project can continue its development in this new scenario.
The text was updated successfully, but these errors were encountered: