FAQ

Revision 8 as of 2010-01-05 01:49:46

Clear message

Frequently Asked Questions

How can I contribute?

What's the point in this Project, isn't there already enough documentation around?

What infrastructure have you got in place for this Project?

  • We use a combination of LaTeX, bzr and Launchpad to handle the core project files, as well as bug tracking, blueprints and answers.

Where is the Translation support?

When will the first release be available?

  • The alpha release is scheduled to be ready on the 10th February, 2010.

Who is the Project Driver?

  • Benjamin Humphrey started this Project at the end of 2009. He has written several chapters as well as most of the wiki. He also maintains the Launchpad blueprints, bugs and branches, mailing list and IRC room, and organizes meetings. You are welcome to contact him directly, although it is best if you email the mailing list instead and address the email to Benjamin - unless it is confidential of course.

How can I contact someone in the Project?

  • There are multiple ways to contact us. The easiest is to email the mailing list, or join our IRC channel. All of these details can be found on the home page.

Where is the manual style defined?

  • Currently, the manual style is not defined in text, per se. It is available as a visual guide on the Project page downloads section in PDF format, for reference only. As for the writing style, we do not have an explicit guide to follow - the best way to see how the manual is written is just to look at the completed chapters and use them as an example as to how you should write your chapter.

Who are your target audience, and for what reason do you expect them to read this manual? What is their level of technical ability?

  • The target audience is complete newcomers to both Ubuntu and Linux. People who have heard about it, and are interested in switching from Windows/Mac. Therefore the manual will give them a brief background of Linux and Ubuntu, and explain that it is not comparable to Windows or Mac - It's completely different. I know that when I started using Ubuntu, I knew nothing about man pages, or the Ubuntu Community Docs. Finding a specific Doc page was difficult, and in all honesty, many of the doc pages are written in a style that presumes you already know your way around. The system documentation, while easier to understand, is not as in-depth as it should be. This manual/book will be easy to understand, have everything in one place so its easy to find, it will be well advertised to new Ubuntu users and it will have everything in correct order, so that users learn how to do one thing before doing the next which relies on the former. Their level of technical ability ranges from complete computer newbie to someone who is familiar with Windows but never used Linux.

Where is the writing style defined?

  • It's not defined at the moment, this is on the agenda for the next meeting in early January.

Who will be responsible for maintaining the document, and what sort of infrastructure will they be using to do that (i.e. translations, bug reports, version control)?

  • The Ubuntu Manual Team is in charge of maintaining the document, headed by Benjamin Humphrey. The infrastructure will be mainly based around Launchpad, IRC, Ubuntu Wiki and docbook.

How is the document licensed?

  • At the moment, it is GPL v3, but this is also on the agenda for the next meeting.

Why did you choose the topics that you did?

  • The topics are based off several other Ubuntu manuals, the Community Docs, my own experience with Ubuntu, this thread and my blog post.

Did you carry out any research on the needs of your target audience? e.g. interviews, observation sessions, questionnaires.

  • Yes, see the above question.