We communicate through two majors channels:
our community platform is available to ask questions and report bugs
our ideation board is here if you would like to suggest or request features
In general, things we find useful when reviewing suggestions are:
A description of the problem you're trying to solve
An overview of the suggested solution
Examples of how the suggestion would work in various places
Code examples showing e.g. "this would be an error, this wouldn't"
If relevant, anything useful for establishing context and expected behavior
Some search tips:
Don't restrict your search to only open issues. An issue with a title similar to yours may have been closed as a duplicate of one with a less-findable title.
Check for synonyms. For example, if your bug involves a member, it maybe filed or described with "user".
Search for the title of the issue you're about to log. This sounds obvious but 80% of the time this is sufficient to find a duplicate when one exists.
Read more than the first page of results. Many bugs here use the same words so relevancy sorting is not particularly strong.
If you have a crash, search for the first few topmost function names shown in the call stack
If you have a question, please use our community, file an issue on the relevant Github repository (if available) or contact our support directly.
If you have a question, please use our community or contact our support directly.
If so, be sure to check the ideation board and the community first, and create a new entry necessary!
This code of conduct outlines our expectations for participants within the Amity Engineering team, as well as steps to reporting unacceptable behaviour. We are committed to providing a welcoming and inspiring team for all and expect our code of conduct to be honoured.
Be friendly and patient.
Be welcoming: We strive to be a company that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, colour, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, political belief, religion, and mental and physical ability.
Be considerate: Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we're a world-wide company, so you might not be communicating in someone else's primary language.
Be respectful: Not all of us will agree all the time, but disagreement is no excuse for poor behaviour and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a team where people feel uncomfortable or threatened is not a productive one.
Be careful in the words that you choose: we are a team of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants. Harassment and other exclusionary behaviour aren't acceptable. This includes, but is not limited to:
Violent threats or language directed against another person.
Discriminatory jokes and language.
Posting sexually explicit or violent material.
Posting (or threatening to post) other people's personally identifying information ("doxing").
Personal insults, especially those using racist or sexist terms.
Unwelcome sexual attention.
Advocating for, or encouraging, any of the above behavior.
Repeated harassment of others. In general, if someone asks you to stop, then stop.
When we disagree, try to understand why: Disagreements, both social and technical, happen all the time. It is important that we resolve disagreements and differing views constructively. Remember that we’re different. The strength of our company comes from its diversity, people from a wide range of backgrounds. Different people have different perspectives on issues. Being unable to understand why someone holds a viewpoint doesn’t mean that they’re wrong. Don’t forget that it is human to err and blaming each other doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.
This code is not exhaustive or complete. It serves to distill our common understanding of a collaborative, shared environment, and goals. We expect it to be followed in spirit as much as in the letter.
We encourage everyone to participate and are committed to building a company for all. Although we may not be able to satisfy everyone, we all agree that everyone is equal. Whenever a participant has made a mistake, we expect them to take responsibility for it. If someone has been harmed or offended, it is our responsibility to listen carefully and respectfully, and do our best to right the wrong.
Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities.
If you experience or witness unacceptable behavior —or have any other concerns—please report it by contacting us via developers@amity.co and support@amity.co . All reports will be handled with discretion. In your report please include:
Your contact information.
Names (real, nicknames, or pseudonyms) of any individuals involved. If there are additional witnesses, please include them as well.
Your account of what occurred, and if you believe the incident is ongoing. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger), please include a link.
Any additional information that may be helpful, context, screenshots, etc...
After filing a report, a representative will contact you personally. If the person who is harassing you is part of the response team, they will recuse themselves from handling your incident. A representative will then review the incident, follow up with any additional questions, and make a decision as to how to respond. We will respect confidentiality requests for the purpose of protecting victims of abuse.
Anyone asked to stop unacceptable behaviour is expected to comply immediately. If an individual engages in unacceptable behaviour, the representative may take any action they deem appropriate.
Thanks
This code of conduct is based on the Open Code of Conduct from the TODOGroup. We are thankful for their work and all the communities who have paved the way with code of conducts.
Amity Manage UI Kit - Deprecation Notice
Amity Social Cloud will be deprecating all managed versions of the UI Kits (IOS, Android and Web J.S.) on 31 August 2022. Our UI Kits were built to enable even faster integration of our social and chat features. In January this year, we open sourced all our UI Kits to provide our customers with more flexibility and greater customization options. Since then, we have seen a shift towards the open source version as it gives complete control over the visual style while keeping the integration time as short as possible.
To ensure that you continue to receive the latest updates and improvements, we encourage you to migrate over to the open source version. We’ve written instruction guides to help you migrate to the open source version, get the latest updates, and contribute to the project all available below.
Once the managed version is deprecated, we will transition our support to the open source UI Kit for any bug requests and releases of new features. You will still be able to use the managed UI Kit, however it will no longer be receiving further updates. All documentation relating to the managed UI Kit version will be moved to the deprecation notice section. Any ongoing improvements will be made to the open source version under the Lesser General Public License (GNU).
Keeping users safe and secure is a top priority for us at Amity. We welcome the contribution of external security researchers.
If you believe you’ve found a security issue in any software, service, or website governed by Amity, we encourage you to notify us.
Projects governed by Amity can sometimes allow unsafe things by design. This unsafe behaviour should be explicitly documented and, if it is, is not considered a security issue.
There are no hard and fast rules to determine if a bug is worth reporting as a security issue or a “regular” issue. When in doubt, please do send us a report.
Security issues can be reported by sending an email to security@amity.co, which will go to all relevant team members. The team will acknowledge your email within 48 hours and you will receive a more detailed response within a week.
We will create a security meeting to discuss internally, and if/when needed, invite you to discuss the issue with us.
Amity supports safe harbor for security researchers who:
Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services
Only interact with accounts you own or with explicit permission of the account holder. If you do encounter Personally Identifiable Information (PII) contact us immediately, do not proceed with access, and immediately purge any local information
Provide us with a reasonable amount of time to resolve vulnerabilities prior to any disclosure to the public or a third-party
We will consider activities conducted consistent with this policy to constitute “authorised” conduct and will not pursue civil action or initiate a complaint to law enforcement. We will help to the extent we can if legal action is initiated by a third party against you
Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.
Please provide detailed reports with reproducible steps and a clearly defined impact
Submit one vulnerability per report
Social engineering (such as phishing, vishing, smishing) is prohibited
Important: before participating in our community, please read our code of conduct. By interacting with this repository, organisation, or community you agree to abide by its terms.
There’s several ways to contribute, not just by writing code. If you find bug, have questions or ideas, see the support page.
Code contributions are very welcome in our public repositories. It’s probably a good idea to first post a question or open an issue to report a bug or suggest a new feature before creating a pull request.
See your project details for info on how the project is structured, how to test, and how to build the site
Non-trivial changes are often best discussed in an issue first, to prevent you from doing unnecessary work
For ambitious tasks, you should try to get your work in front of the community for feedback as soon as possible
New features should be accompanied by tests and documentation
Don’t include unrelated changes
Test before submitting code
Write a convincing description of why we should land your pull request: it’s your job to convince us
