Ok, thanks for the explanation. If you need any help around this, I am
available.

Rajika

On Sat, May 1, 2010 at 8:39 PM, Robbie Gemmell <[email protected]>wrote:

> Hi Rajika,
>
> I had been intending to reply to the JIRAs Sebb raised earlier, however the
> JIRA system has not been responding so ill just reply here for now.
>
> The website has always had such a navigation menu, however the ASF's
> Atlassian Confluence installation has just been upgraded following the
> recent outbreak of Atlassian JIRA installations being compromised, and the
> result of this upgrade has been that some existing themes (such as the one
> we are using) are now incompatible and as a result of this various ASF
> project's automated website export systems have been impacted by breakages
> such as the navigation elements not being present on the export.
>
> You have found part of the discussions that have taken place in the last
> week or so relating to our website. We have for some time had intention to
> move away from using a Confluence export as our website, this is just
> another example of why we should. Hopefully very soon we will be moving to
> a
> more static website with documentation generated from DocBook sources kept
> in our code repository.
>
> Robbie
>
> > -----Original Message-----
> > From: Rajika Kumarasiri [mailto:[email protected]]
> > Sent: 01 May 2010 15:38
> > To: [email protected]
> > Subject: Re: Proposed directory structure for web site
> >
> > I think I am not making any noise in middle of this discussion.
> > When I browse through the qpid web site I faced with some of the
> > problems
> > reported in [1]. I think we need to re-arrange the web site with the
> > same
> > content in a more user friendly manner where a user pick what he/she
> > wants
> > in minimum time.  What I suggest is the following left panel menu and
> > site
> > should be generated with maven site plugin[2].
> >
> > + Download
> >  |    + Releases
> >  |    + Source code
> >  |
> > + Documentation
> >  |    + Quick start guide
> >  |    + Wiki
> >  |    + Javadocs
> >  |
> > + Project Information
> >  |    + Mailing lists
> >  |    + Building from source
> >  |    + Issue Tracking
> >  |    + Project Team
> >  |    + Project Summary
> >  |
> > + ASF
> >       + Foundation
> >
> > etc..,
> >
> > Rajika
> >
> > [1] - https://issues.apache.org/jira/browse/QPID-2563
> > [2] - http://maven.apache.org/plugins/maven-site-plugin/
> >
> >
> >
> > On Wed, Apr 28, 2010 at 6:53 PM, Jonathan Robie
> > <[email protected]>wrote:
> >
> > > On 04/27/2010 11:04 AM, Andrew Stitcher wrote:
> > >
> > >> This might actually be a place where the "stupid" arrangement of our
> > >> repo to have a superfluous "qpid" directory might help:
> > >>
> > >> Currently the repo structure is actually:
> > >>
> > >> qpid
> > >>    + trunk
> > >>           +qpid
> > >>    + branches
> > >>           +<branchname>
> > >>                       + qpid
> > >>
> > >> So we could use the existing structure and put the checked in docs
> > in
> > >> parallel like:
> > >> ....qpid/trunk/qpid.apache.org
> > >>
> > >> But actually I'd prefer a simpler solution - why not just make it
> > >> completely separate viz:
> > >>    http://svn.apache.org/repos/asf/qpid/qpid.apache.org
> > >>
> > >> Either of these places will avoid the usual dev check out from
> > picking
> > >> up the checked in web source.
> > >>
> > >> If infrastructure are happy to give us a completely separate repo
> > then
> > >> this might be better as it would be easier to give it its own access
> > >> control.
> > >>
> > >>
> > >
> > > OK, I'll run this by #asfinfra and pick one of the two directory
> > structures
> > > shown above.
> > >
> > > Jonathan
> > >
> > >
> > > ---------------------------------------------------------------------
> > > Apache Qpid - AMQP Messaging Implementation
> > > Project:      http://qpid.apache.org
> > > Use/Interact: mailto:[email protected]
> > >
> > >
> >
> >
> > --
> > http://rajikak.blogspot.com/
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
>
>


-- 
http://rajikak.blogspot.com/

Reply via email to