July 2024 - Boost - lists.boost.org

Two mqtt libraries
by Robert Ramey 03 Oct '24

03 Oct '24

I've been contacted by my friend and sometime collaborator Takatoshi Kondo regarding his submission of a boost library: https://github.com/redboltz/async_mqtt. It has received two endorsements. He has asked me to be review manager and I'm inclined to accept this request as he was very helpful to me during the refinement of the boost serialization library. There is also mqtt client library that is proposed to the Boost. https://github.com/mireo/async-mqtt5 It also has endorsements and a review manager. A cursory examination of the git hub pages suggest considerable overlap between the two submissions. In general, boost has discouraged the acceptance of multiple libraries with this much overlap - and for good reason. An accepted library often becomes the canonical implementation in large parts of the C++ world. Having two high quality libraries that do almost the same thing is not where we would like to be. I would like to propose that we review both libraries simultaneously in order to try to reach a consensus as to which, if either we want to accept. I know this is a difficult task, but I think it is important that we do this. It's going to be tough to reject a well written library because a better one has been accepted. But it would be worse to reject a well written library merely because another one was submitted first. Normally I don't participate as a review manager as I'm pretty bogged down in Boost stuff as it is. But I'm willing to make an exception in this case due to the importance of this case and my strong personal ties to Takatoshi. BTW - who is the review wizard these days? I presume that he will be the one making the decision about this. Robert Ramey

16 38

Re: [boost] [compute] Maintenance status
by René Eng 18 Aug '24

18 Aug '24

Hi all I am no expert in OpenCL nor GPGPU, but very interested in this topic and would love to learn more about it. I volunteer to take care of the maintenance of this library. Since I have no experience with the Boost way of handling PRs etc., I guess would need some support from an experienced library maintainer in the beginning. Until now I was a silent reader here, so let me shortly introduce myself: My name is René Eng, 57 years old, living in Switzerland. I am working as a C++ developer for more than 20 years, in the high performance/low latency area. I have experience with some other Boost sub-libraries, in the past also used b2 to build Boost when there were no packages available yet. If there is no-one else with more experience in this topic, who wants to take over this library, I would. This week I am on holiday, so I would actually start to take a closer look into it next week. Best regards René Von meinem iPhone gesendet > Am 21.07.2024 um 17:04 schrieb Joaquin M López Muñoz via Boost <boost(a)lists.boost.org>: > It was brought to my attention that Boost.Compute seems to be all but abandoned: > no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a > shame given that the library looks pretty popular based on GH stars and references > on Internet. Are there volunteers to take on maintenance of the library? > > Best, > > Joaquin M Lopez Munoz > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 2

[Boost][BGL] new planar_vertex_coloring.hpp ?
by hermann＠stamm-wilbrandt.de 16 Aug '24

16 Aug '24

I have some experience in using BGL and porting my non-BGL graph code to BGL. I want to create pull request for generating random maximal planar graphs. I have 1994 technical report non-BGL implementation on gihub. So before porting that, I want to get some experience on the Boost pull request and review process. I made use of the many planar graph algorithms in straight_line_graphviz.cpp gist: https://gist.github.com/Hermann-SW/99d151a273d290ee0d843c79b2da26a8 So I thought on a providing planar graph vertex coloring algorthm(s) as handson. I would start by taking https://www.boost.org/doc/libs/1_85_0/libs/graph/doc/sequential_vertex_colo… as a template for "planar_vertex_coloring.hpp". My plan is to first port my existing fast linear time "six_coloring()" https://github.com/Hermann-SW/planar_graph_playground/blob/main/c%2B%2B/und… and learn about the review process with it. Later I would implement one of the several linear time "five_coloring()" algorithms: https://en.wikipedia.org/wiki/Five_color_theorem#Linear_time_five-coloring_… And probably the quadratic time "four_coloring()" algorithm mentioned there as well. I looked at commits in Boost graph directory and there is not that much recent activity. Is my plan and the steps outlined the right way to start? Regards, Hermann Stamm-Wilbrandt.

1 3

CMake Announcement from Boost Steering Committee
by Jon Kalb 13 Aug '24

13 Aug '24

The libraries produced by the Boost community have had a greater impact on the way that the C++ community writes code than any other library implementation. The focus of the Boost community will always be on the libraries, but it is undeniable that we are dependent on and often limited by the infrastructure of our trade. Years ago, the move to Git was contentious; yet, it was required to improve development. In a similar vein our build system has become an impediment for many developers and users, existing and prospective. Therefore, we, the Steering Committee, announce to the Boost community our desire and intent to move Boost’s build system to CMake for users and developers alike. We are soliciting comments and proposals from the community to guide the process and the goals. Our desire is that the community can come to consensus by the end of the calendar year with a vision of supporting users and developers. We understand that the actual process of achieving the end goal will be long, time consuming, and not without its share of conflict. We also recognize that the Boost community is comprised of bright and passionate individuals that are eager to get involved and help get work done. The members of the Steering Committee have been encouraged by the discussions and activity surrounding CMake on the mailing lists over the years and know that many people have voiced visions. We hope that each of you rejoins the discussion to support this initiative and contributes to the common goal of improving Boost’s integration into the broader C++ ecosystem. For the Boost Steering Committee, Jon Kalb, Chair jonkalb(a)boost.org

49 200

[config] First steps towards C++20 modules
by Antony Polukhin 12 Aug '24

12 Aug '24

Hi, C++20 modules seem to be a good tool to improve compile times and to hide the implementation details of the libraries. I've been looking throught the sources of {fmt} library. Looks like the fmt library approach to C++20 modularization seems to fit Boost quite well. How about adding the following macro to Boost: * BOOST_BEGIN_MODULE_EXPORT - starts the scope of things to export if Boost is build as a C++20 module * BOOST_END_MODULE_EXPORT - ends the scope of things to export if Boost is build as a C++20 module * BOOST_MODULE_EXPORT - for a single entity export if Boost is build as a C++20 module As a result, if Boost is build as a module the above macros are defined in the following way: #define BOOST_MODULE_EXPORT export #define BOOST_BEGIN_MODULE_EXPORT export { #define BOOST_END_MODULE_EXPORT } Helper macro BOOST_NO_CXX23_IMPORT_STD for detecting availability of `import std` also seems useful. Macro BOOST_NO_CXX20_MODULES - for notifying the libraries that compiler does not support modules or Boost modules are not compiled. With all the above macros the Boost libraries could look like: /// header #include <boost/library_that_is_known_to_not_support_modules.hpp> #ifdef BOOST_NO_CXX20_MODULES #include <boost/library_that_supports_modules.hpp> #else import Boost.LibraryThatSupportsModules; #endif #ifdef BOOST_NO_CXX23_IMPORT_STD #include <iostream> #else import std; #endif namespace boost { namespace detail { template <class T> bool try_do(const T&); } BOOST_BEGIN_MODULE_EXPORT template <class T, class From> bool try_lexiacal_convert(const From& f, T& to) { /*impl*/ } template <class T, class From> T lexiacal_cast(const From& f) { /*impl*/ } BOOST_END_MODULE_EXPORT } /// module src file export module Boost.MyLibraryName; #ifdef BOOST_NO_CXX20_MODULES #error ??? #endif #include <boost/my_library.hpp> -- Best regards, Antony Polukhin

5 14

Boost Governance?
by René Ferdinand Rivera Morell 10 Aug '24

10 Aug '24

A disclaimer: I write this solely as a Boost Library author. And not in any other capacity or representing any other interest. It's now been at least a year since Boost switched from the Software Freedom Conservancy to the Boost Foundation for its governance organization. But have people noticed any difference? Did you know that switch happened? Did you know that they held an election for the Board of Directors and for the Officers? Do you know when that election happened? Do you know who got elected? Do you know how they were selected? Do you know what their responsibilities are? Do you know what their bylaws are? Do you know their financials? More importantly: Did you answer "no" to any of those questions? As a library author, I can say I definitely answered no to many of those questions. This is a problem. As authors, without asking, we should know those answers from the organization that governs our work. We should have input into how that organization governs. In other words, we deserve open and transparent governance; not the closed and opaque status quo. -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

10 10

New Logo Discussion
by Vinnie Falco 10 Aug '24

10 Aug '24

Hi. It is CppCon 2024 season, and the C++ Alliance is working on letting people know all the new and exciting things happening in Boost. We're doing this with Boost labeled conference shirts, and a beautiful brochure. You can see a draft of this promotional piece here (note: work in progress): https://cppalliance.org/pdf/Boost-Brochure-CppCon-2024.pdf The new Boost logo was developed by the Alliance, and a community consensus is needed if we are to fully move forward with its use. I am hoping this will spark the necessary discussion. Here are things to consider: * The logo is professionally designed by https://grainandmortar.com/ at a cost of $12,000 * Peter Dimov likes the image (this should not be construed as his endorsement or opposition to any of the above). * The image is a trademark of The C++ Alliance: https://tsdr.uspto.gov/#caseNumber=98417319&caseSearchType=US_APPLICATION&c… * Usage of the logo is governed by our Logo Usage Policy, a product of legal review at a cost of $4,000: https://www.boost.io/doc/contributor-guide/docs/logo-policy-media-guide.html * The Logo Usage Policy allows free usage without permission in Boost-related contexts. Otherwise, explicit written permission from the Alliance is required. * Trademark ownership by a registered entity with sufficient resources is necessary to protect the mark, which David Sankel alludes to here: https://lists.boost.org/Archives/boost//2024/03/256092.php * Adopting this logo costs Boost nothing. If our proposed arrangement stops working for the community, the libraries can easily adopt a different logo (including the old one, or none). Put simply, I am asking the Boost community to entrust The C++ Alliance.with the responsibility of establishing and maintaining this new Boost logo. Thanks :)

18 63

Paul Bristow
by John Maddock 09 Aug '24

09 Aug '24

I've just heard that Paul Bristow who helped so much with the development of Boost.Math and indeed many other libraries, passed away peacefully last week. RIP Paul. Much missed. John.

7 7

[outcome] Inline GDB pretty printing support
by Niall Douglas 08 Aug '24

08 Aug '24

Dear Boost, The biggest new feature to land into Outcome since it went ABI stable is inline GDB pretty printing support, whereby we embed into all binaries using Outcome the Python script to display the state of `result<>/outcome<>`. As Outcome uses a layered inheritance technique to match triviality of member functions from its configured types, having to click down through the layers to discover the state was always frustrating. MSVC has long shipped with a visualiser to eliminate this, so now support for GDB matches MSVC support. The relevant implementation file can be found at: https://github.com/boostorg/outcome/blob/master/include/boost/outcome/outco… I would appreciate any testing and reporting of any issues or bugs before the 1.86 bugfix window closes. It should "just work" once you have enabled inline script loading in your `.gdbinit`. Thanks, Niall

10 19

A Follow Up to My Original Note Re The Future of Boost
by Kristen Shaker 06 Aug '24

06 Aug '24

