On 05/12/2010 10:53 AM, Rajith Attapattu wrote:
On Wed, May 12, 2010 at 10:43 AM, Jonathan Robie
<[email protected]> wrote:
The first step might be to take inventory of what gets handled as static
HTML. I hope that will be relatively few pages, and that it will not include
the documentation pages.
I would assume the static pages would be
1. Home
2. Mailing lists
3. Source repositories
4. Qpid Integrated with..
5. People
6. Acknowledgements
7. What is AMQP ?
8. Getting Involved
The following should be direct links
1. License
2. Issue Reporting
3. Wiki
4. ASF
I agree with all of this.
I'd prefer the rest to be maintained in svn and export generated HTML.
In particular there is a lot of benefit in maintaining the following
in svn to ensure they are all current at any given time.
1. Download
2. FAQ
3. Getting Started
4. Building Qpid
Yes, that makes sense.
I am not sure what to do about developer pages.
Me neither. Initially, I suggest we simply refer to the existing Wiki
pages. But I think we need to figure out what we really want the
developer pages to include, and what we want them to accomplish, before
redesigning that part.
Jonathan
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
