[Repoze-checkins] r856 - www/trunk/blog.repoze.org/entries

[Chris McDonough]

Author: Chris McDonough <chrism at agendaless.com>
Date: Sun Mar 23 03:40:59 2008
New Revision: 856

Log:
Six months of repoze.


Added:
   www/trunk/blog.repoze.org/entries/sixmonthsofrepoze.txt

Added: www/trunk/blog.repoze.org/entries/sixmonthsofrepoze.txt
==============================================================================
--- (empty file)
+++ www/trunk/blog.repoze.org/entries/sixmonthsofrepoze.txt	Sun Mar 23 03:40:59 2008
@@ -0,0 +1,120 @@
+Six Months of Repoze
+#label general
+<h4> Six Months of Repoze </h4>
+
+<p> <a href="http://repoze.org">Repoze</a> is now roughly six months
+old and it's a pretty good time for some self-analysis.  What have we
+done?  What are we doing?  What do we want to do?  </p>
+
+<h5> What have we done? </h5>
+
+<ul>
+
+  <li>We've <a
+  href="http://svn.repoze.org/repoze.zope2/trunk/">reimplemented the
+  Zope 2 publisher</a>, so Zope 2 applications such as Plone can be
+  run without modification within a WSGI environment</li>
+
+  <li>We've successfully externalized features Zope such as <a
+  href="http://svn.repoze.org/repoze.tm/trunk/">transaction
+  management</a>, <a
+  href="http://svn.repoze.org/repoze.retry/trunk/">conflict error
+  retry</a>, <a href="http://svn.repoze.org/repoze.vhm/trunk/">virtual
+  hosting services</a>, and <a
+  href="http://svn.repoze.org/repoze.who/trunk/">identification and
+  authentication</a>, <a
+  href="http://svn.repoze.org/repoze.errorlog/trunk/">error
+  logging</a>, and <a
+  href="http://svn.repoze.org/repoze.profile/trunk/">profiling</a>
+  into WSGI middleware, so they can be reused outside the Zope stack
+  in a way that's largely familiar to Zope and non-Zope users
+  alike.</li>
+
+  <li>We've packaged up <a
+  href="http://svn.repoze.org/repoze.plone/trunk/">Plone</a>, <a
+  href="http://svn.repoze.org/repoze.grok/trunk/>Grok</a>, <a
+  href="http://svn.repoze.org/repoze.trac/trunk/">Trac</a>, and <a
+  href="http://svn.repoze.org/repoze.django/trunk/>Django</a> so they
+  can be used without much effort in a Repoze WSGI environment.</li>
+
+  <li>We've created bridges to traditionally-CGI applications like <a
+  href="http://svn.repoze.org/repoze.mmwsgi/trunk/">Mailman</a> so
+  they can be served up via WSGI servers.</li>
+
+  <li>We've created applications like <a
+  href="http://svn.repoze.org/repoze.kiss/trunk/">repoze.kiss</a>,
+  which are "Zope-like", but do not use any ZODB.</li>
+
+  <li>We've evangelized <a
+  href="http://www.openplans.org/projects/deliverance/introduction">Deliverance</a>
+  as a theming mechanism.</li>
+
+  <li>We've reached out to other Python web projects like TurboGears,
+  Pylons, and Django, attempting to reuse some of their components,
+  and we've made them aware of ours.</li>
+
+  <li>We've given many, many talks at Zope/Plone/Python user groups
+  and conferences, attempting to bring more folks into the fold </li>
+
+  <li>We've created <a
+  href="http://svn.repoze.org/buildouts/">buildouts</a> using
+  zc.buildout for Plone and Trac.</li>
+
+</ul>
+
+<h5> What are we doing? </h5>
+
+<ul>
+
+  <li>We're playing around with exernalizing <a
+  href="http://svn.repoze.org/repoze.decsec/trunk/">declarative
+  security</a>, so we can better integrate dissimilar WSGI applications using the same security model.</li>
+
+  <li>We're attempting to create alternate <a href="http://svn.repoze.org/repoze.browserid/trunk/">sessioning</a> components for use under WSGI stacks.</li>
+
+  <li>We're working Repoze into our (Agendaless') own customer deployments</li>
+
+</ul>
+
+<h5>What we intend to do </h5>
+
+<ul>
+
+  <li>We intend to do more evangelism via presenting to
+  Python/Zope/Plone user groups and conferences.</li>
+
+  <li>We intend to reach out more to other web projects by helping
+  them integrate Repoze code into their own projects.</li>
+
+  <li>We intend to push for Plone (and possibly Zope 2) to base a
+  release on Repoze technologies.</li>
+
+</ul>
+
+<h5> Where we need help </h5>
+
+<p> We need help a) evangelizing, b) bringing things to ground and c)
+maintaining our various web presences.  On the evangelism front, we
+need Python folks to understand that Repoze is <b>not</b> just about
+Zope, instead it's a generically useful set of WSGI components
+inspired by features of Zope.  We need to get Zope people excited
+about a future that allows them to make use of best-of-breed
+components created by Python web developers that are not Zope
+developers.  We need to get Python folks excited about the fact that
+the Zope community is reaching out to the larger Python web
+development community by making it possible for them to use components
+that Zope folks have been using for years without knowing anything
+whatsoever about Zope itself.  We need to improve Deliverance's
+conditional theming support.  We need Zope and Plone folks to start
+using repoze.zope2 and Deliverance "in anger" to start to bring things
+to ground.  We need help maintaining repoze.org, maintainly to keep
+content fresh.  We need more developers to start contributing code to
+the Repoze repository.  </p>
+
+<p> If
+you want to help doing any of these things, please join the <a
+href="http://lists.repoze.org/">repoze-dev</a> maillist and the <a
+href="irc://irc.freenode.net/#repoze">#repoze IRC channel on
+freenode.net</a>, and yell! </p>
+
+<p><cite>-Chris</cite></p>