[logback-dev] Logback source code organization and extensions
les at hazlewood.com
Fri Mar 9 23:35:45 CET 2012
Oops - my apologies - I just clicked the Github link. I'll add you asap.
On Fri, Mar 9, 2012 at 2:35 PM, Les Hazlewood <les at hazlewood.com> wrote:
> Hi Tony,
> What's your Github username?
> On Fri, Mar 9, 2012 at 1:53 PM, Tony Trinh <tony19 at gmail.com> wrote:
>> +1 (see below)
>> On Fri, Mar 9, 2012 at 4:35 PM, ceki <ceki at 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
>> 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".
>> logback-dev mailing list
>> logback-dev at qos.ch
More information about the logback-dev