Peter, > Ok. I don't quite get what your point is here.
Do you realize that I'm not disagreeing with you? I simply pointed out, as a precaution against oversight, that there are some items that need to be moved. > As far as ASF/CVS requirements, I don't believe that there is any such > animal. > I've never read any documentation that indicated that it is either > necessary or desirable in the eyes of the ASF that the website > HTML/images be stored in CVS in an immediately deployable form. If > anyone knows of such docs, please send a link to the list so we can > discuss. Here you go: http://www.apache.org/dev/committers.html#web I suspect that the correct place to discuss the issue with the ASF would be in infrastructure@. From a recent discussion there, it appears that there are certain topics, e.g., site security, that they do not want discussed in a publicly archived list. > Ugh. Same problem with updates, just deferred to a different module. > We'd have to manually update changes to the Javadoc. Not from what I had in mind, Peter. In my model, we automatically generate james-site from sources in our repository. A cron task would update its local tree from james, build james-site, and commit james-site as necessary. None of us would ever need to manually update james-site. james-site would be nothing more than the interface between the cron job and the web site. To an extent, I don't care, since we can reconstruct the site from our source CVS. I mention this approach simply because it appears to be used elsewhere in the ASF, and it addresses what I perceive to be an infrastructure concern. --- Noel -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
