Seems all the recent commits are listed here: https://github.com/pygame/pygame/commits/master
Last one is from March 26th. I see Lennard, Ian Mallett, and a few others have their email settings in github as private. However their names are listed in commits, but not on the contributors page here: https://github.com/pygame/pygame/graphs/contributors Email settings can be configured using these tools. - public email can be set here: - https://github.com/settings/profile - verify email if you haven't(really old account) - https://help.github.com/articles/verifying-your-email-address/ - using the private address - https://help.github.com/articles/keeping-your-email-address- private/ If you're not happy with your email address being public, but want to be shown on the contributors page, then you need to set a "private address". If you have a really old github account, I think it's still possible to not have verified an email address. On the other hand... if you included your email address in the pygame repo... then it is already public. In this case you probably don't mind to set it public in github: https://github.com/settings/profile Some people set their emails as things like "bob@localhost", or not even an email address. Although I linked their github account, their settings are marked as private. So we should respect that. On the other hand, perhaps people haven't really considered what those github email settings even mean. So, let's give this a few days for people to update their github email settings. (even in the future we can rewrite settings, but it will be annoying for all upstream having to reset the repo) On Mon, Mar 27, 2017 at 7:54 AM, Lenard Lindstrom <le...@telus.net> wrote: > Well, I am not showing up in GitHub. And almost everything in src having > the last commit on Dec. 1, 2016. > > Lenard Lindstrom > > On 17-03-26 10:38 AM, René Dudfield wrote: > >> Hello, >> >> https://github.com/pygame/pygame >> >> TLDR; git repo, and issues are there. A bit more work to do on other >> things. Authors, please check your github email privacy settings if you >> care right away. >> >> cheers, >> >> >> *Import, and Author mapping. >> * >> >> I used the built in github tool for importing the pygame repo from >> bitbucket. >> >> Everything seems to be there, including branches and tags. >> >> If you have permission for the repo you can see the authors, and how they >> were mapped. I managed to find everyone almost. >> https://github.com/pygame/pygame/import/authors >> >> (If you don't have permissions on github, that just link just shows the >> pygame repo) >> >> If you don't have your email set to public on your github profile, or a >> private hidden email via github, you don't get linked up on the >> pygame/pygame repo page. (I guess if you do want to be private, then that >> is no problem to you... but maybe someone didn't realise). But if you want >> to be visible, please either make your email public, or use a github hidden >> email. I can change the mapping still... but I don't know for how long that >> page will be there, or if that has an effect later. >> >> Here's some relevant email help pages on github: >> >> * public email can be set here: https://github.com/settings/profile >> * verify email if you haven't(really old account) >> https://help.github.com/articles/verifying-your-email-address/ >> * using the private address >> https://help.github.com/articles/keeping-your-email-address-private/ >> >> >> >> *Issue migration* >> >> Then I migrated the issues from bitbucket to github with this script. >> https://github.com/jeffwidman/bitbucket-issue-migration >> >> The issue numbers are the same on each one. Issue 147 on github is issue >> 147 on bitbucket. The issues on gh link to the old bb issue, and the old >> username. >> >> Unfortunately the script does not make a note on the bitbucket issue >> about the move. Probably a good idea to do this, but I couldn't find a tool >> to do it. >> >> >> >> *What's next? >> * >> I'll update the bitbucket to point a url to the github page where I can. >> >> The things below still need to be done. >> >> *Buildbots. >> * >> >> All of the places should be able to be moved to git. appveyor, travis, >> launchpad, ... >> >> >> *Downloads.* >> https://bitbucket.org/pygame/pygame/downloads/ >> >> Github doesn't really have downloads. We could put all the files in a >> repo though. This is better I think. >> >> We can leave those downloads as they are on bitbucket for now. >> >> However, we need to go around the web and find links which might need >> updating. (well, at least on our websites). >> >> >> *Website integration. >> * >> >> Need to add a new webhook when something has been moved into the default >> branch. >> The downloads repo could go into /ftp/ >> >> *Maintainers contacted, and announcements >> * >> >> We need to contact various system maintainers to let them know of the >> updates. eg, Debian maintainers. >> >> >> *Other repos on pygame to be moved* >> >> There's a few other repos that might need moving. >> >> https://bitbucket.org/pygame/ >> >> Maybe just these ones? >> >> * https://bitbucket.org/pygame/build-external-dlls >> * https://bitbucket.org/pygame/pygamegsoc12 >> * https://bitbucket.org/pygame/imgblit >> >> Lennard, what do you think about which ones need moving to bitbucket? >> >> *Wiki. >> * >> >> The bitbucket wiki was spammed into oblivion, and most updates then >> happened on the pygame webpage wiki. I'll make a backup, and then disable >> the bitbucket wiki in time. >> >> If someone wants to go through and manually check if there's useful >> content in there that's not already in the main wiki... please feel free. I >> guess the easiest way to do that is not through the web, because I couldn't >> see a history button (maybe it's there somewhere). There is a wiki repo >> though. >> >> *pygame. bitbucket. org >> * >> >> Seems they disabled this some time ago. >> >> >> *Keeping bitbucket repositories there. >> * >> I think we need to keep the pygame bitbucket there for the foreseeable >> future. There's still things we need to migrate, and there's no way of >> redirecting links. Can decide later if we want to remove it entirely. >> >> >> >> >
