cloudstack-marketing mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Musayev, Ilya" <>
Subject Re: Packt Book - Publish on our website?
Date Sat, 25 May 2013 00:08:00 GMT
I see both sides of the argument.

Positive side:
We need quality books and content to bring more people on board with ACS.

Negative side:
By mentioning a book on official ACS page, we are inderectly recommending the publication,
and if we begin being selective on what we recommend  (we dont want incompetent books), we
get ourself into a wrong business. Once the book is published in print - its not easy to pull
the books of the shelf, revise and reprint or discard them in trashbin, due to all costs involved.
Telling publisher your book sucks, has errors, or plain wrong - won't help with sunked in
costs, since they are not going to pull the book of the shelf post print - so bad press lives

Sebastian and Kelcey, im not against good content or books for ACS, im against hurting ACS
image by poor publishers and inturn  setting authors and publishers against us because their
book did not get mentioned on ACS page.
Unless you want to be indiscriminant and mention all books that have CloudStack in their title
and mention "we are not responsible for this content neither do we endorse it" (which may
cover us to some extent, but really does not help with bad/poorly written books).
Also imagine there are 20 books, who gets the spotlight  and who will be on the bottom? If
im author or publisher I want my book always to get the spotlight, like google search result
people tend to get fixated on the first 5.

Reason I proposed to stay neutral, is for us not to deal with all of the above.

How do you propose we deal with negative points above?

-------- Original message --------
From: Noah Slater <>
Subject: Re: Packt Book - Publish on our website?

On 24 May 2013 23:06, Sebastien Goasguen <> wrote:
> Not well enough apparently because I still don't get them.

Maybe you could list the opposing arguments and why you don't agree with

(Me repeating them is likely to just take us round in circles.)


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message