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
+23Lines changed: 23 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,7 @@
1
+
# CONTRIBUTING
2
+
3
+
## Bug Reports
4
+
1
5
Did you encounter an issue with using Slic3r? Fear not! This guide will help you to write a good bug report in just a few, simple steps.
2
6
3
7
There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/alexrj/Slic3r/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report.
@@ -24,8 +28,27 @@ Please make sure only to include one issue per report. If you encounter multiple
24
28
25
29
Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to Slic3r.
26
30
31
+
## Submitting a Patch
32
+
27
33
Do you want to help fix issues in or add features to Slic3r? That's also very, very welcome :)
28
34
35
+
Basically you can follow the [GitHub
36
+
flow](https://guides.github.com/introduction/flow/) for submitting
37
+
patches, but please also read below for more specific information about
38
+
contributing to the Slic3r project.
39
+
40
+
* Development
41
+
* [Low Effort tasks](https://github.com/slic3r/Slic3r/labels/Low%20Effort): pick one of them!
42
+
* [Help Wanted tasks](https://github.com/slic3r/Slic3r/labels/help%20wanted): pick one of them!
43
+
* [More available tasks](https://github.com/slic3r/Slic3r/milestone/32): let's discuss together before you start working on them
44
+
* Please comment in the related GitHub issue that you are working on it so that other people know.
45
+
* Contribute to the [Manual](http://manual.slic3r.org/)! (see its [GitHub repository](https://github.com/slic3r/Slic3r-Manual))
46
+
* You can also find us in #slic3r on [FreeNode](https://webchat.freenode.net): talk to _Sound_, _LoH_ or the other members of the Slic3r community.
47
+
* Add an [issue](https://github.com/slic3r/Slic3r/issues) to the GitHub tracker if it isn't already present.
48
+
* Update Slic3r's test suite to improve test coverage [Writing Test Cases](https://github.com/slic3r/Slic3r/wiki/Code:-Writing-Test-Cases)
* A good place to start if you can is to look over the [Pull Request or Bust](https://github.com/alexrj/Slic3r/milestones/Pull%20Request%20or%20Bust) milestone. This contains all of the things (mostly new feature requests) that there isn't time or resources to address at this time.
30
53
* Things that are probably fixable via scripts (usually marked as such) have the lowest bar to getting something that works, as you don't need to recompile Slic3r to test.
31
54
* If you're starting on an issue, please say something in the related issues thread so that someone else doesn't start working on it too.
0 commit comments