Die Meister bedanken sich für Ihre Treue und die gute Zusammenarbeit im Jahr 2009.

Ab 24. Dezember bis zum 10. Jänner sind wir in Winterfrische. Wenn es in der Zwischenzeit was dringendes zu tun gibt, senden Sie uns ein Email an office@webmeisterei.com oder rufen Sie uns einfach an:

Weihnachtshotline +43 5572 908877

Erholsame Feiertage und ein erfolgreiches Jahr 2010.

Gerd Moser, Webmeisterei

PS: Wir verzichten bewusst auf Postwurfsendungen oder Geschenke und haben das Geld, hoffentlich auch in Ihrem Sinne, bedürftigen Einrichtungen zukommen lassen.

ihren neuen Mailcluster. In der Nacht von Gestern auf Heute haben wir unseren neuen Mailcluster in Betrieb genommen. Ein Mailcluster bringt für Unsere Kunden Ausfallsicherheit und Hochverfügbarkeit. Bei einem Ausfall von Rechnereinheiten, werden die Arbeiten von anderen Einheiten übernommen.

In diesem Zuge, haben wie das Mailsystem von Zimbra 5 auf Zimbra 6 gehoben um noch aktueller auf Anforderungen reagieren zu können.

Wir wissen Hochverfügbarkeit ist ein grosses Thema. Niemand kann heutzutage auf Mail und Internet verzichten. So trachten die Meister stets danach die Services für Ihre Kunden zu verbessern.

Eine grossen Dank für die Umsetzung gebührt Julian Golderer und Datenstrom.

We plan to add commenting infrastructure to a portal currently running on plone 3.3.x so I did some research and came up with a (probably uncomplete) list of candidates that will be described below in more detail.

• iqpp.plone.commenting (aka EasyCommenting)
• collective.disqus
• quintagroup.plonecomments (aka qPloneComments)
• collective.discussionplus
• plone.app.discussion

Hope this will kick off a discussion with the product authors / people using them and will help others to decide which package (not) to use.

Summary

I did not look really deep into all of these packages (installed and tested plonecomments and plone.app.discussion) so please feel free to comment and put me into the right direction.

collective.disqus looks promising and has great advantages in the area of social web.
on the other side comments are not as well integrated into plone (eg search) and it’s hard or even impossible? to implement custom notifications or other additional features within your application.

quintagroup.plonecomments is a very mature product with lots of configuration options and notification features.
Editing of comments is possible (maybe there should be a way to turn this evil? feature off).
Comments are compatible with standard plone comments (right?) so they might be migrateable to the new commenting system for plone 4.x (plone.app.discussion).

collective.discussionplus peps up plone’s standard discussion items with workflow while keeping them migrateable to plone.app.discussion later. it’s more leight-weight than plonecomments with the downside of no notifications and less configuration options.

plone.app.discussion is currently in alpha state but offers basic configuration options and a moderation view for batch managing comments. Its much more leightweight than standard plone comment types (plonecomments and collective.dicsussionplus are using). I don’t know how many people are contrubuting currently and i hope timo is still motivated after his plip did not make it into plone 4.0.

I’m not sure if it’s a good idea to use plone.app.discussion in alpha1 state on production servers (comment of the authors welcome). But it seems by using collective.discussionplus or quintagroup.plonecomments (not sure about that) one can migrate all comments with the migration script of plone.app.discussion as soon as there is a more stable release or it even is shipped with plone 4.x

This is just a quick overview, more details for each package follow below. There is a project on coactivate about commenting in plone, too. Founded in 2007 it currently seems to be not very active or completely up to date (eg products like disqus missing) but there are reviews of some other commenting products and a collection of commenting related usecases.

(more…)