-
Notifications
You must be signed in to change notification settings - Fork 35
Contributions, Requests and Bug Report guidelines
Please open an new issue on Github here.
Create a fork of the repository and a pull request for your changes. Make sure you have some unit tests and descriptive git commit messages. Overall, you should adhere to the guidelines defined by Codacy.
join OWASP Slack forum #owaspsecurity-logging
Thanks for letting us know about issues with the code. Please include the following information when submitting a bug report:
- Detailed steps to recreate
- Expected Results
- Actual Results
- version of the security logging library being used
- jdk/jre details
- OS
- name or type (web app, web service, standalone app, etc.) of application
- logging toolset (log4j, logback)
The project team will be notified of new bug reports and will respond within 1 week (Ideally, within a couple days though). The response will generally result in an acknowledgement that we received the the report and that it will be assigned to someone to review to determine the next steps.
Community participation is the key to our success. If you have an enhancement to this project, please provide the following information:
- What is the use case?
- Any information on specific changes to the API
The project team will be notified of enhancement requests and will respond within 2 weeks. The response will generally be one of the following 1)yes, and we need more information to continue 2)yes, we have enough information and will prioritize this 3)unsure and we need more information to be able to decide or 4)no, with some description as to why.