-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP]GCI 2019 Task List #6239
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
POINTS TO REMEMBER WHILE WRITING ISSUES IN ISSUE LIST
|
From last year's experience, I mainly faced problems in understanding the task/issue when reading on the GCI dashboard as it wasn't properly stated what's to be done, and also I think we should add a link to the respective files found in the codebase to fix the error, and the issue # on GitHub on the GCI task description itself. |
Sure! Nice suggestion!
…On Thu, Sep 12, 2019, 12:43 AM Oorjit Chowdhary ***@***.***> wrote:
From last year's experience, I mainly faced problems in understanding the
task/issue when reading on the GCI dashboard as it wasn't properly stated
what's to be done, and also I think we should add a link to the respective
files found in the codebase to fix the error, and the issue # on GitHub on
the GCI task description itself.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ5ZIZ6IONKCPGTXEP3QJE7N7A5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6PSRXY#issuecomment-530524383>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQ7XKCABLXFU3YTZRVLQJE7N7ANCNFSM4ITP5BQQ>
.
|
@oorjitchowdhary I am taking up your suggestion and making a pending suggestion - where we call for help from all mentors |
@oorjitchowdhary will you be a mentor this year?? Excited to work with you!! I remember I joined PL right at the end of your Google Code In program |
Hello @sashadev-sky I think we can add these to the task list too #3534 , #5181 |
Yes, it is a good fto issue. So, I think it should be added to the list. |
Debasish go ahead. Please don't forget to add labels and link it over here.
Thanks
…On Mon, Sep 16, 2019 at 5:21 PM Debasish Sahoo ***@***.***> wrote:
Yes, it is a good fto issue. So, I think it should be added to the list.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ3FHFSM2P5HQLTKK73QJ5XLTA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Y4OBA#issuecomment-531744516>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQ7I27FF7WQWCQF6AN3QJ5XLTANCNFSM4ITP5BQQ>
.
|
Can I refer some issues for GCI, @SidharthBansal . I am willing to mentor GCI this year. |
Yeah sure.
Go ahead!
…On Tue, Oct 1, 2019 at 1:31 AM Sudipto Ghosh ***@***.***> wrote:
Can I refer some issues for GCI, @SidharthBansal
<https://github.com/SidharthBansal> . I am willing to mentor GCI this
year.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ4YD2CUW4N22JVIIQ3QMJLJLA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD76467Q#issuecomment-536727422>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFAAEQ7WOMQQJJWZEHVYF63QMJLJLANCNFSM4ITP5BQQ>
.
|
Hey everyone, I have noticed a few issues on the GCI tasks dashboard, (basically tasks reserved for GCI) already have PR's by non GCI candidates. These are mainly issues labeled both as GCI candidate and First time issues. I think we should be more specific while creating issues and let people know if an issue is reserved for GCI before they claim and open a PR. This would cause a lot of confusion to GCI students, if they claim a task officially and it has a PR made. Thanks! |
We need to ensure that the ftos reserved by gci have a tagline `Reserved
for GCI` as we did last year.
Mentors need to ensure non gci folks don't solve gci issues.
We need to be alert.
Thanks Ananya for bringing this to our attention.
…On Sun, Nov 10, 2019 at 11:52 AM Ananya Arun ***@***.***> wrote:
Hey everyone, I have noticed a few issues on the GCI tasks dashboard,
(basically tasks reserved for GCI) already have PR's by non GCI candidates.
These are mainly issues labeled both as GCI candidate and First time issues.
I think we should be more specific while creating issues and let people
know if an issue is reserved for GCI before they claim and open a PR. This
would cause a lot of confusion to GCI students, if they claim a task
officially and it has a PR made.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ3VNDRGP7BAH3C3SFLQS6SCFA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDUWPCA#issuecomment-552167304>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQYX2VNPI6YCFKVXBTDQS6SCFANCNFSM4ITP5BQQ>
.
|
Please add checks in the checkboxes that are uploaded to the GCI dashboard! |
@SidharthBansal why does it say Read through Code Climate "smells", Suggest new changes & Report Bugs (described in #3460), and Help add code links to existing issues (described in #3424) are published on GCI dashboard (what I think is indicated by "-- gci dashboard") but they are not? Did we decide to delete them for some reason? Were we planning to do google forms for these or something? If not i'll add all of these! |
Please edit it as it is copied from last year. Thanks
…On Sun, Nov 17, 2019 at 11:55 PM Sasha Boginsky ***@***.***> wrote:
@SidharthBansal <https://github.com/SidharthBansal> why does it say Read
through Code Climate "smells", Suggest new changes & Report Bugs (described
in #3460 <#3460>), and Help add
code links to existing issues (described in #3424
<#3424>) are published on GCI
dashboard (what I think is indicated by "-- gci dashboard") but they are
not? Did we decide to delete them for some reason? Were we planning to do
google forms for these or something?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ53I72TMJS5J6IK2FLQUGEAHA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEISPNY#issuecomment-554772407>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ7QGLZ7JHIMFVNKK3LQUGEAHANCNFSM4ITP5BQQ>
.
|
That will be awesome, thank you
…On Mon, 18 Nov 2019, 5:37 pm Sasha Boginsky, ***@***.***> wrote:
@SidharthBansal <https://github.com/SidharthBansal> cool ill fix them up
and add them later today!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQZ4WGB64ANWAXW5CUTQUKAPPA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEKHFKQ#issuecomment-554988202>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ3GA6CV2NEZODWGOETQUKAPPANCNFSM4ITP5BQQ>
.
|
@SidharthBansal what would be awesome? I was trying to confirm that we were dropping the forms idea posted above and moving forward with just adding supportive tasks to GCI like last year? |
I am sorry, I actually didn't receive any image on my Gmail and replied to you without the image. |
I have updated the guidelines. Mentors are requested to re-read it! |
all supportive tasks uploaded to GCI dashboard! 2 still pending publish |
Thanks
…On Mon, 9 Dec 2019, 6:49 am Sasha Boginsky, ***@***.***> wrote:
all supportive tasks uploaded to GCI dashboard! 2 still pending publish
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ3JU4OHXNDTTXFVDPTQXWMLXA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGHRBHA#issuecomment-563024028>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ5UZDF36NN5YK3II4LQXWMLXANCNFSM4ITP5BQQ>
.
|
@keshav234156 @SidharthBansal are we allowed to solve these issues before they are uploaded to the GCI dashboard or do we have to wait for them to be uploaded? Thanks. |
@VladimirMikulic I responded in gitter but pasting here as well -
|
You can solve it. Once merged we will upload it to the dashboard
If we forget to upload due to some reason then I am there to consider
points for that task
No worries
…On Fri, 10 Jan 2020, 1:16 pm Sasha Boginsky, ***@***.***> wrote:
@VladimirMikulic <https://github.com/VladimirMikulic> I responded in
gitter but pasting here as well -
i will try to add some GCI tasks this weekend!!
Sasha Boginsky @sashadev-sky <https://github.com/sashadev-sky> 02:25
if you guys see an open issue and are interested in solving it - I am not
opposed to you commenting that and i'll get it uploaded to the dashboard
quickly / assign it the difficulty level. Otherwise most tasks take me a
bit of time to write
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ5VCKQEJGQYGUVHZXLQ5ARTRA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIS7PNI#issuecomment-572913589>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ5LR7O52TVTT4YGWX3Q5ARTRANCNFSM4ITP5BQQ>
.
|
@CodeSarthak kindly get it approved https://codein.withgoogle.com/dashboard/tasks/5689351694974976/ |
@VladimirMikulic @Uzay-G are you willing to refactor this folks? |
Open up a new issue with ONLY changes that are needed. |
Of course @SidharthBansal. |
No I think he wants us to open a new reactors issues with potential tasks
for the next gci. I'd love to work on it 👍
…On Fri, Jan 24, 2020, 19:35 Vladimir Mikulic ***@***.***> wrote:
Of course @SidharthBansal <https://github.com/SidharthBansal>.
If I understand you correctly, you want us to finish the unsolved issues?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AMTREYIIERZWMZ7DPICXSG3Q7MYIJA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ3V7PA#issuecomment-578248636>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMTREYMEARIG5VRB7WX4UELQ7MYIJANCNFSM4ITP5BQQ>
.
|
I think it will be great to refactor the list as @Uzay-G said before finishing this list @VladimirMikulic |
Hey @SidharthBansal I am working on refactoring this now and I had a question. I think it would be useful to just group tasks by type (design, code, outreach) instead of by repository. What do you think? |
Idea accepted. Great thinking
Thanks
…On Wed, 29 Jan 2020, 2:31 am Uzay-G, ***@***.***> wrote:
Hey @SidharthBansal <https://github.com/SidharthBansal> I am working on
refactoring this now and I had a question. I think it would be useful to
just group tasks by type (design, code, outreach) instead of by repository.
What do you think?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#6239?email_source=notifications&email_token=AFAAEQ5QS2SGWB2OJBTQLF3RACMLJA5CNFSM4ITP5BQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKE4HYA#issuecomment-579453920>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ2QCDOHBU7NTRN5OUDRACMLJANCNFSM4ITP5BQQ>
.
|
Refactored in #7408 |
Please add pending issues from #3276
An uploaded task has a tick in the tasklist whereas not - uploaded task does not have a tick in the tasklist but is present in the tasklist.
Code: writing or refactoring
Design: graphic design or user interface design
IS
Quality Assurance: testing and ensuring code is of high quality
Code
LBL
Quality Assurance: testing and ensuring code is of high quality
LDI
Coding
#replaceTool
method #6793 M -- GCI dashboard#469 M -- GCI dashboard
#replaceTool
method in MapKnitter #6793 M -- GCI dashboard#cancelExport
method#479 H -- GCI dashboard
Design
Documentation/training
#_calculateProjectiveTransform
works #484 H -- GCI dashboardQuality Assurance
MapKnitter
Code
Outreach/Research
Quality Assurance: testing and ensuring code is of high quality
Plots2
Quality Assurance: testing and ensuring code is of high quality
PublicLab.Editor
simple-data-grapher
Quality Assurance:
Code: writing or refactoring:
SWB
Quality Assurance: testing and ensuring code is of high quality
Outreach/Research
Infragram
Coding
Design
All
Supportive Tasks / Outreach/Research
Refer: https://github.com/publiclab/plots2/wiki/Supportive-Tasks
WIP
The text was updated successfully, but these errors were encountered: