C++Now 2021 -- Library in a Week: Boosting Boost
C++Now 2021 is next week. For those that have never been, every year we have a workshop session called Library in a Week. While the goal of the session might be obvious from the title, needless to say, final Boost libraries don't happen in a week. So, actually, the real underlying goal is to build boost community and discuss c++ library design with projects that don't conflict with attendees day jobs. Every year at the end of the session, I solicit ideas from the community about what 'library' we should work on in the following year. One consistent suggestion has been to work on boost community maintenance. With the conference all virtual this year, I think this is the year to do it. The goal will be to generate pull requests from new or even old boost participants to improve our code base. While I'm sure we could wander around the various libraries and find issues that need some work to generate pull requests, I'm posting this looking for suggestions from the bigger community. Note that this doesn't need to be exclusive to new code -- it can be documentation or tests. Are there particular libraries we should look at? Are there particular issues that someone would like a hand tackling? Are there some upgrades to newer c++ features that someone could jump in on? Thanks, Jeff
On 30/04/2021 23:55, Jeff Garland via Boost wrote:
C++Now 2021 is next week. For those that have never been, every year we have a workshop session called Library in a Week. While the goal of the session might be obvious from the title, needless to say, final Boost libraries don't happen in a week. So, actually, the real underlying goal is to build boost community and discuss c++ library design with projects that don't conflict with attendees day jobs.
Every year at the end of the session, I solicit ideas from the community about what 'library' we should work on in the following year. One consistent suggestion has been to work on boost community maintenance. With the conference all virtual this year, I think this is the year to do it. The goal will be to generate pull requests from new or even old boost participants to improve our code base.
While I'm sure we could wander around the various libraries and find issues that need some work to generate pull requests, I'm posting this looking for suggestions from the bigger community. Note that this doesn't need to be exclusive to new code -- it can be documentation or tests. Are there particular libraries we should look at? Are there particular issues that someone would like a hand tackling? Are there some upgrades to newer c++ features that someone could jump in on?
Yes. Boost.Graph could do with a close look, in particular: * There are pull requests for new features which need reviewing by someone competent in the field. * The code base is rather ancient, and some careful modernization wouldn't go amiss. Best, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
On Sat, May 1, 2021 at 2:50 AM John Maddock via Boost
Yes. Boost.Graph could do with a close look, in particular:
* There are pull requests for new features which need reviewing by someone competent in the field.
* The code base is rather ancient, and some careful modernization wouldn't go amiss.
Thanks -- that's a good one since there's also now a standards proposal
for graph which cites boost.graph as a primary implementation. I assume you have write permissions for the repo? http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2020/p1709r2.pdf btw, one of the 'wander around' projects in my back pocket if I don't get suggestions is to cleanup warnings -- especially in boost.locale. Everytime I test a release candidate there are hundreds of them -- it's very annoying. Jeff
participants (2)
-
Jeff Garland -
John Maddock