-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Any thoughts on having a docs-bug list where people can subscribe and get a copy of all BZ tickets that are assigned for the Project?
- --Eric
On Fri, 2010-11-19 at 11:19 -0500, Eric "Sparks" Christensen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Any thoughts on having a docs-bug list where people can subscribe and get a copy of all BZ tickets that are assigned for the Project?
- --Eric
Just one. Would it be a good idea to create a component (or something like it) for each language? I'm thinking mostly in the guides, and assuming that most of the bugs are typos or missing strings to translate. If those errors can be directly assigned to the translation teams, not only they'll be solved faster, but you guys will be less overwhelmed. Regards, Daniel Cabrera (es)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/19/2010 12:42 PM, daniel cabrera wrote:
On Fri, 2010-11-19 at 11:19 -0500, Eric "Sparks" Christensen wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Any thoughts on having a docs-bug list where people can subscribe and get a copy of all BZ tickets that are assigned for the Project?
- --Eric
Just one. Would it be a good idea to create a component (or something like it) for each language? I'm thinking mostly in the guides, and assuming that most of the bugs are typos or missing strings to translate. If those errors can be directly assigned to the translation teams, not only they'll be solved faster, but you guys will be less overwhelmed. Regards, Daniel Cabrera (es)
I wonder if this couldn't be done using the existing L10n components. If someone submitted a ticket with a translation bug it could be sent over to the appropriate language component.
- --Eric
I'm cc'ing this thread to translators, because we really need most ideas like this one, in order to tracking more easily our own bugs.
EL Tue, 23 Nov 2010 11:40:51 -0500 "Eric "Sparks" Christensen" sparks@fedoraproject.org escribió:
On 11/19/2010 12:42 PM, daniel cabrera wrote:
On Fri, 2010-11-19 at 11:19 -0500, Eric "Sparks" Christensen wrote:
Any thoughts on having a docs-bug list where people can subscribe and get a copy of all BZ tickets that are assigned for the Project?
- --Eric
Just one. Would it be a good idea to create a component (or something like it) for each language? I'm thinking mostly in the guides, and assuming that most of the bugs are typos or missing strings to translate. If those errors can be directly assigned to the translation teams, not only they'll be solved faster, but you guys will be less overwhelmed. Regards, Daniel Cabrera (es)
Actually, we have components for languages (i don't know since when); This for Spanish (es):
https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=fl10n-...
Product: Fedora Localization; Component: Spanish
I wonder if this couldn't be done using the existing L10n components. If someone submitted a ticket with a translation bug it could be sent over to the appropriate language component.
- --Eric
As i've pointed above, we have the tools yet, but we are not using it, i think. Maybe lack of training?
Everybody, please share your search parameters to found bugs, i have this:
Product: Fedora; Keywords: Translation; New, Assigned, Modified https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=f-tran...
Product: Fedora Documentation; Keywords: translation; N, A, M, V, Closed. https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=f-docs...
Product: Fedora Localization; Status: Mod, New, Assigned, ON_DEV, ON_QA, RELEASE_PENDING, POST https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed&namedcmd=fl10n_...
Having *just one* bugs list would be a great tool to handle the ubiquitous newcomers to docs or translation teams, showing them a single source to suscribe for lot of tasks. I think in a pretty easy address to include in feedback/translation notes; something like the feedback for webmaster@fedoraproject.org would be better (being forwarded to websites@l.fp.o list without hassle). I have the feeling we lose a lot of feedback (i'm thinking a lot of translation bugs, you know) since the process to file a single bug forces anyway to create an account into Bugzilla.
Anyway, for everybody looking for something to do about docs&L10N bugs:
Well, you know, maybe it would be better a docs-bugs list and a separate trans-bugs list. Again, something not demanding one more register process for people kind enough to file a bug, even in an informal way.
Kind regards, Jesús Franco http://identi.ca/tzk
On Fri, Nov 19, 2010 at 11:19 AM, Eric "Sparks" Christensen sparks@fedoraproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Any thoughts on having a docs-bug list where people can subscribe and get a copy of all BZ tickets that are assigned for the Project?
- --Eric
Permit me to play devil's advocate for a moment.
Would this be mandatory for docs group members to join? (I am supposing the answer to the above to be no) So only those who want to get a copy of all bugs. Why would they not just add themselves to watchbugzilla? (Actually now that I think about it, that might not be an option for non-packages, but I am pretty sure bugzilla has a function to let you receive a copy of all of a component's bugs) So my fear really is this - we'll point new people to this bug list, they'll subscribe and they'll be overwhelmed. I know that just the relnotes content and the IG bugs are a pretty heavy load. I'd rather describe a process where a person can watch a specific documents bugs rather than get the firehose. (while not as bad as docs-commits, I imagine it'd still be relatively high-traffic and for most people, low relevance)
What other benefits accrue to having a list for these bugs?
-
Daniel Cabrera -
David Nalley -
Eric Christensen -
Jesús Franco