Re: [pygame] The long-ish pygame github migration status email.

[Nicholas H.Tollervey]

Hi,

I believe this may be the technique you're looking for:

https://github.com/ntoll/microfs/blob/master/microfs.py#L55

(See the raw on / off / execute functions for sending arbitrary data via
UART to the device.)

Hope this helps.

N.

On 02/04/17 10:47, René Dudfield wrote:
> Added some help for creating a pull request on github here:
> 
> http://www.pygame.org/wiki/Hacking#Submitting%20changes%20to%20github
> 
> The wiki/Hacking page is the pygame development guide. I tried to update
> it the other week to make it up to date.
> 
> 
> 
> 
> On Sun, Apr 2, 2017 at 11:35 AM, René Dudfield  > wrote:
> 
> I've updated the travisci, appveyor, and launchpad for the pygame
> github repo, and added a Coverity code scanner.
> 
> As you can see branches for pull requests get built as well. This is
> much nicer for testing if changes are ok than what we had.
> https://github.com/pygame/pygame/pull/332
> 
> 
> best,
> 
> 
> On Mon, Mar 27, 2017 at 8:56 AM, René Dudfield  > wrote:
> 
> Note, everyone has been sent an invitation to become a
> github.com/pygame  organization member
> if they want. Of course members need that before they can
> commit. But it's not required for the name to be shown on the
> contributors page.
> 
> cheers,
> 
> 
> 
> On Mon, Mar 27, 2017 at 8:39 AM, René Dudfield  > wrote:
> 
> I think we should probably give it a few days before going
> ahead with big pull requests and such. If anything happens
> on the bitbucket in the mean time, I can manually move
> commits over to github.
> 
> 
> 
> 
> On Sun, Mar 26, 2017 at 11:29 PM, Thomas Kluyver
> mailto:tak...@gmail.com>> wrote:
> 
> Thanks René!
> 
> I take it that we should now continue all development on
> Github, make pull requests there and so on?
> 
> 
> On 26 March 2017 at 18:38, René Dudfield
> mailto:ren...@gmail.com>> wrote:
> 
> *pygame. bitbucket. org
> *
> 
> Seems they disabled this some time ago.
> 
> 
> They moved all project websites to bitbucket.io
>  subdomains. They didn't leave the
> redirect in place for as long as I'd like.
> 
> Thomas
> 
> 
> 
> 
> 




signature.asc
Description: OpenPGP digital signature

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

Added some help for creating a pull request on github here:

http://www.pygame.org/wiki/Hacking#Submitting%20changes%20to%20github

The wiki/Hacking page is the pygame development guide. I tried to update it
the other week to make it up to date.




On Sun, Apr 2, 2017 at 11:35 AM, René Dudfield  wrote:

> I've updated the travisci, appveyor, and launchpad for the pygame github
> repo, and added a Coverity code scanner.
>
> As you can see branches for pull requests get built as well. This is much
> nicer for testing if changes are ok than what we had.
> https://github.com/pygame/pygame/pull/332
>
> best,
>
>
> On Mon, Mar 27, 2017 at 8:56 AM, René Dudfield  wrote:
>
>> Note, everyone has been sent an invitation to become a github.com/pygame
>> organization member if they want. Of course members need that before they
>> can commit. But it's not required for the name to be shown on the
>> contributors page.
>>
>> cheers,
>>
>>
>>
>> On Mon, Mar 27, 2017 at 8:39 AM, René Dudfield  wrote:
>>
>>> I think we should probably give it a few days before going ahead with
>>> big pull requests and such. If anything happens on the bitbucket in the
>>> mean time, I can manually move commits over to github.
>>>
>>>
>>>
>>>
>>> On Sun, Mar 26, 2017 at 11:29 PM, Thomas Kluyver 
>>> wrote:
>>>
 Thanks René!

 I take it that we should now continue all development on Github, make
 pull requests there and so on?


 On 26 March 2017 at 18:38, René Dudfield  wrote:

>
> *pygame. bitbucket. org*
>
> Seems they disabled this some time ago.
>

 They moved all project websites to bitbucket.io subdomains. They
 didn't leave the redirect in place for as long as I'd like.

 Thomas


>>>
>>
>

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

I've updated the travisci, appveyor, and launchpad for the pygame github
repo, and added a Coverity code scanner.

