This is an automated email from the ASF dual-hosted git repository. rzo1 pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/storm-site.git
commit df0f70d15ed9f8fdb4b8d3c9736962f39b9e41c8 Author: Richard Zowalla <[email protected]> AuthorDate: Fri Apr 3 19:36:55 2026 +0200 Fix grammar and typos --- about/free-and-open-source.md | 2 +- about/simple-api.md | 2 +- contribute/BYLAWS.md | 2 +- contribute/Contributing-to-Storm.md | 2 +- contribute/People.md | 2 +- documentation/Understanding-the-parallelism-of-a-Storm-topology.md | 2 +- getting-help.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/about/free-and-open-source.md b/about/free-and-open-source.md index 0dcc660cfe..b521d989dc 100644 --- a/about/free-and-open-source.md +++ b/about/free-and-open-source.md @@ -8,7 +8,7 @@ Apache Storm is a free and open source project licensed under the [Apache Licens Apache Storm has a large and growing ecosystem of libraries and tools to use in conjunction with Apache Storm including everything from: 1. *Spouts*: These spouts integrate with queueing systems such as JMS, Kafka, Redis pub/sub, and more. -2. *storm-state*: storm-state makes it easy to manage large amounts of in-memory state in your computations in a reliable by using a distributed filesystem for persistence +2. *storm-state*: storm-state makes it easy to manage large amounts of in-memory state in your computations reliably by using a distributed filesystem for persistence 3. *Database integrations*: There are helper bolts for integrating with various databases, such as MongoDB, RDBMS's, Cassandra, and more. 4. Other miscellaneous utilities diff --git a/about/simple-api.md b/about/simple-api.md index 4ed8439238..9812520a1d 100644 --- a/about/simple-api.md +++ b/about/simple-api.md @@ -10,6 +10,6 @@ A **bolt** processes any number of input streams and produces any number of new A **topology** is a network of spouts and bolts, with each edge in the network representing a bolt subscribing to the output stream of some other spout or bolt. A topology is an arbitrarily complex multi-stage stream computation. Topologies run indefinitely when deployed. -Apache Storm has a "local mode" where a Apache Storm cluster is simulated in-process. This is useful for development and testing. The "storm" command line client is used when ready to submit a topology for execution on an actual cluster. +Apache Storm has a "local mode" where an Apache Storm cluster is simulated in-process. This is useful for development and testing. The "storm" command line client is used when ready to submit a topology for execution on an actual cluster. The [storm-starter](https://github.com/apache/storm/tree/master/examples/storm-starter) project contains example topologies for learning the basics of Apache Storm. Learn more about how to use Apache Storm by reading the [tutorial](/releases/current/Tutorial.html) and the [documentation](/releases/current/index.html). diff --git a/contribute/BYLAWS.md b/contribute/BYLAWS.md index cba1d8452a..381f693a05 100644 --- a/contribute/BYLAWS.md +++ b/contribute/BYLAWS.md @@ -86,7 +86,7 @@ This section describes the various actions which are undertaken within the proje | Actions | Description | Approval | Binding Votes | Minimum Length | Mailing List | |---------|-------------|----------|---------------|----------------|--------------| | Code Change | A change made to a source code of the project and committed by a Committer. | A minimum of one +1 from a Committer other than the one who authored the patch, and no -1s. The code can be committed after the first +1. If a -1 is received to the patch within 7 days after the patch was posted, it may be reverted immediately if it was already merged. | Active Committers | 1 day from initial patch (**Note:** Committers should consider allowing more time for review based on the [...] -| Non-Code Change | A change made to a repository of the project and committed by a Committer. This includes documentation, website content, etc., but not source code, unless only comments are being modified. | Lazy Consensus | Active Committers | At the discression of the Committer | Github pull request (with notification sent to [email protected]) | +| Non-Code Change | A change made to a repository of the project and committed by a Committer. This includes documentation, website content, etc., but not source code, unless only comments are being modified. | Lazy Consensus | Active Committers | At the discretion of the Committer | Github pull request (with notification sent to [email protected]) | | Product Release | A vote is required to accept a proposed release as an official release of the project. Any Committer may call for a release vote at any point in time. | Majority Approval | Active PMC members | 3 days | [email protected] | | Adoption of New Codebase | When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue. This also covers the creation of new sub-projects and submodules within the project as well as merging of feature branches. | 2/3 Majority | Active PMC members | 6 days | [email protected] | | New Committer | When a new Committer is proposed for the project. | Consensus Approval | Active PMC members | 3 days | [email protected] | diff --git a/contribute/Contributing-to-Storm.md b/contribute/Contributing-to-Storm.md index eec8531093..c77e21bbe2 100644 --- a/contribute/Contributing-to-Storm.md +++ b/contribute/Contributing-to-Storm.md @@ -6,7 +6,7 @@ documentation: true ### Getting started with contributing -Some of the issues on the [issue tracker](https://github.com/apache/storm/issues) are marked with the "Newbie" label. If you're interesting in contributing to Storm but don't know where to begin, these are good issues to start with. These issues are a great way to get your feet wet with learning the codebase because they require learning about only an isolated portion of the codebase and are a relatively small amount of work. +Some of the issues on the [issue tracker](https://github.com/apache/storm/issues) are marked with the "Newbie" label. If you're interested in contributing to Storm but don't know where to begin, these are good issues to start with. These issues are a great way to get your feet wet with learning the codebase because they require learning about only an isolated portion of the codebase and are a relatively small amount of work. ### Learning the codebase diff --git a/contribute/People.md b/contribute/People.md index 11abaf1ba5..b5be3cb47b 100644 --- a/contribute/People.md +++ b/contribute/People.md @@ -4,4 +4,4 @@ layout: documentation documentation: true --- -Current list of committers and PMC's are [here](https://projects.apache.org/committee.html?storm) +Current list of committers and PMC members is [here](https://projects.apache.org/committee.html?storm) diff --git a/documentation/Understanding-the-parallelism-of-a-Storm-topology.md b/documentation/Understanding-the-parallelism-of-a-Storm-topology.md index 46b641f273..e3f77e41e3 100644 --- a/documentation/Understanding-the-parallelism-of-a-Storm-topology.md +++ b/documentation/Understanding-the-parallelism-of-a-Storm-topology.md @@ -1,4 +1,4 @@ --- --- <meta http-equiv="refresh" content="0; url=http://storm.apache.org/releases/current/Understanding-the-parallelism-of-a-Storm-topology.html";> -<link rel="canonical" href="httpw://storm.apache.org/releases/current/Understanding-the-parallelism-of-a-Storm-topology.html" /> +<link rel="canonical" href="https://storm.apache.org/releases/current/Understanding-the-parallelism-of-a-Storm-topology.html"; /> diff --git a/getting-help.md b/getting-help.md index 6ea637b57e..042552103f 100644 --- a/getting-help.md +++ b/getting-help.md @@ -29,5 +29,5 @@ If you are using a pre-built binary distribution of Storm, then chances are you If you are building storm from source, developing new features, or otherwise hacking storm source code, then [[email protected]](mailto:[email protected]) is more appropriate. -If you are committers and/or PMCs, or contributors looking for following up and participating development of Storm, then you would want to also subscribe [[email protected]]([email protected]) in addition to [[email protected]]([email protected]). +If you are committers and/or PMCs, or contributors looking to follow and participate in the development of Storm, then you would want to also subscribe to [[email protected]]([email protected]) in addition to [[email protected]]([email protected]).
