At Enfold Systems, we put our code in our public svn.  Then it sort of sits there.  This happens to lots of Open Source consulting firms.  Its easy to put it in your own SVN repository because you want full control.  Does it really matter that others are using your code?  Its your itch that is being scratched.  Who cares if people dont visit your repository and see your code?  You, the developer - is who should care.

The reason you should care about getting your code into a collective repository is simple, it lowers the bar for cross pollination with other projects and organizations.  See, it takes quite a bit of effort to release software.  You need to write the LICENSE file, README, tests, a webpage that describes its functionality.  Its quite a formal ceremony.  And not exciting if all you did is scratch a itech and want others to discover your software.  This is where the collective's momentum kicks in -- as people start working in the collective; monitoring the collective's check-in mailing list -- you might notice a component that is being worked on that is interesting.  Then you can potentially scratch your itch with someone else's work.  The most slackinest thing that can happen -- reuse of work. 

Anyway - I hope that the code that we contributed and the other 1000 check-ins per month are useful outside the person who is working on the code.  After all - that is what this whole open source thing is -- isnt it?

ATCSVImport

Plone UI for importing CSV files into Archetype based content types.  Very
simple but used on many of our projects.  Have a CSV file where each row
needs to be a content object in Plone?  This is the product for you.

MultiPathIndex

PathIndex was suppose to handle this use case.  The ability to have multiple 
path's indexed in the catalog and being able to query by them.  We used this
on Oxfam America to have content appear in multiple regions.  Then we could
query for all content in a Region and all content in its subregions would show up.
Ultimately this should roll into ExtendedPathIndex.  Very useful.

CaseStudy

A content type that we wrote for plone.net.  Plone.net has been a very interesting
exercise of community/business relationships.  soon we should see a result -- which
is fantastic!  This was a content type that would serve as a "Case Study".

ZipCodeTool

This is a great example of something that should not be a tool.  It should be refactored
into a python library so anyone can use it.  Basically given a zipcode you can ask for
zipcodes in N mile radius.  Used on some of our customer websites.  They love the functionality.

DeprecationWorkflow

This workflow is similar to the standard Plone workflow, with some
minor modifications to account for deprecation (and subsequent review)
of outdated documents.  A Real World workflow.

ContentPortlet

No idea what this is.  I believe its a simple mechanism to edit a portlet
as if it were content.  Probably pretty self explanatory once you install it.

FSReST

For use with any CMF based system, such as Plone.  FSReST is a 
FSObject that supports displaying filesystem based Restructured-Text 
documents.  Makes it effortless to display restructured-text in your website.

ExtendedHistory

This module makes a simple modification, it changes the history that is shown
on a document to include the history from OFS.History.Historical, showing you 
all the edits and changes to a piece of content.
   
Unfortunately the details shown in that changes are still as obscure as the
transaction notes in the history log and don't tell you anything useful.

Well thats it for this weekend.  Not sure if I left anything else out.  There will be quite a few more commits coming as we sort out our repositories.  But I have been looking at some of the amazing stuff in the collective.  Very cool stuff in there.  Lots of rubish but some good stuff.  Other things I suggest you look at:

Teamspace, CMFEditions, LinguaPlone

I'm trying to get our staging system sorted out and pushed into the collective as well.  We currently make releases of it at http://plone.org/products/ensimplestaging .This product needs to be renamed and refactored into z3 adapters.  Its fairly generic and could be immensely useful for lots of other projects.  It basically keeps track of changesets of objects in a folder. 

Dont forget - Plone Symposium in New Orleans.  I hope I will see you there.

Alan Runyan