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? On Fri, Jul 3, 2015 at 6:00 PM Marcin Zalewski wrote:

I would help out as well.

On Fri, Jul 3, 2015 at 11:16 AM GAURAV GUPTA wrote:

...

I could help in reviewing english text. On Jul 2, 2015 3:13 AM, "Oodini" wrote:

...

Hello,

I've been working on BGL for several days, and I'll probably have to

work on it for a long time.

...

The documentation is not very clear (I suspect it is outdated on some

points), and as it doesn't seem complete.

...

Also, the official maintener, Jeremiah Willcock, hasn't commited since

the end of 2013.

...

I'd like to work on the documentation, in the first time on the

organization and presentation.

...

If I amend the text later, I will need a reviewer (my english is not good enough).

What would be the process ? I havn't participated to any Boost library.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

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 lot. thanks Aniket On Tue, Jul 7, 2015 at 2:57 AM, Vladimir Prus wrote:

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?

Marcin,

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 unanswered - 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?

Thanks, Volodya

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

-- Thanks and regards, Aniket Pugaonkar