-
Notifications
You must be signed in to change notification settings - Fork 5
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
Teamwork Contract #2
Comments
I added a number of items to the teamwork contract. Take a look and we can discuss when we meet if there are issues |
Looks great, I made a couple updates based on your suggestions. Is everyone good with publishing this on github? |
I think the teamwork contract looks great. I also added an extra sentence to 'c'. Yeah, I'm fine with publishing it on Github. |
If we were to publish it on Github, I think we should remove it when we finish the project. The contract has too many personal details (strengths, weaknesses, interets) |
We could also put a link to the google doc instead and then just change the
permissions when the project is over. That way the history won't be
available.
…On Wed, 13 Jan 2021 at 11:19, CalSchafer ***@***.***> wrote:
If we were to publish it on Github, I think we should remove it when we
finish the project. The contract has too many personal details (strengths,
weaknesses, interets)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALS2GJAEWH5IDYF2ROGS2DSZXW5BANCNFSM4V76DZXQ>
.
|
All looks good to me. My vote is for just leaving it on google docs to keep things simple. |
Added a link to the README, we can include the link when we submit to canvas as well. I've changed the settings so it is viewable with a link, once the project is over I can change the settings so only we can view it. |
No description provided.
The text was updated successfully, but these errors were encountered: