Splitting up logback-extensions project

Hello all, Following up on a discussion on github [1], it seems reasonable to split the logback-extensions project into two separate umbrella projects with CLAs on file serving as the only separation criteria. The split does not have any relation to code quality or community health. The list of contributors with CLA on file can be found at [2]. Looking at the logback-extensions umbrella project, it appears that the following projects have been contributed by developers with CLAs on file eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz) as such, I propose that they remain in logback-extensions and be released under the ch.qos.logback.extensions groupID in Maven Central. If any contributor feels that the second umbrella project (see below) would be a better home, he/they is/are welcome to move to the second umbrella project and without prejudice. The following project contains contributions from developers without CLAs non file loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller) Marten Gustafson, Bryan Turner and Juergen Hoeller do not have CLAs on file. I propose that these projects be moved to a new umbrella project named logback-stuff/logback-etcetera/logback-sundries. We still have to determine the name. This project will be released under a groupId outside the "ch.qos" namespace. Given that this split bears no relation to code quality or community health, contributions should pick the umbrella project that pleases them most. Before going forward with the split, we must first pick a name for the second umbrella project. Here are the names I find suitable: logback-stuff, logback-etcetera and logback-sundries. Are there other suggestions for names? Cheers, [1] http://tinyurl.com/ckue3cu [2] http://tinyurl.com/signedCLAs -- Ceki http://tinyurl.com/proLogback

On Tue, Sep 11, 2012 at 7:16 AM, ceki <ceki@qos.ch> wrote:
Before going forward with the split, we must first pick a name for the second umbrella project. Here are the names I find suitable: logback-stuff, logback-etcetera and logback-sundries. Are there other suggestions for names?
logback-unsigned (as in "from devs who have not signed the CLA") logback-contrib (like "ant-contrib" [1] and "clojure-contrib" [2]) [1]: http://ant-contrib.sourceforge.net/ [2]: http://code.google.com/p/clojure-contrib/

+1 for releasing /mongodb under ch.qos.logback.extensions groupID in Maven Central. Christian 2012/9/11 ceki <ceki@qos.ch>:
Hello all,
Following up on a discussion on github [1], it seems reasonable to split the logback-extensions project into two separate umbrella projects with CLAs on file serving as the only separation criteria. The split does not have any relation to code quality or community health.
The list of contributors with CLA on file can be found at [2]. Looking at the logback-extensions umbrella project, it appears that the following projects have been contributed by developers with CLAs on file
eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz)
as such, I propose that they remain in logback-extensions and be released under the ch.qos.logback.extensions groupID in Maven Central. If any contributor feels that the second umbrella project (see below) would be a better home, he/they is/are welcome to move to the second umbrella project and without prejudice.
The following project contains contributions from developers without CLAs non file
loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller)
Marten Gustafson, Bryan Turner and Juergen Hoeller do not have CLAs on file. I propose that these projects be moved to a new umbrella project named logback-stuff/logback-etcetera/logback-sundries. We still have to determine the name. This project will be released under a groupId outside the "ch.qos" namespace.
Given that this split bears no relation to code quality or community health, contributions should pick the umbrella project that pleases them most.
Before going forward with the split, we must first pick a name for the second umbrella project. Here are the names I find suitable: logback-stuff, logback-etcetera and logback-sundries. Are there other suggestions for names?
Cheers,
[1] http://tinyurl.com/ckue3cu [2] http://tinyurl.com/signedCLAs
-- Ceki http://tinyurl.com/proLogback _______________________________________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev
-- Christian Trutz Von-Flotow-Straße 24 D-45772 Marl Festnetz (privat): +49 (0)2365 3840327 E-Mail: christian.trutz@gmail.com

