Re: [Zope] Happy Valentine's Day from Zwiki HQ
Simon Michael schrieb: Hello Zopistas.. a happy Valentine's day to all! as martin said (or hinted) before me, a new wiki solution needs to be seamlessly integratable into plone. I like zwiki very much and still use it often. but rarely in new projects. the userinterface is to different from plone. thanks for the incredible useful zwiki you provided us with. if you move towards something plonelike, I would be happy to help. robert ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Happy Valentine's Day from Zwiki HQ
robert rottermann wrote: Simon Michael schrieb: Hello Zopistas.. a happy Valentine's day to all! as martin said (or hinted) before me, a new wiki solution needs to be seamlessly integratable into plone. I like zwiki very much and still use it often. but rarely in new projects. the userinterface is to different from plone. thanks for the incredible useful zwiki you provided us with. if you move towards something plonelike, I would be happy to help. Still I'm not so much a friend of Plone. While having the hooks in place, a lightweight wiki-core would really be great. Perhaps split into document type/parser/editor, storage and link calculation engine, searchcatalog and security? Then just some glue code to adapt to plain zope, CMF, Plone, Five... I mean the biggest improvement would be skipping that DTML stuff ;)) Regards Tino ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Happy Valentine's Day from Zwiki HQ
Tino Wildenhain wrote: Still I'm not so much a friend of Plone. While having the hooks in place, a lightweight wiki-core would really be great. A lightweight wiki engine that was agnostic to the framework used would be *awesome*, especially if it let you customise the dialect of the wiki easilly. Perhaps split into document type/parser/editor, storage and link calculation engine, searchcatalog and security? I'd mainly be interested in the parser for text with the ability to plug in storage and finding of other pages. ie: would be lovely to see this as just a python package with no ties to Zope, etc cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Happy Valentine's Day from Zwiki HQ
Hello Zopistas.. a happy Valentine's day to all! Continuing with my spring cleaning theme over at http://zwiki.org/GeneralDiscussion , here are some musings. Like many of you, I'm always wondering where is the most useful place to spend my community hacking time. Sometimes Zwiki seems like the very best place; other times it doesn't. Development pretty much came to a full stop at times last year. So I'm kicking around some ideas. I'm pondering what slows down my Zwiki hacking. First, let me get one thing off my chest: for me, Python is a `blub http://en.wikipedia.org/wiki/Blub`_! There, I said it. Moving on.. then, there are the usual questions of project and platform maturity, legacy cruft, how many people actually use this thing, what is the benefit, what's the future potential, etc. Don't get me wrong, I expect Python and Zope 2 to keep growing and succeeding for a very long time. And so I guess Zwiki will continue to be used and perhaps grow in user base. At the current rate of development, though, we will not stay competitive with other software or even catch up with our own bug reports. Looking at current code, I am reminded that Zwiki 0.x is mature, built on early zope 2 architecture, and that cleanup continues to be expensive (compared to starting something fresh). Of course, many hands make light work. Imagine ten developers working on Zwiki at once - cleanup expense would no longer be noticeable, we could pretty much do whatever we want. That's not our current reality. Is it possible to find ten Zwiki developers now or in future ? I'm sure I could increase our numbers (from two active) by sustained effort, but how far and how smart a strategy that is I don't know. Another idea which inspired this post is to branch, mothballing 0.x as-is and moving development focus to a Zwiki 2.x where we would do aggressive disruptive cleanup. Say we did that. What would you throw out of Zwiki 0.x ? What would you keep ? This is to air these thoughts, solicit your ideas, and also a kind of ping to gauge support for the project circa 2008, I guess. Warm regards - Simon -- forwarded from http://zwiki.org/[EMAIL PROTECTED] Joyful Systems http://joyful.com ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
