@JuhaManninen : does not matter if the page is rather static or dynamic (from the perspective of content). The main advantage is the possibility to upgrade the functionality by adding new modules and components. As I said - I have experience with CMS specially with Joomla. As SMF is is available as a Joomla component it could be implemented.
Maybe I don't have enough knowledge to understand the benefits.
SMF is running the forum. The new page fetches announcements using PHP. For this Joomla is not needed.
The page also has a download button that identifies the client OS and links to the correct installation package. I don't see how Joomla could help there either.
Maybe Joomla has modules related to SW development. Then it could be interesting.
If you really think there is a need for it, you can put up a prototype somewhere and demonstrate it. There is even a FreeBSD 9.1 server waiting at FirmOS.
The Joomla system should not compete with the project main web site but offer something additional.
It is also important to only add web tools that are actually needed. There has been claims that better tool chain would increase code contributions dramatically which is not true. It is wishfull thinking at most. Creating code for a big and complex project is the hard part, the current tool chain does not really slow anybody down.
One favorite issue was the Git / SVN debate. Many people wrote that a distributed development model + Git would attract many new developers.
Now it is technically possible :
http://wiki.lazarus.freepascal.org/Creating_A_Patch#Using_a_forked_Git_repository_directlybut nobody (I mean NOBODY) has yet offered a forked GitHub branch with his code contributions. The whining stopped though, it is good.
One suggestion if you have time and energy: The Lazarus Wiki sucks and would need improvements.
The search feature does not find anything. There are other issues listed by Chronos in other threads. It is possible to fix those issues in the MediaWiki system. Somebody with knowledge, motivation and time should work on it using the test server.
Do you have some details to the fact that "they are difficult to configure"? For me - using CMS could be a real community driven project...
No details, sorry.
Ok, one detail is that I had a chance to participate in an EU inter-school project DOSSEE (Developing Open Source Systems Expertise in Europe) in Austria over a year ago.
Teams from different countries built something fancy using open source products during 2 weeks.
One team's name was "Hey, this is Joomla". They could not configure their system in a week.
They changed their name to "Hey, this is NOT Joomla" and tried some other SW (don't remember was it Drupal, or maybe the original one was Drupal), but they ran out of time.
Finally it was the only team that failed to finish their project.
The original team had made a proof-of-concept configuration in their country (Spain) before the event but they used different library versions etc. and those instructions did not work any more.
Bummer.
In the end they had a presentation of their "project" and had to explain why they failed. Other people also confirmed difficulties in their own CMS experiments. Nobody could explain why they are difficult though. They were clever people, I believe if they say so.