[cvs] [Wiki] changed: Project/HordeWeb

Tue May 27 21:21:43 UTC 2008

chuck  Tue, 27 May 2008 17:21:43 -0400

Modified page: http://wiki.horde.org/Project/HordeWeb
New Revision:  1.2
Change log:  lots of raw notes on what should be on or linked from the
horde website

@@ -48,7 +48,143 @@
 * store versions of content like wicked does

 ----
 CMS Suggestion: Add some native support for Horde_Blocks or a new kind of
widget. That will encourage more people to build Blocks which one can
integrate into Websites.Currently you only need few lines of code but if the
CMS is going to be a new app for release, this may really push Horde
deployment a step forward.See also the CMS module of egroupware which allows
joomla templates to be used, and easily integrates all egroupware apps (but
is a bit clumsy)
+
+----
+++ Raw Notes
+post somewhere that once horde 3.2 is out, it will be the only supported
stable version. horde 4 work will commence. there will be a migration path
to horde 4 from 3.2 once it is stable, but not necessarily at every point
in between
+
+horde demo videos
+
+details from http://bugs.horde.org/ticket/6559
+
+
+http://wiki.debian.org/Horde#head-c3fc1641153f054dc99df6d638bfecec7783a8be
+http://eosdirectory.com/project/304/Horde.html
+http://pooteeweet.org/blog/780
+
+http://www.bigsoft.co.uk/blog/index.php/2007/08/30/horde_spamassassin_imap_plesk_user_confi
+http://www.socialsciences.uottawa.ca/eng/PaulRoy_horde_customizations.asp
+http://gpmail.globalpinoy.com/webmailv2ur/horde/imp/login.php?Horde=i74smss13884kies374lbre2d6
+
+http://web.archive.org/web/20070103221851/http://www.gentoo.org/proj/en/devrel/copyright/index.xml
+
+
+Link to todo lists from phpdoc
+
+Link to Todo lists (like http://dev.horde.org/api/framework/todolist.html)
from application pages, perhaps from roadmaps? Consolidate so we have docs
for an app (api and otherwise), todo list, open bugs, etc. all in one place.
+
+Probably http://dev.horde.org/ is a good place to do this - move current
stuff into a sidebar, with default links to online apidoc for all the apps;
ideally a custom phpdoc theme with our frame, the generated hordedoc
documentation, links to wiki pages, etc.
+
+
+Horde website community building:
+  http://rubyonrails.com/community
+  http://live.gnome.org/GnomeLove
+  http://live.gnome.org/JoinGnome
+  http://www.symfony-project.com/content/download.html
+  http://solarphp.org/wiki/SolarFaq#HowdoIgetmycodeincludedinSolar
+  http://solarphp.com/manual/Getting_started
+  http://99clients.blogspot.com/2006/11/creating-open-source-desktop.html
+  http://www.ii.com/internet/messaging/imap/isps/ - lots of horde mentions.
need to blog!
+ 
http://bergie.iki.fi/blog/midgard-in-2007--the-year-of-the-web-developer.html
+  http://bakery.cakephp.org/
+  http://pylonshq.com/
+  http://en.wikipedia.org/wiki/Horde_%28Software%29
+  http://suggestions.yahoo.com/
+  http://wiki.horde.org/Quotes
+  http://fourmont.org/drupal/node/2
+
+Community Horde apps:
+  https://webdns.bountysource.com/
+  http://projects.alkaloid.net/news.php
+  http://scopserv.com/
+  pmacct? http://www.google.com/search?q=pmacct
+  http://ispman.net/
+  http://sourceforge.net/projects/dts ?
+  http://fourmont.org/drupal/node/2
+  http://sourceforge.net/projects/sinapse/
+
+  http://forums.sjgames.com/showthread.php?p=433859#post433859
+  http://gurps.natemac.com
+
+ 
http://www.phpkitchen.com/index.php?/archives/641-Installing-Horde-and-IMP.html
+  http://www.whitemiceconsulting.com/node/51
+  http://www.icthubknowledgebase.org.uk/opensourcegroupware
+  http://www.qmailrules.com/
+  http://www.insidehighered.com/news/2007/11/27/email
+  http://www.spursreport.com/forums/showthread.php?t=79001
+
+  "while looking for mature code to combat XSS, Bob had
+  pointed out the CodeIgnitor which EE is built on top of.  The CodeIgnitor
people listed
+  where they got their inspiration from and basically if you follow the
chain, it ends up
+  back at Horde"
+
+  I just want to let everyone know that ossec
+  (an open source project for log analysis) now
+  supports Horde IMP logs. More information:
+  http://www.ossec.net
+
+  http://mxtreme.com/products/mxtreme
+
+  The Borderware MXtreme Firewall is a Mail proxy against SPAM.
+
+  Every user has a SPAM-Folder on the Proxy and is able to log in.
+
+  The mailbox-GUI seems to be IMP (the URLs are like
+  /borderpost/imp/message.php3?index=7&array_index=6)
+
+  use of Zend_Feed (== Horde_Feed) http://www.dotvoid.com/view.php?id=71
+  etc.
+
+http://producingoss.com/html-chunk/social-infrastructure.html
+http://producingoss.com/html-chunk/consensus-democracy.html
+http://foundationcenter.org/getstarted/tutorials/fiscal/
+
+http://spriggs.no-ip.info/cgi-bin/trac.cgi/wiki/Programming/HordeWTG
+
+
+"Looking at the horde website for the first (serious) time, I'd say that
Jan's paper (http://www.horde.org/papers/fosdem2005/) is an excellent
+developer's introduction to the framework. I think the homepage could use a
link to that. Alternatively, extract the non-technical pages into
+a summary and use that as a general "Horde overview" presentation (linked
to from the homepage).
+
+Point being, an "overview" link might be useful."
+
+
+Taking the Symfony homepage by example, their first topic on the sidebar is
"Discover": 1. Read the about page, 2. build your first project or 3. start
browsing the book. That's the intro ZF still doesn't have. A "what is this
and how this can help me?" page is missing.
+
+From Duck:
+> http://dev.horde.org/~jan/groupware-handout.pdf
+
+In general all Horde presentations are too technical or even only feature
list. For example the Wiki howtos are manly all configuration tips. The
helps files are out of date, comparing too all futures that apps supports.
Horde will benefit a lot if the ?Horde User's FAQ? will be updated for all
promoted applications (those in groupware and webmail edition). At least
with those futures listed in presentations. And if is possible to add screen
shoots step by step. Or why not create a movie with
http://www.debugmode.com/wink/.
+
+Then I mission 3 basic Wiki pages. Maybe just a little Wiki reorganization
will help a lot.
+
+Imagine that you persuade an administrator that decides to use Horde. The
first problem is the complexity of Horde. The first things that comes into
my mind is ?Where is the 'my Horde first installation link'??. A link that
explains the first step to do after successful horde install. Like adding
users, set permissions. Maybe this Wiki exist but are not directly
accessible.
+
+Then image a fist time user. The help is outdated. Some informations is
available in Wiki but not linked from help. Even if the user finds the Wiki,
the first page don't consist of a list of all available topics. Use must
directly see what they need, not search it, or get confused on what they
must read FAQ or Howtos, that are in fact administration tips not user
manual etc. You can get KDE documentation as example. Is a pure end user
explanation with screen shots.
+
+And last but not least, the first time developer. There is no general
explanations of the concepts of programing in horde or application
interaction. Some info are available in Library but again not linked in
Wiki. Then api documentations is not enough. The programmer must always find
out what methods does, which methods uses what they do and so on. The job is
made harder by not having a class index end explanation. You must actually
open every class and read what it does or look out the sources. I purpose a
general framework Wiki  page with all explained classes with piratical
examples.
+
+The conclusion is that all that we must give more attention of first time
users and Horde, and much more on end user documentation.
+
+
+Subject:  	[nyphp-talk] CAKE Ain't Soup!
+In defense of Brian Daley's rant about CAKE and contrary to Nate Abele's
illness,
+I believe Brian's point are well founded and justified completely.
+
+As a complete CAKE novice, I knew/know nothing about Cake except the
misinformation that is contained on their home page, i.e *"No Configuration*
- Set-up the database and watch the magic begin". So I decided to check it
out to see for myself what all the hype was about so after wading through a
miriad of "give us money" I finally was able to download the package and
attempted to install it on my local Apache Webserver. Give that the
installation instruction are clear as mud, I attempted to install it like
any other PHP Application but when I attempted to run it, I get  a "Your
database configuration file is not present." and a screenful of junk that
tells me nothing about how to install the product, except an instruction
that says, "run the install" but never says what that is. Installation
instructions, never mind documentation, are suppose to be specific, precise
and correct. Cake is none of the above.
+
+Cake may be cake but it is certainly not soup!
+
+Cake may be indeed a great leap forward but if you can not install it "out
of the box" no one will ever know. I, personally, don't "shop around" for
information that isn't where it is "suppose" to be. That means that Cake
only had one shot to impress me, they did, negatively! All the whining on
the planet won't fix an installation process that is fatally flawed.
+
+
+
+We're using Symfony for a major project. Yahoo Bookmarks is built on
+Symfony. Its pretty good (totally OOP and lots of Railsisms in it).
+
+The Yahoo! team had to re-architect several parts of the framework to get
it to do what they wanted.  Regardless of that, I hear they were having some
significant scaling issues.  The Firefox Add-ons portal
(https://addons.mozilla.org/) was built on CakePHP, and you can check out
the source code here: http://svn.mozilla.org/addons/trunk/site/app/.  To
date, the site has handled the arguably higher load without a hitch.
+

 ----
 Back to the ((Projects|Project List))
