As far as what plugins we should be including in core, I'd suggest goingabout as lean as possible. Here's my first pass: AdminUI Authentication::Password CompressedCSSandJS ErrorTemplates I18N OnlineDocs SkeletonApp UserBasically, anything that people should be using, or which helps a lot inthe first hour of playing with Jifty.
+ 1Do we want to start off with a "recommends" line in the core dist to add "all the plugins that most developers will want" for the first release?
Who wants to branch jifty to do this refactoring?If we're going to do this, I'd like to move us to regular releases at the same time. Parrot has had huge success with a ~large set of release engineers and a monthly release schedule.
Which of you would like to join the releng pool? -j
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ jifty-devel mailing list [email protected] http://lists.jifty.org/cgi-bin/mailman/listinfo/jifty-devel
