I don't think a boycott is a good idea. The thing is, all this stuff needs to be in the contract before you write the thing...if you want to re-negotiate the conract afterwards, you're fighting an uphill battle. BUT, if you feel O'Reilly is misrepresenting the authorship of the book, you might want to have your lawyer send a letter (but be prepared to sue). So I say,
1. No boycott (most ppl like O'Reilly books and they are helpful)
2. Reread the contract. If O'Reilly is acting according to the contract (i.e. there is no provision in the contract for royalties or authorship credit, or provisions specifically stating that these would not be granted), then you are fighting an uphill battle and unless you want to threaten to quit writing for them, etc. you will probably not get anything from them.
If, however, they are in violation of the contract (i.e. you were promised something that they didn't deliver, or there are no specifc provisions stating that you would not be given credit for authorship AND you feel that they are misrepresenting who wrote the book), then talk to your lawyer.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
