[board] Fwd: [horde] Horde projects and proposals resource

[Kevin Konowalec]

I think the one thing that's missing there that should be paramount is  
DOCUMENTATION.  I mean I've been running horde/imp/turba for several  
years now and I still don't know what a lot of the "features" actually  
do.  I think before we get too far ahead in planning new projects and  
ways to extend horde further (which we absolutely SHOULD) I think it's  
important to pause and go back over what's already been built and  
write up comprehensive documentation about it.

Just my $0.02

K



On Apr 3, 2008, at 4:36 PM, Chuck Hagenbuch wrote:

> I'm sure that most of you are on dev@, horde@, or both, and saw this
> message a minute ago. I want to highlight it to the board members,
> though, because:
>
> - I hope that all of you will take some time to enrich some of the
> project descriptions and add your own
>
> - I hope that you, especially those of you at universities, will use
> this as a resource for students that want an IT project but are at
> loose ends on what to do. I hope it's better than sending them at a
> random bug, and hopefully it'll inspire some people to do what's
> listed or to do something different/better
>
> Thanks,
> -chuck
>
> ----- Forwarded message from chuck at horde.org -----
>     Date: Thu, 03 Apr 2008 18:33:17 -0400
>     From: Chuck Hagenbuch <chuck at horde.org>
>  Subject: [horde] Horde projects and proposals resource
>       To: dev at lists.horde.org, horde at lists.horde.org
>
> Hi all-
>
> I've spent some time organizing proposals and project descriptions on
> the wiki - things from the Summer of Code ideas pages, from the old
> InterestingLinks page, etc. Everything is now available in one
> "clearinghouse":
>
> http://wiki.horde.org/Projects
>
> This page will hopefully grow a lot in the future. Each project should
> have a description, a status, a list of resources, etc. Discussion on
> individual project pages is encouraged (it is a wiki after all). And
> if you are working on a Horde-related project, please create a page
> (using the ProjectTemplate - http://wiki.horde.org/ProjectTemplate)
> describing it!
>
> If you'd like to see something done, please feel free to propose it,
> but do keep in mind that having something on this page doesn't mean a
> Horde developer will work on it. If you have a great idea and write a
> beautiful, detailed spec for it, though, the chances certainly go  
> up. :)
>
> This list is not intended as a replacement for a formal Horde roadmap.
> It IS intended to keep people up to date about what is happening
> "under the covers" of Horde as it were, and to give people a list of
> things to get involved in that's slightly friendlier than the bug
> list. And of course my hope is that this will be a strong resource for
> us next year when we re-apply to Google's Summer of Code as a
> mentoring organization.
>
> Propose away!
>
> -chuck
>
> --
> "I have concerns that we are not behaving like a mature, responsible,
> collection of interdependent organisms." - Rick O.
> --
> Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org
>
>
> ----- End forwarded message -----
> __
> board mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: board-unsubscribe at lists.horde.org
>