At the end of the semester, a local education company offers to "take over StudyBuddy" and sell it to other universities. Before anyone signs anything, prepare an IP and licensing plan:
- Ownership: who owns what — team members' code, the university (policy?), instructors' course materials, AI-generated code, the name and logo. What must be checked and with whom?
- Dependency audit: what must be done with the dependency list (licences, obligations) before the software can be sold; which licence families would be a problem and why.
- Outbound licence options: compare (a) keeping it proprietary and licensing it to the company, (b) releasing it as open source under Apache 2.0, (c) under AGPL v3 — one advantage and one drawback each for the team, the university and future users.
- Content: how Buddy's use of instructors' slides (and any textbook figures in them) affects the sale.
- Recommendation in 4–6 sentences.