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: CONTRIBUTING.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,20 +29,20 @@ All types of contributions are encouraged and valued. See the [Table of Contents
29
29
## Code of Conduct
30
30
31
31
This project and everyone participating in it is governed by the
32
-
[profet Code of Conduct](https://github.com/alan-turing-institute/profetblob/master/CODE_OF_CONDUCT.md).
32
+
[profet Code of Conduct](https://github.com/ccpem/profetblob/master/CODE_OF_CONDUCT.md).
33
33
By participating, you are expected to uphold this code. Please report unacceptable behavior
34
34
to <>.
35
35
36
36
37
37
## I Have a Question
38
38
39
-
> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/alan-turing-institute/profet).
39
+
> If you want to ask a question, we assume that you have read the available [Documentation](https://github.com/ccpem/profet).
40
40
41
-
Before you ask a question, it is best to search for existing [Issues](https://github.com/alan-turing-institute/profet/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
41
+
Before you ask a question, it is best to search for existing [Issues](https://github.com/ccpem/profet/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
42
42
43
43
If you then still feel the need to ask a question and need clarification, we recommend the following:
44
44
45
-
- Open an [Issue](https://github.com/alan-turing-institute/profet/issues/new).
45
+
- Open an [Issue](https://github.com/ccpem/profet/issues/new).
46
46
- Provide as much context as you can about what you're running into.
47
47
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
48
48
@@ -61,8 +61,8 @@ We will then take care of the issue as soon as possible.
61
61
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
62
62
63
63
- Make sure that you are using the latest version.
64
-
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/alan-turing-institute/profet). If you are looking for support, you might want to check [this section](#i-have-a-question)).
65
-
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/alan-turing-institute/profetissues?q=label%3Abug).
64
+
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](https://github.com/ccpem/profet). If you are looking for support, you might want to check [this section](#i-have-a-question)).
65
+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/ccpem/profetissues?q=label%3Abug).
66
66
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
67
67
- Collect information about the bug:
68
68
- Stack trace (Traceback)
@@ -76,7 +76,7 @@ A good bug report shouldn't leave others needing to chase you up for more inform
76
76
77
77
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
78
78
79
-
- Open an [Issue](https://github.com/alan-turing-institute/profet/issues/new). (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 not to label the issue.)
79
+
- Open an [Issue](https://github.com/ccpem/profet/issues/new). (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 not to label the issue.)
80
80
- Explain the behavior you would expect and the actual behavior.
81
81
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
82
82
- Provide the information you collected in the previous section.
@@ -95,14 +95,14 @@ This section guides you through submitting an enhancement suggestion for profet,
95
95
#### Before Submitting an Enhancement
96
96
97
97
- Make sure that you are using the latest version.
98
-
- Read the [documentation](https://github.com/alan-turing-institute/profet) carefully and find out if the functionality is already covered.
99
-
- Perform a [search](https://github.com/alan-turing-institute/profet/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
98
+
- Read the [documentation](https://github.com/ccpem/profet) carefully and find out if the functionality is already covered.
99
+
- Perform a [search](https://github.com/ccpem/profet/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
100
100
- 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 convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
101
101
102
102
<!-- omit in toc -->
103
103
#### How Do I Submit a Good Enhancement Suggestion?
104
104
105
-
Enhancement suggestions are tracked as [GitHub issues](https://github.com/alan-turing-institute/profet/issues).
105
+
Enhancement suggestions are tracked as [GitHub issues](https://github.com/ccpem/profet/issues).
106
106
107
107
- Use a **clear and descriptive title** for the issue to identify the suggestion.
108
108
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
To test the installation, you need to have pytest and pytest-cov packagages installed which can be done as follows.
@@ -128,11 +128,11 @@ a .pdb file. The file will be cached in the "~/.pdb" directory for future use.
128
128
129
129
## Documentation
130
130
131
-
You can find more documentation including a description of the python api [here](https://alan-turing-institute.github.io/profet/).
131
+
You can find more documentation including a description of the python api [here](https://ccpem.github.io/profet/).
132
132
133
133
## Issues and Feature Requests
134
134
135
-
If you run into an issue, or if you find a workaround for an existing issue, we would very much appreciate it if you could post your question or code as a [GitHub issue](https://github.com/alan-turing-institute/profet/issues).
135
+
If you run into an issue, or if you find a workaround for an existing issue, we would very much appreciate it if you could post your question or code as a [GitHub issue](https://github.com/ccpem/profet/issues).
0 commit comments