-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
An on-boarding document that NEEDS EDITING #306
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey Rich, this is a great start to #302 (I think it solidly covers the first two bullet points, and the remaining points are a bigger scope.)
I left some feedback, hope it helps. We've been needing a "Getting Started" doc for some time and I think this is a promising start.
sudo pip install -r requirements.txt | ||
gem install pg bundler | ||
bundle install | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about just directing people to the README
of the backend here, rather than copying the steps? Do you think it explains the setup well enough or could it be improved?
|
||
## Making Changes / Development Process | ||
|
||
Notes on our development approach and preferred coding style are written in [ :warning: ** TODO ** :warning: CONTRIBUTING.md ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems legit, did you have a question here?
…to documentation_for_new_people
This is a markdown doc I started to help with on-boarding new folks to opendisclosure. All of the information is already somewhere in the projects' 3 repos, but I tried to combine things into one doc that links all the resources I can think of so as to create "the only bookmark you'll ever need" aka "stuff I wish I knew to get started". Target audience is technically [somewhat] experienced folks that already know git/bash and want to jump into working on the codebase and issues, not a square-1 how-to-____ or list of tutorials.
Feel free to reject the pull, I just want to share what I started to help with #303 but it doesn't actually close the issue. The doc needs editing - See the
:warning: **TODO** :warning:
all over the doc for things I don't know or can't answer clearly.(Also, I've created a "Documentation" folder, but obviously that should only be used if we'd expect to use it for more files in the future.)