Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 187A1100B7 for ; Sat, 4 May 2013 17:49:26 +0000 (UTC) Received: (qmail 86109 invoked by uid 500); 4 May 2013 17:49:26 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 85987 invoked by uid 500); 4 May 2013 17:49:25 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 85977 invoked by uid 99); 4 May 2013 17:49:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 May 2013 17:49:25 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.219.42 as permitted sender) Received: from [209.85.219.42] (HELO mail-oa0-f42.google.com) (209.85.219.42) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 May 2013 17:49:20 +0000 Received: by mail-oa0-f42.google.com with SMTP id i10so1254387oag.1 for ; Sat, 04 May 2013 10:48:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=m87apvxNbM1r7rmjUXHPB9x56oP7nvsdRm3oj2A/Q+A=; b=h5MgWjHDXw1/hVpGccmAgPr6W+gIgLh3sYyu8Q5E3CoO8iUziP1fZdnfTKbd4vqUpe VMJxaoYqCv39MmyH4xlpKU41eLZueBjOMlnFGA4xQKvmDPoGhKOi6aGaccNpSLoa7TQj kimDoGfjbzqsLWzMHN4opbmCKFifpG0YetL56Q5dKkkxC2dtR+JBj/L4VJ/2CyMsccVJ /bdvFperxxD83xetY2fMTb8kuBDDqEaScg1sJv9W0PVMQUZtFRbML2rzvn1KAynuGG5U L5CCKjc9GO5aEcyLmCipeDFedxn6SDV1n/bwf+u50XpacE3tE+skf/AJqcLoHVuDiJ/U 6Iyw== X-Received: by 10.60.63.174 with SMTP id h14mr3384958oes.137.1367689739501; Sat, 04 May 2013 10:48:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.97.2 with HTTP; Sat, 4 May 2013 10:48:39 -0700 (PDT) In-Reply-To: References: From: Christian Grobmeier Date: Sat, 4 May 2013 19:48:39 +0200 Message-ID: Subject: Re: log4cx: attic or incubation? To: Logging General Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Fri, May 3, 2013 at 4:04 PM, Rhys Ulerich wrote: > The library is, more or less, stable and feature complete. There's > not much shepherding to be done in terms of driving the functionality > in some particular direction. That is, unless there's some burning > feature set that folks need that hasn't been discussed on the log4cxx > mailing list in the years that I have been lurking. The problem seems > to be that the overhead of contributing small fixes is off-puttingly > high. It's hard to elicit a YAY from anyone under these > circumstances. All true. I find it hard to believe that in all these years nobody needed a new feature. Maybe it's a language thing and all cxx devs are really happy with what they have. But on the other hand you are right, contributing is difficult. >> For now I would like to propose that I am cloning log4cxx to my GitHub >> account and move the svn repos to the attic. That way I can overlook >> if there is a team growing around log4cxx or not. Also I can ask for >> ICLAs before accepting pull requests, which should help when we go >> back to incubation. If there is, we can go back to incubation at any >> time. If there is not, then well, no harm done. >> >> Comments? > > I like this approach. Please also see the mail from Gary. He proposed to set up an official ASF mirror, from which we could directly accept patches (I heard). > I would ask that, before you do this, you please make one last 10.2 > release off the Apache-blessed sources. Trunk differs in slight but > important ways from 10.1 (e.g., it builds). This way the distro > package managers can at least get one last blessed version into their > pipelines before the log4cxx community goes off and experiments with a > reboot. The sad truth is that I never built log4cxx and I am not sure if I can do it - i simply have never done anything with cxx. Maybe I will get it with the help of the community. This at least would prove the interest of the people who raised their hand over at log4cxx land Thanks for speaking up! Cheers Christian > > - Rhys -- http://www.grobmeier.de https://www.timeandbill.de