The schedule for future weeks is tentative, given as a reference only. The prof will finalize the details of a week near to the start of the week, although major changes are highly unlikely.
nusossprojects slack channel when you receive the invitation. As our projects use slack for chats, please keep slack running (and notifications enabled) during periods in which you are actively involved in our projects (or check slack at least once a day).
Keep records of your work
As you learn the codebase, investigate issues, learn related tools etc., try to get them recorded somewhere. Some options:
Reasons: It increases the visibility of your work. Those records can be useful references to you and others.
Don't worry if your RepoSense graph doesn't have as many ramps as others. Data shown on the RepoSense report are not directly comparable across projects or even within a project, as different projects have different commit rates and the nature of one dev's work may be very different from another. The RepoSense report is just a means for conveniently accessing your work in one page, and also a means of stress testing RepoSense.
By the end of this semester, we expect you to,
If you can't work out a plan that achieves the above, you can seek guidance from the seniors and/or the prof as well.
Help to maintain a healthy supply of beginner-friendly issues: If you encounter small non-urgent issues (so called 'low hanging fruits'), it is best to leave them for future new contributors, because we expect several new contributors to join the project during the upcoming summer.
In fact, go the extra mile to create such issues when you can, as a good supply of such beginner-friendly issues is an essential asset for an OSS project.
As we are now reaching the end of the semester:
Soft deadline: end of week 13; hard deadline: end of reading week