Add entry on the new issue triage team, from Vladimir Krstulja
This commit is contained in:
Benjamin Kaduk
parent
c7bf0a5834
commit
ce0c195e7c
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=48005
1 changed files with 120 additions and 0 deletions
|
|
@ -2021,4 +2021,124 @@
|
|||
archive or see the Phabricator review.</p>
|
||||
</body>
|
||||
</project>
|
||||
|
||||
<project cat='team'>
|
||||
<title>The &os; Issue Triage Team</title>
|
||||
|
||||
<contact>
|
||||
<person>
|
||||
<name>Bugmeister</name>
|
||||
<email>bugmeister@FreeBSD.org</email>
|
||||
</person>
|
||||
|
||||
<person>
|
||||
<name>
|
||||
<given>Kubilay</given>
|
||||
<common>Kocak</common>
|
||||
</name>
|
||||
<email>koobs@FreeBSD.org</email>
|
||||
</person>
|
||||
|
||||
<person>
|
||||
<name>
|
||||
<given>Vladimir</given>
|
||||
<common>Krstulja</common>
|
||||
</name>
|
||||
<email>vlad-fbsd@acheronmedia.com</email>
|
||||
</person>
|
||||
|
||||
<person>
|
||||
<name>
|
||||
<given>Rodrigo N.</given>
|
||||
<common>Hernandez</common>
|
||||
</name>
|
||||
<email>rodrigo.FreeBSD@minasambiente.com.br</email>
|
||||
</person>
|
||||
</contact>
|
||||
|
||||
<links>
|
||||
<url href="https://pad.riseup.net/p/FreeBSD-triage-brainstorming">Issue Triage Team's Brainstorming Pad</url>
|
||||
</links>
|
||||
|
||||
<body>
|
||||
<p>By the end of the Q4 2015 period, &a.koobs; (koobs@)
|
||||
started an initiative to form an experimental Bugzilla Triage
|
||||
Team. The main goals of the team are to increase community
|
||||
involvement (addition/training of new triagers) and enhance
|
||||
current procedures and tools, among others. This experiment was
|
||||
started with the participation of Vladimir (blackflow on
|
||||
irc/freenode) and Rodrigo (DanDare on irc/freenode), who
|
||||
approached koobs@ with a desire to contribute and get more
|
||||
involved with the &os; Project. This experimental pilot project
|
||||
has the task of setting up procedures for enhanced Issue (Problem
|
||||
Report) management that include better
|
||||
classification/prioritization, eventually leading to faster
|
||||
resolution of the issues.</p>
|
||||
|
||||
<p>We are now happy to report on the progress of this
|
||||
experimental team:</p>
|
||||
|
||||
<ul>
|
||||
<li>We have set up the #FreeBSD-bugs IRC channel on
|
||||
Freenode and we are successfully using it to exchange information
|
||||
about triage processes, ask for help, propose changes and discuss
|
||||
related topics.</li>
|
||||
|
||||
<li>We have identified the primary role of an Issue Triage
|
||||
Team to be that of classification of problem reports of all kinds
|
||||
(currently limited mostly to ports and obvious src issues) and
|
||||
facilitation of issue assignment, which is making sure that the
|
||||
reported issues are explained well, contain all the appropriate
|
||||
information (or as much of it as possible), and are brought to
|
||||
attention of the people who can act upon them.</li>
|
||||
|
||||
<li>Vladimir and Rodrigo are successfully training in bug
|
||||
triage as well as porting processes (Vladimir is also taking
|
||||
maintainership of some ports).</li>
|
||||
|
||||
<li>This experiment is benefiting from the introduction of
|
||||
newcomers to issue tracking. It naturally resulted in a entire
|
||||
review of the tracking proccess from its very elementary aspects.
|
||||
This "fresh eyes" participation spotted minor details
|
||||
along the proccess, giving the opportunity to scrutinize actual
|
||||
procedures on a number of smaller points, followed by proposals on
|
||||
how to improve the overall Issue Tracking and Management. The new
|
||||
ideas include both organizational and technical ideas and
|
||||
solutions, such as new or modified keywords or flags for better
|
||||
classification, the triage workflow, and Bugzilla technical
|
||||
improvements among others.</li>
|
||||
|
||||
<li>An important goal is producing documentation not only
|
||||
aimed at people directly engaged on issue triage tasks, but also
|
||||
documentation aimed at general users, about best practices for
|
||||
using Bugzilla and the issue management workflow. Another
|
||||
relevant point is that feedback from triage team can be used to
|
||||
improve Bugzilla in terms of adjusting existing features to best
|
||||
fit &os;'s needs, and development of new features (please see
|
||||
Mahdi "Magic" Mokhtari's report on "Bugzilla
|
||||
improvements").</li>
|
||||
|
||||
<li>We are still collating ideas in preparation of setting
|
||||
up a Wiki namespace for the overall topic of issue management,
|
||||
containing information for all the parties involved in issue
|
||||
tracking: from users (reporters) to maintainers and committers.
|
||||
The unorganized brainstorming document is linked in this
|
||||
report.</li> </ul>
|
||||
|
||||
<p>Since the Issue Triage Team is very young, we expect more
|
||||
information be available and more actions be reported upon in the
|
||||
next Status report.</p>
|
||||
</body>
|
||||
|
||||
<help>
|
||||
<task>
|
||||
<p>Set up the Wiki namespace and organize the brainstorm
|
||||
document into a meaningful set of documents.</p>
|
||||
</task>
|
||||
|
||||
<task>
|
||||
<p>Recruit more suitable triagers into the team.</p>
|
||||
</task>
|
||||
</help>
|
||||
</project>
|
||||
</report>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue