>We plan to partner with one to three corporate clients in order to run a pilot
>program throughout the first half of 2017. After it has been successfully
>completed, we'll then widen our offer to more corporate customers and,
>ultimately, to small business customers. Our main constraint is the scalability
>required to cover each additional client. Hence, we plan to focus on larger
>customers first.
Does this mean that Qubes will somehow become networkable or will it still only be for a single device?
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJYP2b6AAoJENtN07w5UDAwJ4kQAMClOUh/vmxWr0Hb7ENgeBAq
xLQQrKuUBeK5yZ7+Jpeoqc/ni8VsZ8vwbXWayHLWHk1IMn22OMn/cd66T6tljt0x
UdcZ4Ng4nxl0j8sN0Ycw4iEx29LRwPs4m0EOPPEYRaqql+QNEPjs8mItE/vRtkd3
KTudISYCflBwFB2SlVn8NHd8gNbaV/y8oy7gRLCpzEtf3rU4WAf2jKdRpGWx3RFx
uqYLJ/vfEOBs2SctsuNLzm+8eX7hZ6DOBQNBGgAtdLMnaWqBBA3uEjmwjGbNL2jm
BGVYUnPyKIgCcGHGuInCgRb8vatrV6Vesduw9IRbQHB2BOQT41pdhlbtbPUkOSu4
HXn4j9/w3TXE4Qnvq5EeA3VTYM9cnf4COQ4XuaXNxUX9ojiuRgFqNxQ1vHw98rST
nsS//+9AoL2PQmElunWwhPe/srWDcODZ/iVDd2uafc0gEdNTYUHzDSQkhhd5GOEM
2xe9zMfR8m+mpXTX5/ObVbsQ61EXUw6YYb9IH0vBvnG6QUSRe6xzXKVK8h/9JaHt
5rhQxb+njEcovZ9cLadwA9IIZP4FJhYU0cvXpRbPSHueFRf7j4JfplClPEnL2vEC
NqG/lcgCKjA6tmk2x+CXU0rue35OwzjMUaWq8YZ0MmX0fc+/MFw121LpBu+0Ke0H
VOFj+L9DRea6g7k0OPtI
=3Y/D
-----END PGP SIGNATURE-----
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9b9eb0ce-db38-7434-6d28-ff0e14a1b32b%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.
either way, im happy for this and hope it works!
I'm excited about this, and wish to support Qubes.
My first thoughts are "How can Qubes reach a broader community", and "Can the HOWTO's be made more approachable?".
For example, the section 'assigning-devices' on the /doc/, didn't get into how to actually use a mouse with a sys-usb qube, before at the very end.
And there, the way it was written gave the impression of giving the answer almost as an afterthought, as if it should have been obvious to everybody.
As such, it reads as it was written by somebody "too close to the problem".
Somebody being so familiar with the system that outsiders' inability to grasp the "obvious", escapes him. Or her.
This is not a unique issue for ITL though, the same problem pops up everywhere when highly technical minded people try to convey something to people who just wants to be *users*!
So that's what I'm thinking, maybe it would be good for the "evangelization" of Qubes to make some very simple, brief, and to-the-point videos and howto's?
> > So that's what I'm thinking, maybe it would be good for the "evangelization" of Qubes to make some very simple, brief, and to-the-point videos and howto's?
> >
>
> Yes, certainly. Would you be willing to help us with that? :)
theres already a nice one in english linked from the front page of the qubes-os site.
and one in french. now we just need more languages covered.
Also, you forgot to post this to qubes-announce Andrew.
Absolutely!
Would it be okay if I started with some of the /doc/-articles?
I've noticed that some of them could benefit from an update, as an example the one on Kali (https://www.qubes-os.org/doc/pentesting/kali/).
Please let me know if this is something that I could help out with.
But ya, If you got a good sales guy to go to some small to midsize companies and give a presentation, how can anyone refuse!!!??? This sounds exciting to me.
oh and like Fran said don't be ashamed to name drop everyone and everything right off the bat.
I am new to Qubes - just installed it on my computer. I can note the problems that I encounter. Where to send this?
Z.
> In an attempt to keep the open source development of Qubes going, we've teamed
> up with Open Collective [07], which makes it easier to donate to the Qubes
> project. Now, in addition to our Bitcoin fund [08], we can also accept
> donations via credit card.
Good to hear, but I would recommend adding more payment options like Paypal so it's easier for users in other parts of the world, where credit card is not a widely used, to support you.
Andrew,
I'm very willing to donate - and well noted that you all will continue to update the core changes in the public domain. I do understand the why, the what and the dollars for the change - however, will there be anyone left to work on the core, for the sake of the core? Just wondering where the donation dollars will be going. I ask because I agree with the person noting 20,000 current licenses. If we all sent in $100 US each then that's $2 million US.
Is it possible to set up some separation of funding to ensure each group is getting what they want? Set up the public funding better with separate marketing, and let that fund improvements for the public domain (not just maintenance and slight core improvements) - and then fund your corporate goals using the methods you mentioned.
As a relatively new user I'm concerned about investing more time in this and it not progressing.
Thanks,
Patrick
Dallas, Texas
Hi Andrew, ok - after reading it a couple more times I got the total gist. Not sure who all was hired but hopefully there will be sufficient marketing efforts to get them funded long term.
Thanks,
Patrick
Dallas, TX
--
You received this message because you are subscribed to the Google Groups "qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscribe@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fe5ecfd0-8869-2c19-6309-e870f8377eef%40leeteq.com.
if I understood you correct, what your clientele want's to have is constant improvements for Qubes OS. They don't want to compile or test things.
This is a subscription based model, where people pay the Qubes OS team for their ongoing work rather than for an existing product.
Furthermore, I agree with you "memberships-based support services (premium
communities) is a good business model for" Qubes OS.
However, I think that testing new features and introducing new features can be done together with the open source community and Qubes OS could offer a LTS version for money. LTS version could focus on guaranteeing backports and fixes for specific LTS version over a period of 3 or more years, whereas the community support will only be offered for a year or till the next version of Qubes OS appears.
I think the Qubes OS team should focus on getting paid for their ongoing work rather than Qubes OS as a product and the only way to do this is to offer monthly or yearly subscriptions for customers and additionally support memberships for IT professionals (consultants, IT departments etc.).