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
The following commit(s) were added to refs/heads/main by this push:
new 09556ce765 Remove references to Jira
09556ce765 is described below
commit 09556ce765efd05309d9d252b77cd5266c83081d
Author: Richard Zowalla <[email protected]>
AuthorDate: Fri May 2 20:37:35 2025 +0200
Remove references to Jira
---
contribute/Contributing-to-Storm.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/contribute/Contributing-to-Storm.md
b/contribute/Contributing-to-Storm.md
index 351503a1aa..511501c122 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://issues.apache.org/jira/browse/STORM) 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 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.
### 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 [JIRA 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. Read through the developer documentation on how to build, code style,
testing, etc
[DEVELOPER.md](https://github.com/apache/storm/blob/master/DEVELOPER.md)
