Re: DEP 12: Per-package machine-readable metadata about Upstream
On Fri, Jan 4, 2013 at 12:59 AM, Russ Allbery wrote:
> Of course, the other issue that this DEP raises is how much sense it makes
> to put all this stuff in the source package, either in debian/control or
> in a new file, given that most of these fields (even including Maintainer,
> although moving that probably isn't a good idea) can change independent of
> any functional change in the source package.
That sounds like you maybe want DEP-2: