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.

The process is currently pretty simple. It's not that different than the standard open source model. Feel free to fork that repo and submit pull requests. Watch the repo and comment on development. For this particular library there are currently 23 open pull requests. Please feel free to comment on those pull requests as well. At some point BLOMs will be able to commit directly to the library, but for now PRs are the way to go. For more information about the BLOM program check out this page : http://beta.boost.org/community/official_library_maintainer_program.html I still need to update that site and get it merged to the live site, which hopefully will happen soon. Alex. On 06/03/2016 02:06 PM, Juan Ramírez wrote:

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 mailto: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 mailto:Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- Juan :wq

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

Christian, completely understandable. :) We also rely heavily on iostreams and I've added it to my watchlist. I'll try to help with it as well. Alex. On 06/03/2016 11:06 PM, Christian Meesters wrote:

Hi,

I kind of anticipated this answer. And I would love to participate. However, job and family obligations make me very hesitant to take on more long-term tasks.

This being written, I would like to thank Juan for his offer. I myself will look into an issue or two. I do, however, think some of the unhandled pull requests effect the overall situation and the issues I perceived. Juan, if you start working as a BLOM on iostreams, feel free to contact me directly: I do not want to make the situation worse, yet once you gain some overview I can make fresh pulls, test, fix and make commits / pull requests sometimes.

Perhaps it would be a good idea to meet some of you in Berlin, later this year. But so far my boss is very reluctant to pay ...

Thanks a lot to all of you, have a nice weekend, Christian

On 06/03/2016 05:11 PM, 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

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

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

Thanks for the info! A co-maintenance model is definitely going to be a feature of the BLOM project, since this same issue has come up for other libraries with authors who are currently actively maintaining them, but would welcome help. On my todo list is to add that option to the BLOM site. Alex. On 06/04/2016 08:13 AM, Bjorn Reese wrote:

On 06/04/2016 03:19 PM, Alex Olivas wrote:

...

We also rely heavily on iostreams and I've added it to my watchlist. I'll try to help with it as well.

When I asked Jonathan 2-3 years ago, he responded that he had been too busy, but that he intended to resume proper maintenance. Needless to say that he never did.

However, you may consider some kind of co-maintenance model with Jonathan as he may have valuable input to the various change requests.

He can be contacted via:

http://www.coderage.com/contact/

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

On 06/04/2016 02:23 PM, Robert Ramey wrote:

On 6/4/16 10:14 AM, Alex Olivas wrote:

...

A co-maintenance model is definitely going to be a feature of the BLOM project, since this same issue has come up for other libraries with authors who are currently actively maintaining them, but would welcome help. On my todo list is to add that option to the BLOM site. Alex.

I would be careful about this. I believe that a key requirement for library maintenance is assignment and acceptance of responsibility authority by/to one specific, publicly identifiable person. That person can parcel out authority for fixing different things to different people. Indeed this happens all the time (e.g. github prs) but one person has to act as the gate keeper. If this is not done, persons will conflict, problems will be everyone's problem rather than my problem and things will peter out to standstill.

So consider just tweaking the authority of the BLOM to include the delegation of fixes to persons he deems suitable.

I definitely agree and I should probably have been clearer about what the co-maintenance model might look like. This is what I'm thinking... For libraries where the current maintainer would welcome BLOM help, the current maintainer would be the sole person responsible for maintenance of the library. Any BLOMs would be resources the maintainer could enlist to help out with maintenance in a support role. I'll make a point to make this clear to both maintainers and BLOMs. Alex.

On Sat, Jun 4, 2016 at 12:06 AM, Christian Meesters wrote:

Hi,

I kind of anticipated this answer. And I would love to participate. However, job and family obligations make me very hesitant to take on more long-term tasks.

I completely understand your position. However, another way to look at it is what is the time commitment required to maintain the *current* level of maintenance on the library, and could you commit to *that*? -- Chris Cleeland

In the meantime what is the alternative ? What can we use instead ?  Shubha D. Ramanishubharamani@gmail.com shubharamani@yahoo.com On Wednesday, August 31, 2016 7:24 AM, Juan Ramírez wrote: Hi all, I just wanted to let you know that I am starting to contribute to this library.  Right now I am in the first stages, understanding devices, sinks, etc. I am also reading the BLOMP and all the related stuff in order to understand boost's process. In the near future I will be able to take on the existing issues and testing pull requests (there are a lot of them). Best regards,Juan _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users