7 messages in com.googlegroups.pylons-discussRe: ANNOUNCE: Gazest 0.3.7 -- a Pylon...| From | Sent On | Attachments |
|---|---|---|
| Yannick Gingras | 17 Oct 2007 22:48 | |
| Rick Harding | 18 Oct 2007 06:04 | |
| Bruce Wang | 21 Oct 2007 23:37 | |
| Yannick Gingras | 22 Oct 2007 01:54 | |
| Mike Orr | 22 Oct 2007 12:56 | |
| sjh24wvu | 22 Oct 2007 16:36 | |
| Yannick Gingras | 23 Oct 2007 02:41 |
| Subject: | Re: ANNOUNCE: Gazest 0.3.7 -- a Pylons powered wiki![]() |
|---|---|
| From: | Rick Harding (deuc...@public.gmane.org) |
| Date: | 10/18/2007 06:04:16 AM |
| List: | com.googlegroups.pylons-discuss |
On 10/18/07, Yannick Gingras <ygin...@public.gmane.org>
wrote:
Greetings Pyloneers, I'm am please to announce the release of Gazest 0.3.7, a Pylons powered wiki.
Why another wiki? Gazest is heavily inspired by Git and Mercurial. It won't try to flatten the history to a linear succession of commit; instead, it preserves the history graph as a DAG. We get 3-way merge all over the place and that makes "section edit" obsolete. Let me say it another way: the problem with svn is not that it's centralized, it's that it can't merge. Also, thanks to MVC and to Pylons's cascading apps, Gazest's look and feel is much easier to change than it is with other wikis.
That being said, Gazest is still young and it lacks many features commonly seen in other wikis. What I want to implement in the near future is a way to select a handful of pages, branch them to another namespace, edit them, then merge them as a whole when you feel ready for it. We see a typical use-case for this with Pylons: the doc is on the wiki but, when the dev branch changes, we need to update the doc. Since the wiki is the master reference for users, we can't do it live so we wait and when release time is upon us, we have to update everything in frenzy mode.
We often hear new Pyloneers complain that there are not many Pylons apps to learn from. This is a fairly complete Pylons project with relatively polished packaging. It is release under GPLv3; I hope this can help new comers to see what a "finished" app can look like.
Enough rambling!
Very cool. I'll definitely have to poke around this some.
Thanks
Rick




