Regarding Issues on project

[ankitgupta143]

Is Require to make Issue request to the project Owner or directly fork the project and start working on the project in vs code. If needed then how i make the issue request. Please someone tell step by step procedure.

[AkshaySobti]

1. Check the issues which are there. Select the issue in which you are confident that yes I can solve this issue. Ask the project admin or mentor that can I solve this issue? You can ask them there in the Github chat section. Also, there should be a tag of "GSSoC'24" on that particular issue. If someone is already working on that issue, then you will not be assigned that issue.
2. If the mentor or the project admin finds you suitable, then they will assign you that issue.
3. Once the issue is assigned, clone the project and start working on that particular issue. Create a new branch to work on that issue.
4. After resolving the issues, push them to your forked repository.
5. When you have completed all the tasks, create a pull request.
6. Finally, your pull request (PR) will be reviewed and if the mentor or project admin finds everything correct, they will merge the PR.

@ankitgupta143

[Princegupta101]

You can make a new issue and after reach out to Project Admin or owner they assgined you than you will work on issue and make a pr and add PA as a reviwer and merge it
@ankitgupta143

[Ojas-Arora]

The procedure for contributing to a project typically involves creating an issue request to discuss the changes you want to make before starting work. Here's a step-by-step procedure:

1. Find a Project:

• Identify a project on GitHub that you're interested in contributing to. Look for projects that have active maintainers and a clear contribution process.

2. Create an Issue Request:

• Before you start working on any changes, it's a good idea to create an issue request to discuss your proposed changes with the project owner or maintainers.
• Go to the project's repository on GitHub and click on the "Issues" tab.
• Click on the "New issue" button to create a new issue.
• In the issue title, briefly describe the change or improvement you want to make.
• In the issue description, provide details about what you want to change or add to the project. Be clear and concise, and include any relevant information or context.
• Tag the issue appropriately (e.g., bug, enhancement, feature request).
• Submit the issue request.

3. Wait for Feedback:

• After submitting the issue request, wait for feedback from the project maintainers. They may ask for more information, suggest changes, or approve your proposal.

4. Fork the Project:

• Once your issue request is approved or if you haven't received any feedback within a reasonable time, you can fork the project.
• Click the "Fork" button in the top-right corner of the project's GitHub repository. This creates a copy of the repository in your GitHub account.

5. Clone the Forked Repository:

• Clone your forked repository to your local machine using Git. Open your terminal and run the following command:

  git clone https://github.com/your-username/project-name.git

6. Create a New Branch:

• Create a new branch for your changes. This keeps your work isolated from the main branch and makes it easier to manage.

  git checkout -b your-branch-name

7. Make Changes:

• Use your preferred code editor (like VS Code) to make the necessary changes to the project.

8. Commit Changes:

• After making your changes, stage and commit them to your local repository:

  git add .
  git commit -m "Your commit message"

9. Push Changes:

• Push your changes to your forked repository on GitHub:

  git push origin your-branch-name

10. Create a Pull Request:

• Go to your forked repository on GitHub and click on the "Pull requests" tab.
• Click on the "New pull request" button.
• Select the original repository and the branch containing your changes.
• Provide a descriptive title and description for your pull request, referencing the issue if applicable.
• Submit the pull request.

11. Wait for Review:

• Once you've submitted your pull request, wait for the project maintainers to review your changes. They may provide feedback or request changes before merging your pull request.

By following these steps, you can contribute to a project on GitHub in a structured and collaborative manner. Remember to communicate with the project maintainers and follow any guidelines or instructions they provide.

[abhiperfect]

Steps you should follow:

1. Find What to Work On: See what needs fixing or improving in the project.
2. Check if it's Already Reported: Look if someone else has mentioned the same issue.
3. Tell the Owner (if needed): If not, let the project owner know about it.
4. Wait for a Go-ahead: Wait for the owner's okay or advice.
5. Copy the Project: Make your own version of the project on GitHub.
6. Get the Project on Your Computer: Download it to your PC.
7. Create a New Place to Work: Make a separate space for your changes.
8. Make the Changes: Use VS Code to do the fixing or adding.
9. Save Your Work: Keep track of what you've done with clear notes.
10. Put Your Work on GitHub: Upload your changes.
11. Ask the Owner to Look: Request the project owner to check out what you've done.

[KhushmitaKapoor]

Find a Project: Choose an active project on GitHub that interests you.
Create an Issue: Discuss your proposed changes with the project maintainers by creating an issue on the project's GitHub repository.
Wait for Feedback: Wait for the maintainers to respond to your issue. They may approve your proposal or request further information.
Fork the Project: If your proposal is approved or you don't receive feedback, fork the project to your GitHub account.
Clone and Branch: Clone your forked repository to your local machine and create a new branch for your changes.
Make Changes: Use your preferred code editor to make the necessary modifications to the project.
Commit and Push: Stage and commit your changes locally, then push them to your forked repository on GitHub.
Create a Pull Request (PR): Submit a PR to the original repository, detailing your changes and referencing the corresponding issue.
Wait for Review: Await feedback from the maintainers on your PR. They may request modifications before merging your changes.

[EshaalakshmiDS]

To contribute to an open-source project like Girlscript Summer of Code, it's generally recommended to follow these steps:

Fork the Project: Before making any changes, fork the project repository on GitHub. This creates a copy of the project under your GitHub account.
Clone the Forked Repository: Clone the forked repository to your local machine using Git. This allows you to work on the code locally.
Create a New Branch: Create a new branch for your changes. This keeps your work isolated from the main branch and makes it easier to manage and review your contributions.
Make Changes: Use your preferred code editor, such as VS Code, to make the necessary changes to the codebase. Ensure that your changes adhere to the project's coding standards and guidelines.
Commit Your Changes: Once you've made your changes, commit them to your local branch with descriptive commit messages explaining the purpose of each change.
Push Changes to Your Fork: Push your committed changes to your forked repository on GitHub.
Submit a Pull Request (PR): After pushing your changes to your fork, navigate to the original project repository and submit a pull request. In the pull request, explain the changes you've made and why they're beneficial. Be sure to reference any relevant issues if applicable.
Now, regarding the issue request:

Create an Issue (if necessary): If you're proposing a new feature, reporting a bug, or suggesting an improvement, it's best practice to create an issue first. This allows you to discuss the changes with the project maintainers and get their feedback before investing time in coding.
Referencing the Issue in Your PR: When you submit your pull request, reference the corresponding issue in the PR description. This helps maintain a clear link between the issue and the proposed solution.
By following these steps, you can contribute to the Girlscript Summer of Code project in a structured and collaborative manner.