... | ... | @@ -19,7 +19,7 @@ Mail me @ luker _at_ fenrirproject.org if you want. |
|
|
|
|
|
## Copyright & License
|
|
|
|
|
|
For now If you want to send any code you need to write me a [CLA](CLA) (the CLA is the same for all subprojects).
|
|
|
For now If you want to send any code you need to sign a [CLA](CLA) (the CLA is the same for all subprojects).
|
|
|
|
|
|
This will grant me full control over the code, leaving you the copyright and the possibility to use it elsewhere.
|
|
|
|
... | ... | @@ -51,7 +51,7 @@ My main objective is to keep this software free. But a lot of people do not like |
|
|
|
|
|
Their reasons aside, I still want them to be able to use this project. The other licenses will need to be defined, but what I am aiming towards is a new license that
|
|
|
* protects from **patents litigations**.
|
|
|
* grants **usage** on closed source usage, optionally with linking for libfenrir/libRatporQ, without "tivoization" clauses.
|
|
|
* grants **usage** on closed source projects, optionally with static/dynamic linking for libfenrir/libRatporQ, without "tivoization" clauses.
|
|
|
* makes it so the one who gets the license can **not modify the source** code (their contributions must be LGPL3)
|
|
|
* deterministic builds must be used and the data to reproduce them must be public
|
|
|
|
... | ... | @@ -85,14 +85,18 @@ In general I'm trying to write C++11 code. But I've just started learning the C+ |
|
|
|
|
|
## Sending a patch:
|
|
|
|
|
|
**After** you have signed a [CLA](CLA) you can email me @ luker _at fenrirproject.org.
|
|
|
First of all, sign the [CLA](CLA).
|
|
|
|
|
|
Then you can use your github account to login on fenrirproject.org, and do bug reporting/forking/merging there.
|
|
|
|
|
|
Or just email me @ luker _at fenrirproject.org.
|
|
|
|
|
|
Or better, write to the [mailing list](https://www.fenrirproject.org/lists) of the project you are contributing to:
|
|
|
|
|
|
You can use the "git format-patch" to generate the required patch from your local repository.
|
|
|
|
|
|
In the future I will set up a github/sourceforge repository automatically synced with my main one, and you can use those platform to send me pull requests.
|
|
|
Still, use this website for error reporting. signing with github accounts is already active.
|
|
|
In the future I will set up a github repository automatically synced with my main one, and you can use those platform to send me pull requests.
|
|
|
Still, use this website for error reporting. Login with github accounts is already active.
|
|
|
|
|
|
I always generate my commits with "git commit -sS", so that its always signed. All tags are signed. The master branch can only have signed merges. Please check those.
|
|
|
|
... | ... | @@ -100,15 +104,15 @@ I always generate my commits with "git commit -sS", so that its always signed. A |
|
|
|
|
|
### The environment
|
|
|
|
|
|
Everything is developed under GNU/Linux. Currently I'm using qtcreator for its C++ support, clang as a compiler. As soon as I can I will switch to clang's libc++ as the default library.
|
|
|
Everything is developed under GNU/Linux. Currently I'm using qtcreator for its C++ support, clang as a compiler.
|
|
|
|
|
|
Since I work under ArchLinux I might have a newer version of some packages, but I'll try not to be too bleeding-edge on the requirements. The project won't be considered complete for a while, so for now: the newer, the better.
|
|
|
|
|
|
Compatibility with the latest red-hat/contos 7 is required, though.
|
|
|
Compatibility with the latest red-hat/contos 7 is required, though. No unsupported versions of old distros will be considered.
|
|
|
|
|
|
### Linking
|
|
|
|
|
|
If you contribute new features, please don't link to too many libraries. Try to avoid it. We already have the libunbound, libevent, and will have to link libRaptorQ, openssl/gnuTLS for some crypto algorithms, and maybe libcds.
|
|
|
If you contribute new features, please don't link to too many libraries. Try to avoid it. We already have the libunbound, libevent, and will have to link libRaptorQ, openssl/gnuTLS for some crypto algorithms.
|
|
|
|
|
|
That's already enough. If you have to link to something, please try to be sure it is something portable, as later in the development we will have to port this project to **BSD and Windows
|
|
|
|
... | ... | |