From: "Ben Laurie" <[EMAIL PROTECTED]> > James Strachan wrote: > > From: "Sam Ruby" <[EMAIL PROTECTED]> > > > >>Ask Bjoern Hansen wrote: > >> > >>>>>In the case of Maven, it would seem to me that a <bio/> or <homepage/> > >>>>>element inside <developer/> elements in project.xml files would be most > >>>>>appropriate. > >>>> > >>>>Working on adding <url/> element as we speak. > >>> > >>>Gah; bike shedding at work! Just having each project (and the > >>>member list) keep it updated via their own pages seems much simpler > >>>and in a very simple way it makes it clear that the committer did an > >>>opt-in. > >> > >>Actually, I don't believe so. The proposed <url/> element will > >>presumably be added to the input source from which the Maven Project > >>Team page is generated. It will still be up to the individual to > >>explicitly provide it, and will be monitored and maintained by the > > > > project. > > > >>After that point, one of us will screen scrape it. ;-) > > > > > > You won't need to screen scrape. You could use XPath / XSLT... > > > > http://cvs.apache.org/viewcvs/jakarta-turbine-maven/project.xml?rev=HEAD > > > > search for //developer > > > > Looks like there'll be a new <homepage> element in there soon too... > > Doesn't this lead to loads of duplication of developer info? Surely they > need to be included by reference?
Agreed. Thats why I was arguing for a single canonical place (a single developer.xml file available on the web) where all Apache committer info can be put and then reused on each project. James ------- http://radio.weblogs.com/0112098/ __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com
