English فارسی Suomi
Français Nederlands Translate

helen varley jamieson
RSS feed of my changes
Suggestions:
To create new books go to "My Books".
Read the booki-user-guide
Optional snippet context URL:

Timeline of @helen:
@adam [send a reply]
3 years, 1 month ago
@agarton ok... ask them if we can help somehow...happy to chat via voice if it will help
@adam [send a reply]
3 years, 1 month ago
@agarton http://lists.booksprints.net/listinfo.cgi/facilitators-booksprints.net and http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
@adam [send a reply]
3 years, 1 month ago
@agarton ok are u on the fm list...i will email it there..also, feel like joining the booksprints.net faciliation list? and...thought about doing a book sprint? we could think about hos to plan this....fm might be able to help
@adam [send a reply]
3 years, 1 month ago
@agarton hey...nice guide... do you need some help taking it fwd? if so let me know and i see if i can drum up some peeps adam
@adam [send a reply]
3 years, 1 month ago
@Bakudan welcome to fm!
@adam [send a reply]
3 years, 1 month ago
@trueg welcome to fm!
@adam [send a reply]
3 years, 1 month ago
@Migou welcome to fm!
@adam [send a reply]
3 years, 1 month ago
@alimamo welcome to fm!
@adam [send a reply]
3 years, 1 month ago
@graemef welcome to fm!
@helen [send a reply]
3 years, 2 months ago
finding a moment to start proofreading the Wordpress manual :)
@adam [send a reply]
3 years, 2 months ago
@elapid welvcome to FM:)letme knowifyou need any help
@adam [send a reply]
3 years, 2 months ago
@amandawhite hi, welcome to fm
@adam [send a reply]
3 years, 2 months ago
@jusfixit ok, so i am now shortening a few of the chapter names. check the booki.flossmanuals.net/bluegriffin/_edit page and then when u are happy tell me and i will gibve you info on how to push it to the 'read' part of fm :)
@adam [send a reply]
3 years, 2 months ago
@Katymoon hi Katy, welcome to fm :)
@adam [send a reply]
3 years, 2 months ago
@delinia welcome to fm! let me know if i can help... adam
@adam [send a reply]
3 years, 2 months ago
@AliaksandrTsurko welcoem to fm! let me know if i can help :)
@adam [send a reply]
3 years, 2 months ago
@saian wellcome to fm! let me know if i can help...
@adam [send a reply]
3 years, 2 months ago
@helen coolio :)
@helen [send a reply]
3 years, 2 months ago
@adam ah, thanks! i was missing the .php ... :)
@adam [send a reply]
3 years, 2 months ago
@helen www.flossmanuals.net/admin.php :)
@helen [send a reply]
3 years, 2 months ago
@adam - sorry to have to ask you this again, but what is the url for publishing a manual? (& why is it so hard to find ... ? :(
@adam [send a reply]
3 years, 2 months ago
@zhouzhiyong welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@pierrecast welcome to fm pierre :)
@adam [send a reply]
3 years, 2 months ago
@victor welcome to fm victor :)
@adam [send a reply]
3 years, 2 months ago
@marinli welcoem to fm valerie
@adam [send a reply]
3 years, 2 months ago
@CherryWithers welcome to fm cherry :)
@adam [send a reply]
3 years, 2 months ago
@gungho hey Pete welcome to fm :)
@helen [send a reply]
3 years, 2 months ago
@vickismith hi i just created a group on FM for people working on the UpStage manual - not so much to use now but when we get to implementing the new stuff & need to update the manual - actually write a new one i think; i'd like to invite more people to contribute & right now we are having a session about the messaging system on FM. which is what i'm using now :) & you can set up a group then message a group about stuff when working on the manual.
@helen [send a reply]
3 years, 2 months ago
@sisi [send a reply]
3 years, 2 months ago
@helen Yes, I would say so :) and thanks for greeting!
@helen [send a reply]
3 years, 2 months ago
@tomi hi tomi!
@helen [send a reply]
3 years, 2 months ago
@sisi - no if you don't know the /etc then you're another sisi :) (http://www.eclectictechcarnival.org). hello anyway! :)
@sisi [send a reply]
3 years, 2 months ago
@helen Which /etc? are you talking about? I guess not :)
@TomiToivio [send a reply]
3 years, 2 months ago
@helen Hello!
@helen [send a reply]
3 years, 2 months ago
@sisi hi, is that sisi from /etc? :)
@helen [send a reply]
3 years, 2 months ago
#talk hello from berlin
@helen [send a reply]
3 years, 2 months ago
@tuukka hi
@helen [send a reply]
3 years, 2 months ago
hello we are at the FM meeting in berlin
@adam [send a reply]
3 years, 2 months ago
@mahendra welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@poweroftwo welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@carol_law hey carol, welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@Luby welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@volvac welcome to fm!
@adam [send a reply]
3 years, 2 months ago
@waldir hey, yeah i think that would be great idea. first though we need to update the fm-booki manual...we are meeting about that today
@adam [send a reply]
3 years, 2 months ago
@qizhang welcome to fm :)
@adam [send a reply]
3 years, 2 months ago
@waldir welcome to FM waldir, let me know if u need a hand finding your way around.
@adam [send a reply]
3 years, 2 months ago
@gnujunk welcome to FM John :)
@adam [send a reply]
3 years, 2 months ago
@tuukka this ok?
Snippet: [Context]
Seravo
Seravo have helped develop a lot of the tools that FLOSS Manuals uses, they provide continued support for help with maintenance and systems administration and they also have helped the Finnish and French FLOSS Manuals establish their technical framework.
http://seravo.fi/
@adam [send a reply]
3 years, 2 months ago
@jusfixit hey...want to add the manual to the http://booki.flossmanuals.net/groups/html-editors/ group? you need to join the group first...also i had been asked about maybe putting this manual through a pr channel...i wanted tocheck first if you are planning any more work on it at the moment and how you see it gnerally...
@adam [send a reply]
3 years, 2 months ago
@andred hi andre, welcome to floss manuals
@adam [send a reply]
3 years, 2 months ago
@teraspawn hi beth, welcome to floss manuals
@adam [send a reply]
3 years, 2 months ago
@scarper hi scott, welcome to floss manuals
@adam [send a reply]
3 years, 2 months ago
@elag hi Elizabeth, welcometo FLOSS Manuals :)
@adam [send a reply]
3 years, 2 months ago
@jimbearhuang hi Jimmy, welcome to FLOSS Manuals :)
@adam [send a reply]
3 years, 3 months ago
@andy welcome to FLOSS Manuals andy :)
@adam [send a reply]
3 years, 3 months ago
@Nthabiseng hi Nthabiseng, welcometo floss manuals
@adam [send a reply]
3 years, 3 months ago
@gremble hey Ben, welcome to floss manuals
@adam [send a reply]
3 years, 3 months ago
@TrevorParsons nice :) good luck!
@adam [send a reply]
3 years, 3 months ago
@TrevorParsons hey Trevor, welcome to floss manuals
@adam [send a reply]
3 years, 3 months ago
@lzambito welcome leo:)
@adam [send a reply]
3 years, 3 months ago
@dol1956 welcome to booki david
@adam [send a reply]
3 years, 3 months ago
@Yaco to Franco...welcome :)
@adam [send a reply]
3 years, 3 months ago
@kawadri welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@shawnhcorey hiShawn, welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@zanteifc2 welcome to FM :)
@adam [send a reply]
3 years, 3 months ago
@BOSS welcome to FM :)
@adam [send a reply]
3 years, 3 months ago
@upsiddown welcome toFM :)
@adam [send a reply]
3 years, 3 months ago
@jonahboss hijonah,welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@stevieflow no worries! let me know if u need a hand working out it all works...its pretty straight forward but if i can help let me know...
@adam [send a reply]
3 years, 3 months ago
@camille hey :)
@adam [send a reply]
3 years, 3 months ago
@allanbinary hey allan, welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@seank hi sean, welcome to fm
@adam [send a reply]
3 years, 3 months ago
@stevieflow hi steven, welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@mickfuzz - you want me to work on this chapter (below with notes)
Snippet: [Context]

