[Repoze-dev] how to present repoze

[Chris McDonough]

After an enlightening conversation with Paul about what Repoze is, I  
think I've formed a more solidified opinion about how we might  
present it to the world at large, at least initially.

The suggestion is to use something like the tagline "Deploying Zope  
via WSGI" (as opposed to "Breaking up Zope to use WSGI").  The  
operative word in the tagline is "deploy".  Repoze is currently only  
about 10% about development.  It's 90% about deployment.

For example:

- We're breaking up Zope into smaller individually deployable
   middleware pieces in order to allow people to control the behavior
   of a particular deployment without actually needing to change the
   bits inside of Zope-the-appserver.

- We're going to make it possible to deploy Z3 and Z2 applications in a
   similar way, where at least some of the knowledge about deploying the
   Z2 app bleeds over into deploying the Z3 deployment too.

- Likewise you will be able to deploy Zope technologies without actually
   using Zope-the-appserver by using repoze middleware bits.

- We've packaged up Zope 2 as a library to make it more easily  
deployable
   using setuptools and eggs.

And so on.

The other 10% of Repoze that is in CVS right now is about  
development: writing obob plugins that use Zope-the-library but not  
Zope-the-appserver (like repoze.kiss and repoze.virginia).

I suggest that this 10%, while it's important, should not be used  
immediately to define the Repoze "brand" or "elevator speech" (as  
Paul calls it).

If we do believe it's important to pimp the development pieces more  
immediately, perhaps the development pieces should have a separate  
"brand" (or we give the deployment pieces a different name or  
whatever), so that nobody gets confused about what one or the other is.

- C

_______________________________________________
Repoze-dev mailing list
Repoze-dev at lists.repoze.org
http://lists.repoze.org/mailman/listinfo/repoze-dev