On Fri, Jul 22, 2016 at 11:28 AM, Yury Selivanov <[email protected]> wrote: > I recommend to create a new github org -- aio-docs. Let's not bother with > github/python org at all.
+1 > > Sent from my iPhone > > On Jul 22, 2016, at 3:34 PM, Andrew Svetlov <[email protected]> > wrote: > > I think https://github.com/python/asyncio-doc with dedicated team for giving > write access is preferable > > > On Fri, Jul 22, 2016, 15:18 Victor Stinner <[email protected]> wrote: >> >> 2016-07-21 17:13 GMT+02:00 Victor Stinner <[email protected]>: >> > Ok, it's just the 3rd time that someone asked me how to contribute to >> > the asyncio documentation, so I created a new GitHub project: >> > https://github.com/haypo/asyncio-doc/ >> >> Oh, I cannot give adminstrator right on collaborators on >> haypo/asyncio-doc. It looks like the asyncio-doc project should be >> moved to an organization. >> >> I don't know what is the best: should we move the GitHub project to >> the python organization ( https://github.com/python/asyncio-doc ) or >> to a new asyncio-doc organization ( >> https://github.com/asyncio-doc/asyncio-doc )? Do we have some GitHub >> "experts" here? :-) >> >> My goal is to allow more people to push directly in asyncio-doc than >> in the asyncio code (where we prefer to have reviews using pull >> requests). So I prefer two distrinct teams (list of collaborators). >> >> I see that the Python organization on GitHub already has multiple teams. >> >> Victor > > -- > Thanks, > Andrew Svetlov -- Luciano Ramalho | Author of Fluent Python (O'Reilly, 2015) | http://shop.oreilly.com/product/0636920032519.do | Professor em: http://python.pro.br | Twitter: @ramalhoorg
