[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-promo
Subject: Re: [kde-promo] Branding checks to upcoming book
From: Rohan Garg <rohan16garg () gmail ! com>
Date: 2011-10-21 1:33:41
Message-ID: CAEb1ZdipGumSWDSuTb-uvzYq3yDG1d7VfuMqjqUb45_0SxUieA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi Carl
We are going to publish after dinner, so you can do the checks for another
45 minutes or so. None of us will be available on IRC tho, and we are going
to publish as soon as we come back from dinner.
Regards
Rohan Garg
On Thu, Oct 20, 2011 at 6:31 PM, Carl Symons <carlsymons@gmail.com> wrote:
> On Thu, Oct 20, 2011 at 4:51 PM, Rohan Garg <rohan16garg@gmail.com> 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 <carlsymons@gmail.com>
> wrote:
> >>
> >> On Thu, Oct 20, 2011 at 11:55 AM, Rohan Garg <rohan16garg@gmail.com>
> >> 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 <carlsymons@gmail.com>
> >> > wrote:
> >> >>
> >> >> On Wed, Oct 19, 2011 at 5:14 PM, Rohan Garg <rohan16garg@gmail.com>
> >> >> 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 <carlsymons@gmail.com
> >
> >> >> > wrote:
> >> >> >>
> >> >> >> On Wed, Oct 19, 2011 at 4:32 PM, Rohan Garg <
> rohan16garg@gmail.com>
> >> >> >> 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
> >> >> >
> >> >> >
> >> >
> >> >
> >
> >
>
[Attachment #5 (text/html)]
<div dir="ltr">Hi Carl<div>We are going to publish after dinner, so you can do the \
checks for another 45 minutes or so. None of us will be available on IRC tho, and we \
are going to publish as soon as we come back from dinner.</div>
<div><br></div><div>Regards</div><div>Rohan Garg<br clear="all"><br><br><div \
class="gmail_quote">On Thu, Oct 20, 2011 at 6:31 PM, Carl Symons <span \
dir="ltr"><<a href="mailto:carlsymons@gmail.com">carlsymons@gmail.com</a>></span> \
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex;"><div class="im">On Thu, Oct 20, 2011 at 4:51 PM, Rohan Garg \
<<a href="mailto:rohan16garg@gmail.com">rohan16garg@gmail.com</a>> wrote:<br>
> Awesome! Most of our content is currently done, but we would love a extra<br>
> set of eyes to review our work. It would be awesome if we could contact you<br>
> via IRC, the channel is #kde-doc-camp. Editing the book requires you to<br>
> signup with booki.cc and then edit the book via this link<br>
> : <a href="http://www.booki.cc/kde/_edit/" \
target="_blank">http://www.booki.cc/kde/_edit/</a> .<br> > If it's not \
possible for you to come on IRC, we can use email to collaborate<br> > and review \
stuff. The book will be sent to the publisher at 6 PM PST , but<br> > we can \
continue editing it after 6PM PST as well.<br> > To everyone else in the KDE Promo \
team, we think we have fixed most of the<br> > branding issues, could you please \
review the book here<br> > : <a href="http://www.booki.cc/kde/_full/" \
target="_blank">http://www.booki.cc/kde/_full/</a><br> > Thanks for taking out the \
time and reviewing our book on such a short<br> > notice.<br>
> Regards<br>
> Rohan Garg<br>
<br>
</div>I'm just getting in from another meeting. It's after 6 pst. So \
you're<br> published and we'll start polishing together.<br>
<br>
I'm registered at booki. joined #kde-doc-camp. I'm still going to be<br>
/away for a while. But it will probably take a while to get the book<br>
sorted out anyway.<br>
<font color="#888888"><br>
Carl<br>
</font><div><div></div><div class="h5"><br>
<br>
><br>
> On Thu, Oct 20, 2011 at 4:38 PM, Carl Symons <<a \
href="mailto:carlsymons@gmail.com">carlsymons@gmail.com</a>> wrote:<br> \
>><br> >> On Thu, Oct 20, 2011 at 11:55 AM, Rohan Garg <<a \
href="mailto:rohan16garg@gmail.com">rohan16garg@gmail.com</a>><br> >> \
wrote:<br> >> > Hi<br>
>> > I believe I should clarify a couple of things that I should have<br>
>> > included<br>
>> > earlier.<br>
>> > < comments inline ><br>
>><br>
>> that's cool. I got a bunch of information from Claudia and Ingo. \
When<br> >> I first heard about your project, I had no background \
information.<br> >><br>
>> > On Thu, Oct 20, 2011 at 7:45 AM, Carl Symons <<a \
href="mailto:carlsymons@gmail.com">carlsymons@gmail.com</a>><br> >> > \
wrote:<br> >> >><br>
>> >> On Wed, Oct 19, 2011 at 5:14 PM, Rohan Garg <<a \
href="mailto:rohan16garg@gmail.com">rohan16garg@gmail.com</a>><br> >> \
>> wrote:<br> >> >> > Oh, I'm extremely sorry, the link to \
the book<br> >> >> > is <a href="http://www.booki.cc/kde/_full/" \
target="_blank">http://www.booki.cc/kde/_full/</a> . The content will be \
finalized<br> >> >> > till 6<br>
>> >> > PM<br>
>> >> > PST tomorrow and will be sent to publishing. We can still \
makfre<br> >> >> > changes<br>
>> >> > but<br>
>> >> > the first edition of the book won't contain the fixes. \
Would this be<br> >> >> > enough<br>
>> >> > time for you guys to review our work?<br>
>> >> > Regards<br>
>> >> > Rohan Garg<br>
>> >><br>
>> >> Please say why your book is being sent to the publisher at 6:00 \
p.m.<br> >> >> today (10/20/11). Here's the dilemma I have...<br>
>> >> - <a href="http://www.booki.cc/kde/_full/" \
target="_blank">http://www.booki.cc/kde/_full/</a> converts to a 42 page odt. The<br> \
>> >> webpage is not editable in any serious fashion. Google Docs is \
fine<br> >> >> for some kinds of collaborative editing, but it \
doesn't work well for<br> >> >> versioning and involvement of \
multiple editors.<br> >> ><br>
>> > The publishing bit is quite different from the conventional \
publishing,<br> >> > you<br>
>> > can publish books via booki to lulu as soon as you are done fixing<br>
>> > stuff.<br>
>> > So, you can make edits on booki later on as well -> Publish changes \
to<br> >> > lulu.<br>
>> > The book sprint ends at 6 PM PST, which is why it goes to \
publishing<br> >> > right<br>
>> > away.<br>
>><br>
>> Yes, I understand all this now. I think it's a fine idea. And \
I'm<br> >> happy to help. I'm also happy that this is an ongoing \
project.<br> >><br>
>> ><br>
>> >><br>
>> >> - There is a lot of information in the document. And it covers \
many<br> >> >> areas of effort within KDE. Accuracy is almost certainly \
compromised.<br> >> >><br>
>> >><br>
>> ><br>
>> > The information is extensive because we are just getting started, \
the<br> >> > aim of<br>
>> > the book is not to teach you how to code but why to code for KDE and \
how<br> >> > to<br>
>> > get started to code for KDE, setting up a development environment \
and<br> >> > sending in patches.<br>
>> ><br>
>> >><br>
>> >> - The intended audience is not clear. The potential development<br>
>> >> categories are listed below. How will this book be distributed? \
How<br> >> >> does it get into people's hands? Is it published on \
paper? A website?<br> >> ><br>
>> > Lulu offers printing options and the book will be available via the \
PDF<br> >> > and<br>
>> > epub formats from <a href="http://flossmanuals.net" \
target="_blank">flossmanuals.net</a><br> >> ><br>
>> >><br>
>> >> * Submitting a bug fix<br>
>> ><br>
>> > We have a very good techbase page on this that we will incorporate \
into<br> >> > the<br>
>> > book<br>
>> ><br>
>> >><br>
>> >> * Writing a new application powered by KDE<br>
>> ><br>
>> > Kind of outside the scope of the book. Essentially the book is aimed \
at<br> >> > teaching beginners the 'tools of the trade' , the \
community and the<br> >> > technologies behind KDE. How to code has to be \
learnt by the reader<br> >> > himself<br>
>> > by looking at the API's and experimenting.<br>
>> >><br>
>> >> * Contributing to an existing project<br>
>> ><br>
>> > This is covered under multiple chapters, for example, choosing a<br>
>> > project,<br>
>> > where to look for API docs, what IDE to use and how to submit patches \
to<br> >> > revieboard.<br>
>> ><br>
>> >><br>
>> >> * Adding functionality to KDE development libraries<br>
>> ><br>
>> > Same as above, also covered under the documentation chapter ( How \
to<br> >> > write<br>
>> > API Docs for new stuff )<br>
>> ><br>
>> >><br>
>> >> * Writing a new application using KDE tools<br>
>> ><br>
>> > I don't understand how this is different from "Writing a new \
application<br> >> > powered by KDE" , could you please \
elaborate?<br> >><br>
>> I think that all the items preceded by * were taken from your book.<br>
>> Looking now, I don't see all them. I did not intend to add anything.<br>
>><br>
>> >><br>
>> >> - There are ongoing efforts to recruit people to KDE in many types \
of<br> >> >> tasks. How does your work complement those efforts?<br>
>> >><br>
>> > The main objective is to help people who have no idea where to get<br>
>> > started<br>
>> > in KDE, choose a project, teach them how to use tools we use \
everyday,<br> >> > and<br>
>> > submit a patch/fix a bug in KDE. At the end of reading this book, \
the<br> >> > reader<br>
>> > will be able submit a patch to the KDE Review Board ( assuming he \
has<br> >> > had<br>
>> > *some* previous coding experience ). Mainly it's aimed at GSoC \
students<br> >> > but<br>
>> > can be easily extended to cover a broader base. Since this was not<br>
>> > possible<br>
>> > in a 3 day book sprint, our scope was a bit limited. We are going \
to<br> >> > improve<br>
>> > the scope in later editions of the book as well.<br>
>><br>
>> This gets clearer knowing what you are creating. Your book will have \
many<br> >> uses.<br>
>><br>
>> ><br>
>> >><br>
>> >> From somewhere came the idea that this book was needed. From \
somewhere<br> >> >> came the idea that it would be published in less than \
12 hours from<br> >> >> now. It seems to me that it would be an important \
consideration of the<br> >> >> project to address meta-issues. Even if \
that means publishing will be<br> >> >> delayed from what was originally \
planned.<br> >> ><br>
>> > We can easily address this since lulu offers a continuous \
publication<br> >> > model<br>
>> > and there are no 'editions'.<br>
>> ><br>
>> >><br>
>> >> I would be happy to work on your document if your group will \
allocate<br> >> >> enough time and involvement for the job to be done \
well. Otherwise,<br> >> >> I'm not willing to do what seems to me to \
be less than quality work. I<br> >> >> do not intend to diminish the work \
of your group on this book nor on<br> >> >> the GSoC projects that \
y'all have done.<br> >> ><br>
>> > All of us do understand that we will need to commit our time for \
future<br> >> > editions as well, and our decision was based on not a one \
time short<br> >> > sprint,<br>
>> > but something that we will be working on improving continuously in \
the<br> >> > coming months.<br>
>> >><br>
>> >><br>
>><br>
>> My questions and comments were written in ignorance. How it seemed to<br>
>> me was that an extensive book needed to be edited in too short of time<br>
>> to do the job right. Knowing more about the project, please disregard<br>
>> most of what I wrote.<br>
>><br>
>> I would now be interested to know what the plan is going forward as it<br>
>> applies to reviewing and editing.<br>
>><br>
>> Thank you to your team. Claudia sent me a link to the report. It<br>
>> sounds like you had an exciting time of hard work.<br>
>><br>
>> Carl<br>
>><br>
>> >><br>
>> >><br>
>> >><br>
>> >> ><br>
>> >> > On Wed, Oct 19, 2011 at 5:07 PM, Carl Symons <<a \
href="mailto:carlsymons@gmail.com">carlsymons@gmail.com</a>><br> >> >> \
> wrote:<br> >> >> >><br>
>> >> >> On Wed, Oct 19, 2011 at 4:32 PM, Rohan Garg <<a \
href="mailto:rohan16garg@gmail.com">rohan16garg@gmail.com</a>><br> >> \
>> >> wrote:<br> >> >> >> > Hi!<br>
>> >> >> > We are writing a book at the GSoC Doc Camp sprint in \
Mountain View<br> >> >> >> > that<br>
>> >> >> > gets<br>
>> >> >> > new developers started in KDE Software Development \
and we would<br> >> >> >> > like<br>
>> >> >> > you<br>
>> >> >> > guys to review our work in order to ensure that we \
haven't made<br> >> >> >> > any unintentional branding \
mistakes in the book. The book will be<br> >> >> >> > \
finalized<br> >> >> >> > till 6 PM PST, so we need your review \
ASAP.<br> >> >> >> > <a \
href="http://www.launchpad.net/~rohangarg" \
target="_blank">www.launchpad.net/~rohangarg</a><br> >> >> >> \
><br> >> >> >> ><br>
>> >> >><br>
>> >> >> I love your intentionality. However, 1 1/2 hours to review \
something<br> >> >> >> is a pretty audacious request. I'm \
probably the only one available<br> >> >> >> to<br>
>> >> >> do this...most people are in Europe or India. One other \
minor<br> >> >> >> problem...I don't see anything at <a \
href="http://www.launchpad.net/~rohangarg" \
target="_blank">www.launchpad.net/~rohangarg</a> to<br> >> >> >> \
review.<br> >> >> >><br>
>> >> >> What is the magic of publishing at 6 PM?<br>
>> >> >> Do you prefer now or correct?<br>
>> >> >> What is the document that needs to be reviewed?<br>
>> >> >><br>
>> >> >> I may have some time to do this in the next short while, \
but I<br> >> >> >> already<br>
>> >> >> made a commitment to help someone with a Kubuntu upgrade \
to Oneiric.<br> >> >> >> They are sitting in a coffee shop with no \
computer. I'm not gonna<br> >> >> >> leave them high and dry. \
And I don't know how long it will take to<br> >> >> >> get<br>
>> >> >> them afloat.<br>
>> >> >><br>
>> >> >> Please provide more information.<br>
>> >> >><br>
>> >> >> Thank you<br>
>> >> >> Carl<br>
>> >> ><br>
>> >> ><br>
>> ><br>
>> ><br>
><br>
><br>
</div></div></blockquote></div><br></div></div>
_______________________________________________
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.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic