[dev] Horde 5?

[Gunnar Wrobel]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Michael J Rubinsky <mrubinsk at horde.org>:
>
>>> Actually I did so myself: I did integrate several Horde 4  
>>> components with the Zend 1 framework. This works just fine. But of  
>>> course you loose the version control context if you do so. Which  
>>> is a pity in the long run.
>>>
>>>> It's the latter that we are concerned about here. Sure, we can  
>>>> benefit from attracting more developers that are willing to  
>>>> donate time to our project, but I don't think that requiring them  
>>>> to clone a monolithic repository is asking too much.
>>>
>>> Try to bridge Horde with Zend framework 2 and Symfony 2 in the  
>>> context of a larger coding project. Pulling a monolihic repository  
>>> will not be an option. Working based on PEAR will mean that no  
>>> patches will be contributed back. Or at least it will be harder.
>>
>> I still think that external consumers should be using PEAR.  
>> Otherwise, why are we publishing them? Why would a monolithic  
>> repository not be an option? How would that be different from  
>> having to use some custom-to-horde toolchain in order to manage the  
>> multiple git repositories that would be necessary to use some of  
>> our components? I'm not saying you are wrong, I just don't  
>> understand the reasoning here. Either way, there would have to be  
>> some magic involved on the external developer's side.
>
> For developers, now, the easiest way to check out code is to click  
> "clone" on github. If I'm interested in a specific library, but I  
> have to clone a giant repo, that's a barrier. I think ultimately, if  
> we want to bring in developers, they'll find our other repositories  
> if our code is good.

+1

>
> -chuck
> -- 
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de