10000 Where to include user feedback? · Issue #19 · AB1908/CS-Books · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Where to include user feedback? #19

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.

Sign up for GitHub

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

Jump to bottom
Open
AB1908 opened this issue Jun 3, 2018 · 2 comments
8000
Open

Where to include user feedback? #19

AB1908 opened this issue Jun 3, 2018 · 2 comments

Comments

@AB1908
Copy link
Owner
AB1908 commented Jun 3, 2018 •
edited
Loading

Submitting the reader's experience of a particular book is highly encouraged. However, at the time, there is no appropriate place to include these personal notes. At the moment, my idea is to migrate all personal experience to a separate file personal-experiences.md, with the contributor tagging their feedback with a handle. Hopefully, this would keep the actual book list free of personal opinions, which are only mine as of now. Please suggest other alternatives if you have 'em!
AB1908 pushed a commit that referenced this issue Jun 3, 2018
Add link to Issue #19
cd14d3a
AB1908 pushed a commit that referenced this issue Jun 3, 2018
Bring the repository up to open source community standards (#17)
5707026 
* Create PULL_REQUEST_TEMPLATE.md

* Update Code of Conduct

* Rename contributing file and rewrite to better fit community guidelines

* Update readme

* Add missing commit guideline

* Add reference for Issue #18

* Add link to Issue #19

* Update readme for readability

* Improve Pull Request Template

* Improve Contributing Guidelines
 - Rewrote certain sections for readability
 - Rearranged the headers
 - Created links to Pull Request Guidelines
 - Create Commit Message Guidelines
 - Create Issue Guidelines
AB1908 pushed a commit that referenced this issue Jun 3, 2018
Bring the repository up to open source community standards (#17)
d3c18fd 
* Create PULL_REQUEST_TEMPLATE.md

* Update Code of Conduct

* Rename contributing file and rewrite to better fit community guidelines

* Update readme

* Add missing commit guideline

* Add reference for Issue #18

* Add link to Issue #19

* Update readme for readability

* Improve Pull Request Template

* Improve Contributing Guidelines
 - Rewrote certain sections for readability
 - Rearranged the headers
 - Created links to Pull Request Guidelines
 - Create Commit Message Guidelines
 - Create Issue Guidelines
@AsliRoy
Copy link
Contributor
AsliRoy commented Jun 3, 2018

This is along the lines of what I had suggested. We just need to decide of an appropriate way o place them in the repo without clutter

@AB1908
Copy link
Owner Author
AB1908 commented Jun 3, 2018

@AsliRoy , I've updated my comment to reflect what I've written in the contributing guidelines. Take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@AB1908 @AsliRoy
0