View | Details | Raw Unified | Return to bug 190593
Collapse All | Expand All

(-)article.xml (+49 lines)
Lines 1242-1247 Link Here
1242
      gone away, just send a follow-up (in the manner prescribed
1242
      gone away, just send a follow-up (in the manner prescribed
1243
      above) saying that the problem report can be closed, and, if
1243
      above) saying that the problem report can be closed, and, if
1244
      possible, explaining how or when the problem was fixed.</para>
1244
      possible, explaining how or when the problem was fixed.</para>
1245
1246
    <para>In case the PR stays untouched (not assigned or commented
1247
      on by anyone) after a week or two, which may happen in certain
1248
      circumstances, such as when there is an increased PR backlog
1249
      or during a holiday season, it is worth trying to find a
1250
      committer particularly interested in working on the PR.</para>
1251
1252
    <para>There are a few ways to do so, ideally in the following
1253
      order, with a few days between each communication
1254
      channel:</para>
1255
1256
    <itemizedlist>
1257
      <listitem>
1258
	<para>Find out what the relevant FreeBSD mailing list for
1259
	  the problem report is (a full list is here: <link
1260
	  xlink:href="https://lists.freebsd.org/mailman/listinfo"></link>)
1261
	  and send a message informing it about the PR and asking
1262
	  for assistance and/or comments</para>
1263
      </listitem>
1264
1265
      <listitem>
1266
	<para>Join the relevant IRC channels (a partial listing is
1267
	  here: <link
1268
	    xlink:href="https://wiki.freebsd.org/IrcChannels"></link>)
1269
	  and inform the people who are in that channel about the
1270
	  PR and asking for assistance and/or comments - make sure
1271
	  to be patient and stay in the channel after posting, so
1272
	  that the people from different timezones around the
1273
	  world have a chance to catch up</para>
1274
      </listitem>
1275
1276
      <listitem>
1277
	<para>Find the committers interested in the problem that
1278
	  was reported - if it exists in a particular tool, binary,
1279
	  port or source file, check who were the last few
1280
	  committers making substantive changes to it, and try to
1281
	  reach them via IRC or email (the list of committers and
1282
	  their emails can be find here: <link
1283
	    xlink:href="https://www.freebsd.org/doc/en/articles/contributors/staff-committers.html"></link>)</para>
1284
      </listitem>
1285
    </itemizedlist>
1286
1287
    <para>Remember that the people you'll be trying to get help from
1288
      are volunteers just like maintainers and users, so they might
1289
      not be immediately available to assist with the problem report.
1290
      Patience and consistency in the follow-ups is highly advised
1291
      and appreciated.  With enough care and effort dedicated to that
1292
      follow-up process, finding a committer to take care of the PR is
1293
      just a matter of time.</para>
1245
  </section>
1294
  </section>
1246
1295
1247
  <section xml:id="pr-problems">
1296
  <section xml:id="pr-problems">

Return to bug 190593