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