About this Manual

History

version one was by- err...adam willets? mick fuzz? cant remember

 

want some history of the collab process and that this is open to anyone to edit?

Book Jog and version 2

@adam [send a reply]
3 years, 3 months ago
@mickfuzz - you want me to work on this chapter (below with notes)
Snippet: [Context]

About this Manual

History


Book Jog and version 2

@adam [send a reply]
3 years, 3 months ago
@mickfuzz testing new messaging...should update timeline auto
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
tester
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
aaa
@adam [send a reply]
3 years, 3 months ago
aaa
@adam [send a reply]
3 years, 3 months ago
aa
@adam [send a reply]
3 years, 3 months ago
a
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
aaa
@adam [send a reply]
3 years, 3 months ago
aaaaaa
@adam [send a reply]
3 years, 3 months ago
sss
@adam [send a reply]
3 years, 3 months ago
yyyy sss
@adam [send a reply]
3 years, 3 months ago
yyyy
@adam [send a reply]
3 years, 3 months ago
tester
@adam [send a reply]
3 years, 3 months ago
yet another test
@adam [send a reply]
3 years, 3 months ago
another test
@adam [send a reply]
3 years, 3 months ago
another test
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
test
@adam [send a reply]
3 years, 3 months ago
@Ragpickr hey Bhabesh. welcome to fm!
@adam [send a reply]
3 years, 3 months ago
@williec hey willie. welcome to flossmanuals
@adam [send a reply]
3 years, 3 months ago
@mikelittle hey mike, welcome to floss manuals. let me know if you need a hand finding your way around. adam
@adam [send a reply]
3 years, 3 months ago
@lcdservices hey brian! nice to see you here :) adam
@adam [send a reply]
3 years, 3 months ago
@davyrhys hey Davy. Welcome to floss manuals!
@adam [send a reply]
3 years, 3 months ago
@pvincent welcome to floss manials philippe...let me know if you need a hand finding your way around
@adam [send a reply]
3 years, 3 months ago
@jusfixit just replying to your question now about putting luegriffon on fm
@adam [send a reply]
3 years, 3 months ago
#announce
Snippet:

CiviCRM Book Sprint 3 done!

CiviCRM Book Sprint 3 is done. Updated manual, new dev guide and another book that was an experiment in shaping a manual for the human rights sector. All fantastic stuff...more news soon.

 

@adam [send a reply]
3 years, 3 months ago
@michau thanks for the invite to the sprint and thanks for all your work on the manuals...it was a lot of fun working with you once again :)))) good luck with the training.
@adam [send a reply]
3 years, 3 months ago
@petermcandrew hey peter. thanks for the work on the dev guide. looks great :)
@adam [send a reply]
3 years, 3 months ago
@techczech hey Dominik ...thanks for coming to the sprint! :) it was great having you there andwe could not have finished the email seciton without you...thanks a lot. hope to see you again sometime :)
@adam [send a reply]
3 years, 3 months ago
@davem hey dave...just wanted to say thanks for everything. it was a pleasure working with you and your contribution was excellent...thanks also for being a great host :)
@adam [send a reply]
3 years, 3 months ago
@reperry hey Robyn...just wanted to say i enjoyed working with you and thanks for the HUGE effort in the sprint :) it was great working with you and the book looks great...
@adam [send a reply]
3 years, 3 months ago
@avaguilar hey..yep book is done! we saw your chats and worked through and reviewed it...all good. next steps are to put it online(I do that today) and perhaps read over it ina few weeks....
@adam [send a reply]
3 years, 3 months ago
@brisjer sounds good :)
@adam [send a reply]
3 years, 3 months ago
@techczech welcome to fm :)
@adam [send a reply]
3 years, 3 months ago
@bikerChuck hi chuck welcome to fm :) let me know if you need help finding your way around
@adam [send a reply]
3 years, 3 months ago
@less.tx hi Leslie welcome to fm :) let me know if you need ahand finding your way around
@adam [send a reply]
3 years, 3 months ago
@jm_casanueva hi juan :) welcome to fm
@adam [send a reply]
3 years, 3 months ago
@marioroset hi mario :) welcome to fm
@adam [send a reply]
3 years, 3 months ago
!civicrm sprint starst! :)))
@adam [send a reply]
3 years, 3 months ago
#announce
Snippet:

CiviCRM Book Sprint starts!

The CiviCRM book sprint is starting today! Details coming if you want to participate remotely.

@adam [send a reply]
3 years, 4 months ago
@Norbert welcome to fm :)
@adam [send a reply]
3 years, 4 months ago
@avshyd welcome :)
@adam [send a reply]
3 years, 4 months ago
@tom welcome to fm :)
@adam [send a reply]
3 years, 4 months ago
@ElisaDCGuerra
Snippet: [Context]
Inkscape: Introduction

About Inkscape

Inkscape is an open source drawing tool for creating and editing SVG graphics.  More than just a text vector editor, Inkscape provides a WYSIWYG interface for manipulation of vector images, allowing the artist to express himself freely. While other free and proprietary software with similar capabilities exists, Inkscape provides an interface to directly manipulate the underlying SVG code. This allows one to be certain that the code complies to W3C standards. Since the beginning of its development, the Inkscape project has been very active, providing stability for the current software and the capacity for future growth.

Like other drawing programs, Inkscape offers creation of basic shapes (such as ellipses, rectangles, stars, polygons, and spirals) as well as the ability to transform and manipulate these basic shapes by rotation, stretching, and skewing.

Inkscape also allows users to manipulate objects precisely by adjusting node points and curves.  Advanced artists find these functions indispensable in drawing software to freely create what they imagine.

A user can either manipulate the properties of objects individually and precisely through the XML editor or, in a more general and intuitive fashion, with input devices such as mice, pen tablets, and even touch screens.

In addition, Inkscape allows one to insert text and bitmaps (such as PNG—another W3C recommended bitmap image format) into an image, as well as perform some basic editing functions on them.  If an artist requires further bitmap editing, he may use other tools (such as the GIMP) on images before or after importing them. If one does edit a linked bitmap in another program, Inkscape will reflect these changes once the SVG file is reloaded.

All of these characteristics make Inkscape a model drawing application, especially considering its flexibility and many other capabilities. Its strict compliance with the W3C SVG standards allows excellent portability of images to many applications and the varying platforms on which these applications run.

@adam [send a reply]
3 years, 4 months ago
@ElisaDCGuerra
Snippet: [Context]
Inkscape: Introduction

About Inkscape

Inkscape is an open source drawing tool for creating and editing SVG graphics.  More than just a text vector editor, Inkscape provides a WYSIWYG interface for manipulation of vector images, allowing the artist to express himself freely. While other free and proprietary software with similar capabilities exists, Inkscape provides an interface to directly manipulate the underlying SVG code. This allows one to be certain that the code complies to W3C standards. Since the beginning of its development, the Inkscape project has been very active, providing stability for the current software and the capacity for future growth.

Like other drawing programs, Inkscape offers creation of basic shapes (such as ellipses, rectangles, stars, polygons, and spirals) as well as the ability to transform and manipulate these basic shapes by rotation, stretching, and skewing.

