Update new project section

[cunla]

No description provided.

[tim-schilling]

A few small changes, but this looks good.

@cunla what do you think about asking the maintainers to create the release.yml and the test.pypi.org project before scheduling the call? Theoretically, we could also ask them all the various questions to make generating the repo config data easier too.

[ryancheley]

@cunla what do you think about asking the maintainers to create the release.yml and the test.pypi.org project before scheduling the call? Theoretically, we could also ask them all the various questions to make generating the repo config data easier too.

@tim-schilling I was thinking about this after our call yesterday as well! I think it might be a good idea to ask the maintainers to do that OR to add in an extra 15 - 20 minutes (maybe more 🤷 ) to allow us time to do it on the call with them.

[tim-schilling]

My opinion is that we should try to get the information beforehand to keep those meetings as short as we can.

I do think a video will help, but as we optimize the process, it'll keep needing to be updated.

[cunla]

I am all for making it more efficient and this is a nice step forward.

Eventually, I hope we can get to a point where maintainers can transfer packages with our involvement only in the background.
Theoretically, it is already possible: (1) approve PR to become member, (2) approve invite to PyPI, (3) approve PR to add repo to be managed.

Once the process stabilizes, I would like to do another video.