Chose a scoring system for gci students #6278
Comments
|
@SidharthBansal @IshaGupta18 I know only two of you guys and also @gauravano. Please mention others as well for proper consensus. |
|
Please add a comment in call for mentors that "scoring system is discussed
in #6278".
Thanks for opening it on my suggestion!
…On Thu, Sep 12, 2019, 7:23 PM newbazz ***@***.***> wrote:
@SidharthBansal <https://github.com/SidharthBansal> @IshaGupta18
<https://github.com/IshaGupta18> I know only two of you guys and also
@gauravano <https://github.com/gauravano>. Please mention others as well
for proper consensus.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AFAAEQZ2PHDBQ6VJTPDYSWDQJJCXNA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6R636Y#issuecomment-530836987>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQ6G27LVJXZB7N4IVH3QJJCXNANCNFSM4IWEP4NA>
.
|
|
I was thinking of labeling issues as easy-work, medium, or hard and then adding specific points to each task. And then the contributor can be easily evaluated according to the score plus his involvement with the community and other measures. |
|
I think we should have a little more detailed description on the points
system, and discuss it thoroughly, as it will be fixed once decided and we
won't be able to change it once GCI begins.
…On Tue, Sep 17, 2019, 8:45 PM Debasish Sahoo ***@***.***> wrote:
I was thinking of labeling issues as easy-work, medium, or hard and then
adding specific points to each task. And then the contributor can be easily
evaluated according to the score plus his involvement with the community
and other measures.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AJXHQZZ2KL4BVIMYVUDEPFLQKDX7LA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD644BXY#issuecomment-532267231>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJXHQZ2L4D6KRMQFHU73FQTQKDX7LANCNFSM4IWEP4NA>
.
|
|
Okay yes it makes sense to have some sort of labels for the issues. Let us first begin by mentioning all the types of issues that can be there for a gci student like |
|
+1 for labels like hard medium and easy.
…On Tue, Sep 17, 2019 at 11:25 PM newbazz ***@***.***> wrote:
Okay yes it makes sense to have some sort of labels for the issues. Let us
first begin by mentioning all the types of issues that can be there for a
gci student like typo, css fixing etc and rate them accordingly. Firstly
make buckets so as to fit all of the issues and keep a scoring system for
the individual bucket.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AFAAEQZRXACED5AUSHCZHI3QKEKX3A5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65LUTI#issuecomment-532331085>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQ5PTHKSVY4R6BTEU4DQKEKX3ANCNFSM4IWEP4NA>
.
|
|
Yes, but they won't be enough
On Wed, Sep 18, 2019, 1:10 AM Sidharth Bansal <notifications@github.com>
wrote:
… +1 for labels like hard medium and easy.
On Tue, Sep 17, 2019 at 11:25 PM newbazz ***@***.***> wrote:
> Okay yes it makes sense to have some sort of labels for the issues. Let
us
> first begin by mentioning all the types of issues that can be there for a
> gci student like typo, css fixing etc and rate them accordingly. Firstly
> make buckets so as to fit all of the issues and keep a scoring system for
> the individual bucket.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#6278?email_source=notifications&email_token=AFAAEQZRXACED5AUSHCZHI3QKEKX3A5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65LUTI#issuecomment-532331085
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AFAAEQ5PTHKSVY4R6BTEU4DQKEKX3ANCNFSM4IWEP4NA
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AJXHQZ74NDGXYPAG5WECHUTQKEXB3A5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD65VL6Q#issuecomment-532370938>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJXHQZZS5NYY2GQTSA3K373QKEXB3ANCNFSM4IWEP4NA>
.
|
|
@IshaGupta18 yes we know that they wont be enough, that is why we have proposed an idea to list down all the types of issues that a gci can get to solve, and according to the same, we can make further categories. |
|
As far as labels go, google code-in gives some guidelines:
I designed a scoring / label system in this doc that (I think?) fits the model of GCI: https://docs.google.com/document/d/1KW6zIHtrJEl9329Yep5JhTA5CPmA8XV64CMx5Pz_7KU/edit# From here we can tailor it to fit if it doesn't? @newbazz @jywarren |
|
Hey, can I get the access to the document as well, I would like to view the
scoring scheme and suggest changes if there are any!
…On Sat, Sep 21, 2019, 5:19 PM Sasha Boginsky ***@***.***> wrote:
As far as labels go, google code-in gives some guidelines
<https://developers.google.com/open-source/gci/faq#tasks>:
- we should categorize tasks in one of the 5 category labels so people
can filter
- it says students are able to do 2 "beginner" tasks max - so I was
just thinking beginner, medium, hard is sufficient.
I designed a scoring / label system in this doc that (I think?) fits the
model of GCI:
https://docs.google.com/document/d/1KW6zIHtrJEl9329Yep5JhTA5CPmA8XV64CMx5Pz_7KU/edit#
From here we can tailor it to fit if it doesn't? @newbazz
<https://github.com/newbazz> @jywarren <https://github.com/jywarren>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AJXHQZ4JDMRUQ465ISDD7JDQKYC5VA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7IQI6A#issuecomment-533791864>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJXHQZ74BJXSCODGV5IMMSDQKYC5VANCNFSM4IWEP4NA>
.
|
|
I would also like to have the access. I can suggest something if any. |
|
sorry forgot it was private! I guess its best to leave it private.. I shared with @debck @oorjitchowdhary @jywarren and a few other emails I have already. I will need the rest of your emails to share! Just click on share button on the link to request access @IshaGupta18 |
|
Also people I have added have the rights to add anyone else so go ahead if you guys know eachotheres email |
|
Ok the following people still need to be added @newbazz @IshaGupta18 @aashna27 @jesus-montano @coderjolly @Divy123 @ViditChitkara @CleverFool77 |
|
@sashadev-sky really appreciate your efforts. I think the doc seems okay. One more suggestion from my side is, I have noticed that the code whether ruby or js, doesn't confine to the coding standards of the specified language, that is what needs to be added as a beginners issue as well. |
|
@newbazz yes I have always thought that really really neeeds to be fixed add it on |
|
@newbazz I think it can be medium as well. The user should document the standards first, then fix them. |
|
rememeber beginner issues are limited to 2. anyone have any idea how many that means we should make? |
|
The standards are already fixed for programming languages which we use like ruby and javascript. We also have linters, we can add the lint tests in continuous integration as well. |
It depends on the students PL gets this year :P |
|
Can you please share me access to the document @sashadev-sky , so that I too can share my valuable response for the scoring system as well. |
Sure @sashadev-sky , pls add me |
|
@sasha Boginsky <sboginsky17@gmail.com> It will be great if you can give
comment access to all the viewers.
I think we should make hard as 40 points as it takes a lot of time and
effort. Great work Sasha
…On Mon, Sep 30, 2019 at 5:05 AM Harman Jolly ***@***.***> wrote:
Ok the following people still need to be added @newbazz
<https://github.com/newbazz> @IshaGupta18 <https://github.com/IshaGupta18>
@aashna27 <https://github.com/aashna27> @jesus-montano
<https://github.com/jesus-montano> @coderjolly
<https://github.com/CoderJolly> @Divy123 <https://github.com/Divy123>
@ViditChitkara <https://github.com/ViditChitkara> @CleverFool77
<https://github.com/CleverFool77>
Sure @sashadev-sky <https://github.com/sashadev-sky> , pls add me
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AFAAEQ373T3A4AEW4K6TWWLQME3SRA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD74BMJA#issuecomment-536352292>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQYOLBJXYH5ZJMYIV63QME3SRANCNFSM4IWEP4NA>
.
|
|
sorry for the delay! just added you guys to all the docs @pydevsg @coderjolly |
|
Thanks for adding me to the docs. |
|
The |
|
Hi Sudipto. Thanks for your concern about the nobody willing to take the
impossible tasks.
They were proposed to be named as impossible as the existing community
couldn't solve it. They are not necessarily features. So technical features
will be inadequate label.
Regarding points, I think there should be fair difference bw points.
Impossible specially should have 2x hard score as nobody will be able to
provide support on them.
…On Wed, 16 Oct 2019, 11:16 am Sudipto Ghosh, ***@***.***> wrote:
The impossible issues can be renamed to technical_features issues or some
relevant but not impossible . Would like to have opinions on this from
others as well. @SidharthBansal <https://github.com/SidharthBansal> ,
@coderjolly <https://github.com/CoderJolly> , @newbazz
<https://github.com/newbazz> @IshaGupta18 <https://github.com/IshaGupta18>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6278?email_source=notifications&email_token=AFAAEQ5QHFD2TGPHBT3V7BDQO2TDZA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBLFHMA#issuecomment-542528432>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ5WZPWFOC66QYC3IMLQO2TDZANCNFSM4IWEP4NA>
.
|
|
Yes, I also dont think that renaming the issues will help. Renaming will not change the nature of the issue, but yes i think we can partially give them points for the |
Thanks for the access @sashadev-sky. 😄 👍 🎉 |
|
Have we chosen a scoring system for gci students? If so, perhaps should we close this issue? |
|
@ebarry we are there with a scoring system, i think we can close this issue. What say @SidharthBansal |
|
@sashadev-sky , would time taken to complete a ticket also be taken into account? |
|
In short,
# Scoring System
**Beginner Level Task(1pt):** Installation Tasks, FTOs, Typographical
errors, HTML/CSS etc.
**Medium Level Tasks(2pt):** Simple challenging tasks like methods, tests,
designs, demos, documentation(if small) etc.
**Hard Tasks(5pt):** New feature, research, Documentation(long or difficult
for high school students to understand and write), etc.
**Supportive Tasks(1pt):** Bug reporting(1pt/tasks), creating fto(1pt/task),
screenshots(1pt/task), suggest new changes(if change is accepted-1pt/task),
adding code linking(1pt/task) and other tasks of helping like pr reviews,
participating in weekly checkins (1pt/week, however if mentor finds that
mentee is too helpful than mentor can award 2 points at max).
**Impossible Tasks(15pt):** Wontfix issues. Jeff will ONLY make/publish
these tasks.
Please refer: https://github.com/publiclab/plots2/wiki/Supportive-Tasks
Thanks
|
|
I just consolidated the GDoC made by Sasha. Thanks Sasha!
On Tue, Nov 12, 2019 at 11:16 AM Sidharth Bansal <
bansal.sidharthcode@gmail.com> wrote:
… In short,
Scoring System
-
Beginner Level Task(1pt): Installation Tasks, FTOs, Typographical
errors, HTML/CSS etc.
-
Medium Level Tasks(2pt): Simple challenging tasks like methods, tests,
designs, demos, documentation(if small) etc.
-
Hard Tasks(5pt): New feature, research, Documentation(long or
difficult for high school students to understand and write), etc.
-
Supportive Tasks(1pt): Bug reporting(1pt/tasks), creating
fto(1pt/task), screenshots(1pt/task), suggest new changes(if change is
accepted-1pt/task), adding code linking(1pt/task) and other tasks of
helping like pr reviews, participating in weekly checkins (1pt/week,
however if mentor finds that mentee is too helpful than mentor can award 2
points at max).
-
Impossible Tasks(15pt): Wontfix issues. Jeff will ONLY make/publish
these tasks.
Please refer: https://github.com/publiclab/plots2/wiki/Supportive-Tasks
Thanks
On Mon, Nov 11, 2019 at 1:58 PM StellaMaris Njage <
***@***.***> wrote:
> @sashadev-sky <https://github.com/sashadev-sky> , would time taken to
> complete a ticket also be taken into account?
>
> —
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#6278?email_source=notifications&email_token=AFAAEQ4NUNZR3KNSFWB4MLLQTEJTRA5CNFSM4IWEP4NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDWBEQA#issuecomment-552342080>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AFAAEQ4A2J57GWU7QJQJAULQTEJTRANCNFSM4IWEP4NA>
> .
>
|
Discuss it with other mentors and have a proper method for scoring the gci participants.
The text was updated successfully, but these errors were encountered: