blob: 7a3aba45302523f4cb94cf6083a6921bd111f5e6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
|
# Guidance on how to contribute
> All contributions to this project will be released under the Apache 2.0 License.
> By submitting a pull request or filing a bug, issue, or
> feature request, you are agreeing to comply with this waiver of copyright interest.
> Details can be found in our [LICENCE](LICENSE).
There are two primary ways to help:
- Using the issue tracker, and
- Changing the code-base.
## Using the issue tracker
Use the issue tracker to suggest feature requests, report bugs, and ask questions.
This is also a great way to connect with the developers of the project as well
as others who are interested in this solution.
Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in
the issue that you will take on that effort, then follow the _Changing the code-base_
guidance below.
youTrack web can be found here http://trex-tgn.cisco.com/youtrack/
## Changing the code-base
Generally speaking, you should fork this repository, make changes in your
own fork, and then submit a pull-request. All new code should have associated unit
tests that validate implemented features and the presence or lack of defects.
Additionally, the code should follow any stylistic and architectural guidelines
prescribed by the project. In the absence of such guidelines, mimic the styles
and patterns in the existing code-base.
mailer is trex-tgn@googlegroups.com
|
