From: <pau...@us...>
<pau...@us...> - 2009-01-22 23:14:35
|
Hi Nate, Thanks for this.I've been thinking of forking for a while, not so much because Everydevel is linked to Everything2, but because it would stop me feeling constrained by the code base. It would also make version numbering easier. One of the reasons I haven't suggested a release is because the current version is pre-1.0, what should the next release be 2.0? But a name change and starting at version 0.01 would be easier. Also, it means I could host it on a git server. As for being better than Drupal, I actually think Everything is already better in the fact it is far more flexible. Drupal is easier for novices to get up and running with though. Cheers Paul Nathan Oostendorp wrote: > Hey Paul, > > To address point #2, I agree that this list is pretty dead. I'd would > encourage you to put these someplace public, like on a blog or > everydevel (of course still sitting under my desk without network until > the bastards at comcast fix our internet connection). This way people > can just reply as they want to, without being list subscribers. > > I also think if you're really interested in keeping it alive long term > you should consider "forking" or otherwise re-branding the project and > then either doing regular releases, or making it a micro-packaged > SVN-distributed project (ala ruby gems). "Everything Engine" has always > been a kind of an ad-hoc name, and i think most of the people that have > heard of it just associate it with Everything2, which I don't think is > what you're ultimately aiming for. I think you need to reframe the > fundamental pitch to say "HEY, WE'RE LIKE DRUPAL BUT PERL BUT ALSO > BETTER BECAUSE WE DO X AND Y AND Z", since CMSs are a dime a dozen now. > > If there's anything I can do, please let me know. > > --n > > > > > > On Jan 9, 2009, at 4:31 AM, pau...@us... wrote: > >> Hello list, >> >> Two points here: >> >> POINT ONE >> ========= >> >> The latest thing I've been working on in everydevel is changing the >> database structure for more normalisation. The good news is that this >> works. The bad news is that it is taking me longer than I thought >> partly because I've had to do a lot of thinking and partly because there >> is no one to bounce ideas off. >> >> These changes in the db layer have to have knock on effects. I'll give >> you an example: permissions. >> >> As you know permissions in everydevel have five types r, w, x, d, c and >> there are four user types for each permission: owner, group, other, >> guest. >> >> After my db redesign it is obvious that this is arbitrary and there >> could be more permission types and user types. >> >> It is also has become obvious that nodes can't continue to 'know' about >> their own permissions. Because to do so they'd also have to continue to >> 'know' about any 'usertype' nodes in the nodebase to which they belong. >> This means that each and every node would have to have some sort of >> aggregate behaviour as well as their standard behaviour. >> >> This of course is waaaay too complicated and indicates a design problem. >> >> The solution is to change Security.pm into an object class that >> negotiates permissions, or perhaps to make Security.pm a nodetype that >> has the job of negotiating access between the UI and the NodeBase. >> >> Anyway, the point is these knock on effects get a bit involved. >> >> >> POINT TWO >> ========= >> >> I'm not sure there's any point posting to this list any more, because >> I get barely any response and never any assistance .... then some >> smartarse wonders why things are going so slowly.... >> >> Nonetheless, I'd really like to create enthusiasm for everydevel. It is >> afterall one of the few CMS which are perl based in a world where PHP >> rules in the space. The question is how to create this enthusiasm and >> where. >> >> Experience suggests it isn't here. But where? >> >> Paul >> >> ------------------------------------------------------------------------------ >> >> Check out the new SourceForge.net Marketplace. >> It is the best place to buy or sell services for >> just about anything Open Source. >> http://p.sf.net/sfu/Xq1LFB >> _______________________________________________ >> Everydevel-opers mailing list >> Eve...@li... >> https://lists.sourceforge.net/lists/listinfo/everydevel-opers > > > |