We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!
darkeye (199616) writes "With e-ink and e-books coming of age, it would be kind of obvious, that the first adopters of this technology would be tech enthusiasts themselves — who, for the most part, will be reading thick technology books, and also using them as reference. Anyone who has tried to travel with his tech books knows the weight of dead trees in their backpack, and would appreciate all that info in a single e-book, to be read on an e-book reader or on a laptop.
So where are the e-books? When is it, that the default is going to be the environmentally friendly and convenient way of sharing written information? When are the reduced costs of this form of dissemination shared with the readers themselves?" top
darkeye writes "I'm facing a difficult dilemma, in which the Slashdot community might have an opinion that could help me. I've been contributing to an open source project heavily, making considerable changes to code organization and quality, but which are unfinished at the moment. Now a company is approaching me to continue my changes. They want to keep the improvements to themselves, which can be done, as the project is published under the BSD license. While this is still fair, as they have all the rights to the work they pay for in full, but, they want me to sign a non-competition clause, which would bar me from ever working on and publishing results on the original open source project itself, even if done separately in my free time.
Aside from ideological arguments (you should give back to the community you're taking from), how would you approach such a dilemma? On one side, they'd provide resources to work on an interesting project. On the other, it would make me an outcast in the project's community, Moreover, they would take ownership of not just to what they'd pay for, but also of my changes leading up to this moment — as I wouldn't be able to continue on my original codebase in an open source manner if I sign their contract." top