Re: Branding checks to upcoming book

On Thu, Oct 20, 2011 at 4:51 PM, Rohan Garg <[email protected]> wrote:
> Awesome! Most of our content is currently done, but we would love a extra
> set of eyes to review our work. It would be awesome if we could contact you
> via IRC, the channel is #kde-doc-camp. Editing the book requires you to
> signup with booki.cc and then edit the book via this link
> : http://www.booki.cc/kde/_edit/ .
> If it's not possible for you to come on IRC, we can use email to collaborate
> and review stuff. The book will be sent to the publisher at 6 PM PST , but
> we can continue editing it after 6PM PST as well.
> To everyone else in the KDE Promo team, we think we have fixed most of the
> branding issues, could you please review the book here
> : http://www.booki.cc/kde/_full/
> Thanks for taking out the time and reviewing our book on such a short
> notice.
> Regards
> Rohan Garg

I'm just getting in from another meeting. It's after 6 pst. So you're
published and we'll start polishing together.

I'm registered at booki. joined #kde-doc-camp. I'm still going to be
/away for a while. But it will probably take a while to get the book
sorted out anyway.

Carl


>
> On Thu, Oct 20, 2011 at 4:38 PM, Carl Symons <[email protected]> wrote:
>>
>> On Thu, Oct 20, 2011 at 11:55 AM, Rohan Garg <[email protected]>
>> wrote:
>> > Hi
>> > I believe I should clarify a couple of things that I should have
>> > included
>> > earlier.
>> > < comments inline >
>>
>> that's cool. I got a bunch of information from Claudia and Ingo. When
>> I first heard about your project, I had no background information.
>>
>> > On Thu, Oct 20, 2011 at 7:45 AM, Carl Symons <[email protected]>
>> > wrote:
>> >>
>> >> 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 makfre
>> >> > 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.
>> >
>> > The publishing bit is quite different from the conventional publishing,
>> > you
>> > can publish books via booki to lulu as soon as you are done fixing
>> > stuff.
>> > So, you can make edits on booki later on as well -> Publish changes to
>> > lulu.
>> > The book sprint ends at 6 PM PST, which is why it goes to publishing
>> > right
>> > away.
>>
>> Yes, I understand all this now. I think it's a fine idea. And I'm
>> happy to help. I'm also happy that this is an ongoing project.
>>
>> >
>> >>
>> >> - There is a lot of information in the document. And it covers many
>> >> areas of effort within KDE. Accuracy is almost certainly compromised.
>> >>
>> >>
>> >
>> > The information is extensive because we are just getting started, the
>> > aim of
>> > the book is not to teach you how to code but why to code for KDE and how
>> > to
>> > get started to code for KDE, setting up a development environment and
>> > sending in patches.
>> >
>> >>
>> >> - 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?
>> >
>> > Lulu offers printing options and the book will be available via the PDF
>> > and
>> > epub formats from flossmanuals.net
>> >
>> >>
>> >>     * Submitting a bug fix
>> >
>> > We have a very good techbase page on this that we will incorporate into
>> > the
>> > book
>> >
>> >>
>> >>     * Writing a new application powered by KDE
>> >
>> > Kind of outside the scope of the book. Essentially the book is aimed  at
>> > teaching beginners the 'tools of the trade' , the community and the
>> > technologies behind KDE. How to code has to be learnt by the reader
>> > himself
>> > by looking at the API's and experimenting.
>> >>
>> >>     * Contributing to an existing project
>> >
>> > This is covered under multiple chapters, for example, choosing a
>> > project,
>> > where to look for API docs, what IDE to use and how to submit patches to
>> > revieboard.
>> >
>> >>
>> >>     * Adding functionality to KDE development libraries
>> >
>> > Same as above, also covered under the documentation chapter ( How to
>> > write
>> > API Docs for new stuff )
>> >
>> >>
>> >>     * Writing a new application using KDE tools
>> >
>> > I don't understand how this is different from "Writing a new application
>> > powered  by KDE" , could you please elaborate?
>>
>> I think that all the items preceded by * were taken from your book.
>> Looking now, I don't see all them. I did not intend to add anything.
>>
>> >>
>> >> - There are ongoing efforts to recruit people to KDE in many types of
>> >> tasks. How does your work complement those efforts?
>> >>
>> > The main objective is to help people who have no idea where to get
>> > started
>> > in KDE, choose a project, teach them how to use tools we use everyday,
>> > and
>> > submit a patch/fix a bug in KDE. At the end of reading this book, the
>> > reader
>> > will be able submit a patch to the KDE Review Board ( assuming he has
>> > had
>> > *some* previous coding experience ). Mainly it's aimed at GSoC students
>> > but
>> > can be easily extended to cover a broader base. Since this was not
>> > possible
>> > in a 3 day book sprint, our scope was a bit limited. We are going to
>> > improve
>> > the scope in later editions of the book as well.
>>
>> This gets clearer knowing what you are creating. Your book will have many
>> uses.
>>
>> >
>> >>
>> >> 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.
>> >
>> > We can easily address this since lulu offers a continuous publication
>> > model
>> > and there are no 'editions'.
>> >
>> >>
>> >> 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.
>> >
>> > All of us do understand that we will need to commit our time for future
>> > editions as well, and our decision was based on not a one time short
>> > sprint,
>> > but something that we will be working on improving continuously in the
>> > coming months.
>> >>
>> >>
>>
>> My questions and comments were written in ignorance. How it seemed to
>> me was that an extensive book needed to be edited in too short of time
>> to do the job right. Knowing more about the project, please disregard
>> most of what I wrote.
>>
>> I would now be interested to know what the plan is going forward as it
>> applies to reviewing and editing.
>>
>> Thank you to your team. Claudia sent me a link to the report. It
>> sounds like you had an exciting time of hard work.
>>
>> 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.