[dev] [commits] Horde-Hatchery branch master updated. d3fcd5cdd11ada51d44c03fccd529ba9beed543d

[Chuck Hagenbuch]

Quoting Ben Klang <ben at alkaloid.net>:

> I disagree with this statement.  While I don't necessarily feel that  
> a git clone should work 100% out-of-the-box, it should be close.  By  
> making the repository close to a workable Horde install we encourage  
> casual developers and minimize our own work on new installs.  Right  
> now there is a fairly high barrier to begin working on Horde, even  
> for someone like me who is intimately familiar with the process.  I  
> can only imagine what it would be like for someone who may want to  
> fix a bug but has only ever installed Horde from the tarballs.
>
> That being said, there are naturally some concessions that we will  
> need to make to the development and packaging processes that will  
> conflict with Horde working fresh from a git checkout.  But in my  
> opinion, the closer we can align those needs, the better.

I'm still absorbing this thread but I agree strongly with Ben K. here.  
Lowering the barrier to development is a good thing if we want to get  
more contributions - which I do - regardless of how many people do it  
*now*.

-chuck