The Seagull project recently got reviewed by Florian, I’d like to respond to a few of his points:
the site has 0.5.5 as "development release", I tried installing it via PEAR
(instructions here – didn’t work at all)
A stable release is due out shortly, and the PEAR installs have been improved.
then I tried svn-trunk, as was recommended. This worked better, but 2 more things happened:
– first pageload: template issue: "Notice: Undefined property: HTML_Template_Flexy_Token_Text"
There was a small error in Flexy configuration, now fixed.
– memory_limit of 16 MB may or may not be recommended by setup – I did
get a Fatal error in PEAR::Date_Timezone when a "joined at" should’ve
been displayed in a user page
There are a couple of screens where the PHP process grabs just over the 8MB default (when compiled with –enable-memory-limit), we should be able to address these by the next release.
they use trac, and I personally hate to register to file bugs – ok, no bug reports by me then :/
We were cautious at first due to spam worries, but the comment is a fair one, so we’ve changed the config to allow anonymous tickets now.
minimalistic is ok, but when I see the default page introduced after a
fresh install, why can’t I edit it? – too strict separation of
framework and cms? why is it installed then?
I updated the default homepage to give better instructions regarding what to do after install. Now that the admin GUI has been completely redone, the next step is to provide a better front end look and feel.
when I login as admin, I am presented the modules page – when leaving
it, however, I can’t find my way back there without logging out and in
again or remembering the url
Yep, the default navigation needed to be better thought out, this has now been done. As for Florian’s wishlist at the end of the post:
- dish out RCs and releases faster
- unit testing is fine, but how can it be that a new user can’t get
it too work? my dev webserver happily accepted the last ~20 opensource
- make submitting bugs open. don’t force work on users. YOU want them to help your project
Releases – we try to keep to one a month, I think that’s fast enough, at least it’s as fast as we can manage! Install probs – we’re always trying to improve. And anonymous bugs – we’ve taken your cue on this one.
Thanks for the feedback!