I think it's time to speak about our futur work to made on booksprint. It's
better arrived and know a little about what exactly we will do.
We know, it's for write an english manual of user for Inkscape.
If we can write a french manual, too, it's an side effect positiv, but it's
not more my goal.
After, i can translate it.
Fist of all, i thought we have already a TOC.
But with my little experience of author, i think this TOC, (very good also)
Floss Manual advice :
* only use one Heading One (h1) for the chapter, at the top of the page
(and other : * bold technical terms when first used
* explain every step, and include clear screen shots for every step
* explain all jargon 'inline'
* make no references to chapters before or after )
Google need : 40 chapters
One H1 for chapter => other organisation of the TOC.
Actually our official TOC have Part, H1, H2, H3....
Furthemore i have see, with the same content, the organization change for each
What it make for me a little confusion is :
The main goal is write a paper book or an online manual ?
For me the way to write change a little... Less details on online manual.
Short strings and not attention to construct a linear read. Clic in internet
is the king. Etc.
Print manual : organization of the chapter one after one ; why not creat quick
box (like "Be carful", or "HotKeys most used" etc ; I don't know why, but
paper editor love them. Maye it was for a good things. Etc.
Paper book or online manual, we can organize the same TOC, the same of the
kind of organization about our chapter.
Here my proposal of a TOC. Be careful it was not "in order" (french
expression). It's a Twiki, so we don't care if we don't do chapter in order.
* = chapter
* Interface and vocabulary
* Rectangle tool
* Circle tool
* Star tool
* 3Dbox tol
* Pen tool
* Bezier tool
* Calligraphic tool
* Trace bitmap
* Menu Path
* Text tool
* Gris, Guides, Snapping
* Ikscape and Wikimedia
* Color and Style
* Tile Clone
* Spiral tool
* Node tool
* Selector tool
* Gradient tool
* Eraser tool
* Align and Distribute
* Personnaliser son Inkscape
* Propriétés du document
* Effects - color
* Effects - rendu
* Effects - Modifier le chemin
* Effects - Image Raster
* Effects - Visualisation du chemin
* Effets - Générer chemin
* Effects - Générer modèle
* Effects - Images
Proposition of organization for each chapter :
* Chapter example of one tool
Introduction (why to use, purpose of this functionnality)
How to use
Other example :
* Color and Style
How to use
Creat his own markers
etc. I have already think in each organization of each chapter. But this mail
is very long.
I can develop more after yours comments.
Great to finally meet you!
I think we need to make sure at least one license is GPL in keeping with
the software itself. I don't think there's any problem with dual
licensing - at least personally - or even triple, if need be. What does
FLOSS Manuals require/recommend, Adam?
Although I'm not entirely familliar with GFDL (I'll read up on it), it
should be fine.
PS - I'm sending this to the list too, since I think it's an important
discussion to have there.
Brianna Laugher wrote:
> BTW, a question: what license is intended to be used for the material
> created during the book sprint?
> Text at Wikimedia Commons, and almost all of the Wikimedia projects,
> is GFDL. If the booksprint content was licensed (or dual licensed)
> under this license, it would allow it to be easily incorporated and
> integrated into Commons help texts and such. If the content was
> solely licensed under GFDL, it would allow FLOSS Manuals to integrate
> back any useful text from Commons et al.
> Just a thought.
On Mon, 2008-06-02 at 15:41 -0500, Joshua Facemyer / Impressus Art
> If you click on "write" at the top of the FM page, you'll see it in the
> middle of the list of manuals. It's not on the front page because it is
> not complete, so it hasn't been made public yet.
> The two that are there are mostly test spots so we can learn how to use
> it. So feel free to play around with it and learn the interface.
> Mr. Shawn H. Corey wrote:
> > On Mon, 2008-06-02 at 15:04 -0500, Joshua Facemyer / Impressus Art
> > wrote:
> >> A short time ago, those of us who had been actively discussing the
> >> manual on the inkscape-docs list agreed that FLOSS Manuals
> >> (http://flossmanuals.net <http://flossmanuals.net/>) was our best option
> >> for keeping an official manual up-to-date while encouraging
> >> non-technical users to contribute.
> > Ah, but do you have a link to the Inkscape manual? Does it exist?
But it's exact HTTP address is?
Just my 0.00000002 million dollars worth,
Shangri La: 40,000 KM -->
The map is not the territory,
the dossier is not the person,
the model is not reality.
A short time ago, those of us who had been actively discussing the
manual on the inkscape-docs list agreed that FLOSS Manuals
(http://flossmanuals.net <http://flossmanuals.net/>) was our best option
for keeping an official manual up-to-date while encouraging
non-technical users to contribute. It has a simple interface, is readily
available (it is a web application), and there exist translation tools
which are being actively developed to provide a usable translation
interface. There are many other benefits to using FLOSS Manuals (FM) as
well: we would have the ability to organize different setups of manuals
/ how-tos by arranging existing content into new “manuals”; to generate
manuals in different distributable formats (export as pdf, html, and
even print online with lulu.com, et cetera). These powerful capabilities
create an exciting possibility to build and maintain a dynamic manual
with minimal effort.
Recently, FM has received a small grant from Google to host a “book
sprint”. Adam Hyde of FM has personally invited some of the members from
the inkscape-docs list to join him for the book sprint in order to flesh
out a basic, up-to-date manual using the FM tools. (If you have not seen
how this works yet, you can go to the website and check it out. Since
our manual has only some test material in it, you cannot yet view it as
a manual, but if you set up user account, you can view it in the edit
While FM has certain guidelines which the book sprint must follow and
goals to accomplish, we will be discussing on inkscape-docs the
particulars which we want the book sprint to produce in order to make it
most productive for both FM and Inkscape. Adam will be active in this
discussion, and help guide it so that it proceeds toward both FLOSS
Manual goals and Inkscape Docs goals. Anyone who would like to
participate in this discussion is welcome and encouraged to do so.
Also, anyone is welcome and encouraged to take part in the actual book
sprint itself, which will be taking place from July 5^th through the
12^th in Paris. Participants are welcome either in person, if you are
able, or else by internet. (Details will follow on inkscape-docs as they
are worked out.)
The committed participants thus far are:
Adam Hyde (from FLOSS Manuals)
Brianna Laugher from Wikimedia (http://brianna.modernthings.org
Cédric Gemy (pygmee)
Elisa de Castro Guerra (yemanja)
and I (Joshua Facemyer)
We are all looking forward to spending some time getting to know each
other better, seeing Paris (those of us who don't live there ;) and,
most importantly, putting together an Inkscape Manual for the betterment
of the Inkscape community!