Hi all, As indicated in [1] Les would like to keep the name logback-extensions for the umbrella project *not* requiring CLAs residing *outside* the ch.qos namespace. Out of deference to his original initiative of creating logback-extensions in the first place, we should abide by his request. We still have to find a name for the second umbrella project. How about the name "logback-contrib" as Tony suggested? This second umbrella project would be reserved for original contributions from developers with CLAs and would reside under the ch.qos namespace. Now, loggly/ and spring/ need to remain in logback-extensions and their groupId and package names have to change as to reside outside the "ch.qos" namespace. However, the eclipse, jackson/, json/ and mongodb/ projects have the option of moving to the second umbrella project (logback-contrib?) and continue to remain under the ch.qos namespace. Tony, please let us know where you would like to have eclipse/. Christian, Tomasz where youd you like to host mongodb/? Les, where would you like to host jackson/ and json/? BTW, if any of the above is confusing do not hesitate to ask questions. [1] http://tinyurl.com/9f6cve2 On 12.09.2012 00:01, Christian Trutz wrote:
+1 for releasing /mongodb under ch.qos.logback.extensions groupID in Maven Central.
Christian
2012/9/11 ceki <ceki@qos.ch>:
Hello all,
Following up on a discussion on github [1], it seems reasonable to split the logback-extensions project into two separate umbrella projects with CLAs on file serving as the only separation criteria. The split does not have any relation to code quality or community health.
The list of contributors with CLA on file can be found at [2]. Looking at the logback-extensions umbrella project, it appears that the following projects have been contributed by developers with CLAs on file
eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz)
as such, I propose that they remain in logback-extensions and be released under the ch.qos.logback.extensions groupID in Maven Central. If any contributor feels that the second umbrella project (see below) would be a better home, he/they is/are welcome to move to the second umbrella project and without prejudice.
The following project contains contributions from developers without CLAs non file
loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller)
Marten Gustafson, Bryan Turner and Juergen Hoeller do not have CLAs on file. I propose that these projects be moved to a new umbrella project named logback-stuff/logback-etcetera/logback-sundries. We still have to determine the name. This project will be released under a groupId outside the "ch.qos" namespace.
Given that this split bears no relation to code quality or community health, contributions should pick the umbrella project that pleases them most.
Before going forward with the split, we must first pick a name for the second umbrella project. Here are the names I find suitable: logback-stuff, logback-etcetera and logback-sundries. Are there other suggestions for names?
Cheers,
[1] http://tinyurl.com/ckue3cu [2] http://tinyurl.com/signedCLAs
-- Ceki http://tinyurl.com/proLogback
-- Ceki http://tinyurl.com/proLogback

On Wed, Sep 12, 2012 at 5:33 PM, ceki <ceki@qos.ch> wrote:
Tony, please let us know where you would like to have eclipse/. Christian, Tomasz where youd you like to host mongodb/? Les, where would you like to host jackson/ and json/?
Please put it under logback-contrib*. BTW, if any of the above is confusing do not hesitate to ask questions.
To clarify, if a project is under logback-contrib*, does that mean patches to that project would only be accepted by developers with signed CLAs? -Tony

On 13.09.2012 00:19, Tony Trinh wrote:
To clarify, if a project is under logback-contrib*, does that mean patches to that project would only be accepted by developers with signed CLAs?
It depends on the size of the patch. If it the patch is small or trivial than no CLA is necessary. In the past, for bigger changes, I asked for the contributor to email me a signed copy of the CLA which most contributors agree to do. So in practice, requiring a CLA has not been an impediment for the integration of patches or of original work in general.
-Tony
-- Ceki

Hello all, We had several lengthy discussions on September of this year (2012) about splitting up logback-extensions project. See [1,2]. Here is the actionable conclusion as I understand it. 1) The following project contains contributions from developers with CLAs on file. They will be move to the "ch.qos.logback.contrib" namespace (under the ch.qos.logback.contrib Maven group). eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz) 2) The following projects contain contributions from developers without CLAs on file. They will be moved to the org.logback-extensions namespace. loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller) If you have questions or objections please take the opportunity to raise them now. As far as I am concerned, the two umbrella projects would differ only by CLA requirements and namespace. Needless to say, CLA and namespace bear no obvious relation to code quality or community health. No such relation should be assumed. Your comments are welcome. [1] https://github.com/qos-ch/logback-extensions/issues/1 [2] http://markmail.org/message/vuemikgfdh2bdiii -- Ceki 65% of statistics are made up on the spot

