Leah Wasser

i'm going to [close the open pr which is a demo of how this can work](https://github.com/pyOpenSci/python-package-guide/pull/167/files) and just add the link here to that pr when we begin to work...

Ok yay! We could even have review sprints Jesse!! Following the content you are creating !

ok!! i'll put this on my list to review this week! thanks @willingc for pinging me!

@all-contributors please add @ctb for code, review

@sneakers-the-rat i suspect the conflicts here relate to the pr's i merged yesterday where you fixed our requirements and such. can you kindly rebase when you have a chance? in...

here is the [current rendered page](https://output.circle-artifacts.com/output/job/8e6e6112-7d16-476e-8f26-55095fd1ccea/artifacts/0/html/documentation/repository-files/license-files.html) i think a clean reorganiation is the key piece as right now a new user is going to be really confused. but i also...

ok let's see - what do we need to do to get this PR merged? I think 1. a small re-org to make it easier for the reader to follow...

this is a good issue but we have'nt as a community made a decision on what license to recommend for docs /// we've only decided to use mit for code....

thank you both. i'm looking at some of these old issues too - to see if we can close or mark them help-wanted! i agree with you both - 1....

btw i created this little github project board automation that adds any issues with help-wanted to our project board. it's working so well!!