Please add your GitHub username to your bugs.python.org account
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-commiters; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
On 5 April 2016 at 09:45, Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern...
Pre-empting a possible data quality problem: while everyone has left it out so far, at some point we may start to see entries with the leading "@" included in the GitHub username field. The GitHub API doesn't strip that automatically, so we may need to clean it either in Roundup directly or by stripping it in the bots when they retrieve the username information from Roundup.
Cheers, Nick.
On Mon, 4 Apr 2016 at 18:29 Nick Coghlan ncoghlan@gmail.com wrote:
On 5 April 2016 at 09:45, Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username
sometime
this month. You can see who has already filled in their username by
going to
http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern...
Pre-empting a possible data quality problem: while everyone has left it out so far, at some point we may start to see entries with the leading "@" included in the GitHub username field. The GitHub API doesn't strip that automatically, so we may need to clean it either in Roundup directly or by stripping it in the bots when they retrieve the username information from Roundup.
It won't work on the bot end without making redundant calls with the '@' sign when a GitHub username isn't found since we query based on GitHub username. As for the Roundup-side, it can probably be tweaked to error if an '@' sign is entered.
But I suspect it won't happen very often -- I personally don't see people using the '@' sign prepended to their GitHub username when simply stating it really ever -- and when it does at least in the case of the CLA bot it will simply say it can't find a signed CLA and we can work with the person directly to resolve it.
-Brett
Cheers, Nick.
-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
I'll email here again when I'm done so people can check that they were added to the team properly.
On Sun, 1 May 2016 at 14:14 Brett Cannon brett@python.org wrote:
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
On Mon, May 2, 2016 at 10:57 PM, Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
Just a note: above URL is giving 404 for me.
Kushal
Fedora Cloud Engineer CPython Core Developer http://kushaldas.in
On Mon, May 2, 2016 at 11:05 PM, Kushal Das kushaldas@gmail.com wrote:
On Mon, May 2, 2016 at 10:57 PM, Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
Just a note: above URL is giving 404 for me.
It is now showing :)
Kushal
Fedora Cloud Engineer CPython Core Developer http://kushaldas.in
OK, all done! For those of you already members of the Python org on GitHub you should be added already. For those of you who weren't, check your email for an invite (except for Alexander and Paul; you two are getting personal emails about issues).
I have also made Antoine and Georg team maintainers as they are currently for hgaccounts.
And FYI, there are 68 of us assuming everyone accepts their invites.
On Mon, 2 May 2016 at 10:27 Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
I'll email here again when I'm done so people can check that they were added to the team properly.
On Sun, 1 May 2016 at 14:14 Brett Cannon brett@python.org wrote:
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
I still see a 404 at https://github.com/orgs/python/teams/python-core .
Alex
On Mon, May 2, 2016 at 10:45 AM, Brett Cannon brett@python.org wrote:
OK, all done! For those of you already members of the Python org on GitHub you should be added already. For those of you who weren't, check your email for an invite (except for Alexander and Paul; you two are getting personal emails about issues).
I have also made Antoine and Georg team maintainers as they are currently for hgaccounts.
And FYI, there are 68 of us assuming everyone accepts their invites.
On Mon, 2 May 2016 at 10:27 Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
I'll email here again when I'm done so people can check that they were added to the team properly.
On Sun, 1 May 2016 at 14:14 Brett Cannon brett@python.org wrote:
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
If you go to your bugs.python.org account you will notice there is now a "GitHub Name" field. Please fill that in with your GitHub username sometime this month. You can see who has already filled in their username by going to http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... .
Let's aim to have those fields filled in by the end of the month? It's not a huge deal if you don't get to it in time but it makes my life easier if I can add everyone to the python-dev -- or maybe python-committers; haven't chosen the name yet -- team on GitHub at once instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm asking people do this now instead of later.
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On Mon, 2 May 2016 at 10:48 Alex Martelli aleax@google.com wrote:
I still see a 404 at https://github.com/orgs/python/teams/python-core .
Apparently team membership is available only to other team members, so if you have not been added to the team -- as is your case, Alex, as you didn't put a GitHub username on bugs.python.org -- or you have not accepted the invite the link won't work for you.
-Brett
Alex On Mon, May 2, 2016 at 10:45 AM, Brett Cannon brett@python.org wrote:
OK, all done! For those of you already members of the Python org on GitHub you should be added already. For those of you who weren't, check your email for an invite (except for Alexander and Paul; you two are getting personal emails about issues).
I have also made Antoine and Georg team maintainers as they are currently for hgaccounts.
And FYI, there are 68 of us assuming everyone accepts their invites.
On Mon, 2 May 2016 at 10:27 Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
I'll email here again when I'm done so people can check that they were added to the team properly.
On Sun, 1 May 2016 at 14:14 Brett Cannon brett@python.org wrote:
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
Just a quick reminder for folks to please fill in their GitHub username on bugs.python.org by May 1 if possible to make my and your life easier.
We are on track to move our first repository to GitHub before PyCon US (devinabox to start, hopefully another one like peps and/or the devguide as well shortly thereafter if there's time), so it will soon not be a hypothetical thing to want to have GitHub access.
On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote:
> If you go to your bugs.python.org account you will notice there is > now a "GitHub Name" field. Please fill that in with your GitHub username > sometime this month. You can see who has already filled in their username > by going to > http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... > . > > Let's aim to have those fields filled in by the end of the month? > It's not a huge deal if you don't get to it in time but it makes my life > easier if I can add everyone to the python-dev -- or maybe > python-committers; haven't chosen the name yet -- team on GitHub at once > instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, > peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm > asking people do this now instead of later. >
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has been ever since April 4. Not sure why you think it isn't?
Alex
On Mon, May 2, 2016 at 10:51 AM, Brett Cannon brett@python.org wrote:
On Mon, 2 May 2016 at 10:48 Alex Martelli aleax@google.com wrote:
I still see a 404 at https://github.com/orgs/python/teams/python-core .
Apparently team membership is available only to other team members, so if you have not been added to the team -- as is your case, Alex, as you didn't put a GitHub username on bugs.python.org -- or you have not accepted the invite the link won't work for you.
-Brett
Alex On Mon, May 2, 2016 at 10:45 AM, Brett Cannon brett@python.org wrote:
OK, all done! For those of you already members of the Python org on GitHub you should be added already. For those of you who weren't, check your email for an invite (except for Alexander and Paul; you two are getting personal emails about issues).
I have also made Antoine and Georg team maintainers as they are currently for hgaccounts.
And FYI, there are 68 of us assuming everyone accepts their invites.
On Mon, 2 May 2016 at 10:27 Brett Cannon brett@python.org wrote:
I have created https://github.com/orgs/python/teams/python-core and I am now beginning to add names. From this point forward you will need to manually tell me or hgaccounts@python.org your GitHub username if it isn't already on bugs.python.org.
I'll email here again when I'm done so people can check that they were added to the team properly.
On Sun, 1 May 2016 at 14:14 Brett Cannon brett@python.org wrote:
I realized I was ambiguous in my phrasing; yesterday I was given tomorrow off, so I will start adding names on May 2nd at some point (and I'll email here when I start).
On Sun, May 1, 2016, 10:09 Brett Cannon brett@python.org wrote:
Last reminder on this: I got the day off work yesterday and so I'm going to spend it creating a "Python core" team on GitHub and adding all of the usernames you have all put into bugs.python.org (and don't worry, I plan to go for a nice walk after I'm finished to actually enjoy my day off) . I'll reply to this thread one last time when I begin creating the team as after that point you will need to personally let me know and/or hgaccounts what your GitHub username is to be added to the team (I will also update the devguide as part of creating the team about this).
On Fri, 22 Apr 2016 at 16:13 Brett Cannon brett@python.org wrote:
> Just a quick reminder for folks to please fill in their GitHub > username on bugs.python.org by May 1 if possible to make my and > your life easier. > > We are on track to move our first repository to GitHub before PyCon > US (devinabox to start, hopefully another one like peps and/or the devguide > as well shortly thereafter if there's time), so it will soon not be a > hypothetical thing to want to have GitHub access. > > On Mon, 4 Apr 2016 at 16:45 Brett Cannon brett@python.org wrote: > >> If you go to your bugs.python.org account you will notice there is >> now a "GitHub Name" field. Please fill that in with your GitHub username >> sometime this month. You can see who has already filled in their username >> by going to >> http://bugs.python.org/user?iscommitter=1&@action=search&@sort=usern... >> . >> >> Let's aim to have those fields filled in by the end of the month? >> It's not a huge deal if you don't get to it in time but it makes my life >> easier if I can add everyone to the python-dev -- or maybe >> python-committers; haven't chosen the name yet -- team on GitHub at once >> instead of piecemeal over time. I'm hoping to get devinabox, benchmarks, >> peps, and devguide repositories moved to GitHub by PyCon US, hence why I'm >> asking people do this now instead of later. >> >
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
[Alex Martelli]
I still see a 404 at https://github.com/orgs/python/teams/python-core .
[Brett]
Apparently team membership is available only to other team members, so if you have not been added to the team -- as is your case, Alex, as you didn't put a GitHub username on bugs.python.org -- or you have not accepted the invite the link won't work for you.
[Alex Martelli]
My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has been ever since April 4. Not sure why you think it isn't?
I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:
I suspect something isn't working as expected ;-)
BTW, I'm unclear on what "you have the accepted the invite" might mean. I don't recall receiving a plausibly relevant invitation, so perhaps that's my problem here.
On Mon, 2 May 2016 at 13:00 Tim Peters tim.peters@gmail.com wrote:
[Alex Martelli]
I still see a 404 at https://github.com/orgs/python/teams/python-core
.
[Brett]
Apparently team membership is available only to other team members, so
if
you have not been added to the team -- as is your case, Alex, as you
didn't
put a GitHub username on bugs.python.org -- or you have not accepted
the
invite the link won't work for you.
[Alex Martelli]
My GitHub Name, aleaxit, is at http://bugs.python.org/user16700 and has
been
ever since April 4. Not sure why you think it isn't?
I'm working with Alex directly off-list (it turns out he has two accounts on bugs.python.org).
I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:
I suspect something isn't working as expected ;-)
BTW, I'm unclear on what "you have the accepted the invite" might mean. I don't recall receiving a plausibly relevant invitation, so perhaps that's my problem here.
You should have received an invite from GitHub to join the Python core team today. Once you accept that invitation then you will be able to see the team.
[Tim]
I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:
I suspect something isn't working as expected ;-)
BTW, I'm unclear on what "you have the accepted the invite" might mean. I don't recall receiving a plausibly relevant invitation, so perhaps that's my problem here.
[Brett]
You should have received an invite from GitHub to join the Python core team today. Once you accept that invitation then you will be able to see the team.
By what means would the invite have been delivered? I see nothing relevant on my GitHub account, and saw nothing relevant in email. My snail mail for the day hasn't yet arrived, though ;-)
On Mon, 2 May 2016 at 13:10 Tim Peters tim.peters@gmail.com wrote:
[Tim]
I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:
I suspect something isn't working as expected ;-)
BTW, I'm unclear on what "you have the accepted the invite" might mean. I don't recall receiving a plausibly relevant invitation, so perhaps that's my problem here.
[Brett]
You should have received an invite from GitHub to join the Python core
team
today. Once you accept that invitation then you will be able to see the team.
By what means would the invite have been delivered? I see nothing relevant on my GitHub account, and saw nothing relevant in email. My snail mail for the day hasn't yet arrived, though ;-)
You should have received it by email (unless you're not tim-one on GitHub ;).
Anyway, GitHub tells me you can visit https://github.com/python and accept the invite there.
[Brett]
You should have received it by email
If I did, I must have deleted it unread.
(unless you're not tim-one on GitHub ;).
I am.
Anyway, GitHub tells me you can visit https://github.com/python and accept the invite there.
That worked! Thanks :-)
Le 02/05/2016 22:10, Tim Peters a écrit :
[Tim]
I also get a 404, and my GitHub name (tim-one) was added some weeks ago too:
I suspect something isn't working as expected ;-)
BTW, I'm unclear on what "you have the accepted the invite" might mean. I don't recall receiving a plausibly relevant invitation, so perhaps that's my problem here.
[Brett]
You should have received an invite from GitHub to join the Python core team today. Once you accept that invitation then you will be able to see the team.
By what means would the invite have been delivered? I see nothing relevant on my GitHub account, and saw nothing relevant in email. My snail mail for the day hasn't yet arrived, though ;-)
Apparently you should see the invite at https://github.com/python
Perhaps GitHub refuses to send e-mail to the PythonLabs?
python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On Mon, May 2, 2016 at 4:15 PM, Antoine Pitrou antoine@python.org wrote:
Perhaps GitHub refuses to send e-mail to the PythonLabs?
Interesting hypothesis, but... my invite came by email just fine, and there wasn't any problem once accepted. Perhaps the PSU is involv
participants (7)
-
Alex Martelli -
Antoine Pitrou -
Brett Cannon -
Fred Drake -
Kushal Das -
Nick Coghlan -
Tim Peters