[cvs] [Wiki] changed: Project/HordeWeb
Chuck Hagenbuch
chuck at horde.org
Sat Aug 23 03:19:22 UTC 2008
chuck Fri, 22 Aug 2008 23:19:22 -0400
Modified page: http://wiki.horde.org/Project/HordeWeb
New Revision: 1.14
Change log: add plans for commit digest/ongoing development news
@@ -32,8 +32,18 @@
We don't have a lot of end user content right now; it's possible
that area could be dropped?
Questions raised by this include: where do we store the master docs,
CVS or the website? We can automate the process either way - either
have make-release.php pull down files from the website, or have a
cronjob to update the website from CVS. We could write a renderer for
rST docs for the website, and store them there.
+
++++ Ongoing development updates
+
+We should provide a much more visible sense of ongoing Horde
development. Ideas for doing this, possibly requiring work on some
infrastructure such as Whups:
+
+* Provide a weekly diff of CHANGES files, or perhaps generate a feed
from commits to CHANGES
+* Generate feeds from the application news files on www.horde.org
+* Generate weekly or monthly feeds of closed tickets (must be able to
select specific closed statuses, i.e. Resolved and not Duplicate)
globally and/or on a per-queue basis. Put these feeds on Planet Horde.
+* Provide a feed from the RecentChanges wiki page. Perhaps also allow
restricting it to showing changes below a specific path, such as /Doc.
+
+++ The CMS
See ((Project/Hydra))
More information about the cvs
mailing list