On Wed, 2010-09-29 at 17:34 -0400, Chuck Payne wrote: > On Wed, Sep 29, 2010 at 5:29 PM, Rémy Marquis <[email protected]> wrote: > > On Wed, Sep 29, 2010 at 8:27 PM, Javier Llorente <[email protected]> > > wrote: > >> Hello there, > >> > >> I was thinking that having an openSUSE Handbook (or handbuch ;) in pdf > >> format > >> ready to be downloaded, printed and even ready to be sent to a publishing > >> company is a good idea. > >> > >> So, here's my proposal: > >> > >> First, we would have to make a list of topics to be included and organise > >> them > >> in chapters, like the following draft: > >> > >> ****************************** > >> The openSUSE Handbook > >> ****************************** > >> Introduction > >> - What's the openSUSE project? > >> - What's openSUSE? > >> > >> Installing openSUSE > >> - Different types of install methods > >> - AutoYaST > >> > >> Installing applications > >> - Using 1-click > >> - Using YaST > >> - Using zypper > >> > >> Desktop environments > >> - An introduction to DEs (KDE, GNOME, XFCE, LXDE). > >> - Enabling proprietary drivers (ATI, NVIDIA) > >> - Multimedia > >> - Printing > >> - Games > >> > >> System administration > >> - Introduction to the command line > >> - Networking > >> - Security > >> - Storage > >> - Virtualization > >> - Keeping openSUSE up-to-date > >> - Upgrading openSUSE > >> > >> Servers > >> - Apache and lighttpd > >> - MySQL and PostgreSQL > >> - Postfix > >> - BIND > >> - Samba > >> - CUPS > >> etc > >> > >> Other openSUSE Technologies > >> - Build Service > >> - SUSE Studio > >> - KIWI > >> > >> Second, we would have to write about those topics not included in the wiki > >> and > >> review those already written. That way we would have more relevant bits in > >> both the wiki and handbook. Each topic doesn't have to be 100 page long ;-) > >> > >> And last but not least we would have to put all the pieces together and > >> make > >> it available in pdf. > >> > >> Drawbacks: > >> We would need to update some of its contents for each openSUSE release. > >> It needs more than two people to make it happen ;-) > >> > >> On the other hand, I think that the handbook would make openSUSE more > >> "visible" and a bit more "ready to use." > >> > >> Comments and suggestions are welcome! :-) > > > > Hi, > > > > What do you intend to do differently from the official PDF doc? > > Maybe there is an opportunity to build something on the Lesson for > > Lizards foundation here? > > > > See http://en.opensuse.org/Portal:Documentation and > > http://developer.novell.com/wiki/index.php/Lessons_for_Lizards > > > > Regards, > > > > R. > > -- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > I think it would be great to do the how-to's, maybe some > tips-n-tricks. This would be helpful for all users. Maybe make it like > one of those Bible OS books that get publish. > > -- > ----------------------------------------- > Discover it! Enjoy it! Share it! openSUSE Linux. > ----------------------------------------- > openSUSE -- en.opensuse.org/User:Terrorpup > openSUSE Ambassador/openSUSE Member > skype,twiiter,identica,friendfeed -- terrorpup > freenode(irc) --terrorpup/lupinstein > > Have you tried SUSE Studio? Need to create a Live CD, an app you want > to package and distribute , or create your own linux distro. Give SUSE > Studio a try. www.susestudio.com.
I'd like to recommend that we also consider making this available on ebooks such as Kindle or Nook. I recently got my Kindle and I'm really enjoying the ability to quickly get my books and have it ready at all times. It will also make for turning the Kindle into a nice reference tool for users that can easily carry around the Kindle than a book and even make their own notations into the book when they're going around giving support, etc. We can offer it as a free book or charge a small publishing fee through Amazon and funnel a few bucks into the future openSUSE Foundation. The potential opportunities abound here! Bryen -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
