After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 117796 - Suggestion: FAQ should not be version or software specific
Suggestion: FAQ should not be version or software specific
Status: RESOLVED OBSOLETE
Product: gnome-user-docs
Classification: Core
Component: user-faq
2.2
Other Linux
: Normal normal
: ---
Assigned To: Telsa Gwynne
Alexander Kirillov
Depends on:
Blocks:
 
 
Reported: 2003-07-18 18:54 UTC by Jeff Waugh
Modified: 2011-06-08 21:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jeff Waugh 2003-07-18 18:54:50 UTC
Updating a central FAQ for every GNOME version is going to be silly, and
there are lots of general GNOME questions that people ask all the time
like, "Why have you removed all those options?" and "Does the Foundation
make decisions for the hackers?" and things like that.

Version-specific FAQs should be in the release notes published under each
start/*/ page.
Comment 1 Telsa Gwynne 2003-07-20 11:14:28 UTC
Agreed. I was going to turn it into general stuff and release-specific
stuff.  The plan was to have sections within the faq which were
release-specific, but separate version-specific ones sounds more
manageable.
Comment 2 Jeff Waugh 2003-07-20 11:31:20 UTC
Cool. You know, we could do the same thing with the documents that are
on the learn page: <http://www.gnome.org/learn/>.

Seems like the start/VERSION/ pages would be much better as
"everything you ever wanted to gnow (ha ha) about GNOME <version>", so
we could shift the user guide, version faqs, admin guide, release
notes, etc., etc. to there. Then we can just interlink everything
under start/

What do you think? I reckon it will be much better exposure for the
docs. Not enough people have seen how cool they are! :-)
Comment 3 Telsa Gwynne 2003-07-20 12:16:08 UTC
Seems a good way. I need to look at the pages, I suppose :) 

What would you think is "release-specific"? The more small docs
which can be individually finished/maintained/updated/removed,
the better, I think. So knowing general category ideas would be
a big help. I have some ideas, but I have probably missed stuff.
I don't use the websites much...
Comment 4 Jeff Waugh 2003-07-20 12:19:45 UTC
just off the top of my head, to start with:

- release notes
- user guide (lots references to release notes probably)
- developer guide (basically links to docs and list of changes hackers
should be aware of)
- frequently asked questions (possibly inspired by "known issues" in
the release notes)
- admin guide (probably fairly static)