reassign 447231 debian-policy,python-defaults
thanks

[adding the debian-python list again, I guess you've missed it].

Matthias Klose wrote:
> Bernd Zeimetz writes:
>> Then let's maintain it again. We maintain a lot of packages in a team,
>> so I can't see a problem to maintain the policy there, too.
> 
> The policy files are not unmaintained; 

They are. Maintaining is more than having a minimal update every other year.

> proposed policy changes should
> be filed as bug reports against python-defaults.

If that's the preferred way - I'm reassigning a related bug from
d-policy to d-policy AND python-defaults to make sure it's not forgotten.

Also in my opinion the Python policy should be team-maintained
(preferable by a small and _active_ team) like most Python related
packages.

Manoj's Python 'policy' is much more complete, formal and uptodate then
the official one, so it should replace the current one.

-- 
Bernd Zeimetz
<[EMAIL PROTECTED]>                         <http://bzed.de/>




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to