diff options
author | Michael Richardson <mcr@sandelman.ca> | 2018-06-24 21:38:09 -0400 |
---|---|---|
committer | Michael Richardson <mcr@sandelman.ca> | 2018-06-24 21:38:09 -0400 |
commit | 82001f32ed9e76b0515a19ee0cc5be28c8ee0541 (patch) | |
tree | a0a9851f081babc86f0f7955b2ada7a8b80255a2 /CONTRIBUTING.md | |
parent | 49847a29b6cf55ce57d51e9f47f192931998badd (diff) |
rename/reformat documentation to markdown
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r-- | CONTRIBUTING.md | 29 |
1 files changed, 29 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 00000000..a3c2bd68 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,29 @@ +Guidelines for contributing +=========================== + +To report a security issue (segfault, buffer overflow, infinite loop, arbitrary +code execution etc) please send an e-mail to security@tcpdump.org, do not use +the bug tracker! + +To report a non-security problem (failure to compile, failure to capture packets +properly, missing support for a network interface type or DLT) please check +first that it reproduces with the latest stable release of libpcap. If it does, +please check that the problem reproduces with the current git master branch of +libpcap. If it does (and it is not a security-related problem, otherwise see +above), please navigate to https://github.com/the-tcpdump-group/libpcap/issues +and check if the problem has already been reported. If it has not, please open +a new issue and provide the following details: + +* libpcap version (e.g. from tcpdump --version) +* operating system name and version and any other details that may be relevant + (uname -a, compiler name and version, CPU type etc.) +* configure flags if any were used +* statement of the problem +* steps to reproduce + +Please note that if you know exactly how to solve the problem and the solution +would not be too intrusive, it would be best to contribute some development time +and open a pull request instead. + +Still not sure how to do? Feel free to [subscribe](http://www.tcpdump.org/#mailing-lists) +to the mailing list tcpdump-workers@lists.tcpdump.org and ask! |