I'd like to get feedback on two possible visions for the future of
Zope 2 and Zope 3.
1) Our current vision (AFAIK) is that Zope 3 will eventually
replace Zope 2
- There will be lots of overlap between the Zope 2 and Zope 3
lifetimes. (Zope 2 might be supported more or less
forever.)
- Eventually, the gap between Zope 2 and will become very small.
requiring a small leap.
In this vision, Zope 3 would have to become a lot more like
Zope 2, or we would lose features.
2) In an alternate vision, Zope 2 evolves to Zope 5.
- Zope 5 will be the application server generally known as Zope. It
will be backward compatible (to the same degree that Zope 2
releases are currently backward compatible with previous Zope 2
releases) with Zope 2. Zope 5 will similarly be backward
compatible with Zope 3 applications built on top of the current
Zope 3 application server.
Note that Zope 5 will leverage Zope 3 technologies to allow a
variety of configurations, including a Zope 2-like configuration
with implicit acquisition and through-the-web development, and a
Zope 3-like configuration that looks a lot like the current Zope
3 application server. Maybe, there will be a configuration that
allows Zope 2 and Zope 3 applications to be combined to a
significant degree.
- Zope 3 will explode. :)
For many people, Zope 3 is first a collection of technologies
that can be assembled into a variety of different applications.
It is second a Zope 2-like application server. I think that
these folks aren't really interested in the (Zope 2-like)
application server.
Zope 3 will continue as a project (or projects) for creating
and refining these technologies.
(It would probably make sense for this activity to to have some
name other than "Zope". On some level, the logical name would
be "Z" (pronounced "Zed" :). An argument against "Z" is that
it would be hard to google for, but Google handles such queries
quite well and I'd expect that we'd move to the top of Google Z
search results fairly quickly. However, I'll leave naming
decisions to experts. ;)
Advantages of this vision:
- Zope 2 users don't need to leave Zope 2.
- Zope 3 doesn't have to reproduce all Zope 2 features.
- There wouldn't be confusion about 2 Zopes.
It is important that Zope 5 be backward compatible with both Zope 2
and Zope 3, although not necessarily in the same
configuration. Many people are building Zope 3 applications today
and they should not be penalized.
Thoughts?
Jim
--
Jim Fulton mailto:jim@zope.com Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.comhttp://www.zope.org
Hi All,
I see there are no Zope 2.9 releases for Windows.
There probably should be ;-)
What can I do to help with that?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
A while ago, we had some discussion on when to make releases and
how long to support deprecated features. The discussion has died down
so I'll summarize what I think the conclusions were:
- We'll move releases up one month to may and November from June and
December. This means that the next release is scheduled for May and
the next feature freeze is April 1.
- We will support deprecated features for 1 year.
I consider there to be decisions. :)
Jim
--
Jim Fulton mailto:jim@zope.com Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.comhttp://www.zope.org
On 2/28/06, Andreas Jung <andreas(a)andreas-jung.com> wrote:
> - if name[0] == '_':
> + if name.startswith('_'):
Just a question: Is this only a matter of stylistic changes, or is
there some, like, speedup involved?
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
Greetings,
for a product I am writing, i need to experiment with inhibiting
URL-traversal to the methods and subobjects of it. I still wnat the
methods and objects to be available via direct call, for instance:
from a script or template:
container.my_product_instance.some_method(...)
but not
http://some/url/my_product_instance/some_method?...
In effect I am hiding that part of the zodb for external access-
Also, can such a behaviour be imposed on templates (they being methods
really) and Script(Python)s?
Thanks,
/dario
--
-- -------------------------------------------------------------------
Dario Lopez-Kästen, IT Systems & Services Chalmers University of Tech.
Lyrics applied to programming & application design:
"emancipate yourself from mental slavery" - redemption song, b. marley
Python/Zope Dev, Rockville, MD | 60-100k | Relo OK
Job Description: The main part of our development will take place in our Rockville, MD office. We are looking for a developer who will work from this office. The envisioned services are web applications and thorough knowledge and expertise in developing these kinds of applications is essential. We seek core competencies in web application development, both on the client side creating rich internet applications (RIA/AJAX) and on the server side of the application. Fine tuning and scalability expertise is of interest. Next to technical and computer science expertise, the developer should be comfortable in a multi-disciplinary context and should be able to explain technical issues to smart but not-so-technical colleagues. Familiarity with the biomedical domain and language is a plus.
Qualifications: Python / Zope / Java / Object Oriented Programming, HTML / CSS / XML / JavaScript / Rich Internet Applications (RIA / AJAX), Linux / Windows.
Candidates should be willing to work in the MD, VA, D.C. area and be authorized to work in the USA. Relocation assistance provided.
This is an on-site, salaried position in Rockville, MD. Please no offshore or telecommuters.
To be considered, please submit your resume, a paragraph highlighting your Python / Zope experience and your salary requirements to
beau(a)open-source-staffing.com
Python/Zope Jobs: http://groups.yahoo.com/group/pythonzopejobs
Open Source Jobs: http://groups.yahoo.com/group/opensourcejobs
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.1.1/270 - Release Date: 2/27/2006