Inkscape also allows users to manipulate objects precisely by adjusting node points and curves.  Advanced artists find these functions indispensable in drawing software to freely create what they imagine.

A user can either manipulate the properties of objects individually and precisely through the XML editor or, in a more general and intuitive fashion, with input devices such as mice, pen tablets, and even touch screens.

In addition, Inkscape allows one to insert text and bitmaps (such as PNG—another W3C recommended bitmap image format) into an image, as well as perform some basic editing functions on them.  If an artist requires further bitmap editing, he may use other tools (such as the GIMP) on images before or after importing them. If one does edit a linked bitmap in another program, Inkscape will reflect these changes once the SVG file is reloaded.

All of these characteristics make Inkscape a model drawing application, especially considering its flexibility and many other capabilities. Its strict compliance with the W3C SVG standards allows excellent portability of images to many applications and the varying platforms on which these applications run.

@adam [send a reply]
3 years, 4 months ago
@nicestep hey james...will u apply for the gsoc doc camp?
@adam [send a reply]
3 years, 4 months ago
@olm-e welcome:)
@adam [send a reply]
3 years, 4 months ago
@agarton hello mr garton :) long time :) good to see you here! you should make an application here https://sites.google.com/site/docsprintsummit/ ... You can apply as an individual or a group. Applications close Friday (5th), application process takes about 2-5 mins :)
Snippet:
This is a call for proposals for the 2011 Google Summer of Code Doc Camp. Individuals and projects are invited to submit proposals for the GSoC Doc Camp to be held at Google's Mountain View headquarters (California) 17 October - 21 October.

The GSoC Doc Camp is a place for documentors to meet, work on documentation and share their documentation experiences. The camp aims to improve free documentation materials and skills in GSoC projects and individuals and help form the identity of the emergent free documentation sector.

The Doc Camp will consist of 2 major components - an unconference and 3-5 short form Book Sprints to produce 'Quick Start' guides for specific GSoC projects.

The unconference will explore topics proposed by the participants. Any topic on free documentation of free software can be proposed for discussion during the event.

Each Quick Start Sprint will bring together 5-8 individuals to produce a book on a specific GSoC project. All participants of the Doc Camp must attend a sprint. The Quick Start books will be launched at the opening party for the GSoC Mentors summit immediately following the event.

Individuals with a passion for free documentation about free software may apply to attend by filling out the application form <https://sites.google.com/site/docsprintsummit/registration> and submitting before 5 August, 2011. Those wishing to attend do not need to be from a GSoC project. Accommodation and food will be covered by the GSoC Doc Camp. Part or complete travel costs can also be applied for as part of the application process.

Quick Start Sprint projects will be chosen from proposals submitted to the GSoC Doc Camp before 5 August, 2011 through the application form <https://sites.google.com/site/docsprintsummit/registration>. Applications for Quick Start Sprints are invited from projects that are part of the 2011 GSoC program. Quick Start Sprint proposals can nominate up to 5 individuals to attend and participate in the proposed sprint. A Quick Sprint proposal does not have to nominate individuals to participate - you can also use this as an opportunity to promote your project to Doc Camp participants. If the proposal is accepted the accommodation and food costs will be covered by the Doc Camp for any listed individuals and part or complete travel costs for each can be applied for (if applicable).

The GSoC Doc Camp is co-organised by GSoC and FLOSS Manuals. Books Sprints and unconference facilitation conducted by Adam Hyde.

If you have questions, please contact Carol Smith at carols@google.com and/or Adam Hyde at adam@flossmanuals.net.
@adam [send a reply]
3 years, 4 months ago
@aalex hey :) was good to see you in s'bourg...hows the doco going? let me know if you need any more info from me :)
@adam [send a reply]
3 years, 4 months ago
@bdunnette hey Brian. Saw the Tryton manual...looks good...let me know if I can help navigating around FM...
@adam [send a reply]
3 years, 4 months ago
@RitaF hey Rita....etoys ref manual looks great! all going ok with booki for you?
@adam [send a reply]
3 years, 4 months ago
@ahofmann back from hols...how did it all go?
@adam [send a reply]
3 years, 4 months ago
@VxV back from holidays...did u work out the id thing? #talk
@adam [send a reply]
3 years, 4 months ago
@Rahulmakhare welcome Rahul. let me know if I can help finding your way around fm
@adam [send a reply]
3 years, 4 months ago
@gustavo_cm hi Gustavo...hope you are finding your way around FM, let me kniw if I can help in anyway.
@adam [send a reply]
3 years, 4 months ago
@JacobWeickum welcome welcome Jacob. Adam here (founder of fm) let me know if you need any help.
@adam [send a reply]
3 years, 4 months ago
@makowiecki hey Pawewl - welcome to FM :) let me know if i can help in anyway...
@adam [send a reply]
3 years, 5 months ago
@goofy_framasoft cool...so i start making them at 1500...message me if thats not ok ;)
@adam [send a reply]
3 years, 5 months ago
@goofy_framasoft word-wrap: break-word; is the diff
@adam [send a reply]
3 years, 5 months ago
@goofy_framasoft use this css - open advanced settings in export tab, choose custom css and use this
Snippet:
body {
  font-family: "fontin sans";
  background: #fff;
  color: #000;
  font-size:12pt;
  max-width: 700px;
  word-wrap: break-word;
}
p {
  word-wrap: break-word;
}

