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 feb0f64f833e79f0ccd0f2edcfc814cdc2844d63 Author: Richard Zowalla <[email protected]> AuthorDate: Fri Apr 3 19:34:06 2026 +0200 A few website fixes: - _includes/footer.html — Copyright year updated from 2024 to 2026 - contribute/BYLAWS.md — Replaced "JIRA or Github pull" with "Github pull request" in the Code Change and Non-Code Change action rows - releases/2.8.5/Contributing-to-Storm.md — Issue tracker and "Newbie" label links changed from Jira to GitHub Issues - getting-help.md — Removed the Google Groups deprecation notice, the googlegroups Q&A section, and the IRC/freenode section --- _includes/footer.html | 2 +- contribute/BYLAWS.md | 4 ++-- getting-help.md | 9 --------- releases/2.8.5/Contributing-to-Storm.md | 4 ++-- 4 files changed, 5 insertions(+), 14 deletions(-) diff --git a/_includes/footer.html b/_includes/footer.html index 57cf00a7d6..f68877e5e7 100644 --- a/_includes/footer.html +++ b/_includes/footer.html @@ -51,7 +51,7 @@ <hr/> <div class="row"> <div class="col-md-12"> - <p align="center">Copyright © 2024 <a href="https://www.apache.org";>Apache Software Foundation</a> + <p align="center">Copyright © 2026 <a href="https://www.apache.org";>Apache Software Foundation</a> . All Rights Reserved. <br>Apache Storm, Apache, the Apache feather logo, and the Apache Storm project logos are trademarks of The Apache Software Foundation. <br>All other marks mentioned may be trademarks or registered trademarks of their respective owners.</p> diff --git a/contribute/BYLAWS.md b/contribute/BYLAWS.md index f0725bfd59..cba1d8452a 100644 --- a/contribute/BYLAWS.md +++ b/contribute/BYLAWS.md @@ -85,8 +85,8 @@ 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 |JIRA or Github pull (with notification sent to [email protected]) | +| 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]) | | 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/getting-help.md b/getting-help.md index b369103f3c..6ea637b57e 100644 --- a/getting-help.md +++ b/getting-help.md @@ -4,8 +4,6 @@ title: Documentation --- ## Getting help -__NOTE:__ The google groups account [email protected] is now officially deprecated in favor of the Apache-hosted user/dev mailing lists. - ### Storm Users Storm users should send messages and subscribe to [[email protected]](mailto:[email protected]). @@ -33,10 +31,3 @@ If you are building storm from source, developing new features, or otherwise hac 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]). -#### What will happen with [email protected]? -All existing messages will remain archived there, and can be accessed/searched [here](https://groups.google.com/forum/#!forum/storm-user). - -New messages sent to [email protected] will either be rejected/bounced or replied to with a message to direct the email to the appropriate Apache-hosted group. - -#### IRC -You can also come to the #storm-user room on [freenode](https://freenode.net/). You can usually find a Storm developer there to help you out. \ No newline at end of file diff --git a/releases/2.8.5/Contributing-to-Storm.md b/releases/2.8.5/Contributing-to-Storm.md index 2c6ad1f2d9..57dbe9be29 100644 --- a/releases/2.8.5/Contributing-to-Storm.md +++ b/releases/2.8.5/Contributing-to-Storm.md @@ -6,7 +6,7 @@ documentation: true ### Getting started with contributing -Some of the issues on the [issue tracker](https://issues.apache.org/jira/browse/STORM) are marked with the ["Newbie"](https://issues.apache.org/jira/browse/STORM-2891?jql=project%20%3D%20STORM%20AND%20status%20%3D%20Open%20AND%20labels%20in%20(newbie%2C%20%22newbie%2B%2B%22)) 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 requ [...] +Some of the issues on the [issue tracker](https://github.com/apache/storm/issues) are marked with the ["Newbie"](https://github.com/apache/storm/labels/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 @@ -18,7 +18,7 @@ Contributions to the Storm codebase should be sent as [GitHub](https://github.co For small patches, feel free to submit pull requests directly for them. For larger contributions, please use the following process. The idea behind this process is to prevent any wasted work and catch design issues early on: -1. Open an issue on the [issue tracker](https://issues.apache.org/jira/browse/STORM) if one doesn't exist already +1. Open an issue on the [issue tracker](https://github.com/apache/storm/issues) if one doesn't exist already 2. Comment on the issue with your plan for implementing the issue. Explain what pieces of the codebase you're going to touch and how everything is going to fit together. 3. Storm committers will iterate with you on the design to make sure you're on the right track 4. Implement your issue, submit a pull request, and iterate from there.
