[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 description:
[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: | ---+ Comment(by massimo): (In [28758]) PLIP-implementation status document for amberjack implementation. refs #9324 -- Ticket URL: http://dev.plone.org/plone/ticket/9324#comment:28 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): ready for review -- Ticket URL: http://dev.plone.org/plone/ticket/9327#comment:22 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] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by smcmahon): (In [28781]) Interpolation now working with Minimal Dublin; refs #9256 -- Ticket URL: http://dev.plone.org/plone/ticket/9256#comment:22 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
[Framework-Team] Minutes: 12 August 2009
Highlights from the meeting -- * We'll include the well-formed-XHTML PLIP even if it's partly done. * Finished PLIPs are marked at http://spreadsheets.google.com/ccc?key=rR4UAIObeTZtdUExfYophHw on the Implementation Reviewers sheet by a green color in the row background. * All the Plone tests now pass (when run in known-to-be-compatible groups by a script Hanno wrote). To do -- * PLIP implementation deadline is Sunday the 16th. Cheers, Erik Rose ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[PLIP-Advisories] Re: [Plone] #9256: Expand variable substitution in mailing action of plone.app.contentrules
#9256: Expand variable substitution in mailing action of plone.app.contentrules ---+ Reporter: smcmahon |Owner: smcmahon Type: PLIP | Status: assigned Priority: minor |Milestone: 4.0 Component: Content Rules | Resolution: Keywords: | ---+ Comment(by smcmahon): (In [28787]) Use plone.stringinterp for variable expansion in mail action. refs #9256 -- Ticket URL: http://dev.plone.org/plone/ticket/9256#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
Re: [Board] Re: [Framework-Team] Re: [Plone 4] PLIP #9249 Add TinyMCE as the default visual editor
2009/7/29 Martin Aspeli optil...@gmail.com 2009/7/29 Jon Stahl jonst...@gmail.com: So, my question is: what qualifies as explicit agreement? Does it have to be on the permanent record in some manner? In our business, an email that you keep tends to be enough. I would: - Ask the relevant people by email - Ask them to reply by email giving explicit consent - Store those emails forever - Make a note in a CONTRIBUTORS.txt or similar that these people consented on a particular date If that's ever in dispute, you can go back to those emails. I don't see a reason for any kind of wet signature so long as they've signed the contributor agreement. We're not *trying* to be difficult. :) +1. One thing that SFLC taught us is that any lawyer will always advice you to have their name signed in blood etc, to make *really* sure that nothing goes wrong. In practice, as long as you can show reasonable intent (and an email should be plenty, if there's forgery going on, that's a different issue), so I think this should be good enough. Keeping the dates in a text file is also convenient. FWIW, Mozilla runs their entire project without a contributor agreement — so we are already way ahead of what most large open source projects do on this front. :) — Alexander ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[PLIP-Advisories] Re: [Plone] #9250: Add jQuery Tools to base install
#9250: Add jQuery Tools to base install +--- Reporter: limi|Owner: smcmahon Type: PLIP| Status: assigned Priority: minor |Milestone: 4.0 Component: Javascript | Resolution: Keywords: | +--- Comment(by smcmahon): (In [28800]) Pick a spot for jqtools in jsregistry. refs #9250 -- Ticket URL: http://dev.plone.org/plone/ticket/9250#comment:29 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
