Nothing as the prospect of releasing to the general public to make you work harder. I've just finished porting the excellent Kitten's Spaminator to WPFF. I did not test very thoroughly (it's a 0.1 alpha release after all), but it seems to work. I also fixed a few minor things and released wpff-0.1a2.tar.gz, if you try it let me know.
Here is the ChangeLog for this release.
-
2004-11-28 - ludo includes/post.php: insert comment before displaying comments
-
2004-11-28 - ludo config.php, includes/mail.php, includes/post.php, styles/default.css, templates/default/en_US.UTF-8/index.xml, templates/default/en_US.UTF-8/post.xml: spam check and fields/labels names in English
-
2004-11-28 - ludo classes/Paging.php: comment header
-
2004-11-27 - ludo templates/default/en_US.UTF-8/footer.xml: developers
Make sure you're tracking my CVS if you want to keep spaminator current.
Will do, thanks for a great work on Spaminator.
I like what you are doing. Went through your code (index.php) and it's clean and very nice. Keep up the good work :)
Do you have a roadmap for what you are planing to include ? Muli blog maybe ?
PerS yes, I have a tentative roadmap which is heavily influenced by a few things: my involvement with the blogs for which I started this whole project (such as this one), my day job, etc.
The first thing I am going to do is integrate the new features I have added to the commercial blogs:
- next/previous links in the home/categories/archives pages, like Engadget does
- rss feeds for categories (Luca has produced a patch for this today), very useful if you feed the "planet" blogs
The second thing I'd like to do is encapsulate a few things inside index.php and make it more modular, so that you can choose whether to use next/previous links, etc. and there's less chance of overriding important variables if you hack on the source code (no namespaces in PHP unfortunately)
Then depending on what people asks for I would like to write the backend, which will be a multiblog backend based on a common, pluggable user base and roles a la Zope (that's the idea, Zope is better ofc). I have already laid out the DDL for the main tables, and have a working modular framework that provides the basic functionality (authentication, profiling, menu/header support, etc.) for the single administrative modules (manage users / blogs / posts etc.).
The backend will be more "architected" as there will be less need for speed, but I hope to have a clean and performant infrastructure anyway.
So much one want to do and so little time, I know the problem.
The roadmap looks good, and if you need someone asking for the multiblog backend, I do :)
So we're two people voting for the backend :)