> Similar to SQLite, diagrams.net is open source but closed to contributions.
> The level of complexity of this project means that even simple changes can break a lot of other moving parts. The amount of testing required is far more than it first seems. If we were to receive a PR, we'd have to basically throw it away and write it how we want it to be implemented.
> We are grateful for community involvement, bug reports, & feature requests. We do not wish to come off as anything but welcoming, however, we've made the decision to keep this project closed to contributions for the long term viability of the project.
No; see my second point definition. A thing is open source if, essentially, people are free to re-mix it; whether that be by modifying it upstream, or by forking it downstream. If there is no ability to make changes and then legally use your own changed version, then the thing is not open source in the way any developer would understand the term.
Yes, but "whether" is kinda weird here. The first (community development) requires the second (open sorce). If upstream can accept your contributions, this means you've already forked it for yourself.
> Similar to SQLite, diagrams.net is open source but closed to contributions.
> The level of complexity of this project means that even simple changes can break a lot of other moving parts. The amount of testing required is far more than it first seems. If we were to receive a PR, we'd have to basically throw it away and write it how we want it to be implemented.
> We are grateful for community involvement, bug reports, & feature requests. We do not wish to come off as anything but welcoming, however, we've made the decision to keep this project closed to contributions for the long term viability of the project.