[core-workflow] Reviewing/updating the README for GitHub migration?

[Nicholas Chammas]

On Fri, Apr 22, 2016 at 11:40 PM Nick Coghlan <ncoghlan at gmail.com> wrote:

> The reason I suggest that is that with the way code hosting services like
> GitHub work, the README changes from something people may read for local
> development after they've already cloned the repo to instead being the main
> landing page for the repo.
>
> That means it becomes a good place to point out things like:
>
> - the location of the main dev guide
> - the issue tracker
> - the communications channels
> - the PSF CLA (and the need to sign it for non-trivial contributions)
>

I wonder if some of these bits of information could go in a GitHub pull
request template:

https://github.com/blog/2111-issue-and-pull-request-templates

That way they get presented to the contributor as soon as they hit the "new
pull request" button.

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160423/e94147e2/attachment.html>