Hello Everyone, Thank you for patiently waiting while we had the opportunity to discuss things. Many of you have not heard my name before - this is largely because as a board, we do much of the non - dev work behind the scenes, such as administrative tasks like paying bills. However, I do want to take this opportunity to introduce myself quickly and to emphasize that - should anyone wish to reach out to me directly - I am happy to correspond via phone or email. My name is Kristen - I spent many years at Google on the C++ Core Libraries Team. I am heavily involved as an organizer in CppCon and C++Now. If anyone is curious about what I did at Google, I did give a talk <https://www.youtube.com/watch?v=torqlZnu9Ag> on automated refactoring and Clang Tidies that you can find on Youtube. My duties as Board Chair involve sending out meeting agendas, taking meeting notes, and collating meeting minutes. It is not our role to lead, but rather to support the Boost project. The leadership and direction of the Boost project has and should remain with the Boost Developers. The original Boost Steering Committee home page articulates its purpose as follows: “In the Boost community decisions have always been made by consensus and individual members have shown leadership by stepping forward to do what they felt needed to be done. Boost has not suffered from a lack of leadership or volunteer participation. It is not the role of the Steering Committee to inhibit this kind of spontaneous leadership and action, which has served Boost and the wider C++ community so well. On the contrary, it is the role of the Steering Committee to facilitate community-based leadership and decision making. The role of the Committee is to be able to commit the organization to specific action either where funds are required or where consensus cannot be reached, but a decision must be made.” We generally encourage any Boost Developer who would like to be more involved in administrated or organizational decisions to consider joining the board. We have multiple open board seats. Several Boost Developers are on the board and additional developers have been invited in the past - however they have decided against joining due to their distaste for the type of administrative work we do. We would love to hear more from you. Please reach out. You can reach all of us at once via boostfoundationdirectors(a)boost.org. Additionally, if you’d like to attend one of our board meetings, we regularly host guests. The C++ Alliance and the Boost Board of Directors have had their disagreements. Recently, it has become apparent - in particular via their attempt to purchase the boost.org domain name and the proposed new Boost Logo - that The Alliance would like to exert a greater sense of ownership over Boost Library assets. The desired control over assets is what I was referring to in my original note regarding their attempt to take ownership over the Libraries. While the C++ Alliance is a non profit organization, it is wholly funded and effectively controlled by one individual - Mr. Falco. The Board of Directors has a stewardship responsibility to Boost and we are wary of a single individual exerting such a level of control over the Boost Libraries. The Board has existed for many years and will continue to exist - as new members are regularly on boarded as tenured ones retire. Given the structure of the Board and the nature of the volunteer work, we believe ourselves to be the more permanent entity. Many have mentioned a desire for cool headed coordination between the two organizations. I also believed this to be the most advantageous outcome, so I reached out to Mr. Falco to establish a direct line of communication. Even now I would characterize our personal relationship as quite positive. Due to some pre-existing personality clashes, it is now our understanding that Mr. Falco believes collaboration to be an impossibility. Therefore, a large part of Mr. Falco’s motivation to acquire the domain name stemmed from a desire to cut the Board of Directors out of all future decision making processes. Given that I believed we had made great progress toward greater collaboration, I was personally gutted by this turn of events. Accordingly, we did not see a well lit path forward regarding coordination between the Boost Board and the C++ Alliance. This decision was in no way meant to minimize the great contributions The Alliance has made to the Boost Libraries. We do not want to discourage Alliance members from contributing to Boost. This is fundamentally a question about the stewardship of the Boost Library Assets. As mentioned above, the Boost Board of Directors exists largely to facilitate community based decision making. Accordingly, we feel the most appropriate thing to do at this juncture would be to let the developers make a decision on how they would like to proceed regarding what level of ownership the C++ Alliance should have on Boost Library assets. Here are what we believe to be the available options. 1. The C++ Alliance assumes control of the Boost assets, including the boost.org domain name. The Boost Foundation becomes uninvolved in any decisions related to the Boost Libraries. 2. The Boost Foundation continues to be the stewards of the boost.org domain name and related assets. New assets that are meant to be associated with the Boost Libraries are transferred to the Boost Foundation. In any matters related to the Boost Libraries, the Board will abide by any decisions made by the developers but will no longer vote themselves on issues as they relate to the Boost Libraries unless there truly is no clear consensus or path forward. There was some discussion about the assets being held in a third party non profit controlled by a subset of the Boost Developers. However, given that there are already many Boost Developers on the Boost Foundation Board of Directors, we don’t see this as a meaningful deviation from the status quo. Also as one final note, many on the mailing list expressed a distaste for the political nature of this disagreement. Of course, being involved in political spats is not why you joined Boost! We completely understand this. Believe me when I say we don’t like dealing with political disagreements either - no one does. They’re draining and they can distract from an organization’s larger mission. However, sometimes, they are truly unavoidable. We’re articulating our thought process here, not to annoy you, but so every Boost Developer has a say in how things turn out. Warm Regards, The Boost Board of Directors Also here are some answers to some of the more specific questions. There were a lot of them and I believe some were answered in the preceding paragraph. Sincerest apologies if I missed a question or two. Beman Dawes did pass away in 2020. The Boost Foundation did take action when the domain expired. In fact, Michael Caisse spent many hours on the phone with support figuring out how to pay for the bill so the website would be accessible. Additionally, he invested significant time in procuring the death certificate so we could own the domain. Progress was being made, albeit slowly.

