-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Dec 8, 2009 at 7:15 PM, Karsten Wade wrote:
I'm really pleased at the quantity _and_ quality of bug reports
coming
in for Fedora 12 documentation. (I seem to be on a number of QA
checks for various guides, which I'm glad about.)
We should run the statistics with bugzilla, but I'm getting a gut
feeling about this release based on what I've seen so far. Anyone
else notice this?
* Overall, more bugs across a few main documents (Installation Guide,
Release Notes) and a few others (IIRC). This means:
I have definitely noticed an uptick in volume for the IG and RN.
In addition, the bugs are higher quality IMO, and the reporters are
going to more lengths to offer suggested changes (I even received a
Docbook patch for a bug filed today, which you referenced below)
* More people are reading the content;
* They care enough to file bugs;
* Bug reports are a needed part of improving open content, it's the
open source way;
* Bug reports are a sign of a healthy and engaged community.
* The quality of the bug reports is up. They are mostly associated
with the correct component, are clear in what they find wrong, and
offer solutions and fixes. In fact, just now I saw a bug report[1]
that included a patch, which prompted me to write this email. We've
received a few bugs in translations, including correction
suggestions.
* The component owners have been highly responsive. The recent
improvements around bugzilla process, bug clean-up, and bug
maintenance are showing quality and attention from this team. You
are making Fedora Docs look really good!
Considering that we have more than doubled the number of guides for
the release, with l10n to match, I reckon we actually have _fewer_
bugs per guide.
If anyone cares to know what our real health statistics are around bug
reports, I could get together with you and any others in IRC for a
few hours and draw what we need from bugzilla.
It would be very interesting to see those statistics, though I am
unsure what we can infer from it. I think bugs are a bit of a double
edged sword.
On the one hand it means we have an engaged community, who cares
enough to spend time filing bugs.
On the other hand it means there is something wrong with the documentation.
So have we screwed up more, or have a more passionate community, or both?
In my mind either is ok, as long as we are responsive to the bugs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Use GnuPG with Firefox :
http://getfiregpg.org (Version: 0.7.10)
iEYEARECAAYFAksfLzgACgkQkZOYj+cNI1cBWgCgjuzXVI0d2yeW9cCE0vUULvfw
mQUAoLK67kFuuznP7BpRcpp7GWQoJHNP
=f66H
-----END PGP SIGNATURE-----