Hi all,
PloneGazette is good newsletter product for Plone. I'm using it for
sending newsletter to about 4500 users every month. It is fast, easy,
subscribing for anonymous users is simple.
I'm not sure who is maintaining the product, but there are several
branches with interesting functionality which should be merged.
There are 11 branches and I'v tried to review them a bit.
* at-integration-branch - started by gawel and recently mj did some
changes. Branch seems interesting, because rewrites CMF based
PloneGazette to AT based types. I'v never tried this branch yet. Anyone
using it and knows status?
* attopic - active branch (PloneSolutions?). Uses ATTopic instead of
PG/Topic.
* complexity-reduction - base branch for most of other branches :)
* lovely-richreference - introduces NewsletterRichReference type,
addable to Newsletter.
* naro-i18n-fix - my branch started due to problems with non-ascii
characters in Czech language. Fixes unicodeerrors in Plone 2.5 etc.
There is new feature - subscriber search form (fschulze did it recently
in attopic branch too). This double-developed feature started me
thinking about merging branches together. Read README.branch if you are
interested in details.
* persistent-dynamic-content - my branch of previous branch. If you
are using dynamic newsletters, based on (AT)Topic, newsletter in archive
will be always dynamically generated even if some user displays this
newsletter months after original emission date. This branch stores
rendered HTML code in persistent attribute and displays this code
instead of rendering current content. Read README.branch if you are
interested in details.
* pg_custom - most recent branch by alecghica, based on
tags/1.1-pre-final. Source is not copied but imported so it is not
possible to easily track changes. At least there is diff with changes
and description of changes.
I suppressed other, probably obsolete, branches.
I'v tried to merge into trunk: coplexity-reduction + naro-i18n-fix +
persistent-dynamic-content + attopic + lovely-richreference with success
(most problems were in nl translation), other files merged without
significant collisions. All these branches adds some functionality. Only
one collision is two subscriber search forms. ehm.... I included my
version, but it is not problem to remove it and replace with Florian's
version.
I did not include at-integration-branch because types are not compatible
and there is no migration.
So, if you are interested in PloneGazette, please vote :)
Should I commit merged version into trunk?
Should I create another branch ? (review branch)
Should I do nothing and leave branches as is ?
--
Radim Novotny
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
