[logback-dev] Git as a version control system?
rgoers at apache.org
Fri Aug 7 16:32:20 CEST 2009
I've glanced at git but never used it. I've read that it is more
complicated than SVN because it works very differently. I have enough
interest in logback that I'd probably do what it takes to get access
to the source but I imagine there are others who wouldn't if setting
it up is more difficult than just installing a bit of software.
I'm not 100% sure what the real benefit would be. Ultimately the code
needs to be committed back to logback. How would using git make it
easier? Would we be able to commit somewhere that would allow you to
commit stuff to the "real" repository?
On Aug 7, 2009, at 6:54 AM, Ceki Gulcu wrote:
>> If you want to encourage more collaboration and contributions, I
>> believe this is not primarily a technical issue, but more a
>> question of community building. This has proven to be very hard.
>> Linus and Apache have done so. Sun have failed for most of their
>> open source products. For logback it appears that there are
>> around 10 active individuals on the developer list.
> Maybe not 10. I believe that any number of participants equal to or
> higher than 2 is already a good beginning.
> Ceki Gülcü
> Logback: The reliable, generic, fast and flexible logging framework
> for Java.
> logback-dev mailing list
> logback-dev at qos.ch
More information about the logback-dev