[dev] [commits] Horde branch master updated. 0d3a559c058aa995b7764d85b80df42f50324938

Eric Jon Rostetter eric.rostetter at physics.utexas.edu
Thu Oct 7 19:08:23 UTC 2010


Quoting Ben Klang <ben at alkaloid.net>:

> For what it's worth, I concur with Chuck here.  I think the easiest  
> thing to do in the short term is to mark what the official Horde  
> apps are.  Today I think that means everything that comes with  
> Groupware plus probably tickets, wiki, files, photos and  
> timetracker.  Fair candidates might also be SCM browser, news and  
> bookmarks.

And do what with them?

Shouldn't horde be one level (since it is a framework, that could be
used for anything), then the "supported horde apps" be the next level
(since that is what the core developers support and focus on), and
all other apps be labeled "contrib" or "unofficial" or "beta" or
"devel" or pick your favorite categories (since there would likely
be more than one category here).

Then what to do with them?  How to organize them on the web site?
How to organize them on github?  How to support them on the mailing lists?

> This obviously will require further discussion and actual effort,  
> but finding some way to have a directory of Horde apps (like what  
> Firefox does for extensions) would be a good thing for the rest of  
> the project in my opinion.

Now that, if I read it correctly, sounds very interesting...

> /BAK/

-- 
Eric Rostetter
The Department of Physics
The University of Texas at Austin

This message is provided "AS IS" without warranty of any kind,
either expressed or implied.  Use this message at your own risk.



More information about the dev mailing list