As you can see branches for pull requests get built as well. This is much
nicer for testing if changes are ok than what we had.
https://github.com/pygame/pygame/pull/332

best,


On Mon, Mar 27, 2017 at 8:56 AM, René Dudfield  wrote:

> Note, everyone has been sent an invitation to become a github.com/pygame
> organization member if they want. Of course members need that before they
> can commit. But it's not required for the name to be shown on the
> contributors page.
>
> cheers,
>
>
>
> On Mon, Mar 27, 2017 at 8:39 AM, René Dudfield  wrote:
>
>> I think we should probably give it a few days before going ahead with big
>> pull requests and such. If anything happens on the bitbucket in the mean
>> time, I can manually move commits over to github.
>>
>>
>>
>>
>> On Sun, Mar 26, 2017 at 11:29 PM, Thomas Kluyver 
>> wrote:
>>
>>> Thanks René!
>>>
>>> I take it that we should now continue all development on Github, make
>>> pull requests there and so on?
>>>
>>>
>>> On 26 March 2017 at 18:38, René Dudfield  wrote:
>>>

 *pygame. bitbucket. org*

 Seems they disabled this some time ago.

>>>
>>> They moved all project websites to bitbucket.io subdomains. They didn't
>>> leave the redirect in place for as long as I'd like.
>>>
>>> Thomas
>>>
>>>
>>
>

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

Note, everyone has been sent an invitation to become a github.com/pygame
organization member if they want. Of course members need that before they
can commit. But it's not required for the name to be shown on the
contributors page.

cheers,



On Mon, Mar 27, 2017 at 8:39 AM, René Dudfield  wrote:

> I think we should probably give it a few days before going ahead with big
> pull requests and such. If anything happens on the bitbucket in the mean
> time, I can manually move commits over to github.
>
>
>
>
> On Sun, Mar 26, 2017 at 11:29 PM, Thomas Kluyver  wrote:
>
>> Thanks René!
>>
>> I take it that we should now continue all development on Github, make
>> pull requests there and so on?
>>
>>
>> On 26 March 2017 at 18:38, René Dudfield  wrote:
>>
>>>
>>> *pygame. bitbucket. org*
>>>
>>> Seems they disabled this some time ago.
>>>
>>
>> They moved all project websites to bitbucket.io subdomains. They didn't
>> leave the redirect in place for as long as I'd like.
>>
>> Thomas
>>
>>
>

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

I think we should probably give it a few days before going ahead with big
pull requests and such. If anything happens on the bitbucket in the mean
time, I can manually move commits over to github.




On Sun, Mar 26, 2017 at 11:29 PM, Thomas Kluyver  wrote:

> Thanks René!
>
> I take it that we should now continue all development on Github, make pull
> requests there and so on?
>
>
> On 26 March 2017 at 18:38, René Dudfield  wrote:
>
>>
>> *pygame. bitbucket. org*
>>
>> Seems they disabled this some time ago.
>>
>
> They moved all project websites to bitbucket.io subdomains. They didn't
> leave the redirect in place for as long as I'd like.
>
> Thomas
>
>

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

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  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.
>>

Re: [pygame] The long-ish pygame github migration status email.

[René Dudfield]

Did you check out your github email settings?


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/




On Mon, Mar 27, 2017 at 7:54 AM, Lenard Lindstrom  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.
>>
>>
>>
>>
>

Re: [pygame] The long-ish pygame github migration status email.

[Lenard Lindstrom]

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.

Re: [pygame] The long-ish pygame github migration status email.

[Thomas Kluyver]

Thanks René!

I take it that we should now continue all development on Github, make pull
requests there and so on?


On 26 March 2017 at 18:38, René Dudfield  wrote:

>
> *pygame. bitbucket. org*
>
> Seems they disabled this some time ago.
>

They moved all project websites to bitbucket.io subdomains. They didn't
leave the redirect in place for as long as I'd like.

Thomas

Re: [pygame] The long-ish pygame github migration status email.

[Leif Theden]

> Github doesn't really have downloads. We could put all the files in a
repo though. This is better I think
.
Typically "downloads" are under the releases section in github.

On Sun, Mar 26, 2017 at 12:38 PM, 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.
>
>
>
>

[pygame] The long-ish pygame github migration status email.

[René Dudfield]

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.