/*Page widths */
/* just in case body max-width doesn't work */
div, p, ul, pre, h1, h2 {
  max-width: 700px;
  overflow: hidden;
}

table, tbody, tr, td {
  max-width: 700px;
  overflow: hidden;
}

img {
  max-width: 100%;
  height: auto;
  overflow:hidden;

}
/*end widths */

.objavi-chapter{
  color: #000;
  display: none;
}

a {
  text-decoration:none;
  color:#000;
}

h1 .initial{
  color: #000;
  display:none;
}

.objavi-subsection{
  display: block;
  page-break-before: always;
/*  page-break-after: always;*/
  text-transform: uppercase;
  font-size: 20pt;
}

body .objavi-subsection:first-child{
  page-break-before: avoid;
}


.objavi-subsection .initial {
  font-size: 1em;
  color: #000;
  display:none;
}

.objavi-subsection-heading {
  font-size: 20pt;
  text-align: center;
  line-height: 300px;
  font-weight: normal;
}


h1 {
  page-break-before: always;
  background: white;
  font-weight:normal !important;
}

/*h1.first-heading {
  page-break-before: avoid;
}*/


h2 {
  margin-bottom:-10pt;
  font-weight:normal ! important;
  font-size:15pt;
}

/*try to avoid a page break between an h2 and a p XXX: doesn't work */
h2 + p {
  page-break-before: avoid;
}

h2 + img {
  page-break-before: avoid;
}

h2 + table {
  page-break-before: avoid;
}

h2 + ul {
  page-break-before: avoid;
}


h2 + ol {
  page-break-before: avoid;
}

table {
  float: none;
}

h1.frontpage{
  page-break-after:always;
  margin-top:70%;
  font-size: 20pt;
  text-align: center;
  page-break-before: avoid;
  font-weight: normal;
}

div.copyright{
  padding: 1em;
}
/* TOC ******************************/
table {
  float: none;
}

table.toc {
  font-size: 1.1em;
  width: 95%;
}

table.toc td{
  vertical-align:top
  padding-left: 0.5em;
}

td.chapter {
  padding: 0 0.5em;
  text-align: right;
}

table.toc td.pagenumber {
  text-align: right;
  vertical-align:bottom;
}

td.section {
  padding-top: 1.1em;
  font-weight: bold;
}
/* End TOC **************************/


p, li {
  page-break-inside: avoid;
}

pre, code, tt {
  font-family: "Inconsolata", "Courier New", monospace;
  /*font-size: 0.8em;*/
}

pre {
  overflow: hidden;
  white-space: pre-wrap;
}


h1, h2, h3, h4, h5, h6{
  page-break-after: avoid;
  page-break-inside: avoid;
}


.page-break{
  page-break-before: always;
  height: 7em;
  display: block;
}


.glossary hr{
  display: none;
}

/* page number styles -- these are the defaults, and will persist
unless explicitly overridden.*/

#right-footer {
  text-align: right;
}

#left-footer {
  text-align: left;
}

/* page number examples: */
/*
#right-footer .page:before{
  content: " FLOSS Manuals ";
  font-size: 85%;
}

#left-footer .page:after{
  content: " FLOSS Manuals ";
  font-size: 85%;
}

.page-footer {
  color: red;
}
*/

a {
  word-wrap: break-word;
}

.objavi-no-page-break {
  page-break-inside: avoid;
}

/*To force a blank page it is sometimes necessary to add unseen
 content.  Display:none and visibility: hidden don't work -- the
 renderer realises that they're not there and skips the page.  So we
 add a tiny bit of text beyond the margin of the page.
*/
.unseen{
  z-index: -66;
  margin-left: -1000pt;
}

@adam [send a reply]
3 years, 5 months ago
#announce
Snippet:
[PRESS RELEASE] Please Circulate

Call for Proposals Open

Google Summer of Code/ FLOSS Manuals Doc Camp
----------------------------------------------
This is a call for proposals for the 2011 Google Summer of Code Doc Camp. Individuals and projects are invited to submit proposals for the GSoC Doc Camp to be held at Google's Mountain View headquarters (California) 17 October - 21 October.

The GSoC Doc Camp is a place for documentors to meet, work on documentation, and share their documentation experiences. The camp aims to improve free documentation materials and skills in GSoC projects and individuals and help form the identity of the emergent free documentation sector.

The Doc Camp will consist of 2 major components - an unconference and 3-5 short form Book Sprints to produce 'Quick Start' guides for specific GSoC projects.

The unconference will explore topics proposed by the participants. Any topic on free documentation of free software can be proposed for discussion during the event.

Each Quick Start Sprint will bring together 5-8 individuals to produce a
book on a specific GSoC project. All participants of the Doc Camp must
attend a sprint. The Quick Start books will be launched at the opening party for the GSoC Mentors summit immediately following the event.

Individuals with a passion for free documentation about free software may apply to attend by filling out the application form [1] and submitting before 5 August. Those wishing to attend do not need to be from a GSoC project. Accommodation and food will be covered by the GSoC Doc Camp. Part or complete travel costs can also be applied for as part of the application process.

