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
Copy file name to clipboardExpand all lines: README.rst
+3-42Lines changed: 3 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -171,52 +171,13 @@ an example application `here <https://github.com/h2oai/h2o-droplets/tree/master/
171
171
Contributing
172
172
~~~~~~~~~~~~
173
173
174
-
Look at our `list of JIRA
175
-
tasks <https://0xdata.atlassian.net/projects/SW/issues>`__ or send your idea to [email protected].
174
+
Just drop us a PR!
175
+
For inspiration look at our `list of issues <https://github.com/h2oai/sparkling-water/issues/new/choose>`__, feel free to create one.
176
176
177
177
Filing Bug Reports and Feature Requests
178
178
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
179
179
180
-
You can file a bug report of feature request directly in the Sparkling Water JIRA page at `http://jira.h2o.ai/ <https://0xdata.atlassian.net/projects/SW/issues>`__.
181
-
182
-
1. Log in to the Sparkling Water JIRA tracking system. (Create an account if necessary.)
183
-
184
-
2. Once inside the home page, click the **Create** button.
- Select the Project that you want to file the issue under. For example, if this is an open source public bug, you should file it under **SW (SW)**.
197
-
- Specify the Issue Type. For example, if you believe you've found a bug, then select **Bug**, or if you want to request a new feature, then select **New Feature**.
198
-
- Provide a short but concise summary about the issue. The summary will be shown when engineers organize, filter, and search for Jira tickets.
199
-
- Specify the urgency of the issue using the Priority dropdown menu.
200
-
- If there is a due date specify it with the Due Date.
201
-
- The Components drop down refers to the API or language that the issue relates to. (See the drop down menu for available options.)
202
-
- You can leave Affects Version/s, Fix Version\s, and Assignee fields blank. Our engineering team will fill this in.
203
-
- Add a detailed description of your bug in the Description section. Best practice for descriptions include:
204
-
205
-
- A summary of what the issue is
206
-
- What you think is causing the issue
207
-
- Reproducible code that can be run end to end without requiring an engineer to edit your code. Use {code} {code} around your code to make it appear in code format.
208
-
- Any scripts or necessary documents. Add by dragging and dropping your files into the create issue dialogue box.
209
-
210
-
You can be able to leave the rest of the ticket blank.
211
-
212
-
4. When you are done with your ticket, simply click on the **Create** button at the bottom of the page.
After you click **Create**, a pop up will appear on the right side of your screen with a link to your Jira ticket. It will have the form `https://0xdata.atlassian.net/browse/SW-####`. You can use this link to later edit your ticket.
218
-
219
-
Please note that your Jira ticket number along with its summary will appear in one of the Jira ticket slack channels, and anytime you update the ticket anyone associated with that ticket, whether as the assignee or a watcher will receive an email with your changes.
180
+
You can file a bug report of feature request directly in Github Issues `Github Issues <https://github.com/h2oai/sparkling-water/issues/new/choose>`__.
0 commit comments