We've compiled this list of Frequently Asked Questions (FAQ) with answers from FLOSS Manuals community members. These questions surrounding FLOSS Manuals beginnings, history, projects, and concepts offer you more information about the community and toolset that is FLOSS Manuals.
FLOSS Manuals is a collection of manuals about free and open source software together with the tools used to create them and the community that uses those tools. They include authors, editors, artists, software developers, activists, and many others. There are manuals that explain how to install and use a range of free and open source softwares, about how to do things (like design) with open source software, and manuals about free culture services that use or support free software and formats.
Anyone can contribute to a manual – to fix a spelling mistake, to add a more detailed explanation, to write a new chapter, or to start a whole new manual on a topic.
You can read and use the manuals in a number of different ways. They are available online in separately indexed chapters, and you can use the website as a reference base in this way. You can also view, download, or print each manual as a PDF file. It is also possible to ‘remix’ manuals to create a version that only includes specific aspects of a particular manual, or that combines chapters from two or more manuals in a single document. These can be downloaded and printed, added to websites, and used for any purpose. You can also print a manual, or an individually ‘remixed’ manual, as a book via the print-to-order service of Lulu.com.
F. L. O. S. S. stands for Free Libre Open Source Software. Basically, this means software that makes its code available for anyone to use, change, and redistribute under the same terms. If you're still confused, you can read more below.
Open Source emphasizes availability of source code to software users. This means not only that the source code is available at no cost and with little difficulty, but that users can modify the source code and distribute the results under the same conditions. Bruce Perens wrote the original Open Source definition for Debian.
Free Software emphasizes the freedom to modify and reuse software, which of course also requires that source code be readily available. Richard M. Stallman initiated the definition of Free Software as part of the creation of the Free Software Foundation and its GNU project (GNU's Not Unix) to create a completely Free Unix-compatible operating system and set of software tools. GNU software together with the Linux kernel, plus contributions from many other sources, constitute the GNU/Linux Operating System, commonly known as Linux.
So in practice the differences in meaning between the two phrases are not great, but they lead to some differences in attitude, terminology, and use of specific license terms. One reason for the difference in terminology is that "Free" is ambiguous in English. FSF has to explain that it means, "Free as in Free Speech, not as in Free Beer." To counter this, the unambiguous French term "Libre" can be added in, resulting in FLOSS, or Free (Libre) Open Source Software.
FSF maintains a page explaining the various Free and Non-FREE licenses. The BSD (Berkeley Software Distribution) license, for example, allows users to modify source code and put the changes under a restrictive commercial copyright, as Apple has done in Mac OS/X. Since most BSD users put their changes under BSD, it can be considered somewhat, but not entirely, Free.
In addition to these software licenses, there are several licenses for documentation and other content, most notably the GFDL (GNU Free Documentation License) and the various Creative Commons licenses. FLOSS Manuals uses the Free Software GPL for all of its work.
For details of definitions and available licenses, see
Adam Hyde started FLOSS Manuals while a digital artist. Adam had made a living running workshops on free software all over the world and had accumulated a lot of support material in the form of workshop manuals. In 2005 this material was put into a wiki with the help of Aleksandar Erkalovic and Lotte Meijer did the design. In 2006 Lotte Meijer and Adam Hyde applied for and recieved funding from Digital Pioneers to extend FLOSS Manuals. Thus the development and design of FLOSS Manuals as it is now started in 2006. This is the same year the Foundation was registered. Several digital artists were commissioned to write manuals on Audacity, Gimp, Blender, and PureData.
The actual site wasn't ready until May 2007. The first unsolicited edit on the site was in July 2007. FLOSS Manuals was officially launched at a party at Montevideo Time Based Arts (Amsterdam) in October 2007.
In 2008 we created the Farsi version of FLOSS Manuals (http://fa.flossmanuals.net) and started our first Book Sprints.
Now there are over 40 manuals on free software, and 1200 registered contributors and a healthy and active mailing list. Burmese, French, Finnish and Spanish language communities are currently being established.
By using free/libre/open-source software, you have the right to use, change and share the software freely. FLOSS is also usually no-cost. You are not dependent on a big company to add features or fix problems; for FLOSS, these issues are handled by a community of software developers, which often
responds more quickly. If the FLOSS community doesn't address a problem that have with the software, you can hire a programmer to do it for you; this is almost never possible with proprietary software.
Similarly, when you use free/libre/open-source manuals, you have the right to use, modify and share the documentation freely. Manuals on the FLOSS Manuals site are no-cost to use online. For paper copies, we charge just for the paper and printing, and a little extra to support making more books. You can also take the online version as a PDF file and print it yourself. You can also edit the documents on the site, for example, if you find things are incorrect, out of date, or incomplete. (You can also change your own copy, but we appreciate if you help us make the manuals on the site better.)
Book Sprints are an innovative format based on Code Sprints but with the focus on producing documentation instead of code. A sprint brings together a group of writers, editors, and perhaps an artist and production specialist, to go from outline to published book in five days.
Writing a book in a week is an incredible and demanding feat. It was enabled by the FLOSS Manuals platform which has turned the corner from wiki to collaborative publishing platform. The platform enables fluent collaboration with local and remote writers, a low technical threshold and an automated print source generator that produces beautiful book formatted PDF. Upload this to a print on demand service and you have a fast moving process able to produce books at the same rate programmers change the software.
The website hosted at flossmanuals.net is built on a TWiki installation and uses extensions that are given back to the TWiki community. It is all free software. We are building a new platform to replace the existing system. The new platform is called 'booki'.
FLOSS Manuals is registered as a 'Stichting', a non profit foundation, in the Netherlands. There are no employees. Most admin tasks are undertaken by Adam Hyde.
FLOSS Manuals was started to remedy the deficit of good free documentation about how to use Free Software. The original idea (and this philosophy continues today) was to distribute the means to contribute to manuals, text books, teaching materials, etc by creating a very simple and easy to use interface for collaborating on the creation of comprehensive texts about Free Software.
Lots! and you can add more. Here are a few:
Any widely used and insufficiently documented FLOSS product
Getting Started with Free Software
Grannies' Guides
Audio production
Streaming audio
Video production
Streaming video
Web design
Web hosting
Database software
Knowledge bases
Mind mapping
Finding information
Wiki software
Scripting
Regular expressions
Search engines
Learning materials and lesson plans
Sampling (FLOSS + CC)
These questions discuss the content written and distributed on the FLOSS Manuals site.
Software manuals was our starting point, but it is not at all the whole story. We will consider any topic in which FLOSS is an essential element. This includes software products, applications of FLOSS, the reasons for using FLOSS, and the consequences of FLOSS.
The content in FLOSS Manuals comes from a growing community of writers. Originally most of the content was written by founder members. As it became clear what a great tool FM was different communities of users and writers started to adopt FM as their home for documentation. Software writers, the Transmission video network, Sugar Labs are some of those communities.
Book sprints where travel and food are provided are another great source of content [see question on book sprints].
And most importantly to keep the FLOSS Manuals community growing we need the content to come from you. If you see something in FM that is out of date then you can log in and update it. If you see a chapter you would like to add then make a start on it. You can use the mailing list to get feedback and support.
Absolutely. Please do. The only requirements are that you use it under GPL and maintain the original copyright information. The specifics about GPL are list here : http://www.gnu.org/licenses/licenses.html. But, really, we are more concerned with getting the material out there then anything else. If you want to do something else with the material (for example, using it under a different license), you can let us know, or track down the original author yourself.
"Remix" is borrowed from the practice of mixing new music from existing source material, with or without the addition of new material. In FLOSS Manuals, Remix at http://en.flossmanuals.net/remix is a tool that allows you to drag and drop chapters from any book in the FLOSS Manuals "Read" area into a new deliverable. The Remix tool enables you to create a new PDF or a new set of HTML files from the recombined set of chapters. Remixing a chapter from here and a page from there is a standard practice in education, within the limits of Fair Use. Now you can go all out.
The basic outputs you can generate from the FLOSS Manuals tool are PDF, ODT and HTML. The HTML is published on our Web site, and is available for download in Windows and Unix archive formats. Offered in a beta format is an AJAX output that you can embed into a website as an iFrame per chapter that basically queries the FLOSS Manuals content repository and serves the content to your web pages.
This is largely a legacy of the people involved. The original manuals were written by Adam Hyde from his workshops on streaming media. This is why a lot of the manuals are about streaming audio and video. After that initial period more manuals have been added by people with their own interest. Depending on how active they are that topic becomes more populated. For example, FLOSS Manuals has a lot of material about Video Distribution because of the active role of Mick Fuzz in this area, there is a lot of material on OLPC/Sugar because of Anne Gentle's hard work.
So, if you want to see a particular software become more present in FLOSS Manuals it's up to you!
There can be at several reasons why a book on a particular topic or software
doesn't appear on the FLOSS Manuals site:
Maybe, check the FLOSS Manuals site of your language.
Join the FLOSS Manuals mailing list and request a new manual be created.
http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
Join the FLOSS Manuals mailing list and request a new manual translation be created.
http://lists.flossmanuals.net/listinfo.cgi/discuss-flossmanuals.net
Sometimes the documentation written by and for software developers isn't the best for end users. We create docs that are much more user friendly for people approaching the software for the first time. If there is already a manual for a given subject we still encourage anyone that wants to write another one to do it - after all, there is never going to be 'too much' information on free software.
We have the most agile book creation process in the world, and we have an outstanding community of contributors who understand the needs of our target audiences and can turn nerdspeak into language that your grandmother would recognize.
We have many manuals that are excellent material for course work. You can consider including them in your required or recommended reading. If you would like to go further then ask students to contribute to the manuals as part of their course work.
FLOSS Manuals has two examples of our content being used for HTML output, besides the HTML versions of the books published here. One is the online Help Activity shipped with the Sugar operating system. The HTML is exported through the Remix tool and then checked in with the source code of the project. The other example is the Message in a Box tactical technology page at http://miab.tacticaltech.org/welcome that helps people use multimedia, online or offline tools to advance their cause.
Click the Buy Now! link for any FLOSS Manuals publication to go to Lulu.com and order a copy printed and shipped.
We are working on distribution through Amazon. However its slow.
GPL
Here are some of the ways that you can help:
Anybody can contribute to a manual. To get write access to the "write" area of the site, all you need to do is to create a login ID on flossmanuals.net. By creating a login ID, you agree to release what you create here under the GNU General Public License. Your login and profile information is used to attribute copyright to you for what you write. We prefer that you use your real name, but you can use a pseudonym if you don't mind owning copyright under that pseudonym.
You can do a lot of things - PR, write code, reach out to other projects, start a new language community, raise money etc. The best thing is to join the list and ask how you can get involved.
Yes, this is our promise as a provider of books that can be freely altered and redistributed. In fact, we encourage people to improve our books, and to insert new material to meet local needs. You can edit a book on our site, or download the text and change it on your own site. If you take the text elsewhere, please just attribute our work to the authors and to FLOSS Manuals, and to tell readers how you changed the book.
For details, see the entry in this document about the license. You must use the same license when you redistribute our work and anything you add to it, so that others have the same rights we grant you.
Good question...no solid answer. Adam pays the rent by facilitating book sprints. FM overheads are covered by organisations that want us to help them write docs.
Yes, we encourage organizations dealing with free software and freedom in general to work with us to produce their documentation. You must contact our site to begin a book.
Among the organizations that are actively working with FLOSS Manuals to meet their documentation needs are Google, One Laptop Per Child, Sugar Labs, and the Mozilla Foundation.
Money made on book sales goes back to FLOSS Manuals to further their aims. If you have ideas for fundraising or donation campaigns based on book sales, we would love to help you with that concept.
The process of getting translation of a book/manual published on FLOSS manuals includes the following steps:
You can simply register on FLOSS Manuals's translation website, choose your desired manual/chapter and start translating it. Since the FLOSS manuals is committed to maintain the quality of its contents, your contribution will be reviewed by the maintainer of the manual, and be published onto the website after final approval.
No, manuals can be written in any language. We have used French language material extensively as sources for manuals, and we are organizing groups to write in several other languages. If you would like to start a group for another language, please contact us.
There has been error in communication with Booktype server. Not sure right now where is the problem.
You should refresh this page.