I have a 5-day contract for the foreseeable future.
However, as per another post on here, this will enable me to pay for dev time.
My level of knowledge is much more:
Let’s use Qubes APIs to launch VMs with v2ray and import configs via command line.
(As opposed to writing each line of code).
If you would like to work on the project, please feel free to PM me or find my details via github.
Your ‘novice’ ability most likely far exceeds my programming speed.
(Honestly, I just haven’t got the commitment/time to program a project. I need to stick to the management/abstract spec else it will never get done). I can help much better by raising 6 figures in a couple of months, then spending those 2 months programming.
I foresee that I will have 6 figures of liquidity - much of which I would like to allocate to dev/Qubes work - in the next 12 months.
The current corporate structure is planned as follows:
Development Corporation/Conglomorate
- Sub-projects/assets (i.e. flexi-chains).
All assets with fair-use licences.
Business model is from premium support/consulting/plugins, (which are also planned to be open-source&free after lag-time of approx 12-24 months max).
As my current contract business is using MS Windows, and QWT is chugging slowly - I also plan the following:
(Within dev. corporation):
‘QBusiness Company’
(This will be a fork of qubes, contributing directly to this fork - leaving it upto the Qubes core team if they want to adopt anything upstream).
Disclaimer
I need to double-check that this is ok with Qubes licencing and core team
Proclaimer:
There are many reasons the QBusiness company will be setup like this to start with:
- Qubes Core Team is small - forking the project reduces burden in many ways
- Forking the project removes liability/branding issues etc.
- It means Qubes remains non-commercial and nobody can claim that they are being influenced by the company, as we contribute directly to the fork.
Also, I wish to make it very very clear that we will adopt an open-source & free licence for the fork.
Long-term a non-profit corp or a ‘charity’ would probably be ideal for this venture, however I must make the following Disclaimer:
Charity law where I am is some of the most complex in the world, and you would need 5-6 figures/year. (in admin/management overheads), to maintain charity status for such a project.
It would require further admin overheads and disagregration of the project (i.e. separate charity/nonprofit from consulting company), which is simply pointless until the project grows that big.
Also, for anyone wondering, am I really comitted to Qubes?
The answer is Yes. Thankfully, Joanna laid out quite clearly why OpenXT is not all it’s cracked up to be.
Further, I do not ever see SecureView, (OpenXT-based), being open-sourced/free-licenced - the only reason I can see this would be done is if Qubes became a commercial competitor.
In addition to all that: From what I’ve learnt of SecureView, the only really major headstart they have rightnow is the apps builtupon the admin API(s) - which Qubes 4.1 now has (the admin API).
Apologies for leaving everyone without an update - and for the very long post.
I am working hard on building a trustworthy core team, and generating revenue - bare with me please.
If anybody is interested in joining this team or contributing - please get in touch.