Interview: Adam Hyde, FLOSS Manuals (Netsquared)
[and Hyde's experience with it] has been documented somewhat extensively online, and I was fortunate to get to ask him a handful of questions about what he's learned along the way. He has been extremely generous in sharing with us such insightful, in-depth responses.
For more information on Hyde and FLOSS Manuals:
- FLOSS Manuals on Wikipedia
- FLOSS Manuals sprints to build quality free documentation at Linux.com
- The FLOSS Manuals bookstore
- The FLOSS Manuals story on slideshare
- Anne Gentle writes about FLOSS Manuals "booksprints" [where a bunch of folks get together for a few days and bang out a killer manual] for on justwriteclick
I'm involved with FLOSS Manuals for three reasons : to remedy the deficit of good free documentation about free software, to be involved in fostering an emerging community, and to develop innovative publishing processes.
Free Software became important to me when I saw how closed formats and proprietary software stunted creativity. I was a digital artist for a long time and the possibility to work with software as a medium was very interesting. You can do this with free software of course - bend the software out of shape, break it, re-purpose it, but with proprietary software you first have to hire a lawyer. Not many artists can afford that.Does access to Free Software make the world a better place?
Free Software is making the software world better because the proprietary model produces rancid software. Vendors try every trick in the book to trap you in their little stagnant world. When its in the best interests of the vendor to extend the software in meaningless ways so that you need to buy the new version, or change file formats so you have to buy a new version, or to get you so hooked on their way of working that you can't use anything else, then you know its not software they are building - its a trap. The only trap Free Software can try is to make you want to use it - because its good software - and the good news is that the more people use Free Software, the better it gets.
Free Software is making the real world a better place because you can afford to use it Free as in Libre does necessarily lead to Free as in Gratis and sometimes Free as in Gratis does count, especially if you have no money. Also, Free Software doesn't try and turn you into a criminal for wanting to use it. If you use proprietary software without a license you are criminalised. Nasty. Especially nasty if you are a student and your university has prescribed the software but you can't afford it.
I think one of the ways Free Software is about to improve the world faster than closed software is in interface translation. Free Software can migrate across languages relatively easily - if you have the source code, you can translate the interface. With closed software is a much harder proposition. So inevitably I believe that Free Software will get wider distribution worldwide than its rancid cousin.
Those are some of my favorite reasons for loving Free Software.What are some of the troubles, if any, you run into while heading FLOSS?
The oddest trouble is occasionally I find some members of free software projects are protective of their position as 'the authors' of 'the official' documentation. Usually there is one or maybe two individuals that are writing the 'official' docs and they don't want anyone else getting a slice of the action.
This has happened several times, where I have approached projects and I've hit this kind of wall. Its easy to see how these situations arise - its because that's the established way the Free Software and publishing worlds have worked together. Write the free software, then write the closed proprietary documentation for a buck and clock up some status. So until the 'official' documentation is written the intending authors tend to scare anyone off that might be sniffing around.
But this is ridiculous in so many ways, not just because there is a dearth of good documentation about free software. Who heard of a free software project that has too much good documentation? I haven't heard of any. So the tragedy of this kind of attitude is that it hinders 'third party' documentation from being developed and consequently slows the uptake and use of the software which the authors are trying to promote.
However, there are other issues here as well. There are very good reasons why members of the development community should not do the documentation. Developers, for example, often see how the software 'should' work not how it actually does work. Sometimes they also see usability issues as something that has to be fixed in the user. Neither of these approaches fosters good documentation. So 'third party' documentation should be encouraged at all times.
Also, I think the investment in the traditional publishing model does not adhere to the principles of freedom that the licenses for their software endorse. Authors that work with traditional publishers produce proprietary documentation, and closed documentation about open source software is an ideological paradox. Why should the documentation be closed source? It just doesn't make sense. The software is open but the information on how to use it is closed? What part of that makes sense? However this is the way the publishing industry works. Some publishers will tell you that if an author wants the documentation to be open then they will publish it as a Creative Commons license. This is not investing in the ideology of free documentation, its simply marketing. All information about how to use free software should by default be free as in libre.
Lastly, the one author, one publisher, one distributor, all rights reserved model is not working. Publishers are not as important as they used to be... this can be seen in the fall of book sales. There are many reasons for this, not least because readers are increasingly reading from screens and publishers are struggling to monetarise that, and recently of course there is a lack of disposable income. As a consequence there is not so much money or status left to go around which stems from the traditional publishing world. Meanwhile the world of free documentation is developing new processes to replace the old ones. These models are emerging, which is why its exciting to be involved in the ground floor of this sector, however some models clearly make sense already and thats largely because they closely follow the models free software itself has shaped. If you want status, then you can make a name for yourself by leading a team to write the docs ala free software itself, if you want money then build the reputation for the documentation team and contract out your knowledge (eg. extend the docs on contract ala free software).
So if you are figuring on hitting the jackpot and make a name for yourself through the traditional channels, and you are dampening efforts by others to write docs for the same project, do a quick ideological and reality check first. Then contribute to, and encourage as many people as possible to contribute to, free documentation about your project.Is finding funding for creating open source solutions a difficulty? Do entities, organizations and people ever perceive giving to open source solutions an "anti-market" way to invest their money?
There may be people that support free software because they see it as 'anti-market'. If you ask me, Free Software is not-anti market, its advocating another kind of market - one where services make a lot of the revenue instead of license fees. So I think anyone that contributes to free software because they see it as anti-market doesn't understand their enemy.
Personally, I prefer to work with people that support Free Software because it enables the freedom for people to do the things they want to do - whether it be the pursuit of creative, ideological, or financial satisfaction.What effect has the state of the global economy had on FLOSS?
It's worrying for everyone of course. I think we have to source more revenue as we have been operating quite ad-hoc until now. Luckily our overheads are currently low - we don't have any fulltime employees. However we want to grow and currently we have no strategy for funding. So we will have to remedy this.With regard to FLOSS, where do you see yourself in a year? In two years? Is this going to be a long-term involvement for you, or are you interested in handing it over at some point?
At the moment we are experimenting alot with documentation - documentation is not just a 'how to' but it plays many roles, as text books, as proxy marketing material for software, as a process for developing communities of expertise, as self help guides, as a ladder to the next level of expertise in a specific subject, as sales material for developers, as support material for developers, as support material for workshops... there are a lot of corners documentation feeds into and we are trying out many of them.
As for the things that we focus on expressly, this largely comes down to following the energy of the community. If I am doing my job then I have my ear to the ground and can hear if something is creating a buzz within FLOSS Manuals. Then its a matter of opening up those channels. Thats part of effective community building. So, given that, I expect our role in developing educational materials to play a bigger part in the next year as there seems to be a lot of energy in FLOSS Manuals towards this.
We strongly advocate against the teaching of proprietary software for many reasons - not the least being that education facilities become proxy marketing machines for closed software companies while simultaneously criminalizing the students that use pirated software because they can't afford the licenses. So we will work more to translate current textbooks that use proprietary software in the text and examples into textbooks that use Free Software. We call this process "FLOSSify" and we had a very successful event recently in New York translating the wonderful "Digital Foundations" design text book into FLOSS
I found through that process that people are inspired by the idea of liberating textbooks and education from the grips of closed software. So I think there is a lot of energy there for this kind of event and we will pursue it further.
As for my own future [pauses] I'd like to find a more stable way to pay the rent. I hope that maybe FM can provide that but at the very least I am head honcho for now and I intend to be in that role for at least the next two years. Lets see what happens after that.Again, aside from the obvious (of course, your book-writing model and other various open source content exercises and gatherings), what emerging examples of team content creation/building/editing are you seeing? Do you see these techniques and approaches applying to citizen governance? Running nonprofits/businesses? Other non-tech sectors?
Book Sprints are good for documenting any part an organizations operations. for example, if you want to refine your internal processes then having a Book Sprint documenting those processes is a great way to get everyone aligned while identifying inconsistencies and inefficiencies and creating useful a resource for new comers. Its a great team building process. The great thing is that once you have the material each year you can build upon it and improve it.
Our experiments with community book writing have a wide area of application. For example, I would love to be involved in local communities documenting ways to save money, or how to use local resources and services efficiently.What did FLOSS achieve in the last quarter of last year? What will you have achieved in the first quarter of this year? How are things going? What impact does the global economic downturn have on your work?
In the last quarter of 2008 we had two Book Sprints - OLPC/Sugar and How to Bypass Internet Censorship. These were both very successful. The OLPC/Sugar sprint produced about 700 pages of documentation in 5 days and the Bypassing Censorship Book Sprint produced an extremely well written 200 page manual in 5 days.The OLPC/Sugar manuals are now shipped on every OLPC laptop (XO) going out the door. I'm very proud of that for many reasons. Anne Gentle, David Farning, Seth Woodward, and Walter Bender did a lot to make that happen. The XO manual is a remix of several manuals so it shows the power of our remix functionality in FLOSS Manuals. We also completed out CSS-driven book production which drives down the time it takes to create book formatted pdf (for print on demand) from 3 days (using Scribus) to about 3 minutes.
In the last quarter of 2008 we also saw visits to our site increase dramatically so we are now in the process of migrating to a more robust server set up (sponsored by osuosl.org).
In the first quarter of 2009 we have been very busy. We have just had the FLOSSify event in New York (Eyebeam), translating the Digital Foundations text book into free software. In this quarter we also have a Book Sprint about Firefox (with Chris Hofmann) at the Doctrain Technical Writers conference, we have a sprint to create an introduction to the command line for the Free Software Foundation, and we have the first FLOSS Manuals summit with 15 people coming from around the world to talk about all things FLOSS Manuals. In the first quarter we have also started development of our new platform ('booki') and possibly a PureData sprint in New York with Hans Christoph-Steiner and Derek Holzer. We are also researching bi-directional text in our PDF creation processes for print on demand, and we'll change the design for the current site. So this quarter is heatin