-
-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
drafting potential crowdfunding campaign #2452
Comments
if we go GoFundMe route:
I would say these are not necessary at this time. |
I would be willing to write a who uses Qubes page. Im fairly good at explaning technical topics to lesser technical people, as an example:https://write.privacytools.io/my-thoughts-on-security/how-to-choose-a-secure-messenger We would have to decide wheter it is a real "who uses Qubes" page, as this would require sources to back up the examples. Or make it more of a "who we build qubes for" kind of page. |
Thanks @blacklight447-ptio, that would be much appreciated! As for the actual content, there is a lot of info in #1906 already. I'd focus on two major categories, we already know to use Qubes:
|
I see this helps a lot. I would also like to know where this text will be published, the on the qubes website in a similar style to the intro post? Or maybe in the style in which the newsletters are written? And also what audience I should keep in mind, the more average general public, security aware users? People already working in IT? |
let's move this conversation over to #1906 (audience: general public; style: something specific to that page, ideally not too text-heavy). |
things we'll need to do on GoFundMe: |
i think its much better to use many services to let users choose what they want. Also keep in mind that many people (including me) don't have a credit card. |
this thread is to draft:
around a potential crowdfunding campaign.
threads potentially worth completing prior to launch (besides having content for the above) are:
The text was updated successfully, but these errors were encountered: