Gim Seng

Personally I envision the following groups of people and how each group should make the best out of the repo to learn: Group A: super new to machine learning, maybe...

Group B: intermediate machine learning people. I hope that they could be the ones criticising our solutions, proposing a better code, contributing new exercise and solutions. Furthermore this serves as...

Group C: guru in everything we are doing here. Then, I would love for them to help maintain the repo. Help us run the project better. They can implement better...

Others: I am pretty sure I left out a big group of people. If so, please comment and let us know either below or through an issue ticket. Please let...

Perhaps I should polish above and make it into the documentation of ‘how to use this project’

As another use for this project, could the following model/vision be a useful thing: There are many many many coding examples online (see #19), and many of them are excellent....

@AjayKhalsa That's a good idea. We should have one contributor's guidelines and one learner's guidelines. I think we have to standardize or expand on the `readme.md` on the exercise of...

Also pep8 lint test. Actually there's been a discussion on how to do that for Jupyter notebook. See https://stackoverflow.com/questions/26126853/verifying-pep8-in-ipython-notebook-code

[x] Create flake8 (pep8) lint test whenever pull-request occurs. This applies to all `.py` file. See #30 [ ] Create flake8 for Jupyter notebook

I think since we are not building a package or library, it doesn’t make send to do too much testing. At this point pep8 linting and if the codes run...