Hi all,
since our move to Github I noticed a major increase in incoming patches.
I like it. It clearly shows that it was a good decision.
But I don't like the fact that Github reviews are cannibalizing issues
on BPO. Before the migration decisions regarding a new feature or bug
fix were made on t
On Mon, May 1, 2017 at 3:32 PM, Christian Heimes wrote:
>
> 1) Should we try to move discussion back to BPO or are we fine with
> having major decisions just in Github PRs?
How will you do that? For Github, a PR and issue request ( an
equivalent of BPO issue) is same.
And we cannot disable revie
> On May 1, 2017, at 6:32 PM, Christian Heimes wrote:
>
> 3) How can we keep module maintainers and experts in the loop? For
> example I don't have the resources to read all Github PRs, but I still
> like to keep an eye on the ssl and hashlib module.
>
Add yourself to https://github.com/pyth
On 05/01/2017 03:32 PM, Christian Heimes wrote:
With Github I'm seeing a major paradigm shift. New contributors tend to
use BPO as ticket number dispenser. Actual discussion seems to happen
mostly on Github PRs. For me it makes it harder to follow discussion
> [...]
I don't have any answers, b
On 2 May 2017 at 08:32, Christian Heimes wrote:
> This brings me to my questions
>
> 1) Should we try to move discussion back to BPO or are we fine with
> having major decisions just in Github PRs?
>
> 2) How can we retain enough information on BPO to keep it useful as
> research database for past
