On Wed, 29 May 2013 15:55:45 -0600 Martin Sebor <mse...@gmail.com> wrote:
> > FYI: A chair doesn't necessarily need to have a plan to do anything > other than fulfill the duties assigned to them by the ASF: > > http://www.apache.org/dev/pmc.html#chair > > It's mostly a bureaucratic role, and can be a big time sink (reading > all the mailing lists, like board and members can be especially time > consuming). Other than that, being a chair doesn't give one the power > or ability to assure the success of a project than the rest of us. All good points. Although I'd caution against using members@ as any yardstick for chairing a project, the comdev (community development) and the general@incubator lists can be much better lists to follow to observe the pain points in other projects and solutions to help improve the way than an ASF project could function as a community. But those don't have to be all on the chair, anyone from the project can follow those lists, and you might find like-minded C++ developers on a list like general@incubator, or good ideas for recruiting docs authors and building a larger community from comdev. As a 'community' project it is going to take the efforts of more than simply one chair to really reenergize stdcxx to accomplish some of the many things that are being kicked around on the list this week. Glad to see the project has a good candidate for chair, and to see good discussion on moving it forwards :)
