Alex,

I would like to start development on boost::iostreams.

I will start by forking the repo and checking the existing issues.

I'll appreciate any advice you could give in order to become a library maintainer.

Best Regards
Juan


On Fri, Jun 3, 2016 at 3:54 PM, Alex Olivas <olivas@icecube.umd.edu> wrote:


On 06/03/2016 09:11 AM, Robert Ramey wrote:
On 6/3/16 4:47 AM, Christian Meesters wrote:
Hi,

I noticed that there are numerous issues in the bug list, regarding
boost iostreams. However, the current doc states Copyright 2004-2007 and
Tickets do not receive responses. (I even read: "(I tried e-mailing
Jonathan Turkanis directly, but the e-mail address on the website seems
to be not used anymore)" in ticket 7574.

So, my question is: I anyone maintaining this library? If not: I doubt
that there is a good alternative, because iostreams just is convenient
to use and a selling point to for boost. It would be a pitty.


Maybe you'd like to take over the maintainence yourself?  Boost has a program whereby you can become the official library maintainer (BLOM). Since you depend upon the library and presumable have to monitor any issues anyway you might want to consider this.  It would be a good way to make a valuable contribution to Boost and C++ without having to take on alot of work you're not already doing.  And being an official maintainer of a well regarded boost library looks good on your resume as well.  It's a good career move.

Robert Ramey

I'm working on potentially expanding the list of libraries that need maintainers.  Looking at the github repo (https://github.com/boostorg/iostreams), the author did make a few commits last year.  Others have also been maintaining it.  Last commit was by Steve Watanabe.

Christian : If you're interested in becoming a BLOM, just let me know and I'll see if Jonathon is open to the idea.
Alex.

_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users



--
Juan
:wq