... and COREBlog is now a Plone Product! Perhaps some of you remember, that this blog here used to be a COREBlog instance, cosmetically married via CSS to the rest of the (Plone-based) site until I jumped ship and migrated to Quills. (Holy smokes, that's just been eight months ago, it seems like a lot longer!)

Unfortunately I won't have any time to take a closer look at the new version of COREBlog this week but I'm very much looking forward to it. It has always been a very solid application for me (and provided proper XML-RPC-support from very early on).

Together with KNotes, EasyBlog, SimpleBlog and now COREBlog it's really starting to get crowded ;-) But since all of them are Open Source it just means that all of them will profit!

via Rick Hurst

Update: The question Luis poses in his comment to this entry ("Why is this good?") is a very valid one and made me think more about the issue. For those of you not subscribed to the 'with-comments-feed', here's my reply:

The short answer: I'm an optimist ;-) Seriously, though, I definitely share your concern/uneasiness and readily admit that my optimism has a significant "want to believe" component.

Having said that I still firmly believe that separate projects still have one big benefit over one "master" project, namely that each project can focus on its own way of doing things and its own set of priorities. I mean, these projects exist as separate projects for a reason. I'd rather pour some of the goodness of COREBlog2 into Quills than try to convince COREBlogs author of doing some things "the Quills way", for example.

Also, another good example of "productive sibling rivalry" is the Django vs. TurboGears issue where seemingly both projects have benefited from the stimulous that the other project's spur of development has caused.

To sum it up: I think if everybody is allowed to do stuff their own way (i.e. by having their own project because its fun) the overall satisfaction (and thus productivity) is higher (and more worthwhile to achieve) than if everybody formed a single project (because its "sensible") and had to make compromises.

Does this make any sense or am I just trying to sugarcoat the problem? You tell me ;-)