Annotation of htdocs/developers/pkgsrc/pkg-bug-handler.xml, revision 1.2
1.1 jschauma 1: <?xml version="1.0"?>
2: <!DOCTYPE webpage
1.2 ! hrs 3: PUBLIC "-//NetBSD//DTD Website-based NetBSD Extension//EN"
! 4: "http://www.NetBSD.org/XML/htdocs/lang/share/xml/website-netbsd.dtd">
1.1 jschauma 5:
6: <webpage id="pkg-bug-handler">
7: <config param="desc" value="pkg-bug-handler group"/>
1.2 ! hrs 8: <config param="cvstag" value="$NetBSD: pkg-bug-handler.xml,v 1.1 2004/12/11 19:01:22 jschauma Exp $"/>
! 9: <config param="rcsdate" value="$Date: 2004/12/11 19:01:22 $"/>
1.1 jschauma 10: <head>
11: <title>pkg-bug-handler group</title>
12: </head>
13:
14: <sect1 id="pkg-bug-handler">
15:
16: <sect2 id="pkg-bug-handler-group">
17: <title>The pkg-bug-handler group</title>
18: <para>
19: The pkgsrc developers face a fair number of problem reports each day.
20: To handle the incoming reports in an organized fashion the pkg-bug-handler
21: group has been formed.
22: </para>
23: <para>
24: The responsibility of the group is to assign each incoming problem report
25: in the "pkg" category to someone who is willing and able to fix the
26: problem. To cut down new bugs by trying to handle them more or less
27: when they are filed.
28: </para>
29: </sect2>
30:
31: <sect2 id="organization">
32: <title>Organization</title>
33: <orderedlist>
34: <listitem>
35: <sect2 id="rotation">
36: <title>Rotation</title>
37: <para>
38: The pkg-bug-handler group currently consists of four individuals.
39: Each of whom has shift for one week. Every Tuesdays 00:00 UTC
40: an automatic mail is sent to the pkg-bug-handler list which
41: says whose shift will be next. This person's shift start's after
42: he replied to that mail and says that he started his shift.
43: </para>
44: </sect2>
45: </listitem>
46:
47: <listitem>
48: <sect2 id="on-call-person">
49: <title>On-call person</title>
50: <para>
51: The main job of the on-call person should be not to close PRs,
52: but to assign them to whoever is responsible for them.
53: If the package has a maintainer, then the PR should be assigned
54: to the maintainer and that's it. If it doesn't, the on-call
55: person should determine what the problem is, possibly initiate
56: a dialog with the PR submitter and then try to find a person
57: willing to take responsibility or if it could be assigned to one of
58: the role accounts (*-pkg-people) for platform specific bugs.
59: </para>
60: <note><title/>
61: Obvious simple bugs could also be fixed by the on-call person.
62: </note>
63: </sect2>
64: </listitem>
65: </orderedlist>
66: </sect2>
67:
68: </sect1>
69: </webpage>
CVSweb <webmaster@jp.NetBSD.org>