I'm torn on this. It does have a fairly
high noise-to-signal ratio but often it does point out valid omissions.
Having recently done metadata setup for a new project, I definitely appreciated
the validation that everything was set up correctly. As Ed suggests, having
a button where I can validate the data myself without widely broadcasting
the results would be handy. Maybe that, in combination with running it
automatically once or twice a year would be enough.
Wayne Beaton <wayne@xxxxxxxxxxx> Sent by: eclipse.org-architecture-council-bounces@xxxxxxxxxxx
08/08/2011 02:02 PM
Please respond to
meta data is out of date for..."
I tend to regard keeping project metadata/websites/... up-to-date as one
of those "selfish-best interest" sorts of things. That is, projects
should keep this information up-to-date because it is good for the
health of the project.
Every month we have a script that runs to check that certain bits of
metadata are properly specified. Missing, or incorrect entries are
reported via email message to the project mailing list.
Every month, a couple of project leads contact me and the Webmaster
about the messages, generally because something that's being reported
doesn't make sense (e.g. reports that a next release isn't specified
when one seems to have been specified). Every month, the Webmasters and
I spend a good couple of hours chasing down the problem and tend to end
up modifying the check scripts. These good couple of hours could be
better spent doing other more valuable things for the committers and
Most projects--it seems--just ignore these messages anyway.
So... I've been thinking. Is it time to just turn off this notification
mechanism? Or maybe just run it twice a year or something?
Your thoughts are appreciated.
The Eclipse Foundation