On Thu, 2005-03-03 at 02:22 +0000, Brynjar Har�arson wrote: > Hey Matt, here are two links to information related to Debian for > desktop use that I know of. > > http://wiki.debian.net/?DebianDesktop > http://www.linuxquestions.org/questions/showthread.php?s=&threadid=224547 > > I would be really interested in working on a Debian Desktop Guide, > beside being able to do some writing I can also get free hosting under > foo.gothicmars.com if that's something that could be useful to get the > this going. > >
I have used the following links over the years: http://www.debian.org/doc/user-manuals but most importantly the... http://www.debian.org/doc/manuals/reference/reference.en.html http://d-i.alioth.debian.org/manual/en.i386/apa.html for the installer http://www.rage3d.com/content/articles/atilinuxhowto/ for my ATI Card And i just saw this but it could be incorporated as well. http://people.debian.org/~debacle/refcard/ I have mostly used the Debian Reference manual and Googled other stuff as needed. From looking at the documents currently available we could probably start now. Before we proceed we need to isolate exactly what we want to document. I picture this as an end user guide and not a system administration guide. The two really should be seperate things. However the lines will blur a bit as some changes for Desktop will require root access. For instance in your example the user needed to be part of the plugdev group. Changing this requires root access to edit the user profile. I would like to minimize the number fo things that will require root access. On a related note some find it preferable to direct people to use the command line for these things. I would also like to instruct people on how to use the GNOME and KDE configuration tools that are available. This allows less inclined people to work with the ideas before tackling the command line. As such for each recomendation in the document we need directions for command line, GNOME, and KDE methods where available. We also must include a list of requirements for each item so the user can communicate cleary their needs to an administrator if they have to. Additionally if recomendation A requires B and C to be done first we should direct the user to B and C as needed, and in the correct order. I don't know how many times the ordering of a how-to has ruined it usefullness. I would really like to avoid that. I am partial to the start from scratch type of directions. So I think the short installation How-To can be a real help there. From there we need to look at what goes into a default debian desktop installation and see what will need setup, and tweaking. Past that we can talk about common use cases and useful apps. How does all of that sound? -matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
