contributed plugins
will guaraldi <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
Contributed plugins have been a great thing to have, but a thorn in the side to manage for a few reasons I've opined about over the years. The biggest issue being that most of the contributed plugins don't get changed much, but some of them (comments in particular) are undergoing a lot of changing right now. So we need a distribution method that covers both bases without someone releasing a new contributed plugins pack every couple of weeks. To that end, last night I moved everything around in SVN so that the contributed plugins are organized in the same hierarchical structure as the categories of the plugin registry. Additionally, I added some text to each of the contributed plugins stating that they come in the contributed plugin pack, that the pack doesn't get released very often, and that you can also find versions in the SVN repository. My question is two-fold. First, what problems do you PyBlosxom users have when using contributed plugins? Second, is the "new" distribution method good enough? /will ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642