Read Before Contributing: PR and Issue Guidelines #208
Replies: 12 comments 6 replies
-
|
@viru0909-dev Do you require mentors for this project? I am a selected mentor for gssoc26 and I have a experience in spring boot backend system and I am looking for projects to mentor |
Beta Was this translation helpful? Give feedback.
-
|
@PUSHPAK-JAISWAL Happy to work with you. You can work as a mentor in this project. Please go through our idea and codebase. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
#220 #354 These two have not been marked as GSSoC approved. Thanks! @viru0909-dev |
Beta Was this translation helpful? Give feedback.
-
|
#229 @viru0909-dev This PR has been merged but hasn't been marked as GSSoC approved yet. Could you please update the label? Thank You! |
Beta Was this translation helpful? Give feedback.
-
|
#214 @viru0909-dev This PR has been merged but hasn’t been marked as GSSoC approved yet. Could you please update the label so it can be counted for GSSoC? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
#338 is now open for contributors. If anyone would like to work on this issue, please comment below with your approach or implementation idea before starting. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hello Everyone, I may not be as active for the next 5 days as I was before. I’ll still try to review some PRs daily, but responses may be slower during this period. Please continue contributing, exploring the codebase, and bringing in innovative ideas. I’m excited to see your contributions and work together with you all. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi @viru0909-dev ! I’ve started working on the COLMAP sparse reconstruction integration for Phase 3 for PR #149 and completed the initial workspace setup and reconstruction pipeline locally. While testing the automated reconstruction flow, I’m currently facing a CUDA/runtime compatibility issue with the Windows COLMAP build, and feature matching is failing during sparse reconstruction. I’m planning to continue validating the reconstruction flow through the COLMAP GUI and improve the preprocessing pipeline (frame sampling, metadata handling, synchronization, etc.) in parallel. I just wanted to ask if you’d recommend:
Would appreciate any guidance before moving deeper into the reconstruction stage. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @aaryaj154, thanks for the update! Awesome to see this moving forward. Windows CUDA issues are notoriously annoying. A lot of people find it easier to run COLMAP through WSL2 or a Docker container instead of native Windows, so you might want to give that a shot if it keeps failing. |
Beta Was this translation helpful? Give feedback.
-
|
@viru0909-dev
So COLMAP itself is currently unable to start inside WSL despite being installed successfully. Before I spend time rebuilding COLMAP from source or switching to a Docker-based setup, do you have a preferred environment for this project (WSL2 build from source, Docker image, specific COLMAP version, etc.)? I wanted to check if the team already has a recommended setup before proceeding further. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Welcome to Nyay Setu and thank you for your interest in contributing.
Before you open an issue or submit a pull request, please take a moment to review the following guidelines. PRs that do not follow these rules will be closed without review.
Contribution Checklist
Read CONTRIBUTING.md first. It covers the full workflow from forking to submitting a PR.
One issue at a time. Do not request assignment on multiple issues simultaneously. Complete your current task before picking up a new one.
Get assigned before starting work. Comment on the issue to express interest. Do not open a PR for an issue that is already assigned to someone else.
Follow Conventional Commits. All commit messages must follow the format:
feat: add skeleton loading componentfix: wrap console.log with DEV checkdocs: update setup instructionsPRs with messages like "changed file" or "updated code" will be rejected.
Link the issue in your PR description. Use
Closes #<issue-number>orFixes #<issue-number>so the issue auto-closes on merge.Fill out the PR template completely. Do not leave placeholder text like
Closes # (issue).Do not submit duplicate PRs. Check the open PRs list before submitting. If someone already has an approved PR for the same issue, yours will be closed.
Test your changes before submitting. At minimum:
npm run buildmust passmvn compilemust passHow Issues Are Assigned
advanced) are assigned based on the quality of your proposed approach, not arrival order.Questions?
If you have questions about the codebase, architecture, or your approach to an issue, comment directly on the issue thread. Do not open new issues for questions.
Beta Was this translation helpful? Give feedback.
All reactions