Tres Seaver wrote:
> Geoff, we *do* want the Plone developers to participate here. Some of
> the past history we can let pass, in order to share better in the
> future. In general, we would like to see "infrastructure" components
> shared, where possible.
I'm glad to hear it. My sense is that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jens Vagelpohl wrote:
>> We have contributed quite a few bug fixes to CMF, though that has been
>> hampered by problems getting CVS access (I sent in my contributor form
>> over a year ago and have yet to hear anything; as Tres has indicated,
>> this
Jens Vagelpohl <[EMAIL PROTECTED]> wrote:
> Florent: Quick heads-up to me when you're done with your changes,
> please.
Ok I'm done I think.
Heads up for Plone devs (but we were discussing it on #plone):
The change I made impacts the signature of CatalogTool.reindexObject,
which until recently
Alec Mitchell <[EMAIL PROTECTED]> wrote:
> On Monday 01 August 2005 06:55 am, Florent Guillaume wrote:
> > However I'd like to urge the "Plone guys" (95% of which don't bother to
> > read or post in this list) to move their collective butts and actually
> > implement forward-compatibility in Plone
--On 1. August 2005 12:53:20 -0400 Geoff Davis <[EMAIL PROTECTED]> wrote:
On Mon, 01 Aug 2005 17:30:20 +0100, Jens Vagelpohl wrote:
It would help everyone if the CMF side opened up a little
more to ideas coming down from Plone, and if the Plone side stopped
reinventing wheels that would be m
On Monday 01 August 2005 06:55 am, Florent Guillaume wrote:
> However I'd like to urge the "Plone guys" (95% of which don't bother to
> read or post in this list) to move their collective butts and actually
> implement forward-compatibility in Plone itself rather that, once more,
> tying the releas
If we have a go for the beta I suggest cutting the tag and
publishing the release tomorrow morning, about 9am british time.
That way zope.org won't have traffic from the Americas, making it
marginally more responsive ;)
Great, thanks! I am planning to release Plone 2.1 final in 2 weeks.
On 1 Aug 2005, at 17:53, Geoff Davis wrote:
On Mon, 01 Aug 2005 17:30:20 +0100, Jens Vagelpohl wrote:
It would help everyone if the CMF side opened up a little
more to ideas coming down from Plone, and if the Plone side stopped
reinventing wheels that would be much better off (and benefit
ever
On 1. Aug 2005, at 16:24, Jens Vagelpohl wrote:
If we have a go for the beta I suggest cutting the tag and
publishing the release tomorrow morning, about 9am british time.
That way zope.org won't have traffic from the Americas, making it
marginally more responsive ;)
Great, thanks! I am
On Mon, 01 Aug 2005 17:30:20 +0100, Jens Vagelpohl wrote:
> It would help everyone if the CMF side opened up a little
> more to ideas coming down from Plone, and if the Plone side stopped
> reinventing wheels that would be much better off (and benefit
> everyone) in the CMF or other non-Plon
We have contributed quite a few bug fixes to CMF, though that has been
hampered by problems getting CVS access (I sent in my contributor form
over a year ago and have yet to hear anything; as Tres has indicated,
this has been a problem for several other Plone developers as well).
I'm hoping that
> P.S.: I too think that more participation from the main "consumers",
> the Plone developers, is sorely needed on this list.
Rest assured that those of us who are involved in the low-level plumbing
of Plone do read the list regularly.
We have contributed quite a few bug fixes to CMF, though
I learned this morning that the Plone 2.1 RC went out (I am told) with
CMF 1.5.2. The really crucial fix for them (making the pathwalk in
DirectoryView less painfully slow) only really affects people running
from SVN checkouts; OTOH, SVN is the only way to get the RC.
I assume this means they
On 1 Aug 2005, at 16:04, Tres Seaver wrote:
We have been doing it in CPS for a while, in a "CPSCompat"
product. It's
very easy, this is python, we can monkey-patch everything we need.
The problem with that approach is that it introduces the risk that
bugfixes never make it back to the underly
Tres,
Is there anything needed on our end to get them "cleared for access"? I can
assist moving that along if so.
Andrew
--
Zope Managed Hosting
Software Engineer
Zope Corporation
(540) 361-1700
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:zope-cmf-
> [EMAIL PROTECTED] On Beh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Tres Seaver <[EMAIL PROTECTED]> wrote:
>
>>Because the Plone guys are trying to release a 2.1RC at OSCOM, and
>>because it would be sensible for them to use the fixes made since 1.5.2
>>to the 1.5 branch, I'm wondering if we
Tres Seaver <[EMAIL PROTECTED]> wrote:
> Because the Plone guys are trying to release a 2.1RC at OSCOM, and
> because it would be sensible for them to use the fixes made since 1.5.2
> to the 1.5 branch, I'm wondering if we should be tagging a beta of 1.5.3.
>
> Any objections? I may or may not ge
Julien Anguenot wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Godefroid Chapelle wrote:
Hi,
I have nothing against .objects declaration which makes things more
explicit ala Zope3 but having to include .metadata files in the sake of
keeping extension feels really too much.
Would i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Godefroid Chapelle wrote:
> Hi,
>
> I have been working on kupu i18n. This implied i18ning xsl files for the
> drawer.
>
> XSL files now carry the i18n namespace and should be imported as
> FSPageTemplate.
>
> However, FSPageTemplate currently remov
Hi,
I have been working on kupu i18n. This implied i18ning xsl files for the
drawer.
XSL files now carry the i18n namespace and should be imported as
FSPageTemplate.
However, FSPageTemplate currently removes the extension when building
the id. So we cannot simply register .xsl files as FSP
On 1 Aug 2005, at 06:04, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because the Plone guys are trying to release a 2.1RC at OSCOM, and
because it would be sensible for them to use the fixes made since
1.5.2
to the 1.5 branch, I'm wondering if we should be tagging a beta
The following supporters have open issues assigned to them in this collector
(http://www.zope.org/Collectors/CMF).
Assigned and Open
efge
- "CMFSetup: provide non-ascii im- and exports",
[Accepted] http://www.zope.org/Collectors/CMF/292
- "CMFSetup doesn't correctly detect DCWo
22 matches
Mail list logo
