[jifty-devel] plugin cleanups

Jesse Vincent jesse at bestpractical.com
Tue Mar 11 12:43:05 EDT 2008


> As far as what plugins we should be including in core, I'd suggest  
> going
> about as lean as possible. Here's my first pass:
>
>    AdminUI
>    Authentication::Password
>    CompressedCSSandJS
>    ErrorTemplates
>    I18N
>    OnlineDocs
>    SkeletonApp
>    User
>
> Basically, anything that people should be using, or which helps a  
> lot in
> the first hour of playing with Jifty.


+ 1

Do 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.jifty.org/pipermail/jifty-devel/attachments/20080311/875d407f/attachment.pgp 


More information about the jifty-devel mailing list