Re: Branding checks to upcoming book

Carl Symons <[email protected]>
Newsgroups gmane.comp.kde.events
Message-ID <CAPu7pzKtd-mTqOe8+r469+p3J027QpApbr-R1DtqysGA-SEUvA__10874.3734345355$1319121955$gmane$org@mail.gmail.com>
On Wed, Oct 19, 2011 at 5:14 PM, Rohan Garg <[email protected]> wrote:
> Oh, I'm extremely sorry, the link to the book
> is http://www.booki.cc/kde/_full/ . The content will be finalized till 6 PM
> PST tomorrow and will be sent to publishing. We can still make changes but
> the first edition of the book won't contain the fixes. Would this be enough
> time for you guys to review our work?
> Regards
> Rohan Garg

Please say why your book is being sent to the publisher at 6:00 p.m.
today (10/20/11). Here's the dilemma I have...
- http://www.booki.cc/kde/_full/ converts to a 42 page odt. The
webpage is not editable in any serious fashion. Google Docs is fine
for some kinds of collaborative editing, but it doesn't work well for
versioning and involvement of multiple editors.
- There is a lot of information in the document. And it covers many
areas of effort within KDE. Accuracy is almost certainly compromised.
- The intended audience is not clear. The potential development
categories are listed below. How will this book be distributed? How
does it get into people's hands? Is it published on paper? A website?
     * Submitting a bug fix
     * Writing a new application powered by KDE
     * Contributing to an existing project
     * Adding functionality to KDE development libraries
     * Writing a new application using KDE tools
- There are ongoing efforts to recruit people to KDE in many types of
tasks. How does your work complement those efforts?

From somewhere came the idea that this book was needed. From somewhere
came the idea that it would be published in less than 12 hours from
now. It seems to me that it would be an important consideration of the
project to address meta-issues. Even if that means publishing will be
delayed from what was originally planned.

I would be happy to work on your document if your group will allocate
enough time and involvement for the job to be done well. Otherwise,
I'm not willing to do what seems to me to be less than quality work. I
do not intend to diminish the work of your group on this book nor on
the GSoC projects that y'all have done.

Please let us know what you decide.

Carl





>
> On Wed, Oct 19, 2011 at 5:07 PM, Carl Symons <[email protected]> wrote:
>>
>> On Wed, Oct 19, 2011 at 4:32 PM, Rohan Garg <[email protected]> wrote:
>> > Hi!
>> > We are writing a book at the GSoC Doc Camp sprint in Mountain View that
>> > gets
>> > new developers started in KDE Software Development and we would like you
>> > guys to review our work in order to ensure that we haven't made
>> > any unintentional branding mistakes in the book. The book will be
>> > finalized
>> > till 6 PM PST, so we need your review ASAP.
>> > www.launchpad.net/~rohangarg
>> >
>> >
>>
>> I love your intentionality. However, 1 1/2 hours to review something
>> is a pretty audacious request. I'm probably the only one available to
>> do this...most people are in Europe or India. One other minor
>> problem...I don't see anything at www.launchpad.net/~rohangarg to
>> review.
>>
>> What is the magic of publishing at 6 PM?
>> Do you prefer now or correct?
>> What is the document that needs to be reviewed?
>>
>> I may have some time to do this in the next short while, but I already
>> made a commitment to help someone with a Kubuntu upgrade to Oneiric.
>> They are sitting in a coffee shop with no computer. I'm not gonna
>> leave them high and dry. And I don't know how long it will take to get
>> them afloat.
>>
>> Please provide more information.
>>
>> Thank you
>> Carl
>
>

_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on or temporarily stop your subscription.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.