Quick Start Sprint projects will be chosen from proposals submitted to the GSoC Doc Camp before 5 August through the application form [1]. Applications for Quick Start Sprints are invited from projects that are part of the 2011 GSoC program. Quick Start Sprint proposals can nominate up to 5 individuals to attend and participate in the proposed sprint. A Quick Sprint proposal does not have to nominate individuals to participate - you can also use this as an opportunity to promote your project to Doc Camp participants. If the proposal is accepted the accommodation and food costs will be covered by the Doc Camp for any listed individuals and part or complete travel costs for each can be applied for (if applicable).

The GSoC Doc Camp is co-organised by GSoC and FLOSS Manuals. Books Sprints and unconference facilitation conducted by Adam Hyde.

[1] - https://sites.google.com/site/docsprintsummit/

 



@adam [send a reply]
3 years, 5 months ago
@andycat yo...wanna build in the phono to booki?
@adam [send a reply]
3 years, 5 months ago
import working again thanks to @aerkalov :) #talk
@adam [send a reply]
3 years, 5 months ago
@username hey :) yeah replying by email would be good...so much to do...off to france tomorrow...drink/dinner when we get back I think at is still in town till mid aug?
@adam [send a reply]
3 years, 5 months ago
@username yoyo...hassling you with the new messaging system as i KNOW you have been waiting for it ;)
@adam [send a reply]
3 years, 5 months ago
@ScottWNesbitt they should put into some dev...
@adam [send a reply]
3 years, 5 months ago
@ScottWNesbitt interesting! i think booki just came alot more interesting with these new messaging widgets, woul dlove to see a few publishers try an install
@adam [send a reply]
3 years, 5 months ago
@fcormenzana welcome to FLOSS Manuals Fernando :)
@adam [send a reply]
3 years, 5 months ago
#announce
Snippet:

Doc Camp

FLOSS Manuals and Google Summer of Code Doc Camp applications opening shortly...the application process will be online...anyone can apply...get your CV ready! Hopefully launched next week.  Watch this space...

@adam [send a reply]
3 years, 5 months ago
@ScottWNesbitt hey Scott - would you help get people using this system? I will be away over the next 2 weeks on holiday and I am working the network a little before i go to get others to start using it...we need some champions to kick people along...any chance you could take this on andmaybe also convince oythers to do the same?
@adam [send a reply]
3 years, 5 months ago
@ScottWNesbitt rcokn :)
@adam [send a reply]
3 years, 5 months ago
@ScottWNesbitt yo scott...would u mind sending that link for the blog also to the talk hashtag here?
@adam [send a reply]
3 years, 5 months ago
@ahofmann hey if u manage to get a cover done in svg can u send the svg as an attachment to #covers ?
@adam [send a reply]
3 years, 5 months ago
#talk import (for cloning/importing books) feature is currently not working. @edcable
@adam [send a reply]
3 years, 5 months ago
!circumvention-tools-translations @rastapopoulos check css on front page and try it
@adam [send a reply]
3 years, 5 months ago
!circumvention-tools-translations use this css... note itook the negative value out of the h2 ... that is the only difference with the default css
Snippet:
body {
  font-family: "fontin sans";
  background: #fff;
  color: #000;
  font-size:12pt;
  max-width: 700px;
}

/*Page widths */
/* just in case body max-width doesn't work */
div, p, ul, pre, h1, h2 {
  max-width: 700px;
  overflow: hidden;
}

table, tbody, tr, td {
  max-width: 700px;
  overflow: hidden;
}

img {
  max-width: 100%;
  height: auto;
  overflow:hidden;

}
/*end widths */

.objavi-chapter{
  color: #000;
  display: none;
}

a {
  text-decoration:none;
  color:#000;
}

h1 .initial{
  color: #000;
  display:none;
}

.objavi-subsection{
  display: block;
  page-break-before: always;
/*  page-break-after: always;*/
  text-transform: uppercase;
  font-size: 20pt;
}

body .objavi-subsection:first-child{
  page-break-before: avoid;
}


.objavi-subsection .initial {
  font-size: 1em;
  color: #000;
  display:none;
}

.objavi-subsection-heading {
  font-size: 20pt;
  text-align: center;
  line-height: 300px;
  font-weight: normal;
}


h1 {
  page-break-before: always;
  background: white;
  font-weight:normal !important;
}

/*h1.first-heading {
  page-break-before: avoid;
}*/


h2 {
 /* margin-bottom:-10pt; */
  font-weight:normal ! important;
  font-size:15pt;
}

/*try to avoid a page break between an h2 and a p XXX: doesn't work */
h2 + p {
  page-break-before: avoid;
}

h2 + img {
  page-break-before: avoid;
}

h2 + table {
  page-break-before: avoid;
}

h2 + ul {
  page-break-before: avoid;
}


h2 + ol {
  page-break-before: avoid;
}

table {
  float: none;
}

h1.frontpage{
  page-break-after:always;
  margin-top:70%;
  font-size: 20pt;
  text-align: center;
  page-break-before: avoid;
  font-weight: normal;
}

