On Wed, Nov 16, 2011 at 16:12, Laurence Rowe wrote:
> While I think there is definitely scope for simplifying the mix of
> competing skin concepts in the Zope/CMF/Plone space, we need to be
> careful not to bite off more than we can chew. We still have a lot of
> CMF skin scripts and templates in
Hi Lennart,
I'm not sure if you're not mixing different issues here.
Am 17.11.2011, 11:35 Uhr, schrieb Lennart Regebro :
> Absolutely. Getting rid of CMFSkins is a part of getting rid of CMF,
> not a part of moving to Zope 4. Different issues.
I assume you are referring to removing Plone's depe
Hi,
I have a bunch of External Methods I'd like to make available in a skin
form, and which reload in the same way a page template would if it was
modified and the server was in debug mode.
What's the recommended product for enabling this now?
-Morten
___
On 17 November 2011 11:28, wrote:
> Hi,
>
> I have a bunch of External Methods I'd like to make available in a skin
> form, and which reload in the same way a page template would if it was
> modified and the server was in debug mode.
External methods should not require restarts either.
> What's
Along with David Glick, I would like to volunteer for the Zope 4
release management role, where I would take responsibility for
producing the initial release of Zope 4 and David would then take over
for the maintenance releases.
In doing so, I thought it would be helpful to set out our
understandi
On Thu, Nov 17, 2011 at 11:52, Charlie Clark
wrote:
> Hi Lennart,
>
> I'm not sure if you're not mixing different issues here.
>
> Am 17.11.2011, 11:35 Uhr, schrieb Lennart Regebro :
>
>> Absolutely. Getting rid of CMFSkins is a part of getting rid of CMF,
>> not a part of moving to Zope 4. Differ
Here's my current understanding of the Zope 4 roadmap.
Zope 4
--
Significant progress has already been made on the following features
and I expect they should all land in time for a Zope 4 release:
- Storing parent pointers (elro, davisagli): we have a branch of Zope
that changes OFS to sto
Hi,
On 17 November 2011 12:25, Laurence Rowe wrote:
> Along with David Glick, I would like to volunteer for the Zope 4
> release management role, where I would take responsibility for
> producing the initial release of Zope 4 and David would then take over
> for the maintenance releases.
w00t :-
On 17 November 2011 14:46, Laurence Rowe wrote:
> Here's my current understanding of the Zope 4 roadmap.
>
>
> Zope 4
> --
>
> Significant progress has already been made on the following features
> and I expect they should all land in time for a Zope 4 release:
>
> - Storing parent pointers (e
On Thu, Nov 17, 2011 at 7:25 AM, Laurence Rowe wrote:
... (Interesting roadmap snipped)
> This process will necessitate a lot of merging, so I want to propose
> that we move to Git for development (something we found very helpful
> at our recent San Francisco Zope 4 sprint.) I don't have any opi
On 17 November 2011 15:50, Jim Fulton wrote:
> On Thu, Nov 17, 2011 at 7:25 AM, Laurence Rowe wrote:
> ... (Interesting roadmap snipped)
>
>> This process will necessitate a lot of merging, so I want to propose
>> that we move to Git for development (something we found very helpful
>> at our rec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2011 07:25 AM, Laurence Rowe wrote:
> Along with David Glick, I would like to volunteer for the Zope 4
> release management role, where I would take responsibility for
> producing the initial release of Zope 4 and David would then take
> ov
On 17/11/2011 16:32, Tres Seaver wrote:
> Note that this question is *not* suitable for "loudest voice on zope-dev
> wins" ressolution. The software belongs to the Zope Foundation, which
> will make any such decision.
Small point: the software is open source and anyone who wants can
maintain it
On 17 November 2011 16:32, Tres Seaver wrote:
>> * Zope 4 will not seek to innovate in itself but encourage innovation
>> in software components shared with the wider Python web community.
>
>
> I smell something funny in here: if we aren't innovating, why are we
> making the effort?
The innova
On 17 November 2011 16:32, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/17/2011 07:25 AM, Laurence Rowe wrote:
>
>> Along with David Glick, I would like to volunteer for the Zope 4
>> release management role, where I would take responsibility for
>> producing the
On 17 November 2011 15:23, Martin Aspeli wrote:
> On 17 November 2011 14:46, Laurence Rowe wrote:
>> Here's my current understanding of the Zope 4 roadmap.
>>
>>
>> Zope 4
>> --
>>
>> Significant progress has already been made on the following features
>> and I expect they should all land in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2011 01:01 PM, Martin Aspeli wrote:
> On 17 November 2011 16:32, Tres Seaver wrote:
>>> * Zope 4 will not have a release cycle independent of Plone. Zope
>>> 4 only exists as a transitional path for Zope 2 based applications
>>> and experien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2011 02:05 PM, Laurence Rowe wrote:
> On 17 November 2011 15:23, Martin Aspeli
> wrote:
>> On 17 November 2011 14:46, Laurence Rowe wrote:
>>> - Move authentication out to WSGI middleware.
>>
>> +1 - anything we can do to make AccessCont
On 17 November 2011 19:45, Tres Seaver wrote:
> Again, this is a choice to be made by the foundation: any polling will
> be done by the members of the foundation (this might be the biggest
> non-election item on the agenda for the next annual meeting).
When is the next annual meeting?
Laurence
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/17/2011 03:14 PM, Laurence Rowe wrote:
> On 17 November 2011 19:45, Tres Seaver wrote:
>> Again, this is a choice to be made by the foundation: any polling
>> will be done by the members of the foundation (this might be the
>> biggest non-elect
On 17 November 2011 20:20, Tres Seaver wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11/17/2011 03:14 PM, Laurence Rowe wrote:
>> On 17 November 2011 19:45, Tres Seaver wrote:
>>> Again, this is a choice to be made by the foundation: any polling
>>> will be done by the members
This is the summary for test reports received on the
zope-tests list between 2011-11-16 00:00:00 UTC and 2011-11-17 00:00:00 UTC:
See the footnotes for test reports of unsuccessful builds.
An up-to date view of the builders is also available in our
buildbot documentation:
http://docs.zope.org/
On Thu, Nov 17, 2011 at 20:57, Tres Seaver wrote:
> FWIW, the port to Python3 of substantial existing web framework code is
> already a dubious proposition: nearly everybody doing it these days is
> suffering pain (making their own code more complicated by straddling) in
> order to gain hypotheti
* Zope tests summarizer [2011-11-18 02:00]:
> [2]FAILED ZTK 1.0dev / Python2.4.6 Linux 64bit
>https://mail.zope.org/pipermail/zope-tests/2011-November/052798.html
> Module: zope.publisher.tests.test_testing
>
> File
> "/home/ccomb/ztk1.0dev-slave/Python2.4.6-Linux-64bit/build/src/
Wolfgang Schnerring wrote:
> Thus, I'm really confused why the builder for ZTK 1.0 is picking this up,
> I've only bumped the version of zope.publisher in toolkit/trunk, nowhere
> else.
>
> Can somebody enlighten me what "ZTK 1.0dev" actually builds?
See the [sources] section including comment:
ht
25 matches
Mail list logo
