Previous Lecture lect14 Next Lecture

lect14, Thu 04/30

Thursday Lecture: public vs private, licenses, 3rd party libraries, more

Today in Lecture

Plenary

In Breakout Groups:

Staff Liaisons

I’ve assigned staff liaisons for each team:

The main role of the staff liaison is to be one central point of contact between each team and the staff.

Some of the roles these liaisons will play:

Your can see which staff member was assigned to your team by visiting this link:

Note that you’ll continue to have interactions with many staff members.

While you might see your course liaison dropping in more often on your breakout groups than other staff members, we will still change things up now and then so you get a variety of perspectives.

public vs. private?

pros/cons of going public (open source)

Pros:

Cons:

License concerns:

Auditing for Secrets:

Another option: “limited” sharing within the class

If you are willing to allows us to give other class teams “read only” access to your code, pleae let us know.

This has the benefits of allowing us to do some sharing (e.g. among teams using socket.io or solving particular issues with MongoDB or uses of React) without risks of making repos fully public.

Let us know by adding a line to top of team/AGREEMENTS.md

If there isn’t already heading at the top of your existing team agreements file, add one, e.g.

# Initial Team Agreements

Then, above that at the top of the file, copy/paste one of these three options. (Optionally, you may also add another other discussion points that seem relevant, e.g. if there was disagreement and you came to a compromise, or the concerns that led you to your decision.)

  1. Fully open source 
    # 4/30/2020
   
Team decided to make repo public (open source under ____ license).

  2. Closed source, but open to classmates as needed

    # 4/30/2020

Team decided to keep repo closed source, but allow read only access to other CS48 S20 teams on a limited basis, 
as determined by course staff when there is an learning opportunity.

  3. Fully closed source, including to classmates

    # 4/30/2020

Team decided to keep repo closed source, with access only by course staff, not by other teams.

Integrating with 3rd Parties

Some comments on how to integrate with 3rd parties

We encourage you to try #2 first, and use #1 only when approach #2 fails.

In addition, today in lecture let us know (in the chat during the plenary if possible) what other third party libraries, functions, etc. you are trying to integrate with your code. We’d like to help cross-pollination where possible to make it easier for all teams, and allow you to build better products.

Big picture patterns

MongoDB Setup