Dave:

Still broken by a minor typo. The "Quick Link" on the blog is now pointing to the nonexistent "DownloadPag" (missing e) on the wiki.

The actual "DownloadPage" looks great. Thanks. I think this will resolve the confusion.

All:

There have been several discussions about where to put the project site and what technology to use. One criterion I would like to introduce is that the "official" project site should have equal access to all committers. I have access to the present wiki, though I remember having problems fixing some image/attachment issues before because it required some local filesystem access. In the present case, I think the Quick Links are on a template in the blog to which I don't have access to fix myself. On a proper project site any of us should just be able to go in and fix this kind of thing.

--a.


----- Original Message ----- From: "Dave Johnson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 19, 2006 5:07 AM
Subject: Re: Confusing Downloads links (was: Issue - creating a blog with 2.3)


On 6/16/06, Anil Gangolli <[EMAIL PROTECTED]> wrote:
The "Downloads" link in the "Quick Links" on the right side of the project
blog goes straight to the Java.net site, and other users might experience
similar confusion.

Fixed. It now points to a downloads page on the wiki:
http://rollerweblogger.org/wiki/Wiki.jsp?page=DownloadPage

Does that look OK?


We should either add some links from the Java.net page to point users to the right place for Roller 2.3-incubating (and future) releases, start our own Downloads page on the wiki, or point the Downloads link to the current News
page.

Does the new downloads page on the wiki go far enough?

I'm not sure it's possible to add text to the Java.Net files page.
Any other references to Java.Net that need attention?


I clarified the text on the wiki section to indicate that the Downloads link
is for the Roller support materials and older Roller versions distributed
from Java.net, but there is still a lot of room for similar confusion.

Thanks,
Dave


Reply via email to