Re: Sponsorship requirements and copyright files
On Sun, Mar 22, 2009 at 01:45:18PM +0000, Noah Slater wrote:
> On Sun, Mar 22, 2009 at 11:42:29AM +0000, Neil McGovern wrote:
> > I'm not quite clear as to why this is an advantage yet Currently, this
> > seems to have been designed to provide interfaces for future tools to
> > use, while not regarding whether or not people want those tools.
> > Could you provide a use case or two to help clarify things? The main
> > one I see is for an end user to look at a packages copyright file and
> > say 'yes, I can use it for $foo', which is a case that's detracted from
> > in the proposal.
> Listing the licences (not necessarily copyright holders) in a machine readable
> format would allow lintian checks to be developed, and maybe even automatic
> license compatibility checks to be performed.
Perhaps this is where we're not quite seeing eye-to-eye. I know that
machine readable copyright files would allow lintian checks. But what
would those checks be, and what would be the point of them?
All I've personally seen so far is 'it makes data mining easier', which
although could be a goal in itself, doesn't improve the quality of
<twb> I don't see why anyone would want to "cyber" with a 16yo. IME none of
them can spell, and they probably haven't had the relevant experience to
write convincing prose. It's not like their ASCII is going to be any more
supple for them being sixteen.