The Wicket project team is deciding whether the current progress justifies another release candidate, and when we should declare 1.0 final. Expect a new release candidate later this week. The votes are still open on declaring 1.0 final.
The current list I’m looking at are:
Drupal seems like overkill, but allows us to do more on the content management. I already have one site up and running Drupal, but haven’t looked at the Wiki integration.
As the drupal wiki engine is a conversion of the PhpWIki, we’d just as good go for PhpWiki.
Due to a recent announcement of the sourceforge.net team saying that all file based programs should use the database services:
Group Directories are Read-Only: The project web servers mount project group directories read-only. The following means are available for storing writable data (i.e. for project applications):
- Place the data in the MySQL database provided to your project. Projects are encouraged to make use of our project database service for application data storage.
- Place the data in the /tmp/persistent directory, accessible from and shared between the project shell and web servers. Projects should create their own subdirectory in /tmp/persistent and make frequent backups of the data. We strongly discourage the use of file-writing applications with our services, due to the security implications of our shared web environment. Users of applications in the project web services that require file-writing are strongly encouraged to look for alternatives that can use a MySQL database for data storage instead.
As such we are searching for a replacement of our Wicket Wiki. There are a few features we need:
If anybody knows of an alternative WIki, please leave a message here, or mail the Wicket development mailinglist.
Just installed the SubVersion integration plugin for Visual Studio, so finally we are killing two birds with one stone:
I also tried to shop for the new Pragmatic Version Control using SubVersion, but my credit card wasn’t accepted, probably my new PowerMac has maxed out the card.
For my current project, I need to work with MS .NET. The project already uses NHibernate and NUnit, both of which I’m familiar with in the Java world.
Although I’m not looking forward to develop mostly in .NET, I anxious to see what .NET does right, and how we can apply that knowlegde for Wicket. Creating a Wicket.NET does’t sound that appealing, though. Microsoft already has done a good job at creating a component framework, so probably no need for yet another component framework.
At the moment, I’m already appalled by the installation of the Visual Studio .Net 2003 Architect program. I’m already 2 1/2 hours under way installing the prerequisites (3 times reboot!), security patches (yet another reboot) and installing Visual Studio itself (20% under way)….