@@ -34,23 +34,23 @@ community looks forward to your contributions. 🎉
34
34
## Code of Conduct
35
35
36
36
This project and everyone participating in it is governed by the
37
- [ django-tasks-scheduler Code of Conduct] ( https://github.com/dsoftwareinc /django-tasks-scheduler/blob/main/CODE_OF_CONDUCT.md ) .
37
+ [ django-tasks-scheduler Code of Conduct] ( https://github.com/django-commons /django-tasks-scheduler/blob/main/CODE_OF_CONDUCT.md ) .
38
38
By participating, you are expected to uphold this code. Please report unacceptable behavior
39
39
40
40
41
41
## I Have a Question
42
42
43
43
> If you want to ask a question, we assume that you have read the
44
- > available [ Documentation] ( https://github.com/dsoftwareinc /django-tasks-scheduler ) .
44
+ > available [ Documentation] ( https://github.com/django-commons /django-tasks-scheduler ) .
45
45
46
46
Before you ask a question, it is best to search for
47
- existing [ Issues] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues ) that might help you. In case you have
47
+ existing [ Issues] ( https://github.com/django-commons /django-tasks-scheduler/issues ) that might help you. In case you have
48
48
found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to
49
49
search the internet for answers first.
50
50
51
51
If you then still feel the need to ask a question and need clarification, we recommend the following:
52
52
53
- - Open an [ Issue] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues/new ) .
53
+ - Open an [ Issue] ( https://github.com/django-commons /django-tasks-scheduler/issues/new ) .
54
54
- Provide as much context as you can about what you're running into.
55
55
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
56
56
@@ -90,11 +90,11 @@ following steps in advance to help us fix any potential bug as fast as possible.
90
90
- Make sure that you are using the latest version.
91
91
- Determine if your bug is really a bug and not an error on your side, e.g., using incompatible environment
92
92
components/versions (Make sure that you have read
93
- the [ documentation] ( https://github.com/dsoftwareinc /django-tasks-scheduler ) . If you are looking for support, you might
93
+ the [ documentation] ( https://github.com/django-commons /django-tasks-scheduler ) . If you are looking for support, you might
94
94
want to check [ this section] ( #i-have-a-question ) ).
95
95
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there
96
96
is not already a bug report existing for your bug or error in
97
- the [ bug tracker] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues?q=label%3Abug ) .
97
+ the [ bug tracker] ( https://github.com/django-commons /django-tasks-scheduler/issues?q=label%3Abug ) .
98
98
- Also make sure to search the internet (including Stack Overflow) to see if users outside the GitHub community have
99
99
discussed the issue.
100
100
- Collect information about the bug:
@@ -114,7 +114,7 @@ following steps in advance to help us fix any potential bug as fast as possible.
114
114
115
115
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
116
116
117
- - Open an [ Issue] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues/new ) .
117
+ - Open an [ Issue] ( https://github.com/django-commons /django-tasks-scheduler/issues/new ) .
118
118
(Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and
119
119
not to label the issue.)
120
120
- Explain the behavior you would expect and the actual behavior.
@@ -146,9 +146,9 @@ community to understand your suggestion and find related suggestions.
146
146
#### Before Submitting an Enhancement
147
147
148
148
- Make sure that you are using the latest version.
149
- - Read the [ documentation] ( https://github.com/dsoftwareinc /django-tasks-scheduler ) carefully and find out if the
149
+ - Read the [ documentation] ( https://github.com/django-commons /django-tasks-scheduler ) carefully and find out if the
150
150
functionality is already covered, maybe by an individual configuration.
151
- - Perform a [ search] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues ) to see if the enhancement has
151
+ - Perform a [ search] ( https://github.com/django-commons /django-tasks-scheduler/issues ) to see if the enhancement has
152
152
already
153
153
been suggested. If it has, add a comment to the existing issue instead of opening a new one.
154
154
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to
@@ -160,7 +160,7 @@ community to understand your suggestion and find related suggestions.
160
160
161
161
#### How Do I Submit a Good Enhancement Suggestion?
162
162
163
- Enhancement suggestions are tracked as [ GitHub issues] ( https://github.com/dsoftwareinc /django-tasks-scheduler/issues ) .
163
+ Enhancement suggestions are tracked as [ GitHub issues] ( https://github.com/django-commons /django-tasks-scheduler/issues ) .
164
164
165
165
- Use a ** clear and descriptive title** for the issue to identify the suggestion.
166
166
- Provide a ** step-by-step description of the suggested enhancement** in as many details as possible.
@@ -180,7 +180,7 @@ Enhancement suggestions are tracked as [GitHub issues](https://github.com/dsoftw
180
180
### Your First Code Contribution
181
181
182
182
Unsure where to begin contributing? You can start by looking through
183
- [ help-wanted issues] ( https://github.com/dsoftwareinc/wiwik /labels/help%20wanted ) .
183
+ [ help-wanted issues] ( https://github.com/django-commons/django-tasks-scheduler /labels/help%20wanted ) .
184
184
185
185
Never contributed to open source before? Here are a couple of friendly
186
186
tutorials:
0 commit comments