robert burrell donkin wrote:
On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
robert burrell donkin wrote:
> On 12/19/06, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
> <snip>
>
>> I'd like to see POM auditing in there somewhere.
>
> +1
>
> henri's been talking about adding this to RAT. IMHO this should be
> implemented as a separate component so that it could be used by a
> variety of applications: for example, it might be interesting to be
> able to apply policy rules as part of subversion commits or staging
> updates.
>
I have a colleague who has been converting all the POMs and .class files
in the repository to RDF, ready for auditing.
cool :-)
We are
1. planning an apache con EU talk, "fear the repository police".
in suitable costumes, i hope ;-)
nothing planned, but if we have someone in the audience cued up to say
"I didnt expect the spanish inquisition" we could have somebody burst in
monty-python style with "nobody expects the spanish inquisition"
2. looking to get management approval to hand the code to the MIT Simile
project (e.g. Stefano)
cool
(there seems to a lot of interest developing around RDF ATM amongst
apache members)
stefano's keen to see discussions related to apache and RDFs in the
labs
http://mail-archives.apache.org/mod_mbox/labs-labs/200612.mbox/[EMAIL PROTECTED]
(which makes sense to me.)
In theory, RDF is a "better" way of gluing together metadata in a way
that is tool neutral. For little tools, it should be effective.
I know Stefano is a fan of the semantic web, but to me the JAR
repository is an interesting analysis of how well it will work. We know
that today there's a lot of inconsistency out there, even though there
are some dedicated people (esp. Carlos) who put a lot of effort in to
keeping things under control. If we have problems chaining together
metadata from a single repository, what are the long term implications
for the semantic web going to be?
3. Thinking of something to audit the metadata. Maybe in prolog (my
choice), maybe something else.
i plan to persuade projects (by including this in RAT rather than a
conventional configuration file) to start recording auditing meta data
about documents which didn't originate at apache in RDF. i've also
been toying with the idea of using RDF to record relationships between
licenses and policy about licenses.
these sound like related problems to me
yes, one of my proposed 'enhancements' for both pom and ivy.xml files is
to include an audit trail in there, such as who created the pom.
Supporting a metadata element that took RDF-as-XML triples would be a
very extensible way to do this. Wagon and Ivy could ignore the data, but
other tools could extract it.
How would you use RDF to differentiate the mysql interpreation of GPL
from everyone elses?
Working title "repo-man". This not only lets us have a good name, it
gives us good quotes
repo man rules :-)
Best film Alex cox ever made.
it's amazing at the cinema...
"It's 4 A.M., do you know where your jar is?"
"You don't even know what's in your own trunk! And you know what? I
think you're afraid to find out! "
+1
Ok. then, we have a name!
I wonder if we could include some of the quotes as error messages (
http://www.imdb.com/title/tt0087995/quotes) . Like when an artifact
fails the audit
[error] artifact rejected.
[error] It happens sometimes. People just explode. Natural causes.
-Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
