[Openid-specs-mobile-profile] [Openid-specs-ab] Bitbucket migration plan suggestions

Edmund Jay ejay at mgi1.com
Thu Apr 2 00:55:14 UTC 2020

 Hi Mike,
The EAP respository does not have an issue tracker or Wiki so it can be directly imported via Github and then reimported back to Bitbucket.
Here's my Git version of the EAP repository.

You can delete the OpenID EAP repository and then import my version into a repository with the same name or simply just import under a different name. Just in case, clone it locally first as a backup.
Only repositories that have an issue tracker or Wiki will need to be run through a migration script.Also admin privilege will be required to export the tracker database.

-- Edmund 

    On Wednesday, April 1, 2020, 03:28:23 PM PDT, Mike Jones via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:  
There are several active Bitbucket Mercurial repositories that we need to migrate to Git.  Those I am sure that we need to migrate are:
   - https://bitbucket.org/openid/connect
   - https://bitbucket.org/openid/openid.bitbucket.org
   - https://bitbucket.org/openid/mobile
   - https://bitbucket.org/openid/eap
Because eap is the smallest and least critical, I propose that we migrate it first.  I’m good with us doing that right away.  If you agree, Edmund and Nat, can you migrate it now and report back to us on how it went?
After that, I’d propose to do them in the order (2) openid.bitbucket.org, (3)mobile, (4) connect.
Also, when we migrate openid.bitbucket.org, let’s change the name toopenid.bitbucket.io, since its content is now at https://openid.bitbucket.io/.
                                                       -- Mike
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-mobile-profile/attachments/20200402/1712513b/attachment.html>

More information about the Openid-specs-mobile-profile mailing list