[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



Hi,

	I would like to further clarify my stance on this issue. I
 want policy to document whatever it takes for other packages to
 interface with the package in question, once that interface spec has
 stabilized. In other words, you violate policy, people can file bugs
 against you.

	I am not attempting to change the fashion in which these sub
 policies have come forth: initially, the policy is formulated by the
 person doing the work, which is going to be most likely the author of
 the interfacing code. Initially, things are not set in stone, and the
 code writer experiments. At that point, rapid development takes
 place, and should not be held back by the policy mechanism. As a
 corollary, at that point the mechanism is not fully policy; you
 can't file bugs against packages not following the convention.

	When you want in interface to have full weight of policy, the
 interface docs should be massaged into the policy set Which means
 that at a certain point we want the developer to offer his sub-policy
 to Debian-policy

	that only happens when the interface is stable, and even then
 if there is a growing installed base of packages affected by the
 convention (like, menu has zillions of packages that cooperate).  We
 also should decide what is important enough to make mandatory -- the
 menu support seems to be very nice indeed).

	If they are mandatory, I think they should not be at the whim
 of the maintainer -- the interface should become a standard, and the
 code just an implementation of the standard. the code can still grow
 -- but other packages, which were forced by policy to conform to the
 standard, should have some protection.

	If we change policy, we may need to look for another package
 to implement it, there is no way one may coerce a developer to write
 code by introducing new requirements. 

	If we make it policy to use package XYZ, and it may be a bug
 not to use XYZ. In that case, you can't just yank the interface out
 from under them -- any changes that affect all packages should be
 under the umbrella of the peer review and debate on the policy list.

	manoj
-- 
 "Conversion, fastidious Goddess, loves blood better than brick, and
 feasts most subtly on the human will." Virginia Woolf, "Mrs. Dalloway"
Manoj Srivastava     <srivasta@acm.org>    <http://www.golden-gryphon.com/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E


Reply to: