This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/storm-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 2539746120 publishing 2025-05-02T18:39:32+00:00
2539746120 is described below
commit 25397461208d932249a99684c752f59737ec505c
Author: GitHub Actions Bot <>
AuthorDate: Fri May 2 18:39:32 2025 +0000
publishing 2025-05-02T18:39:32+00:00
---
contribute/Contributing-to-Storm.html | 4 ++--
feed.xml | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/contribute/Contributing-to-Storm.html
b/contribute/Contributing-to-Storm.html
index bc911ef785..637113efae 100644
--- a/contribute/Contributing-to-Storm.html
+++ b/contribute/Contributing-to-Storm.html
@@ -167,7 +167,7 @@
<div class="documentation-content"><h3
id="getting-started-with-contributing">Getting started with contributing</h3>
-<p>Some of the issues on the <a
href="https://issues.apache.org/jira/browse/STORM";>issue tracker</a> 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.</p>
+<p>Some of the issues on the <a
href="https://github.com/apache/storm/issues";>issue tracker</a> 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.</p>
<h3 id="learning-the-codebase">Learning the codebase</h3>
@@ -180,7 +180,7 @@
<p>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:</p>
<ol>
-<li>Open an issue on the <a
href="https://issues.apache.org/jira/browse/STORM";>JIRA issue tracker</a> if
one doesn't exist already</li>
+<li>Open an issue on the <a
href="https://github.com/apache/storm/issues";>issue tracker</a> if one
doesn't exist already</li>
<li>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.</li>
<li>Storm committers will iterate with you on the design to make sure
you're on the right track</li>
<li>Read through the developer documentation on how to build, code style,
testing, etc <a
href="https://github.com/apache/storm/blob/master/DEVELOPER.md";>DEVELOPER.md</a>
</li>
diff --git a/feed.xml b/feed.xml
index 16d81bf675..77fc6485b0 100644
--- a/feed.xml
+++ b/feed.xml
@@ -5,8 +5,8 @@
<description></description>
<link>https://storm.apache.org/</link>
<atom:link href="https://storm.apache.org/feed.xml"; rel="self"
type="application/rss+xml"/>
- <pubDate>Fri, 02 May 2025 18:35:23 +0000</pubDate>
- <lastBuildDate>Fri, 02 May 2025 18:35:23 +0000</lastBuildDate>
+ <pubDate>Fri, 02 May 2025 18:38:09 +0000</pubDate>
+ <lastBuildDate>Fri, 02 May 2025 18:38:09 +0000</lastBuildDate>
<generator>Jekyll v3.9.3</generator>
<item>
