[PLIP-Advisories] Re: [Plone] #9272: Exposing and editing Dublin Core properties
#9272: Exposing and editing Dublin Core properties ---+ Reporter: jaroel |Owner: jaroel Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Templates/CSS | Resolution: Keywords: | ---+ Comment(by jaroel): Ready for review -- Ticket URL: http://dev.plone.org/plone/ticket/9272#comment:25 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by elvix): Reducing the scope to having the interface and implementation available, but not changing all templates for Plone 4. That is simply too much work to be done on time. -- Ticket URL: http://dev.plone.org/plone/ticket/9327#comment:18 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by elvix): (In [28627]) PLIP-implementation status document for Contentlistings interface. refs #9327 -- Ticket URL: http://dev.plone.org/plone/ticket/9327#comment:19 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9258: Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget
#9258: Replace Products.ATReferenceBrowserWidget with archetypes.referencebrowserwidget +--- Reporter: tom_gross |Owner: tom_gross Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Archetypes | Resolution: Keywords: | +--- Comment(by tom_gross): (In [28640]) added plip outline for PLIP 9258 (refs #9258) -- Ticket URL: http://dev.plone.org/plone/ticket/9258#comment:13 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Description changed by timo: Old description: A proposal for an improved commenting infrastructure for Plone. == Contents == 1. Motivation 2. Proposal 3. Implementation 4. Deliverables 5. Risks 6. Progress Log 7. Participants == Motivation == The current Plone discussion framework is very basic and lacks functionality that is common in many Content Management Systems and blogs these days. Hence, third party developers feel the need to write their own commenting framework (e.g. qPloneComments and iqpp.plone.commenting). This leads to two major drawbacks. First, the comments are inconsistent within a single Plone site and second, the same administrative works as do be done twice. The motivation for this PLIP is to provide an easy to use and adjustable comment system using the existing services of Plone. Additionally to provide the possibility to re-use the commenting framework for third party products (e.g., if a developers feels the need for independent options for their product). In addition to the main goal, there are requirements for a state-of-the- art comment system. The Wordpress system may be used as an example and gives guidelines for a new system: * Moderation: It should be possible to enable moderation so that every comment has to be reviewed before publishing. * E-Mail notification: It should be possible to enable a confirmation email to be sent to the commenter to confirm the comment. * Captcha Support: Captchas or math questions should be supported and should be an option, e.g. 1+1 = 2 * Spam Protection: Akismet and other means of identifying spam should be supported. * Mass Editing Screens: Like in Wordpress, views for handling all comments of a subtree are useful to moderate comments or check their spam state. * Configurable Commenting Forms: It should be possible to decide which fields do actually show up in the form. * Extensibility: It should be possible for components to extend the comment form and the comment handling/workflow. An example is a plug-in which allows commenters to subscribe to further comments via email. == Proposal == As part of the Google Summer of Code 2009, Timo Stollenwerk (with Martin Aspeli as mentor) is developing a new commenting package. Martin set up the basic commenting infrastructure and made the basic design decisions for a zope3ish commenting framework (forms, views, adapters) which can be used by any content type. == Implementation == The plone.app.discussion package already has been created with the following [http://svn.plone.org/svn/plone/plone.app.discussion/trunk/plone/app/discussion/PRINCIPLES.txt architectural principles]: * Discussion items have a portal_type * Discussion items are cataloged * Discussion items are subject to workflow and permissions * Discussion items are light weight objects * Optimise for retrieval speed * Settings are stored in plone.registry * Forms are constructed using extensible z3c.form forms * Discussion items are stored in a BTree container * Discussion items are accessed using a dict-like interface * Discussion items are retrieved in reverse creation date order * Discussion items do not need readable ids * Discussion items send events == Deliverables == The basic commenting infrastructure is already in place. On August 24th, when Google Summer of Code ends, the plone.app.discussion package will be in a state that it can replace the current Plone commenting system. This doesn't necessarily mean that the system will be feature complete, but that the package will provide the basic features for a state-of-the-art commenting system This means, it is well tested and well documented, and migration of existing comments is possible. == Risks == * Already existing comments have to be migrated without restrictions. * There might arise conflicts with other, already installed commenting packages. Thus we have to look at these and make them work. == Progress log == We set up a story-based project planning tool, to manage the project and to track the progress: http://www.pivotaltracker.com/projects/15135 * GSoC started (2009-04-23) * Basic commenting infrastructure is in place (2009-05-13) * First alpha release 1.0a1 (2009-06-07) == Participants == * Timo Stollenwerk * Martin Aspeli * Jon Stahl ??? * David Glick ??? * Lennart Regebro ??? New
[PLIP-Advisories] Re: [Plone] #9324: Use Amberjack to offer guided help for first-time users
#9324: Use Amberjack to offer guided help for first-time users ---+ Reporter: limi |Owner: sknox Type: PLIP | Status: assigned Priority: n/a|Milestone: 4.0 Component: Documentation | Resolution: Keywords: | ---+ Changes (by massimo): * cc: massimo, amleczko (added) -- Ticket URL: http://dev.plone.org/plone/ticket/9324#comment:27 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #9327: unified interface for lists of content
#9327: unified interface for lists of content +--- Reporter: elvix |Owner: elvix Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by elvix): (In [28655]) branc for plip implementation refs #9327 -- Ticket URL: http://dev.plone.org/plone/ticket/9327#comment:21 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8801: Move action icon support into actions, remove CMFActionIcons
#8801: Move action icon support into actions, remove CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by davisagli): (In [28658]) configlet action icons cleanup (refs #8801): * added support for CMF's icon_expr setting on actions of the control panel tool * added support for icon_expr to the control panel GS handler * adjusted the Plone tool's getIconFor to check for an icon from the control panel tool before falling back to the action icons tool * adjusted the default profile to assign configlet icons the new way -- Ticket URL: http://dev.plone.org/plone/ticket/8801#comment:18 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8801: Move action icon support into actions, remove CMFActionIcons
#8801: Move action icon support into actions, remove CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by davisagli): (In [28660]) configlet migration cleanup (refs #8801) * re-add configlet migrations that Hanno had removed * augment the action icon migration to also handle actions provided by the control panel tool -- Ticket URL: http://dev.plone.org/plone/ticket/8801#comment:19 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8814: Replace SecureMailHost with a standard Zope mailhost
#8814: Replace SecureMailHost with a standard Zope mailhost +--- Reporter: hannosch|Owner: alecm Type: PLIP| Status: assigned Priority: n/a |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by alecm): (In [28664]) Branch for PLIP #8814 SecureMailHost removal implementation (refs #8814) -- Ticket URL: http://dev.plone.org/plone/ticket/8814#comment:23 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
[PLIP-Advisories] Re: [Plone] #8801: Move action icon support into actions, remove CMFActionIcons
#8801: Move action icon support into actions, remove CMFActionIcons +--- Reporter: hannosch|Owner: davisagli Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by davisagli): (In [28666]) finish up action icons cleanup (refs #8801): * remove some unused icons * add deprecation warnings when adding, modifying, or retrieving an icon using the action icons tool -- Ticket URL: http://dev.plone.org/plone/ticket/8801#comment:20 Plone http://plone.org Plone Content Management System ___ PLIP-Advisories mailing list plip-advisor...@lists.plone.org http://lists.plone.org/mailman/listinfo/plip-advisories
