4 ms·
Oreilly author and project lead for an open source eclipse foundation (apache style project though!) project that runs a company. Happy to answer questions here
by agibsonccc 8y ago
Oreilly author and project lead for an open source eclipse foundation (apache style project though!) project that runs a company. Happy to answer questions here about the how/what/why this happens.
- davemp 8y agoOSS funding and documentation quality are problems I think about semi-regularly. A few questions I have are: 1) Is the model of keeping software open but education material closed a necessary compromise to fund the project? 1.b) If so, have you explored other funding models that weren’t viable? 2) How is the experience of publishing through OReilly? Do they take considerable profit shares? Do they provide editors, advertising, and/or other valuable services? Essentially are they worth it?
- agibsonccc 8y ago1) Yes I think incentive structures are a part of it. For us as authors,I know I typically think about the website very differently than the book. Having an editor peer review also helps keep me focused. What you find with a lot of open source coders, they tend not to always be good writers (me included). My book is 530 pages and took 2.5 years to crank out in between new releases. My company funded the book's development more as a loss leader. Authors don't make crap from the royalites. You're better selling it as part of a larger package such as training or support. 2. You have to know the right people. Go to the conferences and ask them. It took a long time. The profit shares aren't much. I more did it for the exposure at their conferences. We found it to be worth it as part of a larger package and networking with others in the field more than anything else. The notoriety has really helped as well. It's a lot of work, but definitely worth it if you can get it. Just be ready to put in a metric ton of work.