Hi Dave,I missed this message when I replied to some messages about plugins and their homes.
Sorry for the noise; I agree with what you are saying here, especially with regard to repurposing the old Roller site. As long as it's clear on both sites where active development is done, and what the rationale is for each site, I think it's an excellent solution.
Is a vote needed to formalize this proposal? Craig On Aug 31, 2006, at 9:50 AM, Dave Johnson wrote:
The docs are up-to-date and bugs are under control. Here's an issue I'd like to resolve (and document in the Installation Guide) before the RC: We recently decided to ship only a couple of themes and plugins and we still need to figure out what to do with the themes and plugins that we don't ship with Roller. I'd like to propose that, not only should we remove them from the release, we should also remove them from Apache SVN. We should remove them from SVN and move them to the old Roller project at Java.Net and make them available for download there. Here's why: - We've already re-purposed the old Roller project site as the "Roller Support" site -- to host LGPL components and plugins/themes that depend on LGPL. - The extra themes and plugins aren't essential to the community of developers maintaining Roller. Ideally, Roller should ship with a couple really good themes/plugins and the rest should be provided an maintained by the community of Roller users. - By using the "Struts Applications" model, we can encourage more theme development by the community. Struts team members established a Sourceforge project to host Struts add-ons and contributors who don't necessarily have Apache committer status. - Themes and plugins can use other-licensed components freely, since the Roller Support project is not Apache territory. - Dave
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
