Gentlemen,
If you believe that the future of Open Source should be in the application 
area, your example of using a small portion of Quick Books revenue to improve 
an Open Source product are missing the entire process of having users.... 
Commercialization, advertising, Customer service, documentation, help 
systems... at the end of the entire process is the technical product (program). 
The technically most important part of a product, is almost the least important 
part of bringing a solution to the real world. Try looking at the almost 
non-existent market penetration of Libre Office / Open Office is due to the 
price, FREE, means nobody telling me why I want to use the product, nobody 
telling me the product exists (NO advertising), no training seminars for VARS, 
no product co-commissions = NO REASON I SHOULD Hustle my users into the 
product. I will get to service the product and get nothing for recommending it.

John A. Ward




-----Original Message-----
From: [email protected] [mailto:[email protected]]
Sent: Thursday, July 28, 2016 09:00 AM
To: [email protected]
Subject: Osdc-list Digest, Vol 71, Issue 5

Send Osdc-list mailing list submissions to      [email protected] 
subscribe or unsubscribe via the World Wide Web, visit   
https://www.redhat.com/mailman/listinfo/osdc-listor, via email, send a message 
with subject or body 'help' to   [email protected] can reach the 
person managing the list at       [email protected] replying, 
please edit your Subject line so it is more specificthan "Re: Contents of 
Osdc-list digest..."Today's Topics: 1. DRAFT: Manifesto for an Open Future 
(Kael Shipman) 2. Re: DRAFT: Manifesto for an Open Future (Bryan 
Behrenshausen)----------------------------------------------------------------------Message:
 1Date: Wed, 27 Jul 2016 21:28:32 -0500From: Kael Shipman To: OSDC List 
Subject: [Osdc-list] DRAFT: Manifesto for an Open FutureMessage-ID: 
<[email protected]>Content-Type: text/plain; 
charset=utf-8Hey all!I've been playing with a project for the last few weeks 
and I'm at apoint where I'd really love some feedback and/or help on it. As 
thesubject implies, it's a manifesto that attempts to describe what theOpen 
Future might look like. I'm creating it as a way to inspire ashared vision to 
use throughout the community as we developtechnologies, software, protocols and 
business ideas. My dream is thatonce it's done (i.e., once we've managed to put 
it through the wringeras a community and come out with a document we can all 
more or lessagree on, if that's possible), I can use it to guide the work that 
I donow and into the future, and perhaps others might find it useful forthat as 
well. For example, when I look for jobs, I can look forcompanies that represent 
an opportunity for me to build a small piece ofthe open future, or when I look 
for education, I can look to cultivateskills that will better allow me to 
contribute to it.The manifesto itself is an attempt to provide three elements: 
1)convincing evidence that an open future is inevitable; 2) an image ofwhat it 
might look like and how it might work; and 3) a set of concretesteps we can 
take now to hasten its arrival, including building certainpieces of 
infrastructure.I'm writing it in response to the frustration that I've felt in 
tryingto drive open principles forward today. Many of these principles 
don'tquite work yet because, personally, I don't believe we have realizedquite 
where we're going with it all, or just how much infrastructurewe'll need to get 
there. Just as a basic example, Quickbooks Online nowpulls in $30,000,000 every 
month. If even 1/10th of the customers whopay for Quickbooks online instead put 
a single QBO payment into GNUCashinstead, we'd have a product far better than 
Quickbooks, and the wholeworld would benefit from it -- not just those who 
paid.The ROI on this proposition is obvious enough that even a child couldgrasp 
the implications -- yet we don't have systems in place to leverageit. The 
action item, then, is to fortify our systems for linkingpayments to features 
(BountySource is an open-source start to that, buthas a long way to go), and to 
start getting progressive businesses(probably starting with the ones we work 
at) to redirect their softwarebudgets to open-source projects.There are a 
number of other concrete things like this that we can do tostart moving in the 
direction of the Open Future, and I think having amanifesto in hand that helps 
us remember what that future looks like andwhat we can do to encourage it would 
be extremely useful.So, without further ado, here is the unfinished draft so 
far:https://raw.githubusercontent.com/kael-shipman/Manifesto-for-an-Open-Future/master/Manifesto%20for%20an%20Open%20Future.fodt(you'll
 have to download it and open it in LibreOffice)And here's the full github 
repo:https://github.com/kael-shipman/Manifesto-for-an-Open-FutureI look forward 
to hearing what people have to say! If anyone wants tohelp, please do shoot me 
a line. The irony of drafting a document likethis alone is far from lost on me 
;).Thanks for your time,Kael------------------------------Message: 2Date: Thu, 
28 Jul 2016 10:32:42 -0400From: Bryan Behrenshausen To: 
[email protected]: Re: [Osdc-list] DRAFT: Manifesto for an Open 
FutureMessage-ID: <[email protected]>Content-Type: text/plain; 
charset=windows-1252Hi Kael,Neat! I look forward to reading and exploring this. 
Openness needs moremanifestos, for sure.In that vein, you might also consider 
checking out Robert David Steele'ssimilarly-titled 
project:http://www.goodreads.com/book/show/12998524-the-open-source-everything-manifestoBryan------------------------------_______________________________________________Sign-up
 for our weekly newsletter: http://opensource.com/email-newsletterOsdc-list 
mailing 
[email protected]https://www.redhat.com/mailman/listinfo/osdc-listEnd of 
Osdc-list Digest, Vol 71, Issue 5****************************************
_______________________________________________
Osdc-list mailing list | This is a place for our readers, writers, moderators 
and artists to discuss matters concerning Opensource.com and otherwise do the 
work that makes this a community practicing the open source way.

Sign-up for our weekly newsletter: http://opensource.com/email-newsletter

Send a message: [email protected]
Change preferences: https://www.redhat.com/mailman/listinfo/osdc-list
Unsubscribe: https://www.redhat.com/mailman/options/osdc-list

Reply via email to