Expectations

[davidjgraph]

Just to extend the code of conduct a little in terms of what can reasonably be expected of us in this project.

What users of this project and our implementations can reasonably expect of us (collectively the team members of this project):

• To be able to make feature requests and bug reports to us.
• To maintain the project code base, fix bugs in existing functionality and security holes.
• To keep app.diagrams.net online and secure.
• To make draw.io desktop releases when resources allow and ensure a secure version of electron is used in the latest release.

What users cannot reasonably expect of us:

• That their feature requests will be implemented. We view draw.io as largely feature complete. It may not be for your specific user case, but you have the option to use other software.
• Developer level support. You can ask the question here, but developer level question are often long and complex, it is hard to find the time for these.
• That we need to explain in detail every decision we make for not implementing specific feature requests or changing existing functionality. If we change functionality and it impacts your usage then explain why in well reasoned logic. If you do that and we stick to our position, just accept it.
• That we tolerate users who show entitlement asking for any of the items in this unreasonable list.

Exceptions for paying users on Atlassian integrations

What can be reasonably expected for paying users on Confluence or Jira integrations are detailed in the EULAs of the products. Such users are welcome to post here, since this is the base product for all integrations and the change likely needs to be made here.

Feature requests still cannot be promised, but the difference over free users is you can reasonably ask why a feature request has not been implemented and expect an explaination (just do this in a support ticket for that product).