Re: use README.source to describe whether committing to VCS is desired
On Tue, Dec 22, 2009 at 10:05:10AM +0100, Stefano Zacchiroli wrote:
> Dear policy list,
> during various NMU, it happened to me that the maintainer of the NMUed
> package reply with "thanks a lot, next time please also commit your
> changes to our VCS, which is writable by all DDs".
>
> While we do have a place where to describe the location of a VCS (the
> Vcs-* headers), we in fact have no place, AFAICT, where the developer
> can describe her preferences in how/who/when/.. committing to that VCS
> is indeed welcome.
>
> In the past I've found packages which does use README.source for that
> and apparently Charles (Cc-ed) already tried to advance such a
> proposal. In essence, it would just boil down to amend the description
> of the purpose of README.source in Policy to also cover this.
>
> What's your take on that?
What happen if the package does not have a README.source ?
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: