Return-Path: X-Original-To: apmail-stdcxx-dev-archive@www.apache.org Delivered-To: apmail-stdcxx-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D7DE9FEA for ; Thu, 2 Feb 2012 20:18:48 +0000 (UTC) Received: (qmail 43285 invoked by uid 500); 2 Feb 2012 20:18:48 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 43239 invoked by uid 500); 2 Feb 2012 20:18:47 -0000 Mailing-List: contact dev-help@stdcxx.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stdcxx.apache.org Delivered-To: mailing list dev@stdcxx.apache.org Received: (qmail 43231 invoked by uid 99); 2 Feb 2012 20:18:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 20:18:47 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [64.78.233.62] (HELO moroha.roguewave.com) (64.78.233.62) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2012 20:18:40 +0000 Received: from vw-fw.roguewave.com (eagle.blue.roguewave.com [10.50.5.40]) by moroha.roguewave.com (8.13.6/8.13.6) with ESMTP id q12KIIDK013574 for ; Thu, 2 Feb 2012 20:18:18 GMT Received: from Fountain.Blue.Roguewave.Com (10.55.5.1) by Eagle.Blue.Roguewave.Com (10.50.5.40) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 2 Feb 2012 13:18:18 -0700 Received: from [10.50.4.100] (10.50.4.100) by mymail.roguewave.com (10.55.5.1) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 2 Feb 2012 13:18:17 -0700 Message-ID: <4F2AEF3F.9040500@roguewave.com> Date: Thu, 2 Feb 2012 15:17:03 -0500 From: Andrew Black User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: Subject: Re: [VOTE] Retirement of stdcxx to the 'Attic'? References: <4F2AC1FE.3040604@rowe-clan.net> In-Reply-To: <4F2AC1FE.3040604@rowe-clan.net> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org While I am not completely familiar with the process, I took a couple minutes to look at the website for the Attic project ( http://attic.apache.org/ ), and I thought I'd summarize the implications of this move as I understand them. A move to the attic means the following (major) changes to the STDCXX project: * The STDCXX PMC will be dissolved. * The following resources will be made read-only: ** The subversion repository ( http://svn.apache.org/repos/asf/stdcxx ) ** The JIRA project ( http://issues.apache.org/jira/browse/STDCXX ) ** The wiki ( http://wiki.apache.org/stdcxx/ ) * The dev@, commits@ and private@ mailing lists will be closed Once the project has been moved to the attic, it will only be moved out if one of the following events happen: * The community is restarted in the Apache Incubator. * The PMC is recreated. * The project is forked. I get the impression that there are at least a couple informal forks of the codebase out there, but I have neither the time nor inclination to follow these forks and commit the changes back to subversion. The Attic website says they will link to any forks which have been created, but I don't know what criteria must be met for this to happen. --Andrew Black On 02/02/2012 12:03 PM, William A. Rowe Jr. wrote: > Fans and contributors, > > it appears that the stdcxx project is entirely dormant. The ASF has > launched a new 'Attic' project over the past two years, to neatly > retire dormant works until and unless a community comes along who > wishes to revive the effort. > > As a simple formality your votes please; > > [ ] +1 - stdcxx committee should be retired, with code sent to the Attic > > [ ] -1 - No, stdcxx should not fold, I am still contributing, and > [would serve|am serving] on its project management committee > > The results of this vote will be taken up by the ASF Board of Directors > at their 15 Feb meeting.