[Framework-Team] Re: [plone4] - Initial PLIP drafts coming in
Jens W. Klein wrote: In your PLIPs you wrote i.e. here https://dev.plone.org/plone/ticket/8593 to remove parts out of Plone the Product. I fully agree to remove features from the core! But I think if we do so, there should be a set of Managed Plone Products. Important add-ons like LinguaPlone or the removed parts should get in a managed by the Plone [Foundation|Team X] state. [...] If current teams structure is not sufficient for this task, we could introduce a new Add-On Team. I think none of the current teams or structures we have is able to do the job of maintaining a list of recommended / proven / better / whatever list. There have been numerous discussions around this topic and various ideas on how to solve this (community rating, automatic metrics, self-certified criteria, ...) but so far there is neither a consensus nor someone dedicated to own the task. I'd very much welcome if someone would step up for this, but I'm not willing to have this block the removal of unmaintained code anymore ;) Hanno ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [plone4] - Initial PLIP drafts coming in
In your PLIPs you wrote i.e. here https://dev.plone.org/plone/ticket/8593 to remove parts out of Plone the Product. I fully agree to remove features from the core! But I think if we do so, there should be a set of Managed Plone Products. Important add-ons like LinguaPlone or the removed parts should get in a managed by the Plone [Foundation|Team X] state. In my opinion major tasks of this group of people are i.e.: * identify important add-ons, * ask the maintainer/author of the add-on if she/he agrees, * manage a list of those add-ons, * do quality assurance on those add-ons * ensure an upgrade path to new plone releases, * look at plips and how they may influence managed add-ons. The list of add-ons should be short and only widely used features should make it onto it. I think here of modules like LinguaPlone, PloneFormGen, Collage, archetypes.schemaextender. IMO it is very important to ensure important add-ons to be compatible with future plone releases. This gives trust to integrators of Plone. Risk: Modules not on this list get underestimated. Which would be wrong. If current teams structure is not sufficient for this task, we could introduce a new Add-On Team. Opinions? -- Jens Klein ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: [plone4] - Initial PLIP drafts coming in
Alexander Limi wrote: On Sat, 20 Dec 2008 12:06:38 -0800, Hanno Schlichting hanno...@hannosch.eu wrote: I've started to write up initial PLIP drafts for the major changes that have already been implemented on SVN trunk and that I want to do for 4.0. They can be found in Trac and are associated with the 4.0 milestone. And here's a first stab at a report to track these: http://dev.plone.org/plone/report/24 Sorry if I missed some discussion/decision on this, but the place for PLIP submission is now trac? Or are these just drafts that will eventually origin PLIP's at plone.org? Ricardo -- Ricardo Alves r...@eurotux.com Eurotux http://www.eurotux.com ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: [plone4] - Initial PLIP drafts coming in
On Sat, 20 Dec 2008 12:06:38 -0800, Hanno Schlichting hanno...@hannosch.eu wrote: I've started to write up initial PLIP drafts for the major changes that have already been implemented on SVN trunk and that I want to do for 4.0. They can be found in Trac and are associated with the 4.0 milestone. And here's a first stab at a report to track these: http://dev.plone.org/plone/report/24 (we should probably add component in the table too, but my SQL-fu is weak ;) -- Alexander Limi ยท http://limi.net ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
