I think your current model makes more sense for you. Most projects would probably need some funding to get to where you're at.
Isn't that due partially to understaffing, which is what crowdfunding would help fix, presumably.
-
-
A team of developers would allow implementing a broader, deeper range of features but maintenance becomes an even bigger issue.
-
For example with security updates, we get the code on the day it's pushed and need to integrate and test it on that day.
-
For major releases, there's a lot of time pressure too because Google stops releasing factory images for the old branches.
-
Like you said before, purpose of crowdfunding is to finance the infrastructure to solve initial business problems like this.
-
A lot of it is a technical / political problem for us though. Google dumps the code unpredictably and we simply have to cope.
-
That doesn't sound sustainable. I would expect CopperheadOS to do stuff so as to not need patching for most 0-days.
-
Then at that point, you'd not always be in panic mode. Only rarely.
-
There's not much we can do to change the fact that we need regular security updates to firmware, etc.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.