Subject: Re: [boost] Trac
From: Edward Diener (eldiener_at_[hidden])
Date: 2018-08-30 23:03:05
On 8/30/2018 4:41 PM, jrmarsha via Boost wrote:
> On 8/30/18 4:07 PM, Edward Diener via Boost wrote:
>> On 8/30/2018 1:42 PM, jrmarsha via Boost wrote:
>>> On 8/22/18 8:29 AM, Marc Glisse via Boost wrote:
>>>> On Wed, 22 Aug 2018, John Maddock via Boost wrote:
>>>>>> If so, all github repositories must have issues enabled.Â Right
>>>>>> now, I have
>>>>>> no way to file an issue to Boost.Graph.
>>>>> Now enabled.Â Let me know if there are any other repositories in
>>>>> the same situation.
>>>> At least "algorithm" (I asked about algorithm and graph in July) and
>>>> the super-project, which is were I would expect to report that
>>>> issues are disabled for some subproject...
>>> If graph needs a maintainer, I might be able to step up.Â I have a
>>> more intuitive and extensible implementation nearing completion which
>>> I think people would take interest in.Â Of course, I'm someone
>>> relatively out of the blue and that may not be OK, but it is something.
>> I think that would be great.
> It looks like there is quite a work backlog, and that Jeremiah Willcock
> is the primary person on this.Â There are also pending pull requests.
> What should I be doing?
First you need to get write access to the graph repository if you are
going to be a maintainer. After that the PRs should get top priority.
Following that you can look at any Issues and if you want to go back you
can look at Trac bug reports for graph. Of course if things come up on
this mailing list feel free to be as responsive and active as you like.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk