My "pie-in-the-sky" vision would be to move all of the content of the
HTML pages at fdo.osgeo.org onto the Trac site. The current main page
of the Trac wiki would be pushed a bit deeper into the site, and
probably broken up into separate sections. There may also be an
opportunity to restructure the pages on the web site into different
sections if others are interested, but I don't have any real goals for
that.
One of the benefits I see from this is that the Doxygen docs could be
moved to download.osgeo.org/fdo/, opening the path for automated
documentation builds on one of the telascience servers.
The only hurdle I can see to doing this would be in setting up a menu.
I would like to see the TracNav macro installed on Trac to support a
global menu for all wiki pages.
http://trac-hacks.org/wiki/TracNavCool example:
http://www.hectaresbc.org/trac/wiki/HabcTechnicalInformationIf there is enough agreement for this, I'll write up an RFC for the
move, and make a request to SAC to install that macro.
Jason
-----Original Message-----
From:
[hidden email]
[mailto:
[hidden email]] On Behalf Of Robert
Fortin
Sent: Thursday, October 09, 2008 07:08
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Trac Website
I agree with Frank, the internal part is hidden and not obvious.
Jason, can you elaborate a bit on how what your are suggesting would
impact the FDO site?
Robert Fortin
-----Original Message-----
From:
[hidden email]
[mailto:
[hidden email]] On Behalf Of Frank
Warmerdam (External)
Sent: Thursday, October 09, 2008 1:33 AM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Trac Website
Folks,
I'm in favor of merging the drupal site contents into Trac and
making that our face. I find the current split confusing for
a rather developer oriented thing like FDO.
Zac Spitzer wrote:
> My only concern is that sometimes the osgeo trac grinds to a halt,
> while the drupal
> seems to be pretty reliable...
I'm under the impression that part of the problem is our use of
sqlite backends for Trac and that it is easy to get database
locking issues. We are contemplating using a real multi-user
database like postgres or ingres for Trac in the future to alleviate
this.
> I'm all for a single site, trac is a little hidden at the moment
>
> z
>
> On Thu, Oct 9, 2008 at 2:39 PM, Jason Birch <
[hidden email]>
wrote:
>> No comments on this? Are there folks who are highly attached to the
Drupal website? Is it worth my time to write up an RFC for this?
>>
>> Jason
>>
>> ________________________________
>>
>> From:
[hidden email] on behalf of Jason Birch
>> Subject: RE: [fdo-internals] Trac Website
>>
>> This would definitely require an RFC if there is enough buy-in for
it, but I wanted to get some discussion going first. I agree that it
would be a good idea to list sections and sub-sections in the RFC to
make the transition manageable.
--
---------------------------------------+--------------------------------
------
I set the clouds in motion - turn up | Frank Warmerdam,
[hidden email]
light and sound - activate the windows |
http://pobox.com/~warmerdamand watch the world go round - Rush | Geospatial Programmer for Rent
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
winmail.dat (5K) 