21 41

Notice of Intent To Redirect boost.org to boost.io
by Vinnie Falco 02 Aug '24

02 Aug '24

All: A consensus to launch the new Boost website was reached by both the community and the Boost Foundation. Since then, the Foundation has: * Ignored the consensus decision reached in April [1] * Prevented the C++ Alliance's attempt to secure the boost.org domain [2] * Launched the competing "Beman Project" [3] * Voted to "cut ties with the Alliance" [4] * Avoided important questions asked on the mailing list, for over a month As it is clear now that Foundation control of the boost.org domain may be harmful to Boost, the existing website will be redirected to the new website. Absent objection, this pull request to redirect boost.org to boost.io will be merged on August 5, 2024: https://github.com/boostorg/website/pull/861 Thanks [1] https://lists.boost.org/Archives/boost/2024/04/256602.php [2] https://cppalliance.org/pdf/Domain-Name-Purchase-Agreement.pdf [3] https://www.bemanproject.org/ [4] https://cppalliance.org/pdf/Boost-Foundation-Minutes.pdf

6 11

Master branch is now open for bug fixes
by Marshall Clow 31 Jul '24

31 Jul '24

The master branch is now open for bug fixes and documentation changes. Other changes by release manager permission, as described in https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy Release manager permission is not needed for test changes or documentation changes. The next deadline: On August 7th, master closes for all changes. As always, the calendar is at https://www.boost.org/development/ — Marshall

7 11

Requesting permission for a trivial change to LEAF
by Emil Dotchevski 30 Jul '24

30 Jul '24

It would be nice to include in the current release this small change that marks leaf::result objects as nodiscard: https://github.com/boostorg/leaf/commit/1f745805553934cd76a241649cd9bafa277… . Thanks, Emil

1 0

[release] Boost 1.86.0 beta 1 released
by Marshall Clow 26 Jul '24

26 Jul '24

Boost release 1.86.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.86.0.beta1/source/ The SHA256 checksums are: 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1.zip cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1.7z 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1.tar.gz Release notes (still need updates): https://www.boost.org/users/history/version_1_86_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. Thanks especially to Sam Darwin for his help with the tools, and figuring out what happend with RC3. -- Boost Release Team

1 0

Re: [boost] [release] Boost 1.86.0 Beta 1 Release Candidate 4 is available
by tobi＠die-loews.de 26 Jul '24

26 Jul '24

1 0

[release] Boost 1.86.0 Beta 1 Release Candidate 4 is available
by Marshall Clow 25 Jul '24

25 Jul '24

[ RC3 was malformed as a result of some tooling failures ] The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

5 7

Boost 1.86 release notes?
by Andrzej Krzemienski 25 Jul '24

25 Jul '24

Hi Everyone, Are 1.86 beta release notes available anywhere? I recall that the beta release documentation used to be put on boost.org. Regards, &rzej;

2 1

[release] Boost 1.86.0 Beta 1 Release Candidate 3 is available
by Marshall Clow 24 Jul '24

24 Jul '24

