Website download section: location of Mac OS X Readme

[Christian Stimming]

Zitat von Geert Janssens <janssens-geert at telenet.be>:
> Question 2. Where to fetch the Mac OS X Readme file ?
>
> Different solutions I see:
> * Leave it as is, just live with the redirect.
> * Setup a "Release notes" section in wiki, store all release relevant
> information (release notes, changelog, readmes) there and link there. Also
> replace the SF Readme with a short message that points to the proper wiki
> page.
> * Add a copy of these files in htdocs and link to them there.
> * Post the readme file as a news item whenever a new MacOS X build is
> available.

I'd say it should go into the wiki.

The "normal release notes" used to go into the wiki as well,  
http://wiki.gnucash.org/wiki/Release_Schedule , and they would be  
copied to the static news items because of the nicer presentation on  
the front page. This of course is an annoying duplication of text. I  
guess this duplication was the reason for why the release notes are  
currently not added to the wiki.

> My feeling is that wiki pages are more flexible than plain php/html/css, more
> easily rearranged, improved, reworked and they get a consistent style across
> pages almost for free. Several other free software initiatives I follow [1]
> use wiki like websites to host release notes. I think it simply  
> works well for such information.
>
> Another -perhaps even more long-term- direction would be to migrate large
> parts of the static website to a true cms (like drupal[2]), which shares many
> of the advantages of a wiki, but is more flexible in many ways. For  
> example, a
> wiki isn't very well suited to host a front page for a website. I'm mainly
> checking for potential interest here. If enough people think this is a good
> idea, I may spend some time in the future to actually realise this. I'll have
> to do a number of drupal based websites soon, so I will have some experience
> in that area.

Sounds great! Indeed the wiki is suited for almost any parts of the  
information that we have, with two big exceptions: A dynamic  
frontpage, and consistent translations. Both are difficult or  
impossible to be done with the stock MediaWiki which we currently have  
in use. Additionally, the wiki isn't so good at a stronger structure  
of the website, like more hierarchical menus.

Anyone who has a solution where we can migrate everything into one  
single CMS or Wiki would be very welcome. I can think of either  
suitable MediaWiki plugins for a nicer front page and better  
translations, or a migration to some CMS, where Drupal would be a good  
candidate.

In the end it boils down to the usual answer: Your contribution is  
very welcome. But more specifically: Improving the website either by  
migration to a CMS or to a better integration in the wiki would both  
be very worthwhile goals.

Regards,

Christian