Re: Bug#30036: debian-policy could include emacs policy

[Adam Di Carlo <apharris@burrito.onshore.com>]

I still don't really understand what is intended by moving
sub-policies into the policy manual.  Is it intended that the Debian
Policy group take editorial control over the documents?  Does the
package maintainer lose the ability to change the document, unless
they are also a policy editor?

More objections:

Are you really sure you want to ask the menu documenter to do all the
work to split devel-level policy from user documentation?  I admit its
not a bad idea, but...

I'm just a little worried about this "manifest destiny" attitude
toward policy, i.e., ever-increasing scope.

I stand by my "middle-of-the-road" position that Policy should instead
*point* to a number of "blessed sub-policies", i.e., emacsen policy,
menu policy, etc., telling the user where they may get the documents.
Maybe even blessing a particular version....  This would absolve the
policy group of any confusion about who maintains these sub-policies,
which is often intimately tied to the minute implementation details of
the package.  This also enables maintaniers of subsystems to continue
to innovate.

The danger of course is that Debian could become hidebound.

--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>