Contribution related doubt #101
-
Is it important for the project admin to assign the project to me before I fork the repository and start working on it ? |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments
-
Yes,it's generally considered good practice for the project admin to assign the project to you before you fork the repository and start working on it. This helps in several ways: Avoiding duplication of efforts: By having the project officially assigned to you, other participants are aware that someone is already working on it. This can prevent multiple contributors from working on the same tasks simultaneously, reducing duplication of efforts. Clear communication: Assigning the project to you establishes clear communication between you and the project maintainers. It ensures that they are aware of your intention to contribute and can provide guidance or support if needed. Tracking progress: Assigning the project to you allows the project maintainers to track your progress more effectively. They can monitor the tasks you're working on, provide feedback, and offer assistance if you encounter any challenges. Recognition: Being officially assigned to a project gives you recognition for your contributions. It shows that you are actively involved in the project and have been entrusted with specific tasks by the project maintainers. |
Beta Was this translation helpful? Give feedback.
-
Yes, it is indeed necessary to ask the mentor to assign the issue to you before forking the repository and commencing work on it. This step ensures that your contributions are accurately reflected on the leaderboard in terms of point count. When the mentor assigns the project to you, it establishes a clear ownership of the task, making it easier to track your progress and allocate points accordingly. So, reaching out to the mentor for assignment is crucial for ensuring your efforts are duly recognized within the project framework. |
Beta Was this translation helpful? Give feedback.
-
Hi there @sdass1918 👋🏻 Yeah you're right, you need wait until you're ISSUE is assigned to you. So that it helps to streamline the contribution process and helps us to track your changes easily. Once you're assigned for an ISSUE you can start working on it by forking and making necessary changes on a new branch. Hope this helps! |
Beta Was this translation helpful? Give feedback.
-
It depends @sdass1918 on the workflow and policies of the project you're working on, but generally, it's a good idea to have clarity on who is responsible for what before you start working on a project. Here are few reasons:
|
Beta Was this translation helpful? Give feedback.
-
Hey, @sdass1918 It's beneficial if the project admin assigns the project to you prior to forking the repository and initiating your contributions. This helps in a few ways:
While it's not strictly necessary for the admin to assign the project to you before you fork the repository, doing so can streamline the contribution process and ensure everyone is on the same page. If the admin hasn't assigned the project yet, it's a good idea to reach out and ask for clarification or permission before diving in. |
Beta Was this translation helpful? Give feedback.
-
Hi @sdass1918! |
Beta Was this translation helpful? Give feedback.
Yes,it's generally considered good practice for the project admin to assign the project to you before you fork the repository and start working on it. This helps in several ways:
Avoiding duplication of efforts: By having the project officially assigned to you, other participants are aware that someone is already working on it. This can prevent multiple contributors from working on the same tasks simultaneously, reducing duplication of efforts.
Clear communication: Assigning the project to you establishes clear communication between you and the project maintainers. It ensures that they are aware of your intention to contribute and can provide guidance or support if needed.
Tracking progre…