On 3/3/06, Henri Yandell <[EMAIL PROTECTED]> wrote: <snip/>
> I think we should be folding the site into one site, with manuals per > subproject. Release info would be put in a release structure (src, > javadoc) and other reports would be hooked into the CI system. > Separating the user and developer consumer-requirements, hopefully > making our life easier. If all that was in place, how many sites would the average Commons developer be required to maintain? It sounds like 3 to me - the component site, the shared site, and the CI site. IMO, that is 2 too many. Right now, we're only at 1 too many. If anything, I would be in favour of moving in the opposite direction. Everything about component X stays on the component X site, so the developers of component X only need to worry about maintaining one site. If someone wanted to add some automation to 'pull' some information from component sites to the main Commons site, that would be fine, but don't make the component developers have to go put it there. What makes the site updates a pain today is that there is more than one to maintain. -- Martin Cooper Hen > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
