-
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
Task list staging area for Google Code-In #3276
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.
1 similar comment
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.
Hi, all - I've consolidated the lists, and I think we should improve the text description of each, so they make sense to people who don't know our codebase. Please go ahead and edit but coordinate in the chatroom so you don't overwrite each other. |
I also want to highlight that some example tasks were like this: https://codein.withgoogle.com/archive/2015/organization/4777925899452416/task/4744391868547072/
This means that when we create the tasks, we can generate "multi-use" tasks that refer to an issue list, to save time filing new tasks. We should try to use tags to direct people to "first-timers" vs. "next-step" sized issues. Maybe we can have a task for "Complete your first issue at Public Lab" vs. "Take the next step with a more complex issue at Public Lab" and "Tackle a complex project at Public Lab"? |
Hi Jeff...we already have a great mechanism for directing people towards heavier tasks. When the mentors feel like student has done enough task you generally guide folks to do help me tagged issues. Similarly we can guide gci folks. |
I will say we can have two categories as you told in the above comment
|
That sounds great. I'm also interested in if we could make a task to paste
links to lines of code for new issues, as a task itself?
…On Mon, Sep 17, 2018, 12:52 PM Sidharth Bansal ***@***.***> wrote:
I will say we can have two categories as you told in the above comment
1. Gci candidate for normal to big sized gci tasks
2. Gci candidate and first timer tasks these tasks for first timers
gci folks.
This will reuse our existing labels at public labs.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJxsnsxQ_7m6aOh0A1BsKXFk_AYVMks5ub9NIgaJpZM4WS3nu>
.
|
Yeah if issue is fto and gci candidate labelled then we will paste the code links else if it is only gci Candidate we may or may not paste code links. |
This comment has been minimized.
This comment has been minimized.
Please add |
Looking for GSoCReviewing PRs and collaboration efforts will be judged in your upcoming GSoC proposals |
Hi @SidharthBansal Can you add this task to the list, it has been added to gci dashboard. |
Hi aashna27 please create a task on the GCI dashboard and send me the link
to the issue, I will add.
…On Tue, Oct 23, 2018 at 12:06 AM aashna27 ***@***.***> wrote:
Hi @SidharthBansal <https://github.com/SidharthBansal> Can you add this
task to the list, it has been added to gci dashboard.
publiclab/image-sequencer#429
<publiclab/image-sequencer#429>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQ4TzDIOkKQOEnQf__IcCgSLGgG_Iks5unhA5gaJpZM4WS3nu>
.
|
Hi @SidharthBansal Can you add this task to the list, it has been added to gci dashboard. is this fine? |
Thanks to hard work by @SidharthBansal and others, we now have 75 tasks published on the GCI dashboard, enough for the competition to begin! 🎉 🎉 |
Hi folks, just added this one which would make a good GCI issue if someone wants to add it to the dashboard (please leave a comment here if you do it!): |
And I made one more here! Medium-sized: #3836 |
Hey folks, I think the task 'Install plots2 on local machine' needs more mentors and preferably someone with experience in solving problems with the project installation! 😩 |
Ah, indeed - i see here:
https://codein.withgoogle.com/dashboard/tasks/6264099852779520/
Should we perhaps try to get students to work within a GitHub issue so
there can be more peer support? I didn't even realize this was all
happening, since it was only within the GCI system. What about an issue
like "Install plots2"?
…On Mon, Oct 29, 2018 at 7:01 PM Camila Araújo ***@***.***> wrote:
Hey folks, I think the task 'Install plots2 on local machine' needs more
mentors and preferably someone with experience in solving problems with the
project installation! 😩
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJzWIYK_-Db1KbGgKCEMkcqUPZrbvks5up4jBgaJpZM4WS3nu>
.
|
Install plots2: #3840 |
This list may also be a great source for new GCI issues: #3331 |
Hey, we are running really low on GCI tasks, there are about 6-7 left. |
I have added 10. Mentors are requested to draft the tasks as quickly as
possible.
…On Mon, Nov 19, 2018, 8:54 PM Sarthak Aggarwal ***@***.*** wrote:
Hey, we are running really low on GCI tasks, there are about 6-7 left.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQy1_WQGv6SGBK0zbNKtXGHcdVK6Uks5uws0hgaJpZM4WS3nu>
.
|
@SidharthBansal please publish this https://codein.withgoogle.com/dashboard/tasks/6044626013126656/ |
@jywarren there are many issues which are reported in this issue but are not made into separate issues and are not been worked upon. One way is to close this issue. Other way is to keep this issue open for GCI'19. We can continue things here. What do you suggest? |
Hi @SidharthBansal I think, us GCI participants (@oorjitchowdhary @tsparksh @JonathanXu1 @ValentinaTironi @okonek @kevinzluo ) will be more than happy to look through these tasks, see for which PRs have been made and make a new issue for GCI'19 or otherwise to help future participants. It is too big a task for one or two people but we guys have recently become accustomed to the repos and together I think we can give it a try. Cheers! CC : @jywarren @publiclab/guides |
Sarthak thanks for support. Are you willing to open up an issue listing all
the existing issues in form of checklist? Kevin is busy with school. Oorjit
is on off till 10 January. It will be great if you can do this before other
folks get free.
…On Wed, Jan 9, 2019, 4:33 PM Sarthak Aggarwal ***@***.*** wrote:
Hi @SidharthBansal <https://github.com/SidharthBansal> I think, us GCI
participants ***@***.*** <https://github.com/oorjitchowdhary>
@tsparksh <https://github.com/tsparksh> @JonathanXu1
<https://github.com/JonathanXu1> @ValentinaTironi
<https://github.com/ValentinaTironi> @okonek <https://github.com/okonek>
@kevinzluo <https://github.com/kevinzluo> ) will be more than happy to
look through these tasks, see for which PRs have been made and make a new
issue for GCI'19 or otherwise to help future participants. Cheers!
CC : @jywarren <https://github.com/jywarren> @publiclab/guides
<https://github.com/orgs/publiclab/teams/guides>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQyW6ZrPN8OGA18fotql285ZyK1toks5vBcyDgaJpZM4WS3nu>
.
|
Nice idea for making a separate checklist. And, thank you Sarthak for
support.
On Wed, Jan 9, 2019 at 4:43 PM Sidharth Bansal <[email protected]>
wrote:
… Sarthak thanks for support. Are you willing to open up an issue listing all
the existing issues in form of checklist? Kevin is busy with school. Oorjit
is on off till 10 January. It will be great if you can do this before other
folks get free.
On Wed, Jan 9, 2019, 4:33 PM Sarthak Aggarwal ***@***.***
wrote:
> Hi @SidharthBansal <https://github.com/SidharthBansal> I think, us GCI
> participants ***@***.*** <https://github.com/oorjitchowdhary>
> @tsparksh <https://github.com/tsparksh> @JonathanXu1
> <https://github.com/JonathanXu1> @ValentinaTironi
> <https://github.com/ValentinaTironi> @okonek <https://github.com/okonek>
> @kevinzluo <https://github.com/kevinzluo> ) will be more than happy to
> look through these tasks, see for which PRs have been made and make a new
> issue for GCI'19 or otherwise to help future participants. Cheers!
>
> CC : @jywarren <https://github.com/jywarren> @publiclab/guides
> <https://github.com/orgs/publiclab/teams/guides>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#3276 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AUACQyW6ZrPN8OGA18fotql285ZyK1toks5vBcyDgaJpZM4WS3nu
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AT6S9v3IMCuCjW9Z7XedcoLsxlEhxDHpks5vBc7sgaJpZM4WS3nu>
.
|
Thanks @SidharthBansal @gauravano Here it is : #4581 |
Hey @SidharthBansal Can you make @ValentinaTironi @okonek and @kevinzluo members of Public Lab, so that I can add them in the GCI 18 team I just made? Thanks. |
Sorry, GCI'18 is completed now, so I don't think that there is any need of
such group. We can tag them with their tagnames.
…On Wed, Jan 9, 2019, 5:08 PM Sarthak Aggarwal ***@***.*** wrote:
Hey @SidharthBansal <https://github.com/SidharthBansal> Can you make
@ValentinaTironi <https://github.com/ValentinaTironi> @okonek
<https://github.com/okonek> and @kevinzluo <https://github.com/kevinzluo>
members of Public Lab, so that I can add them in the GCI 18 team I just
made. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3276 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQ3dFulfEwNfq7qEe0vi6uMz_gJ3hks5vBdSmgaJpZM4WS3nu>
.
|
@CodeSarthak what is the progress here. Please do it before 15 January to get points for this task. |
🎉 |
👉 Please append a comment
Added to GCI dashboard
after each task which you have posted so no one else opens the same taskThis is a staging area. Each task has (or will soon have) a link to a full issue including relevant lines of code, screenshots, and other helpful information as we prepare them for solving. Some are harder than others, but those tagged with
first-timers-only
are great to begin with. (more documentation on tasks)Add new items: Look here for new items to adapt for this list: planning issues, break-me-up issues, fto-candidates. Fit tasks into the categories below.
Format items to be descriptive,
[bracket otherwise]
: As we create this list, it's OK to be brief, but if a task lacks description, tags, screenshots, and code links,[Put it in brackets to indicate that it needs to be fleshed out]
Break out items here into their own issues: Use the
gci-candidate
tag instead of thegci
tag to manage the supply. We don't want to have more open issues than we can support at one time, andgci
is what we'll direct students towards.gci-candidate
is for "held back" issues we're saving up.Weighting: some issues don't result in many lines of code, but are still big projects. Use tags
small
,medium
,big
when you'd like to help mark them (read more)Code: writing or refactoring
/comment/
to change to/comments/
-- issue at Remove redundant code #3339GCI dashboard
GCI dashboard
GCI dashboard
GCI dashboard
GCI dashboard
GCI dashboard
These can be moved up once they have code links or issue links:
needs-code-links
Preserve redirect to original destination when accessing/post
while not logged in (follow these steps: 1. publiclab.org/post You will be redirected to login page 2. Login 3. Redirected to dashboard -- Expected Behavior Redirected to /post.)/profile/status/_ID_
for auser
withid
of_ID_
, showing theuser.status
as one of these two SVGs: https://gist.github.com/jywarren/ea0523a09f6f8660486b14eeea15de95needs-code-links
Remove extra space at bottom of /postneeds-code-links
Removal of 1 horizontal lineneeds-code-links
Add generic video icon here, instead of being specific to YouTube. We should give equal priority to all the hosts. (https://github.com/publiclab/PublicLab.Editor/)target="_blank"
on the<a>
tag--
GCI dashboard
needs-code-links
Similar behaviour (needs to open on a new page) reported forOpen Source Your Work
link at https://publiclab.org/signup and /postneeds-code-links
Hover text should redirect to page listing all the wiki articles and research notes with textwater quality
needs-code-links
Hover text should redirect to page listing all the wiki articles and research notes with textballoon-mapping
needs-code-links
RedundantDashboard
in the drop down menu Remove Dashboard from the dropdown menu #3327needs-code-links
Clearly mention that on RHS we have Research notes.Liked by ____
appears ambiguous to me a lotneeds-code-links
sort wiki page likes according to date/timeneeds-code-links
If a person has no barnstars and they click on the nav bar. There must be a message to show them. Just to enhance the readabilityI will suggest that one post should be shown only once.
n
Wiki andm
Research Notes n Research notes & Wiki Edits #2193Error should also come that the fields are empty Sign-up Form Validation message correction #3340 --
GCI dashboard
see that url shows page 2 but the pagination is of page 1. (needs own issue)
needs-code-links
make tags inSuggested tags
on publiclab.org/post appear in tag input box when clicked - https://github.com/publiclab/PublicLab.Editor/Documentation/Training: creating/editing documents and helping others learn more
GCI dashboard
GCI dashboard
Outreach/Research: community management, marketing, or studying problems and recommending solutions
GCI dashboard
first-timers-only
issues (https://publiclab.org/n/13667) --GCI dashboard
fto-candidates
intofirst-timers-only
issues by embedding the friendly message which you can find infirst-timers-only
issues.fto-candidate
issues can be found at fto-candidateGCI dashboard
GCI dashborad
GCI dashboard
Quality Assurance: testing and ensuring code is of high quality
Show more
should change toShow less
on clicking -- GCI dashboardGCI dashboard
.Design: graphic design or user interface design
Hover Text Not working PublicLab.Editor#156
''Read More'' should be center aligned
notes:tagname
inline tag alternative to display a grid of notes, not a table #1097GCI dashboard
Looking for GSoC
Reviewing PRs and collaboration efforts will be judged in your upcoming GSoC proposals
If you are a GSoC'19 aspirant, then we need to tell you a good news. All the reviewing tasks will be judged in the upcoming GSoC'19 proposals. If you can review the PRs, help each other across issues, prs, create ftos and much more. Just commenting on the issues to help other folks is okay.
We will be having a special REVIEW/TEAMWORK section in the GSOC'19 proposal this summer.
All the best!!!
The text was updated successfully, but these errors were encountered: