Should PR be labelled gssoc or issue? Is it necessary to have gssoc label? #131
-
Where gssoc label should be there? PR or issue |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
It should be labelled as gssoc otherwise your contribution may not be considered for evaluation and ask project owner/maintainer to add level as gssoc level 1, 2.. |
Beta Was this translation helpful? Give feedback.
-
The issue and PR both should be labelled gssoc . And level label like level1 , level2 , level3 also should be present there as points were calculated according to that. |
Beta Was this translation helpful? Give feedback.
-
Ensure that both the issue and pull request carry the "gssoc" label, as it is essential for your contribution to be recognized and evaluated. Moreover, kindly request the project owner or maintainer to incorporate level labels such as "gssoc level 1," "gssoc level 2," and so forth. These level designations are significant as they determine the points allocated for each contribution, thereby ensuring fair evaluation and recognition of efforts. |
Beta Was this translation helpful? Give feedback.
-
Project admin should assign that for you, in case you forgot to |
Beta Was this translation helpful? Give feedback.
-
It is necessary to have level as "gssoc" if you don't see that ask them in comments to place it for you. |
Beta Was this translation helpful? Give feedback.
The issue and PR both should be labelled gssoc . And level label like level1 , level2 , level3 also should be present there as points were calculated according to that.