16.06.18 02:59, Victor Stinner пише:
The problem is that there are 3 lists and each has different numbers
of core developers: 90 according to GitHub, 170 according to
bugs.python.org.
* https://github.com/orgs/python/teams/python-core/members
*
https://bugs.python.org/user?iscommitter=1&@actio
16.06.18 03:03, Victor Stinner пише:
Oh. After I sent my email, I checked the translation of "Missing In
Action". It means more or less "lost", but it seems to be commonly
associated to war:
Good illustration of the loss in translation. :-)
___
pyth
> At FOSDEM (last February), I saw an interesting talk by VM (Vicky) Brasseur:
> "Passing the Baton: Succession planning for FOSS leadership"
Sorry, I forgot the link to the video and slides:
https://fosdem.org/2018/schedule/event/community_passing_the_batton_foss_leadership/
Victor
_
This idea also comes from Brett Cannon who proposed something similar:
https://mail.python.org/pipermail/python-committers/2018-June/005526.html
Victor
2018-06-16 1:59 GMT+02:00 Victor Stinner :
> Hi,
>
> Last months, we debated about the number of *active* core developers.
>
> The problem is tha
Hi,
At FOSDEM (last February), I saw an interesting talk by VM (Vicky) Brasseur:
"Passing the Baton: Succession planning for FOSS leadership"
She explains that the maintenance of a project should be splited into
small tasks, and that each task should be done by at least two people.
Why at least t
"Missing In Action"
Oh. After I sent my email, I checked the translation of "Missing In
Action". It means more or less "lost", but it seems to be commonly
associated to war:
https://en.wikipedia.org/wiki/Missing_in_action
"a casualty classification assigned to combatants, military chaplains,
comb
Hi,
Last months, we debated about the number of *active* core developers.
The problem is that there are 3 lists and each has different numbers
of core developers: 90 according to GitHub, 170 according to
bugs.python.org.
* https://github.com/orgs/python/teams/python-core/members
*
https://bugs.
On Thu, Jun 14, 2018 at 8:06 PM Nathaniel Smith wrote:
> On Thu, Jun 14, 2018 at 4:40 AM, Berker Peksağ
> wrote:
> > This isn't about my or someone else's high standards. We keep saying
> > we need more triagers and reviewers, and we keep promoting people who
> > didn't do any issue triaging and
15.06.18 05:05, Nathaniel Smith пише:
On Thu, Jun 14, 2018 at 4:40 AM, Berker Peksağ wrote:
This isn't about my or someone else's high standards. We keep saying
we need more triagers and reviewers, and we keep promoting people who
didn't do any issue triaging and code review. It's not fair to
c
Thanks. It's working as expected now. :-)
On 06/15/2018 16:59, Victor Stinner wrote:
Hi,
It happened sometimes to me one month ago, but then it was fine. The
workaround is to close/reopen the PR. The best way is to use AppVeyor
UI, but here there was no AppVeyor link from the PR.
Close/Reopen
13.06.18 23:46, Victor Stinner пише:
It's not like Pablo proposed the idea himself and force to get this
feature merged. Pablo just implemented an idea proposed by two other
core developers.
It looks like Pablo implements ideas for which he does not fully
understand the consequences and the dr
Hi,
It happened sometimes to me one month ago, but then it was fine. The
workaround is to close/reopen the PR. The best way is to use AppVeyor
UI, but here there was no AppVeyor link from the PR.
Close/Reopen worked: AppVeyor is now running.
https://ci.appveyor.com/project/python/cpython/build/3.
I have just encountered a problem in PR1958. The appveyor CI prevents me from
merging it. I can't see no way to disabling it or rerunning it, no details
link. And is it possible to apply our new CIs, like vsts to it now?
Regards
Xiang Zhang
___
python-
13 matches
Mail list logo
