January 2018 - Boost-announce - lists.stage.boost.cppalliance.org

[boost][review] Outcome v2: Review Period Concluded (Fri-19-Jan through Sun-28-Jan, 2018)
by charleyb123 . 29 Jan '18

29 Jan '18

Hi, Everyone-- The Boost Review Period for the formal review of Niall Douglas' Outcome (v2) library is concluded (having run Fri-19-Jan through Sun-28-Jan, 2018). Reviews were posted from: - Vinícius dos Santos Oliveira (Fri-26-Jan-2018) - Andrzej Krzemienski (Fri-26-Jan-2018) - Bjorn Reese (Sun-28-Jan-2018) - Daniela Engart (Sun-28-Jan-2018) - John P Fletcher (Sun-28-Jan-2018) In addition, online discussions included comments, observations, and critiques from a number of other community participants. It will take some time to review the discussion, make a final determination, and prepare the Review Report. Please: - Contact me (directly or on-list) if I missed identification of your review during the review period; - Contact me (directly or on-list) if you have any concerns; or to raise any salient observations or "final thoughts" Thank you! --charley Boost.Outcome(v2) Review Manager

1 0

Google Summer of Code with Boost
by David Bellot 20 Jan '18

20 Jan '18

Hi everyone, still a few days before we submit our proposal to Google. Don't loose the chance to become a mentor for Boost. It shines on your CV, it is a great opportunity to work with brilliant students around the world, it makes you an official C++ world-wide expert. So far, we have a nice but little list of proposals here: https://github.com/boostorg/boost/wiki/Boost-Google-Summer-of-Code-2018 It would be good to have a bit more before I go and submit to Google. This will increase our chances to be selected again this year. For Boost it's a great funding worth several thousand of dollars every year. We just don't want to miss it. Best regards, David

1 0

[boost][review] Review of Outcome v2 (Fri-19-Jan to Sun-28-Jan, 2018)
by charleyb123 . 18 Jan '18

18 Jan '18

Hi, Everyone, The formal review of Niall Douglas' Outcome (v2) library begins Fri-19-Jan and continues until Sun-28-Jan, 2018. Your participation is encouraged, as the proposed library is uncoupled and focused, and reviewers do not need to be domain experts to appreciate the potential usefulness of the library and to propose improvements. Everyone needs (and has suffered) error handling, and can compose an opinion on that topic. Outcome is a header-only C++14 library providing expressive and very lightweight 'outcome<T>' and 'result<T>' error handling, suitable for low-latency code bases. The library further provides mechanisms for wrapping '<success|error|exception>' state to safely wrap throwing APIs; and poses an idiom of, "islands of exception in a sea of noexcept". Key features: *- Makes using 'std::error_code' from C++11's <system_error> more convenient and safe *- Good focus on low-latency (with tests and benchmarks) *- Error-handling algorithmic composition with-or-without C++ exceptions enabled *- Dependency only on Boost Recall a previous Outcome (v1) Boost Review occurred 19-May to 02-June 2017: *- Outcome (v1) Review Report: *- https://lists.boost.org/Archives/boost/2017/06/235783.php This review for Outcome (v2) includes significant changes as a result of feedback from the Outcome (v1) review. For a list of changes (v1==>v2), see: *- https://github.com/ned14/outcome#changes-since-v1 Reference API docs: *- https://ned14.github.io/outcome/reference/ GitHub: *- https://github.com/ned14/boost-outcome Tarball: *- https://github.com/ned14/boost-outcome/releases/tag/v2. 0-boost-peer-review Online "play-pen" (try it out!): *- https://wandbox.org/permlink/Ji1khzyxoAR0LJQC YOUR REVIEW --------------------- Please post your comments and review to the boost mailing list (preferably), or privately to the Review Manager (to me ;-). Here are some questions you might want to answer in your review: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And most importantly: - Do you think the library should be accepted as a Boost library? For more information about Boost Formal Review Process, see: http://www.boost.org/community/reviews.html Thank you very much for your time and efforts. --charley Outcome (v2) Review Manager

1 0

Google Summer of Code 2018
by David Bellot 10 Jan '18

10 Jan '18

Dear Boost community, once again this year, we will apply to be a mentoring organization for the Google Summer of Code 2018. Our organization has been quite succesful for the last decade and this year we hope to be selected again. As part of filling in our application for 2018, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2018 in order to be approved as an organisation this year. Therefore a lengthy page of awesome project ideas at https://svn.boost.org/trac/boost/wiki/SoC2018 before *January 23rd* would be an enormous help to getting us approved again this year and bringing to Boost another Google funding (worth dozens of thousands of dollars on average). If you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list. If you want to have a better chance receiving funding for your project ideas, it is better to find good students early and that is best done by getting project ideas floated *early*. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost(a)lists.boost.org or via gsoc-admin(a)boost.org. Thank you in advance for your time. Finally, I would like to thank Niall Douglas, our previous Boost admnistrator for GSoC, who did an awesome work during many years and helped the Boost community grow thanks to all the funding we received years after years from Google. Best regards, David

1 0