Welcome!
Everything is fine.

Teamwork

The main activity for today is a team discussion of norms, responsibilities and interaction. This is all about social connections and how we treat one another, not about coding or Flask.

If there's time, we might talk a little about Git and how to use it for your team project.

We will have time next week for Git, so if you don't get to that activity, it's fine.

Motivation

  • Most teams do fine. Everyone works well, collaboratively, helps one another, and the team turns out great work.
  • Sometimes, a team doesn't do fine. Things that can go wrong include:
    • a team member isn't contributing and things that need doing don't get done.
    • communications fail, and no one is clear on what is getting done and who is doing what
    • some members don't feel heard or don't feel that their contributions are valued

So, each team is having this discussion to try to avoid these problems or reduce their impact.

Team Contract

What I want you to do is to, as a team, discuss and fill out this teamwork form

If I got the incantation right, clicking on that link should create a copy of the form in your account. We only need one form per team, so choose one team member to make the copy and share it with the others and with me.

Make copy and then collaboratively edit the document for the information for your team.

When you are done, let me know, and I can review it later.

That's it! Enjoy your discussion!

Git Ideas

Here's my suggestions about how you might use Git in CS 304:

  • Decide on a team "captain". That person will use their personal Github account to have the repo that holds the project code.
  • The captain creates the repo and adds the other team members as collaborators
  • Each team member checks out the repo so that they have a personal copy of the code.
  • All members should be able to push to Github

Git Activity

For today or very soon.

Since many of you are somewhat familiar with Git, rather than go through some orchestrated activities, I'll leave you on your own, but here's my suggestion:

  1. Create a project repo in a team captain's github account, possibly as a clone/fork of my flask-starter, or you can "cp -r" the ~cs304/pub/downloads/flask-starter folder to your local git repo and then push it out to Github. (That's what I've done in the past.)
  2. The captain adds their teammates as collaborators/contributors.
  3. have each teammate git clone the project repo to their personal account on tempest.
  4. have each person commit something locally. Maybe create a file with their name: wendy.py
  5. have each person git push their mod into the captain's repo
  6. have each person git pull the updated repo into their personal account on tempest.

If you have difficulty, that's fine. Talk to me or wait until next Wednesday, when we'll do it all together.