+1 (see below)

On Fri, Mar 9, 2012 at 4:35 PM, ceki <ceki@qos.ch> wrote:
Glad you like the approach.

I was not familiar with the concept of github organizations. Anyway,
inspired by what you have done with the "logback" organization, I've
created the "qos-ch" organization (see https://github.qcom/qos-ch/)
containing a single repo named logback-extensions with you and me
having admin rights.

Assuming projects like slf4j, cal10n, logback-*, mistletoe, etc move
under that organization, I rather have it named qos-ch rather than
logback.

I like the idea of pooling the logback extensions in a central location. I currently manage logback-android in Github and would like to join this organization. Let me know what to do. Thanks :-)

Anyway, as mentioned, I am not very familiar with github
organizations, and if I've made a mistake, please let me know and I'll
correct it promptly.

Github organizations seem like less chaotic way of managing
projects. One advantage of person-based approach is the lack of the
300MB barrier which exists in github "organizations".

Cheers,

--
Ceki
http://twitter.com/#!/ceki