Woohoo! You've decided to contribute? That's amazing! We want to make contributions to the Alliance Business Suite as easy and frictionless as we can. Contributing requires a GitHub account. If you don't have an account, follow the instructions for the GitHub account setup.
Then, you just need to create an Issue to report bugs, propose APIs, request features and tooling, propose designs and improvements.
All of these contributions will be filled as Issues on the Alliance Business Suite Documentation Repository and they adhere to the following Issue Management Policy.
Because we want to create a world-class product, we spend most of our time coding, designing, and architecting a well-designed solution, so we have adopted the .NET's Issue Management Policy to help us manage incoming Issues. This is a brief summary of some of the policies we have in place and the justification for them.
Commenting on closed issues In general, we recommend you open a new issue if you have a bug, feature request, or question to discuss. If you find a closed issue that is related, open a new issue and link to the closed issue rather than posting on the closed issue. Closed issues don't appear in our triage process, so only the people who have been active on the original thread will be notified of your comment. A new issue will get more attention from the team.
In general, we don't mind getting duplicate issues. It's easier for us to close duplicate issues than to discuss multiple root causes on a single issue! We may close your issue as a duplicate if we determine it has the same root cause as another. Don't worry! It's not a waste of our time!
If a contributor reviews an issue and determines that more information is needed from the author, they will post a comment requesting that information and apply the Needs: Author Feedback label. This label indicates that the author needs to post a response in order for us to continue investigating the issue.
If the author does not post a response within 7 days, the issue will be automatically closed. If the author responds within 7 days after the issue is closed, the issue will be automatically re-opened. We recognize that you may not be able to respond immediately to our requests, we're happy to hear from you whenever you're able to provide the new information.
Similar to the Needs Author Feedback process above, PRs also require author input from time to time. When a member of our team asks for some follow-up changes from the author, we mark these PRs with pr: pending author input label. After doing so, we expect the author to respond within 14 days. If the author does not post a response or updates the PR within 14 days, the issue will be automatically closed. If the author responds within 7 days after the issue is closed, the issue will be automatically re-opened. We recognize that you may not be able to respond immediately to our requests, we're happy to hear from you whenever you're able to provide the new information.
If we determine that the issue is a duplicate of another, we will label it with the Resolution: Duplicate label. The issue will be automatically closed in 1 day of inactivity.
If we determine that the issue is a question and have posted an answer, we will label it with the Resolution: Answered label. The issue will be automatically closed in 1 day of inactivity.
After an issue has been closed and had no activity for 30 days it will be automatically locked as resolved. This is done in order to reduce confusion as to where to post new comments. If you are still encountering the problem reported in an issue, or have a related question or bug report, feel free to open a new issue and link to the original (now locked) issue!
Security issues and bugs should be reported privately to Fenix Alliance either by emailing email@example.com or via the portal at https://fenix-alliance.com. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message.
Please do not open issues for anything you think might have a security implication.