div.copyright{
  padding: 1em;
}
/* TOC ******************************/
table {
  float: none;
}

table.toc {
  font-size: 1.1em;
  width: 95%;
}

table.toc td{
  vertical-align:top
  padding-left: 0.5em;
}

td.chapter {
  padding: 0 0.5em;
  text-align: right;
}

table.toc td.pagenumber {
  text-align: right;
  vertical-align:bottom;
}

td.section {
  padding-top: 1.1em;
  font-weight: bold;
}
/* End TOC **************************/


p, li {
  page-break-inside: avoid;
}

pre, code, tt {
  font-family: "Inconsolata", "Courier New", monospace;
  /*font-size: 0.8em;*/
}

pre {
  overflow: hidden;
  white-space: pre-wrap;
}


h1, h2, h3, h4, h5, h6{
  page-break-after: avoid;
  page-break-inside: avoid;
}


.page-break{
  page-break-before: always;
  height: 7em;
  display: block;
}


.glossary hr{
  display: none;
}

/* page number styles -- these are the defaults, and will persist
unless explicitly overridden.*/

#right-footer {
  text-align: right;
}

#left-footer {
  text-align: left;
}

/* page number examples: */
/*
#right-footer .page:before{
  content: " FLOSS Manuals ";
  font-size: 85%;
}

#left-footer .page:after{
  content: " FLOSS Manuals ";
  font-size: 85%;
}

.page-footer {
  color: red;
}
*/

a {
  word-wrap: break-word;
}

.objavi-no-page-break {
  page-break-inside: avoid;
}

/*To force a blank page it is sometimes necessary to add unseen
 content.  Display:none and visibility: hidden don't work -- the
 renderer realises that they're not there and skips the page.  So we
 add a tiny bit of text beyond the margin of the page.
*/
.unseen{
  z-index: -66;
  margin-left: -1000pt;
}

@adam [send a reply]
3 years, 5 months ago
@ahofmann looks good...can you send to me as svg?
@adam [send a reply]
3 years, 5 months ago
@ahofmann the email probably came through but have been crazy busy! will check now
@adam [send a reply]
3 years, 5 months ago
@EdCable thats cool :) hope it all works well for you! let me know if i can help - meesage me and also use the help hashtag
@adam [send a reply]
3 years, 5 months ago
@MifosUser good to see you hear Ed :)
@adam [send a reply]
3 years, 5 months ago
@ahof yo alex...im sloqing up as im getting things done for holidays etc... hows it going with the cover image?
@adam [send a reply]
3 years, 5 months ago
@nicestep dont for get to announce the release of the book to the archive:)
@adam [send a reply]
3 years, 5 months ago
sf-micz cool huh?
@adam [send a reply]
3 years, 5 months ago
sf-micz cool huh?
@adam [send a reply]
3 years, 5 months ago
!mozilla does thunderbird need an update for the new ubuntu unity?
@adam [send a reply]
3 years, 5 months ago
@youlearnmusicprod welcome to FLOSS Manuals Mangal :)
@adam [send a reply]
3 years, 5 months ago
#announce
Snippet:

New FM Features!

So...Aco, Tuukkah and I have been hard at work putting together some new features for booki. FM is the debut of some exciting stuff...big thanks and hurrah goes to Aco and Tuukkah for all the time they spent working on these - planning, implementing, testing. I think these changes represent a big step forward for Booki and thanks from all of 'us' is due to them both.

We also need to stretch out our thanks to that rather fantastic org that has supported FM alot - Internews France. They got behind this dev and supported it by including FM in a grant. Many many thanks for this - they had their own reasons for doing this and I am sure they were also generously inclined to 'just' help us improve booki. Big cheers especially to Laurent (a huge supporter of Fm from the early days) and Sandra and Thomas.

ok...so. What are the changes? well they are numerous. So, first of all...there are now Admin roles for manuals. This is managed in the 'settings' tab in any manual. You will only see this settings tab if you are already an admin for that book. You become an admin by creating a new manual or via the settings tab (you need to ask the admin). It is possible to make others admins for the manuals. Ad admin gets some special abilities. You change attribution information, define language and text direction (important for sending to objavi), *manage chapter statuses* (more on this below), and define who can edit the manual (intended to be used only if spam is an issue).

We will also add to this list of admin abilities the ability to push content to www.flossmanuals.net. That means you dont need two accounts - one on the publisher and one on booki - you can publish content of www.flossmanuals.net directly (I hope to have this up in the next days).

The manage status messages is probably the control that will be most used in the settings tab. On each chapter you can set a status for that chapter. You can see on the right of a chapter on the TOC (Table of Contents) that there is a status. If you click on this you see a pop up and can change the status for that chapter from a selected list (to be proofed, to be published etc). Until now the status possibilities were universal but now they can be defined per manual via the settings tab. This is very very cool and Aco did a really great job of making this work in a way that is straightforward and easy to use. Very very rockn.

I am actually very excited as I am writing all this...:))) I think all this is a huge step forward for fm and booki. Ok..onto more features..Aco also made a really nice diff feature. You can now get side by side highlighted diffs from the history tab.

