Christian Boltz wrote:
Hello,
I think http://en.opensuse.org/Bug_Reporting_FAQ should be splitted into several documents because - it handles several rarely related topics - other not-less related topics have separate pages already - it is too large
Current Content (just main headlines) is: 1. Bugzilla 2. YaST 3. Kernel Bugs 4. SUSE Linux Documentation 5. Beta Testing
I would suggest to create separate pages for: 2. YaST -> Bugs/YaST 3. Kernel Bugs -> Bugs/Kernel 4. SUSE Linux Documentation -> Bugs/Documentation (and merge it with the last section of Report_a_Bug)
Why I ask here before just doing it? Many bug reporters are pointed to the Bug Reporting FAQ - therefore I'd like to know if everybody (especially the Bugzilla Screening Team) likes my idea...
Related question: What is a better page name - Bugs/YaST or Bugs:YaST? - Advantage of Bugs/YaST: This scheme is used by several other pages (Meetings/*, Build_Service/*, Documentation/*, HCL/*, ...) - and you get a back link to "Bugs" for free. - Advantage of Bugs:YaST: Most other pages about bug reporting use this scheme (but could be renamed of course).
If nobody objects, I will split the page in some days, using the Bugs/* name scheme which is more common in the openSUSE wiki.
Regards,
Christian Boltz
Hi Christian, Today I was trying to figure out what would be the best logical structure (wording, naming) of openSUSE wiki so that people find it easy to remember and find articles. Topic Bugs is similar to FAQ, HOWTO (HowTo), Installation, Update, etc. It has it's global meaning for SUSE Linux and local for versions and applications. We can go with SUSE_Linux Bugs 10.0 system kernel driver1 xorg driver1 desktop app1 10.1 system kernel driver1 xorg driver1 desktop app1 or SUSE_Linux 10.0 system kernel driver1 bugs xorg driver1 bugs desktop app1 bugs 10.1 system kernel driver1 bugs xorg driver1 bugs desktop app1 bugs or something in between. The one of ideas is to structure everything similar to directory structure on FTP servers. Once you learn one the other is the same or easy to browse. What to use as glue? Simple / / / might be good, but than automatic categorizing will list all in SUSE_Linux/ / / / and categories will be useless. One of variants is to build groups as Basic_Topic/ / / and locate index that will point to the articles in top node Basic_Topic. The other way around, back to the top node, is already for free :-) Manually created and maintained indexes are a lot of work for editors, but it is easier to educate few editors how to build and maintain indexes than all writers. -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-wiki-unsubscribe@opensuse.org For additional commands, e-mail: opensuse-wiki-help@opensuse.org