Subject: Re: [boost] Boost Graph maintenance
From: Aniket Pugaonkar (aniket.pugaonkar_at_[hidden])
Date: 2015-07-07 10:24:47
I would like to contribute as well. I have worked on BGL extensively for my
thesis and can help in this.
BGL documentation is precise and well written. i believe it is not under
active development but serves as a great library that uses generic
programming, parallel/distributed computing (PBGL) and graph theory
concepts that can be used for benchmarking and comparisons with other
libraries. there are several advantages of BGL as compared with other
libraries as well. BGL also have interface for other graph libraries such
as Stanford Graph Base. Some parts of the library may be confusing and
require some thought to understand it completely.
if we can help it make more detailed and example based, that would help a
On Tue, Jul 7, 2015 at 2:57 AM, Vladimir Prus <vladimir.prus_at_[hidden]>
> On 07-Jul-15 1:45 AM, Marcin Zalewski wrote:
>> Going back to this issue, does anyone know what is the procedure to become
>> a maintainer of a Boost library, specifically BGL in this case?
> I do not believe we have a formal procedure, but it would be roughly the
> same as for every other open-source projects:
> - Submit a number of technically sound patches
> - Ping them until they are accepted, or a reasonable number of pings go
> - When a number of patches are either accepted or ignored, request
> commit access, listing all such patches
> - Ping the request
> - If nothing happens, escalate to the steering committee.
> Does this help?
> Unsubscribe & other changes:
-- Thanks and regards, Aniket Pugaonkar
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk