[Framework-Team] Re: PLIP #197: Add FeedParser as external requirement

Martijn Pieters, on 2008-10-03: > On Fri, Oct 3, 2008 at 23:59, Maurits van Rees ><[EMAIL PROTECTED]> wrote: >> The plip is: >> #197: Add FeedParser as external requirement instead of shipping with it >> http://plone.org/products/plone/roadmap/197 >> >> Originally proposed by Christian Scholz in De

Re: [Framework-Team] Meeting up in DC

On Fri, Oct 3, 2008 at 23:17, Steve McMahon <[EMAIL PROTECTED]> wrote: > I asked our conference social planner, JoAnna Springsteen, for > possibilities for a dinner spot where we could meet up Monday night > and actually hear one another. Here are her suggestions. I won't make it to DC and the con

Re: [Framework-Team] PLIP #197: Add FeedParser as external requirement

On Fri, Oct 3, 2008 at 23:59, Maurits van Rees <[EMAIL PROTECTED]> wrote: > The plip is: > #197: Add FeedParser as external requirement instead of shipping with it > http://plone.org/products/plone/roadmap/197 > > Originally proposed by Christian Scholz in December 2007. Seconded > bij Martijn Pie

[Framework-Team] Meeting up in DC

Hi Framework Team, I asked our conference social planner, JoAnna Springsteen, for possibilities for a dinner spot where we could meet up Monday night and actually hear one another. Here are her suggestions. If one or more of these spots sound particularly good or bad, let me or the list know. Som

Re: [Framework-Team] PLIP #240: Improve locking configurability

I'd like to propose PLIP #240 for inclusion in Plone 3.3: http://plone.org/products/plone/roadmap/240 This PLIP is intended to provide several avenues toward addressing the problem of content accidentally getting left in a locked state. +1 for this, although: "David Glick is willing to ser

[Framework-Team] PLIP #197: Add FeedParser as external requirement

Hi, I propose plip 197 for Plone 3.3. Or really for 3.2 as it is a small packaging change which fits well in the overall theme of 3.2. I mentioned that on this list a few weeks ago without reactions. The plip is: #197: Add FeedParser as external requirement instead of shipping with it http://pl

[Framework-Team] Re: PLIP #126: Link type should automatically redirect when accessed directly

Martin Aspeli wrote: David Glick wrote: I've edited an old PLIP that I'd like to propose for 3.3: http://plone.org/products/plone/roadmap/126 This is about making the built-in Link content type redirect to its target when the link is accessed by a direct URL (not just when it appears as a li

[Framework-Team] Re: PLIP #126: Link type should automatically redirect when accessed directly

David Glick wrote: I've edited an old PLIP that I'd like to propose for 3.3: http://plone.org/products/plone/roadmap/126 This is about making the built-in Link content type redirect to its target when the link is accessed by a direct URL (not just when it appears as a link in navigation). N

[Framework-Team] PLIP #187: Working out-of-the-box WebDAV

I would like to propose PLIP #187 for Plone 3.3. I already have pretty much all the work done, in a branch. It just needs polishing and merging. -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 _

Re: [Framework-Team] OT: problems with Gmane misinterpretations of browse back/forward and other key combinations

Previously Graham Perrin wrote: > To seasoned Framework Team users of Gmane, a plea: > > How do I prevent Gmane from misinterpreting key combinations? I see more and more complaints about gmane. Personally I really wish people who just use the mailing list directly instead of using gateway like g