Alec Mitchell wrote:
On Dec 19, 2007 1:07 PM, Martijn Pieters [EMAIL PROTECTED] wrote:
On Dec 17, 2007 1:36 AM, Laurence Rowe [EMAIL PROTECTED] wrote:
Inspired by Alec's plip #217, I'd like to propose making workflow
history/status storage fully pluggable.
Andreas Zeidler wrote:
On Dec 20, 2007, at 9:04 AM, Raphael Ritz wrote:
[..]
1. Do we give our votes here via the list or on the
website as comment or both?
i'd prefer them to be on the plip pages themselves. that'll make
counting and accepting plips much easier.
OK, then we need to
Hi,
don't know whether this is even submitted for 3.1
http://plone.org/products/plone/roadmap/197
but I agree with Christian that we should not include
a third-party library literally in the Plone core source
distribution.
+1 on this PLIP from me anyways.
Raphael
Raphael Ritz wrote:
Hello again,
while PLIP 192 (Vice Outbound Syndication)
http://plone.org/products/plone/roadmap/192
isn't even submitted to 3.1 (AFAICT) it contains
a point that's worth noting and that might go
into 3.1 IMHO. It's about changing the way the
RSS link is handled. Making
Martin Aspeli wrote:
Thierry Benita wrote:
Hi,
I propose to include the File Preview feature in next plone release.
It is a non intrusive feature that doesn't need to migrate anything in
order to work out of the box.
http://plone.org/products/plone/roadmap/199
IMHO, the PLIP should specify
Hi guys,
I have two, somewhat related questions:
- For pretty much all of my PLIPs, I'll be changing one package only.
I suspect many Plone 3.1 PLIPs will be the same. I can obviously create
a buildout (copying ploneout/branches/3.0 and changing the svn:externals
in src/ to point to my
Hi,
I just put some documentation on the implementation of PLIP 203 up on
the PLIP page (http://plone.org/products/plone/roadmap/203).
I would encourage others to do the same! Perhaps the framework team
should insist on some documentation?
Short of producing or updating how-tos or
