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: .github/CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,14 +16,14 @@ Note that your contributions must be your own work and licensed under the same t
16
16
## Reporting bugs
17
17
18
18
First, search the issue tracker to see if the bug is already there.
19
-
Please use the [discussion forums](http://discussion.oxyplot.org/) if you are unsure whether it is a bug in the library or a problem in your code.
19
+
Please use the [discussion forums](https://oxyplot.userecho.com/) if you are unsure whether it is a bug in the library or a problem in your code.
20
20
When you are sure, please add defects in the issue tracker.
21
21
22
22
It is very helpful to get the generated code (use `CTRL+ALT+C` in the plot control) and report (`CTRL+ALT+R`) of the bug plot. You can also take a screen shot and paste it into the description.
23
23
24
24
Please use markdown to format your code blocks with [syntax highlighting](https://help.github.com/articles/github-flavored-markdown/#syntax-highlighting) to make it easier for everyone to read.
25
25
26
-
You could also use services like http://snipt.org or https://gist.github.com to share code snippets.
26
+
You could also use services like https://snipt.org or https://gist.github.com to share code snippets.
27
27
28
28
A bug report should include:
29
29
@@ -36,7 +36,7 @@ A bug report should include:
36
36
37
37
## Suggesting new features
38
38
39
-
Please use the [discussion forums](http://discussion.oxyplot.org/) or add it directly in the issue tracker in the same way as bug reports.
39
+
Please use the [discussion forums](https://oxyplot.userecho.com/) or add it directly in the issue tracker in the same way as bug reports.
40
40
41
41
42
42
## Create your own fork
@@ -54,7 +54,7 @@ The repository contains two branches:
54
54
55
55
You should base your work on the `develop` branch.
56
56
57
-
See [A successful git branching model](http://nvie.com/posts/a-successful-git-branching-model/) for more information about the branching model in use.
57
+
See [A successful git branching model](https://nvie.com/posts/a-successful-git-branching-model/) for more information about the branching model in use.
58
58
59
59
Create a branch for the bugfix/feature you want to work on: `git branch bugfix-some-error`
@@ -130,10 +130,10 @@ Please contribute by creating pull requests!
130
130
131
131
## Contributing to the website
132
132
133
-
The source of the [oxyplot.github.io](https://oxyplot.github.io/) web site can be found in the [oxyplot.github.io](http://github.com/oxyplot/oxyplot.github.io) repository.
133
+
The source of the [oxyplot.github.io](https://oxyplot.github.io/) web site can be found in the [oxyplot.github.io](https://github.com/oxyplot/oxyplot.github.io) repository.
134
134
Please contribute by creating pull requests!
135
135
136
-
The web-site is built by [GitHub](http://github.com/) with [Jekyll](http://jekyllrb.com/).
136
+
The web-site is built by [GitHub](https://github.com/) with [Jekyll](https://jekyllrb.com/).
Copy file name to clipboardExpand all lines: CODE_OF_CONDUCT.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
34
34
35
35
## Enforcement
36
36
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at mail@oxyplot.org. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
37
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
38
39
39
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
0 commit comments