Hello Ian,

On Tue, Mar 06 2018, Ian Jackson wrote:

> Thanks for bringing this up, here.  FAOD, my primary intent in
> suggesting you do so was to get technicaly input from the denizens of
> d-policy, who have a lot of useful expertise.

Okay.  It's fine to use this list for that, of course.

I had interpreted Pirate's message as requesting the policy delegates do
something qua policy delegates.  Possibly this is because he
misinterpreted what you were suggesting.

> Many language-specific packaging teams have language-specific
> policies.  These are usually shipped in some core dev support package
> for the policy in question.  So far it has not been necessary to
> formally reference the Perl policy (say) from the debian-policy
> package.  But I don't see any reason why debian-policy could not
> formally refer to the Javascript policy.
> I do think that the Javascript policy has to be not in a wiki page.
> We can't have normative references from debian-policy to wiki pages.

Agreed.  Not everything needs to be in our package.

(It might aid in discoverability if team policies were published more
systematically, though, and perhaps incorporating them into our package
is the way to do that.  But that's a discussion for another day.)

Sean Whitton

Attachment: signature.asc
Description: PGP signature

Pkg-javascript-devel mailing list

Reply via email to