Done. Here is the JIRA
http://issues.apache.org/jira/browse/GERONIMO-1298

Cheers!
Hernan

Dain Sundstrom wrote:
+1 to adding a pdf to the release and an xml export to the source tree.

Hernan can you create a PDF and an xml export and add it to a JIRA? Mark it for a 1.0 fix and as Blocker issue.

thanks

-dain

On Dec 6, 2005, at 11:27 AM, David Blevins wrote:

This is cool. How about we also stick a PDF (or a few) of the confluence doco in the release itself as well as check in an xml export of that content?

-David

On Dec 6, 2005, at 9:47 AM, Dain Sundstrom wrote:

+1 lets define some URLs under geronimo.apache.org and setup redirect rules for them

I suggest the following:

http://geronimo.apache.org/issues ==> jira insall
http://geronimo.apache.org/wiki ==> our current wiki
http://geronimo.apache.org/download ==> our download page

maybe

http://geronimo.apache.org/documentation
http://geronimo.apache.org/source

-dain

On Dec 6, 2005, at 8:23 AM, Paul McMahan wrote:

I agree with Hernan that the current links in the welcome portlet are very helpful. But I think we should only keep them if we can be sure they won't change in the foreseeable future. IMO the best way to ensure that would be to set up redirects and/or aliases under the HTTP server for geronimo.apache.org.

For example, the "Problem Tracking Database" link in the welcome portlet currently points at :
http://nagoya.apache.org/jira/secure/BrowseProject.jspa?id=10220
But it's likely that URL could become stale within the lifespan of the Geronimo 1.0 console.

So instead the welcome portlet could point at:
http://geronimo.apache.org/problems
and the server could redirect to the actual address.

Can someone familiar with how the geronimo.apache.org HTTP server is administered please advise whether or not this sounds like a reasonable approach?

thanks,
Paul


On 12/6/05, Hernan Cunico <[EMAIL PROTECTED]> wrote: Hi All,
I would like to keep the link to the confluence site (the one hosted by
Atlassian). Jason is working on getting a confluence site (licensed)
hosted in one of the zones. Whenever the decision is taken on (if)
moving the wiki, then we can update the console in the next  refresh or
as an intermediate "fix".

For an immediate (but yet temporary) solution I would suggest, once the confluence doc is officially moved (if it is moved), to have a redirect
on the Atlassian site.

Cheers!
Hernan

Joe Bohn wrote:
>
> When creating the Welcome Page with the new look & feel and the  web
> console welcome portlet I included a link to the current  confluence
> documentation. This is the "Additional Documentation" link. I added > it because I was thinking that this documentation was too good to not > have an easy way for the end user to access it and was curious to see if
> anybody would complain.
>
> Given all of the debate about confluence and the possibility that the > current confluence content may or may not be moving into a more official
> site, I guess I should remove these links.  Hopefully, whatever is
> decided will ensure that this documentation is readily available to the > users for V1 (even if it requires one level of indirection). So I'll go
> ahead and remove the links unless somebody really, really,  thinks we
> should keep them.
>
> BTW, if we do make a complete change from the wiki to  confluence is
> there any possibility that we could keep the same URL? The Welcome page
> has always included a link to the wiki and it would be great if  this
> didn't become a dead link on the installed images. It would probably be > better if we removed all of the links on the welcome page and the web
> console welcome portlet and just point the user to the Geronimo  home
> page.  This would allow us to keep things "up to date".  Should  I go
> ahead and make this change too while updating the welcome page and the
> web console welcome portlet?
>
> Joe
>
>




Reply via email to