The third (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: a632d1e1465804b26f4d73112f1142c89caf74b026395df2e63a8c8972ac3ab0 boost_1_86_0_b1_rc3.tar.gz e061d83644568178ddece4bd3e241fb2656f49d6157c5d9fbff6c2fa74b1e328 boost_1_86_0_b1_rc3.zip e7f07bbc14915469b1ef80337c16e7a592f3eb547ba2cca828253c0a32372399 boost_1_86_0_b1_rc3.tar.bz2 91dcd8f980362c1c32bf8cc547c547fb02619bea877738b478c052926edc6a2d boost_1_86_0_b1_rc3.7z Changed libraries between RC2 and RC3: Boost.Process fixed some build issues on Windows As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

1 1

[release] Boost 1.86.0 Beta 1 Release Candidate 2 is available
by Marshall Clow 24 Jul '24

24 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: c62c9ab3c448ef4ed1b45f69631e3d7cc425fca96b991e5007b3af49f84344e1 boost_1_86_0_b1_rc2.zip 7e5b42428ed30a7ac9d832e9df9f5150a29d9cffe5aebde4d4c109da89f54b77 boost_1_86_0_b1_rc2.tar.gz 8718b092b37f04a739b647d154901d923fb3c3cdcff9f793d6a472e3f8e7c647 boost_1_86_0_b1_rc2.7z cd63cd3110fafbed8c196a82dd0f72c8600bc5c7fc218ede213947da3b721c06 boost_1_86_0_b1_rc2.tar.bz2 Changed libraries between RC1 and RC2: Boost.Process Boost.Odeint As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

3 3

[release] Status of the Beta release
by Marshall Clow 24 Jul '24

24 Jul '24

We’ve had some problems with the RCs for the 1.86.0 beta. The RC1 had problems with Boost.Odient and Boost.Process. We had an RC2 yesterday, but that didn’t fix all of the Boost.Process build problems. There will be an RC3 today, which (hopefully) will fix them . If nothing else is found the beta release will be Friday. — Marshall

1 0

[release[ Boost 1.86.0 Beta 1 Release Candidate is available
by Marshall Clow 23 Jul '24

23 Jul '24

Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: 90be7ebbaf1c81a849791eb0f49d05a9ec7dbd0ec98b974dfe31d44d811e8298 boost_1_86_0_b1_rc1.7z 543ca3b743250a8b24b25c71209cf911c35613910e78a320835c21c053212ef2 boost_1_86_0_b1_rc1.tar.gz 1bf831ed717fa3e01db6c1f104b95f5a6a8d098a4cc9e61fa6eb81969c78645f boost_1_86_0_b1_rc1.tar.bz2 f739f8761bee6006c60a39fd21ed80b7b0a681c9ed448d1ae1bb28d8d8a69659 boost_1_86_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

7 13

[Release] Master branch is closed for beta
by Marshall Clow 23 Jul '24

23 Jul '24

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

3 4

Q2 2024 Transparency Report on Boost C++ Library
by Louis Tatta 22 Jul '24

22 Jul '24

Hello, Louis Tatta here, CEO of The C++ Alliance, Inc, a registered 501(c)(3) non-profit organization dedicated to supporting C++. This is our Q2 2024 transparency report on our charitable work for the Boost C++ Library Collection. The C++ Alliance actively seeks out highly talented and experienced C++ experts, hiring them, often full-time, so they can fully dedicate themselves to open-source projects. Our Staff Engineers maintain existing Boost libraries, develop new ones, and contribute to other Boost projects. We also employ IT experts full-time to maintain and enhance the infrastructure supporting Boost. This includes the legacy web server, the Drone continuous integration servers, deployment scripts for GitHub Actions on Boost repositories, and scripts that publish Boost releases. Additionally, we provide on-demand technical support services for Boost authors and maintainers facing infrastructure-related issues. The Boost Mailing List remains the premier venue for high-quality discussions on Boost libraries and related C++ Standards topics. The C++ Alliance continues to support the mailing lists, upgrading them to the latest Mailman version and developing an optional web-based front-end for browser-based interaction. We also manage the Official C++ Language Slack Workspace ( https://cpp.al/slack) hosting the most popular interactive discussions on Boost libraries. The C++ Alliance sponsors a paid plan to offer full history, video and audio conferencing, collaboration tools, and unlimited document storage for seventeen dedicated Boost library channels and one main Boost discussion channel. Our largest project for Q2 2024 is the ongoing development of the new Boost website. This new site will be a C++ social media portal with rich support for user-generated content and a robust back-end that provides visibility into contributions made on GitHub and the release process. Our goal is to deliver an enhanced user experience that attracts fresh talent to Boost. Notably, the website features hand-drawn graphics by our contract artist, reflecting our commitment to ensuring Boost not only functions well but also looks visually appealing. In Q2 2024 there were a total of zero Boost Formal Reviews. There were two petitions for endorsement for potential Boost candidates: *async_mqtt from Takatoshi Kondo (https://github.com/redboltz/async_mqtt) *multi from Alfredo Correa (https://gitlab.com/correaa/boost-multi) There's another MQTT library in the works proposed on Nov 2023, Async.MQTT5 from Ivica Siladic, Bruno Iljazovic and Korina Simicevic ( https://github.com/mireo/async-mqtt5) There were a total of three messages from the @Boost_Libraries X (formerly Twitter) account, all submitted by C++ Alliance team members. One of them featured artwork from Bob Ostrom, commissioned by us. Posts with visuals are three times more engaging than those with just text. We see the X platform as a vital tool for educating newer generations about the benefits of Boost. A total of $526,000 was spent on Boost-related contributions, broken down thusly (and rounded to the nearest thousand): Staff Engineers Compensation $392,000 Website Software Development $111,000 Server Hosting $23,000 During Q2 2024 we employed a total of 13 individuals to contribute to Boost. Here is a high-level summary of accomplishments: Sam Darwin (Chief Technical Officer) - Summary: Sam Darwin led major projects, overseeing the integration of new features in the Boost infrastructure. He coordinated between teams, ensuring smooth transitions and high-quality deliverables. His leadership was pivotal in the development of the new Boost website and improvements to the mailing list system. - Link: Sam Darwin's Q2 Update <https://cppalliance.org/sam/2024/07/10/SamsQ2Update.html> Dmitry Arkhipov (Staff Engineer) - Summary: Dmitry Arkhipov focused on maintaining and enhancing Boost libraries. He implemented several bug fixes, optimized existing code, and contributed to the development of new libraries. Dmitry also played a significant role in the continuous integration and deployment processes. - Link: Dmitry Arkhipov's Q2 Update <https://cppalliance.org/dmitry/2024/07/12/dmitrys-q2-update.html> Alan de Freitas (Staff Engineer) - Summary: Alan de Freitas worked extensively on the Boost website redesign, particularly on the back-end systems that support user-generated content and GitHub integration. He also contributed to developing new libraries and maintaining existing ones. - Link: Alan de Freitas's Q2 Update <https://cppalliance.org/alan/2024/07/13/AlanQ2Update.html> Christian Mazakas (Staff Engineer) - Summary: Christian Mazakas worked on enhancing Boost’s infrastructure, including optimizing server performance and improving deployment scripts. His contributions were crucial for maintaining the stability and efficiency of the Boost libraries. - Link: Not provided. Krystian Stasiowski (Staff Engineer) - Summary: Krystian Stasiowski focused on developing new features for existing Boost libraries and worked on performance optimizations. His work included contributing to the ongoing development of new libraries and providing technical support to other Boost authors. - Link: Krystian Stasiowski's Q2 Update <https://cppalliance.org/krystian/2024/07/15/KrystiansQ2Update.html> Peter Turcan (Senior Technical Writer) - Summary: Peter Turcan was responsible for creating and updating documentation for Boost libraries. He ensured that all new features and libraries were well-documented, making it easier for users to understand and utilize Boost’s capabilities. - Link: Peter Turcan's Q2 Update <https://cppalliance.org/peter/2024/07/07/PeterTurcan-Q2-2024.html> Matt Borland (Staff Engineer) - Summary: Matt Borland contributed to the development of new libraries and enhancements to existing ones. His focus was on improving library performance and ensuring that the codebase remained robust and reliable. - Link: Matt Borland's Q2 Update <https://cppalliance.org/matt/2024/07/08/Matts2024Q2Update.html> Ruben Perez (Staff Engineer) - Summary: Ruben Perez worked on several infrastructure projects, including server maintenance and optimization. He also contributed to the development and maintenance of Boost libraries, focusing on performance improvements and bug fixes. - Link: Ruben Perez's Q2 Update <https://cppalliance.org/q2_update/2024/07/09/RubenQ2.html> Mohammad Nejati (Staff Engineer) - Summary: Mohammad Nejati was involved in developing new libraries and improving existing ones. He focused on optimizing code and ensuring that Boost libraries were efficient and reliable. His work also included providing technical support to other developers. - Link: Mohammad Nejati's Q2 Update <https://cppalliance.org/mohammad/2024/07/10/MohammadsQ2Update.html> Fernando Pelliccioni (Staff Engineer) - Summary: Fernando Pelliccioni contributed to the ongoing development of the Boost libraries, focusing on implementing new features and optimizing performance. His work was instrumental in ensuring the high quality and reliability of Boost libraries. - Link: Fernando Pelliccioni's Q2 Update <https://cppalliance.org/fernando/2024/07/08/FernandoQ2Update.html> Joaquin M Lopez Munoz (Staff Engineer) - Summary: Joaquin M Lopez Munoz worked on several key projects, including the development of new Boost libraries and enhancements to existing ones. His contributions focused on improving code efficiency and performance. - Link: Joaquin M Lopez Munoz's Q2 Update <https://cppalliance.org/joaquin/2024/07/06/Joaquins2024Q2Update.html> Kenneth Reitz (Staff Engineer) - Summary: Kenneth Reitz focused on developing and maintaining Boost libraries, implementing new features, and optimizing existing code. His work also involved providing technical support and contributing to the Boost website redesign. - Link: Kenneth Reitz's Q2 Update <https://cppalliance.org/kenneth/2024/07/12/KennethQ2Update.html> Braden Ganetsky (Junior Staff Engineer) - Summary: Braden Ganetsky, as a junior engineer, contributed to various Boost library projects. His work included implementing new features, fixing bugs, and assisting with infrastructure maintenance. Braden’s contributions were valuable in supporting the overall development efforts. - Link: Braden Ganetsky's Q2 Update <https://cppalliance.org/braden/2024/07/14/BradenQ2Update.html>

6 8

Modular Boost status..
by René Ferdinand Rivera Morell 21 Jul '24

21 Jul '24

Yesterday I created PRs for each library that introduces the changes to build (and some code) to implement the modular B2 building. I track all the PRs here: <https://github.com/users/grafikrobot/projects/1/views/2> All the library PRs are in Draft status, as we wait for the tool related PRs to get merged. You can read an explanation of the changes here <https://github.com/grafikrobot/boost-b2-modular/blob/b2-modular/README.adoc> (the explanations may differ slightly from current reality). IMPORTANT: The PRs are all "Draft" as I continue to monitor build errors from any CI errors in the PRs. And to address feedback from authors. After the current release the process will go something like this: * I fix any current fallout in draft PRs. * The 1.86 release happens. * The owners merge the tool PRs to develop and master. * I fix any fallout from that. * Authors, and owners, merge library PRs to develop and master. * I fix any fallout from that. * I create subsequent PRs for the global B2 Boost build infrastructure to remove the old non-modular dead code. * The 1.87 release happens. Questions? -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

1 0

[compute] Maintenance status
by Joaquin M López Muñoz 21 Jul '24

21 Jul '24

It was brought to my attention that Boost.Compute seems to be all but abandoned: no updates in three years, more than 100 issues filed, 27 unattended PRs. This is a shame given that the library looks pretty popular based on GH stars and references on Internet. Are there volunteers to take on maintenance of the library? Best, Joaquin M Lopez Munoz

1 0