Revision viewing -if you choose 'view' for a chapter in the ToC you get a dropdown with all the revisions for that chapter. You can simply choose them and browse back and forward with the drop down if you want to see quickly how the chapter has advanced.

The same view can be accessed by the 'view chapter' button on the editing window - the window where you actually edit a chapter. This view can be floated and moved anywhere so you can see the original text of the chapter as you change it. This is *very* useful for translators of course (this is actually why we built it - so translators can see the source as they translate).

In addition to all this Aco built a very nice info interface for all manuals. Each manual now can be viewed in three ways :
_edit (note: changed from /edit/) - edit interface
_info - gives you information about the manual
_draft - draft view

eg:
http://booki.flossmanuals.net/ardour/_edit/
http://booki.flossmanuals.net/ardour/_info/
http://booki.flossmanuals.net/ardour/_draft

The info page has info on the book including recent activity etc including:
* 'owner' (we will change this as there is no 'owner' - creator might be a better word but suggestions welcome)
* what group it belongs to
* when it was created
* recent activity
* who has worked on it
* who is working on it now
* link to rss to track changes

I have not yet linked this page to the fm interface - need to think where it goes but I will do today or tomorrow - you can get to it directly via any book url ending with _info

Eventually we want to add other info to the _info but and ideas are very welcome.

So thanks thanks thanks to Aco for all of this and for managing the upgrade and merging etc.

Ok...next up and equally exciting. Fm now has micromessaging services. Tuukkah (who we were introduced to via FM finland) has done an outstanding job building in messaging services. When you log in you will see a 'post a message' text appear at the top right of the content box. This persists no matter where you are on the site. Ifyou click on this you get a pop up and you can send messages from it. Messages have the same syntax as status.net (which in turn follows twitter) -
@username - direct message to user
!groupname - message to group
#hashtag - create your own hashtags
βbookname - message book

You can also follow any user/hash/book and if you *join* a group you are then auto following the groups tag

That is not all - the message box allows you to send images ('add option attachment') and it *excitingly* it allows you to include a content snippet through a WYSIWYG editor in the message dialog. The snippet feature is built in so you can send anyone in the fm booki universe a snippet to translate/check/proof read etc. The same is true for the image attchments (you can also pass odt files/pdf etc with this).

thats not all - you can access this dialog from the editor - if you are editing a chapter there is a little button in the editor that pops open the message dialog with the chapter included in the snippet box already. This will shortly include only the highlighted area if there is something highlighted...

Also, messages are sent via email to notify you if there is a message. Youcan control this from the 'my settings' page. The syntax is obscure but in the 'notification filter' you can put (separated by space):
@* - block emails for direct messages to you
#* - block messages from hashtags you are following
!* - block group messages from groups you belong to
~* - block messages form people you are following
ℬ* - block messages from boosk you are following

by default you only get emails from direct messages

You can see all your messages from your profile page.


ok...thats all for now. there is a  bit more but digest this. I am really excited by all of this. The tools Aco and Tuukkah have built aid the working process and the possibilities for collaboration. I would *love* for us to discuss this further on the list or at #talk - both in general and specifics. How can we best use these new tools? How can they be improved? also, all bug reports either to http://booki-dev.flossmanuals.net  or to the list AND http://booki-dev.flossmanuals.net  (please dont *only* send them to the list unless you are trying to work out if it is really a bug)


Many thanks again to Internews, especially the long time allie Laurent, and also of course to Aco and Tuukkah

@adam [send a reply]
3 years, 5 months ago
@sachin hey - did u work out all hte editing issues ok?
@adam [send a reply]
3 years, 5 months ago
@JohnCurwood hey can you test more and file the findings you have in trac?
@adam [send a reply]
3 years, 5 months ago
messages are case sensitive #talk
@adam [send a reply]
3 years, 5 months ago
messages are case sensitive #talk
@adam [send a reply]
3 years, 5 months ago
#Talk if you see this on the frontpage then no
@helen [send a reply]
3 years, 5 months ago
#talk is it case sensitive?
@helen [send a reply]
3 years, 5 months ago
#Talk great work :)
@adam [send a reply]
3 years, 5 months ago
@nachoel01 welcome juan :)
@adam [send a reply]
3 years, 5 months ago
@t-kita welcome kita :)
@adam [send a reply]
3 years, 5 months ago
the new messaging system for FLOSS Manuals is now in place. It looks like a short messaging system but there is no character limit. So use for what ever you like. You can use hashtags, groups syntax, and even message books. Direct messages to other people is also supported using the usernames. #announce
@adam [send a reply]
3 years, 5 months ago
#announce flossmanuals messaging in place
@adam [send a reply]
3 years, 5 months ago
#announce flossmanuals messaging in place
@helen [send a reply]
3 years, 5 months ago
so it does! cool :)
@adam [send a reply]
3 years, 5 months ago
@helen it goes to your profile page :) http://booki.flossmanuals.net/accounts/helen/
Snippet:
http://booki.flossmanuals.net/accounts/helen/
@helen [send a reply]
3 years, 5 months ago
hello testing posting a message from the FM interface ... where does it go?

Following tags:

Stalking: @adam

Stalkers: @adam @makowiecki

Books

Groups