Well, the big project I'm working on is an overhaul of Plucene, the perl port of the Java Lucene search engine library http://lucene.apache.org/. I'm moving a couple things around, but for the most part it should stay as is, and Lucene's pretty well designed.

Beyond that, I'm not sure that it makes sense to constrain development via a severe public-class-all-things-public / devel-class-all-things-devel split. You could do that, but there are bound to be occasions when you wish you could add a protected method to that public class. For sure, it's a good idea to divide responsibility, but unless you take draconian measures, the problem still exists.