Michael Prokop <bts@bts.grml.org>:
> Michael Prokop <mika@grml.org> added the comment:
> * Frank Terbeck <bts@bts.grml.org> [20090613 11:55]:
[...]
> > Also: I don't think the header makes much sense any more.
> 
> > We're using git.
> > That means, we have *detailed* information about when a file what last
> > changed.
> 
> ACK, and "Latest changes" causes headaches when merging stuff.
> So I'm dropping this stuff out of every file which I'm updating anyway.

Good. :)

[...]
> > Filename:
> > maybe Purpose:. Maybe.
> > Author: (And I think "grml-team (grml.org)" would suffice.)
> 
> Good idea, I hate the "who should we include into the Author field
> overall" problem anyway. Let's use instead grml-team. Do we want to
> use something like that? ->
> 
> Author(s):   grml team (http://grml.org/)

Yes, exactly.

> > Bug-Reports: maybe. And if, we should make sure the right URL is used.
> 
> http://grml.org/bugs/ is the right place IMO, because it provides
> all the necessary information for users.

Okay.

> > License: GPL v2 (unless otherwise noted)
> 
> > Those headers don't need constant updating.
> 
> ACK
> 
> > I'm voting for "won't fix" here. Don't add redundant information
> > without reason.
> 
> How to we want to proceed? Should we provide a good, ACK-ed template
> in the grml-policy (which requires some action anyway as you're
> aware ;))?


Well, "won't fix" this issue, merge ft/policy-wip of grml-policy.git
into its master. Add a note about what header we generally expect for
new files in grml.

Regards, Frank