-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add file to note workshop response (to learn from) #50
base: master
Are you sure you want to change the base?
Conversation
adding a feature. We should probably ask users to go inspect the relevant | ||
part of the site whenever their tests pass. | ||
|
||
.. _version 1.0: https://github.com/pythonsd/test-driven-django-development/releases/tag/v1.0 |
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.
That's where that tag came from! I say we reference it as v0.0.1 since that's how rtfd will do it.
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.
@davidfischer agreed let's rename it to reference the v0.0.1 tag.
I think an experiences document is ok. I'm neutral on the subject but perfectly ok with merging. |
|
||
Everyone finished the tutorials in about 5 hours. | ||
|
||
Feedback |
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.
Suggested title: Participant Feedback
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.
I like that title. I also think the file should be renamed to feedback.rst.
Thoughts on this idea and the specific implementation? Should we note this file in the README or on RTD?