[PLIP-Advisories] Re: [Plone] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: closed Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: wontfix Keywords: | +--- Changes (by esteele): * status: assigned = closed * resolution: = wontfix Comment: This PLIP has been rejected for merging into Plone 4.0 The final vote was: Alec Mitchell 0 David Glick 0 Erik Rose - Laurence Rowe +.5 Matthew Wilkes - Ross Patterson -1 The Framework Team felt that the product was not finished enough to be merged at this time. I'd encourage you to continue to pursue your work as an add-on product and please resubmit this PLIP for a 4.x branch if you feel it appropriate. Thank you for your hard work. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:36 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: | +--- Changes (by timo): * cc: t...@zmag.de (added) -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:31 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: | +--- Comment(by timo): (In [30244]) Hide the editable-object border in moderation view. elro review fix. refs #9288 -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:32 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: | +--- Comment(by ldr): Looking at it again today: * @@moderate-comments shows no comments to moderate (I assume this is the indexing bug). - I think it should use the green tabs instead of the fieldsets. - whichever way it needs to tal:define=dummy python:request.set('disable_border', 1) (for green tabs generate your own markup for them, for an example see the users and groups control panel) * Two Login to add comments buttons show up (the second should probably only show if a comment is displayed) * Anonymous commenting bypasses moderation. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:30 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: | +--- Comment(by esteele): Your PLIP has passed the Framework team's initial review. Feel free to discuss any suggested changes either here in the PLIP ticket or on the mailing lists. Final deadline for this PLIP is set for September 30. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#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] #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: | +--- Comment(by cjohansen): No accessibility issues created by new code compared with baseline. Code tested with FAE (http://fae.cita.uiuc.edu/). -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:26 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 description:
[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] #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: | +--- Changes (by grahamperrin): * cc: grahamper...@gmail.com (added) -- Ticket URL: http://dev.plone.org/plone/ticket/9288#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] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: new 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) == Participants == * Timo Stollenwerk * Martin Aspeli * Jon Stahl ??? * David Glick ??? * Lennart Regebro ??? New description: A proposal for an improved commenting
[PLIP-Advisories] Re: [Plone] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by esteele): Approved by FWT vote. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#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] #9288: Improved commenting infrastructure
#9288: Improved commenting infrastructure +--- Reporter: timo|Owner: timo Type: PLIP| Status: new Priority: minor |Milestone: 4.0 Component: Infrastructure | Resolution: Keywords: | +--- Comment(by calvinhp): FWT Vote: +1 much needed and the current implementation makes Plone look low end compared to other similar CMSes. -- Ticket URL: http://dev.plone.org/plone/ticket/9288#comment:17 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