On Thu, Dec 13, 2012 at 5:38 AM, ceki <ceki@qos.ch> wrote:
Hello all,
We had several lengthy discussions on September of this year (2012) about splitting up logback-extensions project. See [1,2].
Here is the actionable conclusion as I understand it.
1) The following project contains contributions from developers with CLAs on file. They will be move to the "ch.qos.logback.contrib" namespace (under the ch.qos.logback.contrib Maven group).
eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz)
2) The following projects contain contributions from developers without CLAs on file. They will be moved to the org.logback-extensions namespace.
Was the hyphen in "org.logback-extensions" intentional? Or did you mean "org.logback.extensions"? Will the Maven repositories be hosted in Sonatype or qos.ch?
loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller)
If you have questions or objections please take the opportunity to raise them now.
As far as I am concerned, the two umbrella projects would differ only by CLA requirements and namespace. Needless to say, CLA and namespace bear no obvious relation to code quality or community health. No such relation should be assumed.
Your comments are welcome.
[1] https://github.com/qos-ch/**logback-extensions/issues/1<https://github.com/qos-ch/logback-extensions/issues/1> [2] http://markmail.org/message/**vuemikgfdh2bdiii<http://markmail.org/message/vuemikgfdh2bdiii>
-- Ceki 65% of statistics are made up on the spot
______________________________**_________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-dev<http://mailman.qos.ch/mailman/listinfo/logback-dev>

Hi Ceki, do you want to integrate ch.qos.logback.contrib into lb project or will it be also a new Github repo and also a separate project? Christian 2012/12/13 ceki <ceki@qos.ch>
Hello all,
We had several lengthy discussions on September of this year (2012) about splitting up logback-extensions project. See [1,2].
Here is the actionable conclusion as I understand it.
1) The following project contains contributions from developers with CLAs on file. They will be move to the "ch.qos.logback.contrib" namespace (under the ch.qos.logback.contrib Maven group).
eclipse/ (Tony Trinh) jackson/ (Les Hazlewood) json/ (Les Hazlewood, Pierre Quinnec) mongodb/ (Christian Trutz, Tomasz Nurkiewicz)
2) The following projects contain contributions from developers without CLAs on file. They will be moved to the org.logback-extensions namespace.
loggly/ (Les Hazlewood, Marten Gustafson) spring/ (Les Hazlewood, Bryan Turner, Juergen Hoeller)
If you have questions or objections please take the opportunity to raise them now.
As far as I am concerned, the two umbrella projects would differ only by CLA requirements and namespace. Needless to say, CLA and namespace bear no obvious relation to code quality or community health. No such relation should be assumed.
Your comments are welcome.
[1] https://github.com/qos-ch/**logback-extensions/issues/1<https://github.com/qos-ch/logback-extensions/issues/1> [2] http://markmail.org/message/**vuemikgfdh2bdiii<http://markmail.org/message/vuemikgfdh2bdiii>
-- Ceki 65% of statistics are made up on the spot
______________________________**_________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-dev<http://mailman.qos.ch/mailman/listinfo/logback-dev>
-- Christian Trutz Von-Flotow-Straße 24 D-45772 Marl Festnetz (privat): +49 (0)2365 3840327 E-Mail: christian.trutz@gmail.com

On 13.12.2012 22:08, Christian Trutz wrote:
Hi Ceki,
do you want to integrate ch.qos.logback.contrib into lb project or will it be also a new Github repo and also a separate project?
Hi Christian, Given the different project life cycles, ch.qos.logback.contrib will definitely be a separate project with its own git repo.
Christian
-- Ceki 65% of statistics are made up on the spot

