Developing a general groupware platform in Zope/Python
Does anyone think it would be practical/feasible to develop a groupware platform in Zope at this point? I'm thinking very big here, taking it to heights that Worldpilot never mentioned, linking email, workflow, filestorage, newsgroups, project management, contacts, journals, Web presence, jabber messaging, calendaring, and Web service interfaces. Following the development of Zope 3 and component architecture, things are looking very promising. The combination of Python 2.2 and Zope 3 could be a *major* glueing layer between multiple service backends (like IMAP, LDAP, SQL, Jabber, etc.), and something like this could probably be attemptable using that as a toolbox. I'm building some of the components already, such as vCard/iCalendar python libraries, and the possibilities of using Zope to do groupware stuff is very exciting. The type of platform I envision would enable (real-world) community groups to take advantage of all the useful groupware services afforded to companies without having to setup Exchange or Domino. phpGroupWare has the right idea, and I believe that if it can be done in PHP, it can seriously be done in Zope. Should I hold off for a while, and let Zope 3 gel some more, or am I completely off my gourd in attempting this? I've gotten some inspiration from that CrankShaft Zope product from Spoke Technologies. Does anyone know what happened to them, anyways? This is the sort of thing I'd like to emulate, only it would be an open-source platform and target community groups, grassroot activists, and small non-profit agencies. Thanks in advance, Eron --- [This E-mail scanned for viruses by Declude Virus]
Eron Lloyd wrote:
Does anyone think it would be practical/feasible to develop a groupware platform in Zope at this point?
I think that is not only possible, but a very logical idea. One thing is being able to publish web pages. But in the future we will need to publish emails, calendar items, news, content etc. We will need to keep trakc of who has gotten what information, and follow information flow in it's own little thread. Like a CRM system. And there is no reason why any kind of comunication should be left out of the system. Imagine: You publish an article on the website. From your list of users you either select some of them that you know are interrested in the article, or they have added themself to a mailing list. So they get the news that the article is posted. Some of them read it. Some of them comments the article on the website, other send you an email. Some icq's or Jab' a comment. A few journalists phone you up and talks to you about an interview or more info. A company calls because they want you to do a presentation. You make appointments with them and add them to your calendar. Normally all this information would end up in different mailboxes scattered all around. It would be so nice if all of that comunication would be stored in one place. Especially if we expand that little scenario to a whole company with different people on the inside talking to different people on the outside.
Should I hold off for a while, and let Zope 3 gel some more, or am I completely off my gourd in attempting this?
Hmm ... You should definitely not start doing it in Zope 3 at this time. Perhaps do version 0.1 in the current Zope version, and then move it when Zope3x becomes stable?
I've gotten some inspiration from that CrankShaft Zope product from Spoke Technologies. Does anyone know what happened to them, anyways? This is the sort of thing I'd like to emulate, only it would be an open-source platform and target community groups, grassroot activists, and small non-profit agencies.
Any group where many to many comunication is going on would benefit from such a system. regards Max M
Should I hold off for a while, and let Zope 3 gel some more,
To be honest, you usually have to do everything wrong once, before doing it correctly. So unless you already have had one attempt at writing this for Zope, you shouldn't hold off. :-)
or am I completely off my gourd in attempting this?
Not at all.
Should I hold off for a while, and let Zope 3 gel some more, or am I completely off my gourd in attempting this?
No, and no. :^) Some more resources on the net. Zope related: Proiektor (from Iuveno) http://demo.iuveno-net.de/iuveno/Products/Proiektor Amphora Light http://www.amphora.ee/freeware/ Not Zope related: Jon Udell, author of "Practical Internet Groupware" http://udell.roninhouse.com/ Brainware http://dev.brainworkers.net/ The last one is because I know the guys. ;^) It doesn't look like much, but there is interesting theory on the main site. Philosophy http://www.brainworkers.net/eng/philos_eng.html Documents http://www.brainworkers.net/eng/dowload_eng.html -- "I was wondering if there's any kind of definitive nickname for Perl programmers, the way we call ourselves Pythonistas?" - Aahz Maruch "Masochists." - Daniel Klein Nicola Larosa - nico@tekNico.net
On Tue, Mar 19, 2002 at 07:26:12PM -0500, Eron Lloyd (lloyd@lancaster.lib.pa.us) wrote:
I'm building some of the components already, such as vCard/iCalendar python libraries, and the possibilities of using Zope to do groupware stuff is very exciting. The type of platform I envision would enable
Do you have those libraries in public CVS? I know someone was working on Python wrappers for libical a while back, but I don't know how far they got. srl -- Shane Landrum (srl AT boston DOT com) Software Engineer, boston.com
I am lobbying to get Cookie Authentication and a User Properties API into Zope 2.6 for exactly this reason. This would allow you to store/capture user properties, whether preferences, profile, or CRM data as properties of the user. Having it part of acl_users would add additonal extensibility and security, rather than creating new user databases. Standardizing an API will stop the proliferation of conflicting User Products trying to do the same things and "allow the community to move on..." from wasting cycles on redundant infrastructure issues to get to the next level of User Property management and developing more personalization products. This data could be stored in properties with support for vCard import/export. Please add your voice to the mix. Maybe someone else can scream louder than me. Cheers, Trevor
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Shane Landrum Sent: Wednesday, March 20, 2002 9:17 AM To: Eron Lloyd Cc: zope@zope.org Subject: Re: [Zope] Developing a general groupware platform in Zope/Python
On Tue, Mar 19, 2002 at 07:26:12PM -0500, Eron Lloyd (lloyd@lancaster.lib.pa.us) wrote:
I'm building some of the components already, such as vCard/iCalendar python libraries, and the possibilities of using Zope to do groupware stuff is very exciting. The type of platform I envision would enable
Do you have those libraries in public CVS? I know someone was working on Python wrappers for libical a while back, but I don't know how far they got.
srl -- Shane Landrum (srl AT boston DOT com) Software Engineer, boston.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
You're not doing your lobbying in the right place, unfortunately... on the maillist, nobody can hear you scream. ;-) You should add this to the Zope 2.6 proposed features list at http://dev.zope.org/Wikis/DevSite/Projects/Zope2.6/ProposedFeatures, then find someone to design and implement it or do so yourself. Note that something like this is a fairly major effort and probably requires a set of proposals in the fishbowl as a result. ----- Original Message ----- From: "Trevor Toenjes" <zope@toenjes.com> To: "Shane Landrum" <srl@mail.boston.com>; "Eron Lloyd" <lloyd@lancaster.lib.pa.us> Cc: <zope@zope.org> Sent: Wednesday, March 20, 2002 10:59 AM Subject: RE: [Zope] Developing a general groupware platform in Zope/Python
I am lobbying to get Cookie Authentication and a User Properties API into Zope 2.6 for exactly this reason.
This would allow you to store/capture user properties, whether preferences, profile, or CRM data as properties of the user. Having it part of acl_users would add additonal extensibility and security, rather than creating new user databases.
Standardizing an API will stop the proliferation of conflicting User Products trying to do the same things and "allow the community to move on..." from wasting cycles on redundant infrastructure issues to get to the next level of User Property management and developing more personalization products.
This data could be stored in properties with support for vCard import/export.
Please add your voice to the mix. Maybe someone else can scream louder than me.
Cheers, Trevor
-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Shane Landrum Sent: Wednesday, March 20, 2002 9:17 AM To: Eron Lloyd Cc: zope@zope.org Subject: Re: [Zope] Developing a general groupware platform in Zope/Python
On Tue, Mar 19, 2002 at 07:26:12PM -0500, Eron Lloyd (lloyd@lancaster.lib.pa.us) wrote:
I'm building some of the components already, such as vCard/iCalendar python libraries, and the possibilities of using Zope to do groupware stuff is very exciting. The type of platform I envision would enable
Do you have those libraries in public CVS? I know someone was working on Python wrappers for libical a while back, but I don't know how far they got.
srl -- Shane Landrum (srl AT boston DOT com) Software Engineer, boston.com
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
participants (7)
-
Chris McDonough -
Eron Lloyd -
Lennart Regebro -
Max M -
Nicola Larosa -
Shane Landrum -
Trevor Toenjes