Skip to content
This repository was archived by the owner on Dec 27, 2023. It is now read-only.

Commit 2b7b815

Browse files
committed
Merge branch 'master' of github.com:Litipk/ColorSharp
2 parents 3883b2e + 5ae9cf4 commit 2b7b815

File tree

1 file changed

+57
-1
lines changed

1 file changed

+57
-1
lines changed

CONTRIBUTING.md

Lines changed: 57 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,57 @@
1-
To be done.
1+
ColorSharp's Contributing Guidelines
2+
====================================
3+
4+
Contributing with Code
5+
----------------------
6+
7+
In first place, if you want to contribute code to ColorSharp, you are going to be able to compile the project.
8+
9+
### Prerequisites to compile ColorSharp
10+
11+
#### MS Windows
12+
13+
* Microsoft .NET >= 4.0 or Mono >= 3.2 .
14+
* MS Visual Studio >= 2013, or MonoDevelop >= 5.5 .
15+
16+
#### Linux
17+
18+
It's prefered to use the last version of Mono (currently 3.12). To install it on your system follow the instructions of this page:
19+
20+
* http://www.mono-project.com/docs/getting-started/install/linux/
21+
22+
In Ubuntu you have to install the monodevelop package after following the previous instructions:
23+
24+
```bash
25+
apt-get install monodevelop
26+
```
27+
28+
### Some comments about NuGet package generation
29+
30+
Currently, [Litipk](https://github.com/Litipk) owns the private key to sign the NuGet packages sent to nuget.org, but you can generate your own DLLs using defered signature (which is, in fact, the default project's setting).
31+
32+
### Testing
33+
34+
It's desirable that every new feature arrives with it's own unit tests. At this point, the unit testing coverage on ColorSharp is pretty low, but we're working on it, and new code without tests will harm this effort.
35+
36+
Contributing with Documentation
37+
-------------------------------
38+
39+
This has to be discussed, because there isn't yet a high volumen of documentation and there are many possibilities. Feel free to suggest us any workpath that you think it's convenient.
40+
41+
Contributing with Bug Reports
42+
-----------------------------
43+
44+
A very important part of every software project is the bugs tracking and solving process. You can send us bug reports through the [tracker](https://github.com/Litipk/ColorSharp/issues).
45+
46+
It's desirable that every bug report explains the bug in a way that the developers can easily reproduce it. The following points are very helpful in order to achieve reproducibility:
47+
* Example code.
48+
* ColorSharp's version.
49+
* Chosen Runtime: It's MS .NET? or it's Mono?
50+
* .NET version (are you using .NET 4.0, 4.5, 4.5.1..?). If you are using Mono it's important to note that a given Mono version can run as different .NET versions.
51+
52+
Contributing with New Ideas
53+
---------------------------
54+
55+
You can use the github [tracker](https://github.com/Litipk/ColorSharp/issues) to send us new ideas, even if those ideas aren't bug reports. In such case, adding something like "SUGGESTION: ...", "IMPROVEMENT: ..." to the report bug it's a good idea.
56+
57+
You can also discuss your ideas with us in our [Gitter chat room](https://gitter.im/Litipk/ColorSharp).

0 commit comments

Comments
 (0)