On 12/19/06, John Tolentino <[EMAIL PROTECTED]> wrote:
Hi Everyone,
Been working on a tool to generate reports for release candidates and
this is a mock of what it should look like:
http://people.apache.org/~jtolentino/release-reports/MockReport.html
We can send this generated page to the dev list when we call for a release.
I appreciate any feedback so I can improve the reporting (and before I
go further into implementation).
IMHO license auditing is quite a lot more subtle than it might first
appear: checking license headers is really only the start. there's a
lot more complexity that a release audit tool needs to cope with in
the wild.
whether maven ends up using RAT or rolling another release audit tool,
it probably makes sense to think about collaborating on some of the
problems.
for example, audit meta-data is important: a machine readable record
of the licensing and provenance of a document. it's not always right
to include a license header in a document but it's not unreasonable to
ask that every document without a header be accumpianied by audit
meta-data. rdf seems a good match for the format.
(see http://mail-archives.apache.org/mod_mbox/labs-labs/200612.mbox/[EMAIL
PROTECTED]
thread)
- robert
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