Hi Ceki, OK, can you please create the logback-contrib GitHub repo. I will then migrate lb-extensions/mongodb ... Christian 2012/12/14 ceki <ceki@qos.ch>
On 13.12.2012 22:08, Christian Trutz wrote:
Hi Ceki,
do you want to integrate ch.qos.logback.contrib into lb project or will it be also a new Github repo and also a separate project?
Hi Christian,
Given the different project life cycles, ch.qos.logback.contrib will definitely be a separate project with its own git repo.
Christian
-- Ceki 65% of statistics are made up on the spot ______________________________**_________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-dev<http://mailman.qos.ch/mailman/listinfo/logback-dev>

Hi Christian, Just created logback-contrib repo available at https://github.com/qos-ch/logback-contrib This repo will start as a duplicate of logback-extensions so as not to lose history. Once that is done I will remove the duplicate projects according to their future homes. This process should take 45 mins or so. I'll keep you posted. On 15.12.2012 21:47, Christian Trutz wrote:
Hi Ceki,
OK, can you please create the logback-contrib GitHub repo. I will then migrate lb-extensions/mongodb ...
Christian
-- Ceki 65% of statistics are made up on the spot

The logback-contrib project builds after migrating Maven group names from logback-extensions to logback-contrib. Package names still need to be modified. Christian, would you do package name migration from ch.qos.logback.ext.* to ch.qos.logback.contrib.* in logback-contrib? I'll now do some work on logback-extensions repository. Cheers, On 15.12.2012 23:05, ceki wrote:
Hi Christian,
Just created logback-contrib repo available at
https://github.com/qos-ch/logback-contrib
This repo will start as a duplicate of logback-extensions so as not to lose history. Once that is done I will remove the duplicate projects according to their future homes.
This process should take 45 mins or so. I'll keep you posted.
On 15.12.2012 21:47, Christian Trutz wrote:
Hi Ceki,
OK, can you please create the logback-contrib GitHub repo. I will then migrate lb-extensions/mongodb ...
Christian
-- Ceki 65% of statistics are made up on the spot

Hi Ceki, OK, I am starting now converting ch.qos.logback.ext.* to ch.qos.logback.contrib.* Christian 2012/12/15 ceki <ceki@qos.ch>
The logback-contrib project builds after migrating Maven group names from logback-extensions to logback-contrib.
Package names still need to be modified. Christian, would you do package name migration from ch.qos.logback.ext.* to ch.qos.logback.contrib.* in logback-contrib?
I'll now do some work on logback-extensions repository.
Cheers,
On 15.12.2012 23:05, ceki wrote:
Hi Christian,
Just created logback-contrib repo available at
https://github.com/qos-ch/**logback-contrib<https://github.com/qos-ch/logback-contrib>
This repo will start as a duplicate of logback-extensions so as not to lose history. Once that is done I will remove the duplicate projects according to their future homes.
This process should take 45 mins or so. I'll keep you posted.
On 15.12.2012 21:47, Christian Trutz wrote:
Hi Ceki,
OK, can you please create the logback-contrib GitHub repo. I will then migrate lb-extensions/mongodb ...
Christian
-- Ceki 65% of statistics are made up on the spot ______________________________**_________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-dev<http://mailman.qos.ch/mailman/listinfo/logback-dev>

I had forgotten to link the logback-contrib-team to the logback-contrib repo. Consequently, you could not have pushed your changes to the logback-contrib repo. This particular issue has been solved a few moments ago. On 15.12.2012 23:56, Christian Trutz wrote:
Hi Ceki,
OK, I am starting now converting ch.qos.logback.ext.* to ch.qos.logback.contrib.*
Christian
-- Ceki 65% of statistics are made up on the spot
participants (4)
-
ceki
-
Christian Trutz
-
Christian Trutz
-
Tony Trinh