-
Notifications
You must be signed in to change notification settings - Fork 3
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 presentation materials for March 2017 #9
base: master
Are you sure you want to change the base?
Add presentation materials for March 2017 #9
Conversation
@@ -0,0 +1,3 @@ | |||
[submodule "2017/03-March/parse-server-setup-guide"] |
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.
Oooh! Fancy submodules!
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.
Do we want to enforce code check-in? Or is submodules ok?
Good question. I only used a submodule here since I did end up creating a public repo with the content of my presentation. I don't have a strong opinion either way. What do you think? |
I think we should enforce check-in since it is an archive. If the developer wants to link back to their own repo, they can put that in the readme. Or we can just fork their projects... but that makes this whole repo irrelevant 😂 |
That makes sense to me. I'll check in the project. |
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.
Check-in version of code presented.
As discussed, we're forking code repos; just slides/notes/general-materials here. |
Adds presentation materials for March 2017.
Checklist:
/01-January/README.md
)Please contact @blakemerryman or @addisonwebb if you have any issues.