What are the rules regarding the number of issues to be opened at a time ?

[sambitsingha]

What are the rules regarding doing issues in GGSoC ?
Like can I choose more than 2 or 3 issues at a time , then start working on them simultaneously

[TANJIRO1709]

the rules can be :

1. Prioritize Quality Over Quantity: When launching a project, it's usually better to prioritize quality over quantity. Opening a lot of issues at once can be overwhelming for contributors and maintainers, making it more difficult to handle and resolve each one. Make sure you are not spamming anywhere.
   2)Observe Contribution standards: Best procedures for creating problems and submitting pull requests are outlined in many projects' unique contribution standards. These policies could stipulate how many issues can be opened concurrently or offer recommendations in this regard.
   3)Work Together and Communicate: Prioritize and resolve current concerns by working with the project's community rather than opening new ones at the same time. Participate in dialogues, add to ongoing debates, and cooperate to more efficiently identify, prioritize, and address problems.
   4)Emphasis on Impactful Contributions: Give top priority to addressing serious problems, feature requests, or enhancements that will significantly advance the project. Don't start pointless or duplicate issues that could divert your attention from more important work.

Hope i was able to answer your question. make sure to mark the answer. Thank you .
Sujal Agarwal
9th May

[Arifkhankhankhankhan]

some organizations might have guidelines or preferences regarding the number of tasks a participant can work on simultaneously. It's advisable to communicate with your mentor or refer to the organization's documentation for any specific recommendations.

In GGSoC, there's no problem with tackling multiple issues simultaneously. You can contribute as much as you can manage effectively. Just make sure to communicate with your mentors and manage your time wisely.

[RamakrushnaBiswal]

It's totally depends upon the organization

[AKASH722]

@sambitsingha

It depends on the organization and project you contribute to.

Some general guidelines would be:
Try to create PR when relevant.
Try to explain what your code does.

Rest rules will be repo specific
So check readme file

Hope you find it helpful

[ShagunSharma17]

I read it on GSSOC's website under the FAQ section there was no such number mentioned here is what was stated "Yes, you can contribute to multiple projects. However, we recommend that you focus on one project at a time to ensure you have a fulfilling learning experience. "

[Ojas-Arora]

In GSSoC (GirlScript Summer of Code), there are typically no strict rules against working on multiple issues simultaneously. However, it's important to keep a few guidelines in mind:

1. Time Management: Make sure you can effectively manage your time and attention if you choose to work on multiple issues simultaneously. Ensure that you have enough bandwidth to dedicate to each task without compromising the quality of your contributions.

2. Understand the Project's Workflow: Different projects may have different workflows and expectations regarding contributions. Some projects may encourage contributors to work on multiple issues at once, while others may prefer contributors to focus on one task at a time. Familiarize yourself with the project's guidelines and adapt accordingly.

3. Communication: If you plan to work on multiple issues simultaneously, it's a good practice to communicate your intentions with the project maintainers or mentors. They can provide guidance, prioritize tasks, and ensure that your efforts are aligned with the project's goals.

4. Prioritize Tasks: Identify which issues are more urgent or critical for the project and prioritize them accordingly. It's essential to manage your workload effectively to ensure that you're making meaningful progress on each task.

5. Manage Pull Requests: If you're working on multiple issues simultaneously and creating pull requests for each, ensure that you manage them effectively. Keep track of your pull requests, respond to feedback promptly, and address any conflicts or issues that arise during the review process.

6. Quality Over Quantity: While it's tempting to work on multiple issues simultaneously to make more contributions, prioritize quality over quantity. Ensure that each contribution meets the project's standards and adds value to the project.

Overall, while there's generally flexibility in how many issues you can work on at a time in GSSoC, it's essential to strike a balance between productivity and quality. Communication with project maintainers, effective time management, and prioritization are key to successful contributions.