The general impression that that is too much info for a generic approach. Unless your goal is to redefine the project pages ;) I was more thinking in line of a "quick" view page, with all the projects with the most basic info (description, lists, cvs repo, latest version, project page link) So people can go to eg http://www.apache.org/projects-info.html and get all "quick" info over there.. This way you don't have to go through the process of every project changing their sites again..
Mvgr, Martin > Yes, this is sort of what I was thinking, we can easily do the same. > > > Personally I prefer to have two files: one describes the project, and it > stays basically fixed; the other is more dynamic and changes frequently. > > _projectinfo.xml_ > > - goals > - credits > - license > - resource URLs (site, mailing lists + archives, VCS stuff) > - description > - short description > - what it does > > _status.xml_ > > - committers > - todos > - changes > - votings ? > > Comments? > > -- > Nicola Ken Barozzi [EMAIL PROTECTED] > - verba volant, scripta manent - > (discussions get forgotten, just code remains) > --------------------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
