Policies and Deadlines

Partnerships (the same ones that you make through the Lab 12: BYOW Intro form on Beacon) are due Tuesday, November 10th at 11:59 PM. After this time, if you do not have a partner yet, you will be randomly assigned.

  • If you are in 61B, you are required to and may only partner with other 61B students
  • If you are in 47B, partners are optional, but you may only partner with other 47B students
  • If you are retaking 61B, you may only partner with those who are also retaking the class
  • Groups may have 2 or 3 members. Groups of 3 have extra requirements: Light Sources (in 5B and 5C) and an additional ambition feature. See the Ambition Features page for details.

Partnership Structure

For Project 5, we require that you work in groups of 2 or 3 (optional for 47B), unless you have a special reason that prevents you from doing so. If this is the case, please make a private Ed post so that staff can be made aware of your situation.

Why Partnerships on Project 5?

The process of working on a team can be quite different than working alone, and it’s great practice to learn how to efficiently work with other people, especially on large complex projects that involve tricky tools like git. While you might be perfectly capable,and even happier to work alone, you’ll only have so many big design projects in college, and we hope you’ll take advantage of this opportunity to develop this important soft skill.

Given that this project is open-ended, having another person to work with might also help with being able to find more creative solutions, especially to the problem of world generation.

Finally, there’s also the fact that when you go to job interviews, it is very likely that you’ll be asked to describe a time you worked with a team under some sort of duress. This project will likely provide such an opportunity.

Rules for Collaboration

For this project, you’re explicitly allowed to divide and conquer. We encourage you to explore the idea of pair-programming, but it is not required. It is also not required that you work in the same room, though it is highly encouraged because this is more fun.

We don’t require that both partners contribute equally, but all partners should do at least a significant amount of work, and should be communicating throughout the project.

Collaboration tips and Merge Conflicts

We highly recommend that partners meet in the Gateway labs or somewhere else on campus and pair program on the assignment together. This means one laptop with the pair taking turns typing and both working and outlining solutions together. Pair programming is an easy way to prevent merge conflicts from happening.

Merge conflicts are when two different users on a git repository both commit changes to the same file, and then some sort of merge is attempted (from doing git pull). Once a merge conflicts happen, you need to decide whether to keep your changes, your partner’s changes, or both, line by line (since git does not know how to order you/your partner’s changes). This is annoying, time-consuming and super preventable! Here are a couple ways to collaborate.

  1. Pair Program. As mentioned above!
  2. Work on different files. Try to split your projects into classes/components.

If you’re unable to meet in-person, you can do a similar thing with Zoom and screen sharing! It’s not always the best idea to split the work directly in half as working in isolation is much worse than collaboration, though you can do so if you want. There are also plugins for IntelliJ (and VSCode, if you use that) that allow for editing of the same file, though course staff won’t provide official help with them.

Dissolutions

DEADLINE: All dissolution requests are due by the Project 5A deadline (Wednesday 11/18 at 11:59PM).

Sometimes your partnership just doesn’t work out for a variety of reasons. In extremely dire cases, we will allow a dissolving of a partnership. Here are some reasons we’ve dissolved partnerships in the past:

  1. A one-sided partnership. This means that you have reached out many times (3+), and you have gotten no response over a 3 day period (counting 3 days since your earliest communication attempt), and your partner hasn’t done any work on the assignment.
  2. A variety of personal reasons where a student was uncomfortable.
  3. One partner has dropped the class.

No dissolution request is guaranteed. All dissolutions will be made at the discretion of staff.

To submit a dissolution request, go to the Groups tab on Beacon and select a
reason. Your reason will not be disclosed to your group members. Once staff have reviewed your request, you and your partner will both receive an email confirming the dissolution. In the meantime, you can proceed as if your dissolution request has been approved.

Please keep in mind the following partner policies:

  • You should have attempted to contact your partner at least a few times.
  • You should not be dissolving your group to be in another group.
  • Finally, requesting a dissolution should be a last resort.

If we find that your reason for dissolving is not within reason, we will treat it as academic misconduct.

If we find that you are not attempting to establish contact with your partner and work with them, you will not be awarded points for partnership formation.

Once your group has been dissolved, you and your original partner will lose write access to your original group repo. You can still read and use your original code, however you will need to work in a new individual group repo that has been made for you.

Re-Pairings

DEADLINE: All re-pairing requests are due by Monday 11/16 at 11:59PM.

If your group has been dissolved and you are currently working solo, or if you a 47B student who wasn’t originally paired, you may request to be re-paired with another student in a similar situation. To be eligible, you must have already dissolved your group and be in a solo group. 47B students will only be re-paired with other 47B students.

To submit a re-pair request, go to Groups tab on Beacon and fill out the form for Dissolutions. If your dissolution is approved, then you will be removed from your current group.

Then, go to the Groups tab on Beacon and select an assignment under the Requests section, then input the student repo ID of the partner you are requesting. Once your partner has reviewed and accepted your request, you and your new partner will receive an email confirming you have been re-paired into a new group.

Please keep in mind:

  • A new group repo will be created for both of you to work in.
  • You will be required to submit a new design document for Project 5A with your new partner by Friday 11/20 at 11:59PM.
  • All re-pair requests will be processed by Monday 11/16 at 11:59PM. Please submit your re-pair requests as early as possible!

If we find that your reason for re-pairing is not within reason, we will treat it as academic misconduct.

We will not be accepting anymore partnership re-pairing requests after re-pairing deadline of Monday 11/16 at 11:59PM.

Re-Pairing into a group of 3:

If you are without a partner after an approved dissolution, and you want to join a group of 2 (thus making it a group with 3 partners now), you are able to do so. In order to join this group of 2, you must first have dissolved your previous partnership. Then, on the Groups tab in Beacon, underneath Requests, select the Lab 12 assignment, and input the student repo ID of one of your new partners. Once they accept this partner request, you will be added to their group and will be able to access their group repository.