I was speaking with a coworker here yesterday, and he was saying that one advantage that perl has over python is CPAN. He said that there are tons of python modules out there, but you really have to go looking for them. I've seen a few Products that people have put together here and posted on their own websites. I think it would be good to take the contrib area on the Zope site seriously, so that it will grow into a repository as useful as CPAN. To get things going in that direction requires the cooperation of everyone. If DC can keep the contrib area organized as the number of Products increases, and if people make sure they submit their Products to the site, we'll have the beginnings of CZAN :) Kevin -- Kevin Dangoor kid@ans.net / 734-214-7349
Kevin Dangoor wrote:
I was speaking with a coworker here yesterday, and he was saying that one advantage that perl has over python is CPAN. He said that there are tons of python modules out there, but you really have to go looking for them.
I've seen a few Products that people have put together here and posted on their own websites. I think it would be good to take the contrib area on the Zope site seriously, so that it will grow into a repository as useful as CPAN.
To get things going in that direction requires the cooperation of everyone. If DC can keep the contrib area organized as the number of Products increases, and if people make sure they submit their Products to the site, we'll have the beginnings of CZAN :)
We are on this. In fact, we are in this deep. Our current scheme is to make a complete open-source development product that uses the concepts behind Eric Raymond's Trove spec to do archiving. In addition we have discussed working in some parts of Collector (our tabula based bug tracker), Confra (the discussion board product) and Mailman to work with lists. I have done some work allready on a Trove implimentation (called ZTrove) that we will be kicking around. We put this on hold till the beginning of Feb, when we can work with Ken. This has also follows on the tails of the 'Zopespot' discussion (a name I don't like, personally) which we want to be the 'core' of all this functionality. Please (everyone) brainstorm some ideas on this. We don't want to make this 'as useful as CPAN' we want to make this way far out there more superior to CPAN in every aspect. If we can especialy do the Trove spec nicely, such supersites as The-Artist-Formerly-Known- As-Sunsite (Metalab) and others have said they'd switch. Immagine that exposure! And to say you helped write it, I think it can be huge. -Michel
Kevin
-- Kevin Dangoor kid@ans.net / 734-214-7349
On Fri, Jan 22, 1999 at 01:58:42PM -0500, Michel Pelletier wrote: ,----- | Kevin Dangoor wrote: | | > I've seen a few Products that people have put together here | > and posted on their own websites. I think it would be good to take | > the contrib area on the Zope site seriously, so that it will grow | > into a repository as useful as CPAN. | | Please (everyone) brainstorm some ideas on this. We don't want | to make this 'as useful as CPAN' we want to make this way far | out there more superior to CPAN in every aspect. If we can especialy | do the Trove spec nicely, such supersites as The-Artist-Formerly-Known- | As-Sunsite (Metalab) and others have said they'd switch. Immagine | that exposure! And to say you helped write it, I think it can be | huge. `----- Between your message and Paul's, it sounds like you guys really are on top of this. That's great! I must agree, as well, that things can certainly be better than CPAN. Is there some place that I can read more about Trove? I'm curious about the types of things that are covered by that spec. Kevin -- Kevin Dangoor kid@ans.net / 734-214-7349
Kevin Dangoor wrote:
Between your message and Paul's, it sounds like you guys really are on top of this. That's great! I must agree, as well, that things can certainly be better than CPAN. Is there some place that I can read more about Trove? I'm curious about the types of things that are covered by that spec.
Kevin, You can get the Trove spec from the Trove site: http://www.tuxedo.org/~esr/trove/ This spec is way out of date, but a great place to start. Specificly the cgi scripts will be replaced by a Zope interface, and the database stuff will be replaced by BoboPOS. Really the only thing we're keeping from Trove is the philosophy and terminology, from there we can be quite creative. The Trove-Dev list can also be a good thing to browse over, but the very last message was in November. The very last *useful* message was in September. Some notes on my original implimentation: I made a Zope Folder product which contained a tree breakdown of TroveFolders and TroveItems. These were basicly extended OSF.Folder and OSF.SimpleItem objects. The visual interface was very Yahoo like in that it could be searched or browsed catagoricaly. If you look at the original Trove code, however, there was much more complexity. There are Person objects, Resource objects, Package (collection of Resources) objects, and even Relation objects to tie all these together. I'm assuming much of that meta-structure will be replaced by Zope's internal object structure and management. I'm assuming the original complexity was due to the idea of stuffing all this into an SQL database. Web objects are SO ideal for this whole project. It seems the original Trove spec breezes over this, it's a bit suprising that none of the original authors thought of Bobo, but at the time it wasn't nearly as proven technology as was just an ORB, now it's a whole system.
Kevin
-- Kevin Dangoor kid@ans.net / 734-214-7349
participants (2)
-
Kevin Dangoor -
Michel Pelletier