yesamer commented on code in PR #22: URL: https://github.com/apache/incubator-kie-website/pull/22#discussion_r1975078312
########## docs/community/support.md: ########## @@ -0,0 +1,75 @@ +--- +id: support +title: Support +sidebar_position: 1 +--- + +## Getting help + +If you are experiencing problems using KIE or one of its components, then please report your problem to our mailing list or the Zulip chat. +This allows the entire community to help with your problem. +If indeed a bug has been identified in the KIE software, +then document the problem in our [Issue Tracker](https://github.com/apache/incubator-kie-issues/issues). +Please refrain +from immediately opening a ticket in the issue tracker unless you are certain it's a problem in the KIE software. + +If you are in doubt, we appreciate asking the [mailing list](/docs/community/#mailing-list) or [Zulip](https://kie.zulipchat.com) chat first. + +Please read the section below (How to get help), and follow the bullets advised there first: + +* [Issue tracker](https://github.com/apache/incubator-kie-issues/issues) + +### Reporting bugs - Please read this first + +We prefer people to get in touch first using the mailing list, or Zulip chat. Or take time to read FAQs, or search in the mailing list archives to find answers. +Unfortunately, some people create the issue ticket as first thing. **Please don't do that!** Only if you are sure it really is a bug etc. Issue tickets create noise +for the KIE team to react on issues that are not bugs but are already covered in FAQs, in the mailing lists etc., or in the existing documentation. +Also on the mailing lists, there are more people active to help you better. + +Also, please avoid sending direct emails to members of the KIE team (we are busy already). +And conversations about KIE should happen in the public mailing lists, instead of via private emails. + +### Reporting security issues + +If you have found a security issue in KIE, +please contact the Apache Software Foundation [security team](https://www.apache.org/security/). +Don't share the details in public (i.e., chat or users/developer mailing lists). +We will receive details you send and resolve the issue as soon as possible. +We might also contact you requesting further details as needed. + +### Using deprecated components + +Deprecated components or older versions than 10.0.0 are *not* supported and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component and any version prior to 10.0.0. Review Comment: V ```suggestion Deprecated components or older versions than 10.0.0 are *not* maintained and issues such as bugs may not be fixed. We encourage users to migrate away from using any deprecated component and any version prior to 10.0.0. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
