What do if someone does pull request on my own issue created despite the fact I raised the iisue to get assigned to me first

[Sibam-Paul]

I find out an issue and Wanted to get assigned but someone done the task before me despite the fact he is not assigned ;
So is it the write way to do OS
See https://github.com/Rajan-Barnwal/jobproject/issues/90
for better review

[Sibam-Paul]

This happened to be the 2nd time today

[CoderXYZ14]

The project administrator is responsible for deciding who to merge, although they may not appear on the leaderboard until approved by the admin. As multiple people can be assigned so if u think u can do better than him then in my opinion u can also focus on that issue but do not forget to inform the admin

[Sibam-Paul]

Wait the PA should Assign it then we shoudl start working???

[CoderXYZ14]

The ethical way is this only

[SpandanM110]

So to be very specific the in Open Source as a Contributor the perspective is who comes up with a better solution and a feature the point is if you find a issue that's indeed a great thing as first step to Open Source and after that you it all depends on the Project Admin who actually holds the project and the issue will be assigned to you as well and you both create a PR with proper screenshot and changes you made but now Vercel has a feature of viewing your changes directly if your contribution is great it will be merged and the Project Admin will close the issue.

Hope it helps
Spandan | Mentor

[Piyushsahu99]

In a well-structured operating system (OS), tasks should typically be assigned to individuals before they are completed to ensure clarity, accountability, and effective workflow management. If someone completed a task without being formally assigned to it, it could lead to confusion, duplication of efforts, and potential conflicts. It's important to establish clear procedures for task assignment and communication within the team to prevent such issues. Reviewing the specific situation mentioned in the GitHub issue link you provided can provide more context and insights into what might have happened and how to address it effectively.

[ishankumax]

In open-source projects, contributors like us focus on identifying and solving issues. Once an issue is found, the project admin assigns it, and we work on it, providing clear documentation and changes. Platforms like Vercel make it easier to review contributions. If our work is deemed valuable, it gets merged by the admin. It's a collaborative effort where everyone plays a part in driving progress.

Checkout following points for better understanding :

• The project administrator is responsible for deciding who to merge, although they may not appear on the leaderboard until approved by the admin.
• Multiple people can be assigned, so if you believe you can provide a better solution, it's important to focus on the issue, but also inform the admin.
• In open source, contributors aim to come up with better solutions and features.
• Finding an issue is a crucial first step.
• The project admin holds the project and assigns the issue.
• Both the contributor and admin create a PR with proper screenshots and changes made.
• Vercel offers a feature to view changes directly.
• If the contribution is great, it will be merged, and the admin will close the issue.

Hope this helps clarify the process!
Ishan | @ishankumax

[Piyushsahu99]

It's common for multiple contributors to work on the same issue in open source projects, even if the issue isn't explicitly assigned to them. In the case you've mentioned, it appears that someone has already submitted a pull request to address the issue before you had a chance to get assigned.

While it might feel frustrating to miss out on an opportunity to contribute, it's essential to remember that open source is collaborative, and contributions from multiple contributors are encouraged. Here are a few things to consider:

1. Collaboration: Reach out to the contributor who submitted the pull request and express your interest in collaborating on the issue. They may welcome additional contributions or feedback, and you could work together to improve the solution.

2. Review and Feedback: Even if you weren't the first to submit a solution, you can still review the existing pull request and provide feedback or suggestions for improvement. Your input can help ensure that the final solution meets the project's requirements and quality standards.

3. Other Opportunities: If you're unable to contribute to this particular issue, don't worry! There are usually many other opportunities to contribute to open source projects. Keep exploring the project's issue tracker, look for other areas where your skills can be valuable, and don't hesitate to reach out to maintainers or other contributors for guidance.

Ultimately, while it's natural to feel disappointed when you miss out on an opportunity to contribute, it's essential to maintain a positive and collaborative attitude in the open source community. There will always be more chances to make meaningful contributions and learn from others along the way.

[sanjay-kv]

This happened to be the 2nd time today

We passed strict guideline regarding this to mentors and project admin . First come first service on issue assigning . If you keep the issue stale for days it will be passed to other person .
The issue you mentioned is unethical will take strict action

[Sibam-Paul]

thanks @sanjay-kv