Hi Dion,

There's nothing to stop individual components from omitting the
"generic" &viewmenu; menu and adding their own one that links
specifically to the svn locations for that component. In fact, that
would be a nice idea.

However most don't bother. And at the moment, I think the commons-level
default &viewmenu; that most component pages do include doesn't give
enough info; just two links to viewcvs. So users then go up to the
jakarta-level version control info, at which point the info is *very*
generic (including info about CVS that is irrelevant to commons).

I can't see anything that can be done at the commons-build level to
provide components with better version control access info than the
patch I'm proposing.

Regards,

Simon

On Fri, 2005-05-20 at 13:10 +1000, Dion Gillard wrote:
> Do users of one component really care about the entirety of commons?
> I'd rather see component specific info being more prominent than an
> all-of-commons link which may be irrelevant.
> 
> On 5/20/05, Simon Kitching <[EMAIL PROTECTED]> wrote:
> > Hi,
> > 
> > Currently the commons site navbar (and all component navbars) have a
> > "View SVN" entry with links to proper and sandbox via viewcvs:
> >   http://jakarta.apache.org/commons/
> > 
> > I would like to enhance this a little. Here's a new version of the site
> > containing an updated "View Source Code Repository" navbar entry:
> >   http://people.apache.org/~skitching/commons/site/
> > 
> > I would appreciate people's feedback on this.
> > 
> > Please note:
> >  * this is still referred to by "&viewmenu;" so all components would
> >    get updated to this new section when they publish new sites.
> >  * the "general information" is an absolute URL so it works from
> >    child components. Obviously, however, it doesn't work now as the
> >    new page hasn't been put on the real site. Here's the link you
> >    need to use for the moment:
> >      http://people.apache.org/~skitching/commons/site/svninfo.html
> > 
> > 
> > Regards,
> > 
> > Simon
> > 
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to