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 10126F5FE for ; Wed, 29 May 2013 20:48:47 +0000 (UTC) Received: (qmail 78771 invoked by uid 500); 29 May 2013 20:48:47 -0000 Delivered-To: apmail-stdcxx-dev-archive@stdcxx.apache.org Received: (qmail 78673 invoked by uid 500); 29 May 2013 20:48:46 -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 78665 invoked by uid 99); 29 May 2013 20:48:46 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 20:48:46 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ltcmelo@gmail.com designates 209.85.223.171 as permitted sender) Received: from [209.85.223.171] (HELO mail-ie0-f171.google.com) (209.85.223.171) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 May 2013 20:48:42 +0000 Received: by mail-ie0-f171.google.com with SMTP id s9so8416074iec.30 for ; Wed, 29 May 2013 13:48:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=3e2BA36nshdJfkYjVru/kruIkmJRYm9UsHdKPxlufls=; b=nM/nae6ds21pGHGrUiNiVdOTFCicb5QYtsyiVmmiPGRedZgElpSywF218kk30JaYct 7oGc/Z1H6OspjuJ6Omenh7bjHXElWekSzhTJSSvqS1E0ifL4lwQ/AQiRzWIPyX73L705 rHhgM/M+18mfj2+lzG//3TnHzsdrEmK1BmPkoituKCywP+2rjPYQVuZF3fmjV7kDEBqo kwCS01kfN5aT7V8JVtnCthkSc2GdXjcb9kgk1iFOPAr6KxuuGKeDsaUR90mMWFzjuKdE 2nqFmGr3QJysk+E+gRTtJVcxzAwt+apBqeh20otfkz0Odwj3NAz18obUOuQY6hf15kZK TvRQ== X-Received: by 10.50.114.99 with SMTP id jf3mr2512940igb.66.1369860501379; Wed, 29 May 2013 13:48:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.43.58.198 with HTTP; Wed, 29 May 2013 13:48:01 -0700 (PDT) In-Reply-To: <51A6058D.4060605@pathscale.com> References: <378AB13E-3EB4-4108-85E0-490F81322D25@jaguNET.com> <51A5E7A5.2040908@pathscale.com> <51A6058D.4060605@pathscale.com> From: "Leandro T. C. Melo" Date: Wed, 29 May 2013 22:48:01 +0200 Message-ID: Subject: Re: Search for new chair To: dev@stdcxx.apache.org Content-Type: multipart/alternative; boundary=047d7b4146e093a18d04dde1801f X-Virus-Checked: Checked by ClamAV on apache.org --047d7b4146e093a18d04dde1801f Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, May 29, 2013 at 3:41 PM, "C. Bergstr=C3=B6m" wrote: > On 05/29/13 08:27 PM, Stefan Teleman wrote: > >> On Wed, May 29, 2013 at 7:33 AM, "C. Bergstr=C3=B6m" >> wrote: >> >>> On 05/29/13 06:29 PM, Jim Jagielski wrote: >>> >>>> I am stepping down as Chair of the C++ StdLib PMC. >>>> >>>> So the question is: Does this project and community >>>> elect a new Chair, or does it enter the Attic? >>>> >>> I'd be willing to chair if others are supportive >>> >> OK, so before I give you a +1, could you please outline what is your >> Plan(TM) regarding resurrecting this project? >> >> How are you going to do it, and, more specifically, what are you going t= o >> do? >> > Off the cuff reply and I'll give this more thought and planning if others > are supportive > > 1) I think the most important thing is grow the community > a. Let people know how important and STL is > b. Advocate for wider adoption/testing (See if we can get prebuilt > packages and clear instructions for how people can use/test STDCXX) > > > 2) Evaluate and get feedback from you and others about how we can improve > the project (Communication, code review, growth opportunities.. etc) > > 3) From my $JOB I can advocate to help with code review, QA and ensuring > good contributions like what you've done before actually get committed > -------------- > One thing I don't yet have a clear idea how to accomplish is C++11 > support. A C++03 STL is far from dead, but we need a 2-4 year plan to > catch-up with others. > > My guiding principle is : > Use, love and contribute back > > We need to increase our userbase 1st to start this cycle > > Hi, although I follow this list for a few years, it's actually my first post. I agree community would be on top, so let's say one would like to contribute to the project... What would be the greatest motivating factor? I mean: This project has been relatively quiet; There's now libc++, which can probably better attract developers (specially given its connection with clang) - as fair as I know Window/Linux are not complete yet; I guess STLport is also missing C++11, but I'd assume it's more widely spread than the STDCXX and with more derivations, then more potential as well. >From a more practical side, regarding popularity and consequently an active community: How much people (and who) are using STDCXX (I couldn't find this on the page, sorry if it's there somewhere) and in which areas can the STDCXX be awesome and differentiate from the others. Portability, i18n... -- Leandro http://www.ltcmelo.com --047d7b4146e093a18d04dde1801f--