Hi, as pointed out on https://bugs.gentoo.org/show_bug.cgi?id=58651#c29 and again on https://bugs.gentoo.org/show_bug.cgi?id=115791#c2, current list of components for docs-user is a bit outdated. What about some cleanup? So, I'd propose the following Products instead of docs-user and docs-developer: a) Documentation (www.gentoo.org/doc/, NOT manapages etc) a.1) Handbook (w.g.o/doc/en/handbook/) a.2) Articles (w.g.o/doc/en/articles/) a.3) Other guides (w.g.o/doc/en/) a.4) Translated documentation a.5) Submit new b) Other documentation b.1) Project specific docs (w.g.o/proj/en/) b.2) Manpages b.3) Other Let's make a decision and forward it to jforman.
fixing summary, sorry :-(.
Small proposition: Let's add "development documentation" and let's make all the components automatically fill in "assigned to" field. For our docs and translations it would be docs-team@gentoo.org, for dev docs it would go to devrel@gentoo.org, for man pages to portage team, and so on. Project documentation could go to bug-wranglers, and they would decide to which project assign the bug. What do you think?
(In reply to comment #2) > Small proposition: > Let's add "development documentation" What for? > and let's make all the components automatically fill in "assigned to" field. Sure, but this is the case already. > for man pages to portage team You probably meant bug-wranglers as manpages are usually provided by the respective packages or manpages-$LANG or something... > Project documentation could go to bug-wranglers, and they would decide to which project assign the bug. > What do you think? Yep.
(In reply to comment #3) > > Let's add "development documentation" > What for? To have all the bugs in developer handbook by default assigned to devrel, not to us? > > for man pages to portage team > > You probably meant bug-wranglers as manpages are usually provided by the > respective packages or manpages-$LANG or something... I meant gentoo-related man pages like manuals for gentoolkit programs, portage, emerge and so on. Other manuals are made by TLDP or program authors, so mistakes in them should probably go upstream.
(In reply to comment #4) > (In reply to comment #3) > > > Let's add "development documentation" > > What for? > > To have all the bugs in developer handbook by default assigned to devrel, not > to us? Well, Developer's Handbook is under /proj/en/devrel, so it will probably go throught the bug-wranglers as any other project-specific stuff. Doesn't really matter, IMHO.
Ok, so as we have agreed on the list and there are no signs of resistance, you can CC jforman probably... BTW: (question of "yeah, keep dreaming" type) Maybe we could somehow force users to submit a link to the guide they are referring to in bug reports and, using path, assign it to the appropriate group of people?
Okay, Jeff, I think we're done. The list in comment 0 is valid. Is it possible to fix that? What about existing bugreports? Could they be converted automagically?
Sorry guys, didnt see this one pop up in my email queue. Below are my thoughts: (In reply to comment #0) > Hi, as pointed out on https://bugs.gentoo.org/show_bug.cgi?id=58651#c29 and > again on https://bugs.gentoo.org/show_bug.cgi?id=115791#c2, current list of > components for docs-user is a bit outdated. What about some cleanup? > > So, I'd propose the following Products instead of docs-user and docs-developer: > > a) Documentation (www.gentoo.org/doc/, NOT manapages etc) > a.1) Handbook (w.g.o/doc/en/handbook/) > a.2) Articles (w.g.o/doc/en/articles/) > a.3) Other guides (w.g.o/doc/en/) > a.4) Translated documentation > a.5) Submit new > Okay, documentation is documentation. Whether it's on w.g.o or in the man pages, or written in sanskrit on someone's forehead. I would tend not to split it up in a documentation and "other doc" products. You dont need a 'submit new' component of the product. That's more a property of the bug status. open, resolved, etc. > b) Other documentation > b.1) Project specific docs (w.g.o/proj/en/) > b.2) Manpages > b.3) Other See above. > Let's make a decision and forward it to jforman. > I'm up for anything that makes sense to me. But one thing I will warn you about. When we rm the old product, its going to send out a shitton of emails. That's just something we cant get around.
(In reply to comment #2) > Small proposition: > Let's add "development documentation" and let's make all the components > automatically fill in "assigned to" field. For our docs and translations it > would be docs-team@gentoo.org, for dev docs it would go to devrel@gentoo.org, > for man pages to portage team, and so on. Project documentation could go to > bug-wranglers, and they would decide to which project assign the bug. > What do you think? > Each component under the product can have a different default assignee.
(In reply to comment #8) > Okay, documentation is documentation. Whether it's on w.g.o or in the man > pages, or written in sanskrit on someone's forehead. I would tend not to split > it up in a documentation and "other doc" products. Okay, so what about something like "Manual Pages" which will assign it to the bug-wranglers? > You dont need a 'submit new' component of the product. That's more a property > of the bug status. open, resolved, etc. We do, it is for submitting new documentation. It could go under "Other docs under /doc/en/", but it's already included in the current state. > I'm up for anything that makes sense to me. But one thing I will warn you > about. When we rm the old product, its going to send out a shitton of emails. > That's just something we cant get around. :-(
The bottom line is users can't fill in bugs properly and the GUI is not helping whatsoever. We currently have two products (docs-user & docs-developer) and the distinction between them is not clear. Besides, their respective component lists are outdated, incomplete and too long. Couldn't we have two new products with more sensible descriptions & component lists and remove the current doc-* products from https://bugs.gentoo.org/enter_bug.cgi ? This way we don't have to change anything to current bugs.
*** Bug 118545 has been marked as a duplicate of this bug. ***
Not sure whether this bug just went stale. But give me products/components you want. with descritiptions and default assignees for each and I can see on implementing it.
Can the following products be flagged as obsolete and hidden from https://bugs.gentoo.org/enter_bug.cgi? .Docs-developer: Developer oriented documentation and Tools. This includes portage. .Docs-user: User oriented documentation. and be replaced by the following products: .Documentation: guides and handbooks located under www.g.o/doc and all translations <b>on www.g.o</b> .Other documentation: project-specific docs (www.g.o/proj), man pages, etc. Components for first product (all assigned to docs-team): .Installation handbook (w.g.o/doc/en/handbook/) .Other documents (w.g.o/doc/en/) .Translated documentation on www.g.o .Submit New Documentation I don't care much what goes into the second product. I guess some projects will want a component entry, like devrel for their handbook. We'd like an entry (GDP, assigned to docs-team). I suppose man pages would go to bug-wranglers. Does that sound reasonable?
How about having translations as separate product with languages as components? This way we wouldn't need to kludgily prefix all translation bugs with [ll] and it could help a lot with filtering translation bugs as well. This is also the method that most other projects (eg. gnome) use to handle translation bugs in bugzilla. At least it would be nice if something was done to make reporting translation bugs easier, as with current method I keep getting misreported spam from translation teams and translation bug reports at least weekly.
(In reply to comment #15) > How about having translations as separate product with languages as components? Yup, seems like a great idea as long as it's easy for jforman to add new languages. We will have to have an "Other Languages" item as well.
(In reply to comment #16) > (In reply to comment #15) > > How about having translations as separate product with languages as components? > > Yup, seems like a great idea as long as it's easy for jforman to add new > languages. We will have to have an "Other Languages" item as well. How easy is it to add or remove a language from the component list? I'd want to restrict the list to the actively maintained languages, and use Other with the language code in the subject as we do now. FYI, the list of known languages on www.g.o is pl de fr ja it es ru pt_br zh_tw ro cs fi nl da tr ko id hu pt sv vi lt ca el The component list should only display pl,cs,de,fi,fr,ja,it,es,ru,pt_br,zh_tw,ro,other
Final call, if you disagree, react fast to let jforman know in time. Docs-developer & Docs-user products should be replaced with: . Documentation: guides and handbooks located under www.gentoo.org/doc/ . Translations: all documents not in English on www.gentoo.org . Other documentation: project-specific documentation, man pages, etc. Please try to assign to the project or maintainer in charge. Components (title, default assignee, description): . Documentation: .. Installation handbook, docs-team@gentoo.org, Our main installation handbook. .. Other documents, docs-team@gentoo.org, All other guides and books. Please fill in the URL field. .. Submit new document, docs-team@gentoo.org, If you have a brand new document . Translations: (all go to docs-team) .. [cs] Czech .. [de] German .. [es] Spanish .. [fi] Finnish .. [fr] French .. [it] Italian .. [ja] Japanese .. [pl] Polish .. [pt_br] Brazilian Portuguese .. [ro] Romanian .. [ru] Russian .. [zh_tw] Traditional Chinese .. Other . Other documentation .. Developers HOWTO, devrel@gentoo.org, The Developers HOWTO on creating ebuilds properly and using ports. .. Portage Documentation, dev-portage@gentoo.org, Man pages, helpful output, etc. .. Project-specific documentation, bug-wranglers@gentoo.org, Project pages under www.gentoo.org/proj. Please try to assign to the relevant project. .. Other, bug-wranglers@gentoo.org, If it doesn't fit anywhere else ... (List inspired by current components, feel free to adjust, not GDP's turf)
Done. DOCS TEAM: YOU NEED TO SEARCH FOR YOUR BUGS (I CLOSED YOUR PREVIOUS PRODUCTS) AND MOVE THEM OVER TO THE NEW SETUP.
