Rules
-
This period is all about, well, community bonding. Rather than jumping straight into coding, you’ve got some time to interact with other open-source enthusiasts! In community bonding period students can start interacting with their mentors over discord, this helps students to deep dive into the projects and gives them time for learning any new technology related to the project.
-
Students are expected to set up 1:1 meeting with mentors to discuss the project, seek out help if needed, set up work sessions or talk about professional growth or industry. Contributors can discuss about project requirements, timeline, improvements & problems that they was facing at that moment.
-
This period will helps both mentors and mentees to make concrete milestones for the project before the actual coding period starts.
-
Since different students are working on different idea list, we are supposed to have team spirit & this session really helps in getting to know each other.
Understanding the codebase is always overwhelming, but remember that Rome was not built in a day. Try to understand the workflow of code, execution starts at which file, which files and folders are responsible for which program logic. By doing this one can quickly get a high-level overview of the program logic and workflow.
Before your first pull request (PR)
- Read about the code style guide and understand the coding convention followed (when to use camel case, pascal case, 2 space or 4 space indentation, etc.)
- Check if any code formatting tools or linters are used
- Understand the automated tests that run on every pull request
- Understand basics of git like how to add Developer Certificate of Origin, squashing commits, rebasing branches, resolving merge conflicts, etc.
After this, you can start contributing to the codebase making specific feature and bug related pull requests aligned with your weekly miletsones.
