developer's reference, and some points raised in Raphaël's platform
Just a quick note in response to
<URL:http://www.debian.org/vote/2002/platforms/raphael>, point 2.1 and
2.2. Raphael describes a "best packaging practices" proposed new
document and issues with the maintenance of the Developer's reference.
I would hardly object to his assessment that the document doesn't
always track infrastructure changes as quickly as it ought to.
Certainly much of that has been due to my workload (both in my
business and within Debian; the Debian workload of boot-floppies
project management will be slackening soon).
However, I would like to to take the occaision to make sure it is
known that anyone who wishes to join in on the maintenance of the
developers-reference can and should put themselves forward. The fact
is that documentation is quite time-consuming to maintain; it is a
group effort. Currently contributing are Antoine Hulin, Josip Rodin,
Gustavo Noronha, and Martin Michlmayr.
You can send patches to the BTS, of course, but we can also do one
better and bless CVS write permissions. Those who are serious about
helping should send me or the BTS a proposed patch for review, and
state your desire for CVS write permissions.
With respect to proposed best practices document proposed in the
platform by Matthew Wilcox, I feel that best practices is precisely
what the developers-reference is all about, and I encourage him or any
interested party to expand the scope of the Developer's Reference
Please CC me on replies, I don't always have time right now to keep up
with all the mailing lists ...
...Adam Di Carlo..<email@example.com>...<URL:http://www.onshored.com/>