It's done. I've just copy-pasted content from original, except for contributing page, I've changed text for GitHub workflow: https://github.com/python/tulip/wiki/Contributing
BTW, if you have this option in Google Code admin panel, it should be better to define a 301 HTTP redirection from http://code.google.com/p/tulip/wiki/ThirdParty to https://github.com/python/tulip/wiki/ThirdParty With that, we shouldn't lose the natural referencing level that the old page had. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ 2015-04-11 13:40 GMT-04:00 Ludovic Gasc <[email protected]>: > Ok, I can help to do that. > > Ludovic Gasc (GMLudo) > http://www.gmludo.eu/ > On 11 Apr 2015 13:02, "Guido van Rossum" <[email protected]> wrote: > >> The wiki pages are preserved in the wiki branch of the repo. If you want >> to help putting them back in the github wiki slot I can give you repo >> access. >> On Apr 11, 2015 9:58 AM, "Ludovic Gasc" <[email protected]> wrote: >> >>> Hi, >>> >>> At least to me, the most important wiki page of Tulip project was: >>> http://code.google.com/p/tulip/wiki/ThirdParty >>> With the Github migration, this wiki page has been gone. >>> The performances list page was also interesting. >>> Personnally, I've followed both pages via RSS feeds to follow AsyncIO >>> ecosystem. >>> >>> BTW, small suggestion: instead of to create a wiki page in Github, we >>> should maybe create a docs/ folder published on readthedocs or use github >>> pages. >>> The goal isn't to have another place for AsyncIO documentation, we >>> already have that in the official Python doc, only for the previous wiki >>> content. >>> This should facilitate contributions for theses pages via pull requests >>> and follow changes. >>> >>> Regards. >>> >>
