If the investors eventually stop paying the bills (or if the set of people that want to contribute is larger than the set of people the investors will pay), then fork it. This seems like a win-win, in that developers win because they get Free tools, and in that developers win because the get paid well to develop open source software.
- I want this project to be a success (and open source) - To make it a success I need to live - To live I need to pay for food
Commercialization in OSS is pretty straight forward as there aren't many options: - Support, managed hosting, paid plugins/features, sponsors.
With the exception of Sponsors, all of these require a number of changes to code and infrastructure that should not be public and this would not be possible without a CLA.
Ergo: CLA -> OSS Developer gets to live.
Yes, it does open the door to license changes and that is a whole other story. But what it boils down to is that funding an OSS project without a CLA is basically impossible.
Where is that time spent?
As mentioned in a comment below php execution including db call is: P95 is 120.9ms P99 is 634.11ms
Which means the rest is DNS lookups and js execution.
It is a simple PHP application using Mysql as the database backend. We are using a domain driven design architecture across the application and decided to skip the slow ORMs in favor of a repository layer with hand written sql.
We are framework agnostic to not be locked into any flow but you will see classes from Symfony and Laravel. The goal has always been to make Leantime as lean as possible to allow hosting it on any shared host out there. That means we don't use any exotic extensions or OS features. You can run it safely on the smallest Godaddy instance if you wanted to.
We recently introduced htmx into the stack to offload some of the rendering back to the server and we love it.
PHP itself is really not a bottle neck anymore especially since PHP 8.0
We haven't had a chance to run a lot of large scale load tests yet so take the following with a grain of salt but a direct Task hit currently takes about 2.08 sec to load on our production site. (that includes javascript processing time as it loads in a modal)
I know we have instances with thousands of tasks and users in the wild and generally performance is not an issue we get reports on on our github repo.
I kinda like the term 'people first project management' used further down on the product page. Maybe have a dedicated page talking about why your software is inclusive with respect to neurodiversity, but it seems counter productive to call yourself 'projekt planner for ADHD people', at least if you want to market to enterprises. Just my 2ct.