Weekly Community Check-In #3 - "Achievements" #4476
Comments
cesswairimu
added
outreach
|
This week I will be redesigning the The UI open-hour made me happy, meeting all the amazing people and having a peep at how people use the website. |
|
This week I am planning to complete the email verification feature #3798 that I had started working upon along with @Radhikadua123 . This issue consisted a total of 7 sub issues out which 4 have been completed and their PR's have been merged. One of the issues has a PR made and is under review, while the remaining 2 need to be implemented. So I plan to solve these two issues(#3851 and #3853) this week. Initially I was not aware of such a community check in that happens in plots2. I think planning your tasks ahead in the week is a very good idea! Kudos to this great idea of week check ins! Thank you so much! |
|
Hi everyone.
This week I will be working on the remaining issues of OAuth with Oorjit,
Isha, Kunal, Kevin, Dina, Rishabh, and many more.
We have achieved login and signup through modals and their linking
theoughout the website this December.
Cess thanks for the theme of this week.
Thanks everyone.
…On Mon, Dec 31, 2018, 3:53 PM Shubham Sangamnerkar ***@***.*** wrote:
This week I am planning to complete the email verification feature #3798
<#3798> that I had started
working upon along with @Radhikadua123 <https://github.com/Radhikadua123>
. This issue consisted a total of 7 sub issues out which 4 have been
completed and their PR's have been merged. One of the issues has a PR made
and is under review, while the remaining 2 need to be implemented. So I
plan to solve these two issues(#3851
<#3851> and #3853
<#3853>) this week.
Also in the remaining week, I am planning to research more on #4362
<#4362> regarding what else can
be done to speedup things.
Initially I was not aware of such a community check in that happens in
plots2. I think planning your tasks ahead in the week is a very good idea!
Kudos to this great idea of week check ins!
Thank you so much!
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#4476 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQyReuXk50xX2dDiGx9RBp5J0l4lLks5u-eWJgaJpZM4ZlQ8g>
.
|
|
Hi everyone, I would be completing the Comment moderation system this week #3331. Thanks to Valentina for her work during GCI on this project, only some parts are remaining now 😄 . Thank you! |
|
I wanted to share that I managed to get a VERY long-running issue to pass all tests last night! It may not be 100% ready but we're testing it on the unstable server now: This would complete the deprecation of our very old Thanks Cess for a great theme!!! |
|
Happy New Year! Today i used my refreshed brain to revisit the Tagging and Topics Milestone: https://github.com/publiclab/plots2/milestone/13 In a comment on an existing issue #2720, and in one new issue #4500, i suggest we begin getting more use out of the great "Search By Tag" interface that is currently only on the Questions page :) Also on tagging, i'm excited to see this issue #3482 get solved which would remove the powertags from the display on https://publiclab.org/tags I have asked for help locating the relevant lines of code for this issue: #3246 Thanks all! |
|
Hi, all, round 2! I've kicked off a brainstorming post for the ideas page for Summer of Code 2019 - it's early but I thought we'd best get some ideas into discussion ahead of time. People have been brainstorming already - let's do it together! https://publiclab.org/notes/warren/01-02-2019/brainstorming-for-summer-of-code-2019 Not every project would be chosen, nor attract a student to work on it, but this will let us discuss, compare, critique ideas and then develop a smaller final list. Thanks everyone! |
|
hi all, I'm wondering if i could hear some thoughts from you (if you are reading this, this means you!) about when during 2019 will be a good time to run a Software Contributors Survey? We did this the year before last, and would like to do it again. Here is where we first discussed the idea in October 2017: https://publiclab.org/questions/warren/10-25-2017/help-with-a-standard-mini-evaluation-for-assessing-software-outreach-efforts Here's the survey as sent out on December 14, 2017: #1890 |
|
Hi @ebarry I would say right now(in a week) because contributors are very active now-a-days. Also, we could get feedback of GCI students. Thanks! |
|
We'd really love to do this survey in part because I believe we have a very
diverse community, and we work hard to welcome people in. But we can't
clearly measure that we are succeeding in either (welcoming or diversity)
without a strong response to a survey (last time was great but only 17 ppl
i think responded, so not very comprehensive). Thanks Liz!
…On Thu, Jan 3, 2019 at 3:35 PM Liz Barry ***@***.***> wrote:
hi all, I'm wondering if i could hear some thoughts from you (if you are
reading this, this means you!) about *when during 2019 will be a good
time to run a Software Contributors Survey?* We did this the year before
last, and would like to do it again.
Here is where we first discussed the idea in October 2017:
https://publiclab.org/questions/warren/10-25-2017/help-with-a-standard-mini-evaluation-for-assessing-software-outreach-efforts
Here's the survey as sent out on December 14, 2017: #1890
<#1890>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4476 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ1ekDmEgaWUENehieburTBgyuXb-ks5u_mlvgaJpZM4ZlQ8g>
.
|
|
during the survey open period, we could also include it in the Welcomebot's
"congratulations" message when a PR is merged, and in other places for high
visibility. We didn't have these systems last time!
…On Thu, Jan 3, 2019 at 3:41 PM Jeffrey Warren ***@***.***> wrote:
We'd really love to do this survey in part because I believe we have a
very diverse community, and we work hard to welcome people in. But we can't
clearly measure that we are succeeding in either (welcoming or diversity)
without a strong response to a survey (last time was great but only 17 ppl
i think responded, so not very comprehensive). Thanks Liz!
On Thu, Jan 3, 2019 at 3:35 PM Liz Barry ***@***.***> wrote:
> hi all, I'm wondering if i could hear some thoughts from you (if you are
> reading this, this means you!) about *when during 2019 will be a good
> time to run a Software Contributors Survey?* We did this the year before
> last, and would like to do it again.
>
> Here is where we first discussed the idea in October 2017:
> https://publiclab.org/questions/warren/10-25-2017/help-with-a-standard-mini-evaluation-for-assessing-software-outreach-efforts
>
> Here's the survey as sent out on December 14, 2017: #1890
> <#1890>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#4476 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AABfJ1ekDmEgaWUENehieburTBgyuXb-ks5u_mlvgaJpZM4ZlQ8g>
> .
>
|
|
Nice idea @jywarren 💯 |
|
Ok, so far i hear @gauravano 's idea to do it next week. Any other ideas for timing? I guess "a good time" would mean "a time when we could get a lot of respondents". We will also have to set the duration of when the survey is available, for instance two weeks. (Could be shorter or longer). Once the survey period is completed, we will describe the results as |
|
Would we want to update the demographic sections (which remain old
US-centric categories) with the latest from
https://github.com/drnikki/open-demographics ?
I'd also set a longer period esp to get maximum impact from our welcomebot
reminders. We could aim for the period of SoC 2019 organizing? That is
coming up real fast. Or we could do a 2 month period maybe to start sooner
and let it overlap that period? Is that too long?
…On Thu, Jan 3, 2019 at 3:59 PM Liz Barry ***@***.***> wrote:
Ok, so far i hear @gauravano <https://github.com/gauravano> 's idea to do
it next week. Any other ideas for timing? I guess "a good time" would mean
"a time when we could get a lot of respondents". We will also have to set
the duration of when the survey is available, for instance two weeks.
(Could be shorter or longer).
Once the survey period is completed, we will describe the results as
[survey respondents]/[all possible respondents]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4476 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ3DefZ4gk_tFPhioiNf_bf0q0qgcks5u_m8mgaJpZM4ZlQ8g>
.
|
|
If we want to get lot of responses, then another suitable time is after GSoC orgs are announced 😅 |
|
haha but maybe the people arriving after GSoC orgs are announced have not had enough experience with Public Lab to have meaningful feedback? or maybe they will? For demographics/race, currently our in-person surveys are phrased this way: [] Multiracial or multiethnic https://drnikki.github.io/open-demographics/questions/race.html employs two separate questions. Also, they list that "in order to make this question relevant globally, we need to either include different categories, or separate callouts for indigenous people." Note the categories on the second one: Do you identify as a person of color? With which racial background(s) do you identify? (check all that apply) |
|
Also a lot more discussion at drnikki/open-demographics#14 And this addition (the above you link to is pretty old but hasn't been updated with input from drnikki/open-demographics#14, unfortunately):
@emmairwin suggesting:
|
|
Nice Idea. I am in favour of 2 month surveys as Jeff told instead of 2 weeks time period. |
|
Hi @coderjolly you showed interest in opening check-in last week. Just reminding you to open the check-in on Sunday evening or Monday morning. Also, please copy the @jywarren's comment - #4476 (comment) and ebarry's comment - #4476 (comment). Don't forget to acknowledge this message to avoid any confusion. Thanks! |
|
Dont forget to make a checklist of the people you did community check ins
(Gaurav, me, Cess and you) so that each person can get a chance to do it it.
…On Sat, Jan 5, 2019 at 2:37 PM Gaurav Sachdeva ***@***.***> wrote:
Hi @coderjolly <https://github.com/CoderJolly> you showed interest in
opening check-in last week. Just reminding you to open the check-in on
Sunday evening or Monday morning. Also, please copy the @jywarren
<https://github.com/jywarren>'s comment - #4476 (comment)
<#4476 (comment)>
and ebarry's comment - #4476 (comment)
<#4476 (comment)>.
Don't forget to acknowledge this message to avoid any confusion. Thanks!
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#4476 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUACQwXhLbVyNnBEPN3V2BZ0DtSiJVPsks5vAGs9gaJpZM4ZlQ8g>
.
|
|
@gauravano Sure, jst let me know what all I hv to do in order to open a check-in and what is its process or may be someone else can do it dis time so that I can see how its done for the next |
|
You can copy this issue's body and make changes like - changing theme, adding name of new contributors, adding above comments which I have pointed and any other additions you feel relevant and important. You can keep the theme for next week - "Think About Your Audience". (Copying Outreachy's theme 😄 ) |
|
@coderjolly open the check-in and I would update it, if required. Thanks! |
|
Moved to #4548 |
|
Thanks @coderjolly |
|
I am going to add these things too in a few minutes @SidharthBansal @gauravano
|
Hi everyone 👋 !
We all at Public Lab 🎈 - learn, grow, work, brainstorm ideas, contribute together so why not share about our weekly goals and the awesome work we have done at Public Lab with each other, so we can support and collaborate with each other better. Let's start a Community Check-In from this week onwards, where every community member would share something about their work from the past week and about their current week's goal 🎯. You are also welcome to share fun-fact 😄 , new ideas 💡 , your learning goals ☑️ .
If you're new here, welcome 🎈 , and please comment a Hello message below, we love to work with you. If you're looking for new issues, please try some of our first-timers-only issues.
We're SO EXCITED to have your help!
Is there anything, you would like to share with us from past week's work? What is your plan for this week?
If you have not planned yet, just leave a Hello! so that we know that you are in sync with us 🔃 and doing well!
As always, if you're waiting for a review, or if you're stuck, please request help here OR leave a comment with @publiclab/mentors @publiclab/reviewers for some input. 🙌
This week's theme.
This being the last week of this year/first week of 2019, I thought we can share some good moments and achievements we have had on project and the community at large in addition to our weekly updates on what we will be working on. It does not necessarily have to be something that you did but it can also be a feature that was added on the project that made you happy 😸
Happy new year everyone!!! ⚡ 🎆 🎉 🎈 🎉
cc
@thesparks @faithngetich @DakshGondaliya @mohitRJranjan @milaaraujo @kevinzluo
@stefannibrasil @gauravano @ViditChitkara @tech4GT @mridulnagpal @namangupta01 @sagarpreet-chadha @Souravirus @jywarren @MayankKashyap @siaw23 @ryzokuken @ccpandhare @icarito @steviepubliclab @ebarry @jywarren, @sagarpreet-chadha, @icarito, @JonathanXu1, @uzorjchibuzor, @eli6, @kevinzluo, @ValentinaTironi, @rexagod, @sashadev-sky, @IshaGupta18, @milaaraujo, @dinaelhanan, @cesswairimu, @dependabot[bot], @oorjitchowdhary, @okonek, @wanzulfikri, @mohitRJranjan @publiclab/mentors @publiclab/image-sequencer-guides @publiclab/leaflet-environmental-layers-guides @Paarmita @vishalka98 @publiclab/reviewers @Divy123 @pomyo @bhavayAnand9 @ovipa017-xamk @Mridul97 @avsingh999 @Rishabh570 @subhahu123 @asquare14 @Radhikadua123 @quinn-codes-synthesis @amychan331 @mardelvalle @narnt @hydro-m @love-opensource @romanrodriguez @shubhangi-chauhan @Dhiraj240 @geekychaser @codeIriss @CoderJolly .
Thanks 😄
The text was updated successfully, but these errors were encountered: