FOSS Hack
Partner Projects
The Partner Projects program is an effort to provide FOSS Hack participants with time and mentorship to be able to contribute to existing open-source projects.
The programme features a few community FOSS projects and commercial open source projects, with some of their curated issues' list, from which a few could be your potential problem statements for FOSS Hack.
This regards to the fact that at FOSS Hack, you can either build a FOSS project from scratch or contribute to an existing FOSS or commercial open source project. These issues can be considered as potential problem statements if you are unsure of which project/what contribution to make.
Browse through the projects and check for relevant issues that you can work upon.
Comment on the issue with a proposal that you would like to work on the issue.
Once the maintainer assigns a particular issue, you can get started with the prep phase.
Register for FOSS Hack, and start creating your team and project.
While creating projects, choose CONTRIBUTE to an existing project option.
Make sure to check - Contributing to partner project and choose your project from the list.
Fill in the details required and finishing setting up your project
PS: While setting up your project on the hackathon dashboard - the value in the Repo Link field gets auto-fetched with the repo of your selected project.
Nearing to the hackathon, you'd find fields in the dashboard to link your PRs/issues that you're working on.
Interact with the maintainers of the project you are working on, and get your issue specific queries solved.
Be ready to set your commits for during the hackathon hours.
Work on your solution and commit the changes.
Raise a PR to the project and add the PR link to the Repo Link field in your project dashboard.
You can also ask queries to your project maintainer during hacking hours.
Get your PR reviewed by the maintainers.
Make any needed changes that the maintainer suggests to make your PR more valuable.
Mention if you have a rough implementation in mind.
Indicate familiarity with the project stack.
State whether you've worked on similar issues before or if it's your first attempt.
Ask questions and seek help from maintainers for more context.
It's okay to feel unfamiliar at first; start small by setting up the project locally, fixing minor bugs, or adding tests.
Concentrate on a single project throughout for meaningful contributions.
Prefer public group queries over private messages for faster and more broadly helpful responses.
Aim for meaningful contributions rather than numerous PRs. Patience in making one significant contribution is more valuable.
Do not work on issues already assigned to someone else.
Don't be scared to ask for help, or to respond when you know it.
Respect the time and effort of maintainers spent in helping you.
Do not create unnecessary spam on the discussions.
Abide by the code of conduct.