Plots2: Weekly Community Check-In #3 - "Achievements"

This week I will be redesigning the /stats page and also finishing up on #4317.

The UI open-hour made me happy, meeting all the amazing people and having a peep at how people use the website.
I love the new design that @edieblu is working on :fire:.
Every pull request that I make that gets merged makes me happy too :smiley:
Thanks

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.
Also in the remaining week, I am planning to research more on #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!

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 <[email protected]
wrote:

This week I am planning to complete the email verification feature #3798
https://github.com/publiclab/plots2/issues/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
https://github.com/publiclab/plots2/issues/3851 and #3853
https://github.com/publiclab/plots2/issues/3853) this week.
Also in the remaining week, I am planning to research more on #4362
https://github.com/publiclab/plots2/issues/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
https://github.com/publiclab/plots2/issues/4476#issuecomment-450629611,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUACQyReuXk50xX2dDiGx9RBp5J0l4lLks5u-eWJgaJpZM4ZlQ8g
.

Please checkout https://publiclab.org/notes/warren/01-02-2019/public-lab-code-community-report-jan-2019#c21606

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 :smile: .

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:

https://github.com/publiclab/plots2/pull/2857

This would complete the deprecation of our very old DrupalUsers table and unify it completely with the newer Users table -- one more step towards a cleaner and more maintainable and readable codebase! 🎉

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 https://github.com/publiclab/plots2/issues/2720, and in one new issue https://github.com/publiclab/plots2/issues/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 https://github.com/publiclab/plots2/issues/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: https://github.com/publiclab/plots2/issues/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: https://github.com/publiclab/plots2/issues/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 notifications@github.com 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
https://github.com/publiclab/plots2/issues/1890

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/4476#issuecomment-451268846,
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 jeff@unterbahn.com 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 notifications@github.com 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
https://github.com/publiclab/plots2/issues/1890

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/publiclab/plots2/issues/4476#issuecomment-451268846,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABfJ1ekDmEgaWUENehieburTBgyuXb-ks5u_mlvgaJpZM4ZlQ8g
.

Nice idea @jywarren :100:

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
[survey respondents]/[all possible respondents]

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 notifications@github.com 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
https://github.com/publiclab/plots2/issues/4476#issuecomment-451275259,
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 :sweat_smile:

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
[] Native Hawaiian or other Pacific Islander
[] American Indian or Alaska Native
[] Asian
[] Hispanic or Latino
[] Black, African, or African American
[] White or Caucasian
[] Prefer not to say

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?
() Yes
() No

With which racial background(s) do you identify? (check all that apply)
[] Asian
[] Black
[] Latino
[] Native American
[] Pacific Islander
[] White
[] Self Identify: _________________
[] Prefer not to answer

Also a lot more discussion at https://github.com/drnikki/open-demographics/issues/14

And this addition (the above you link to is pretty old but hasn't been updated with input from https://github.com/drnikki/open-demographics/issues/14, unfortunately):

Do you identify yourself as a member of a minority group in the area you live?

@emmairwin suggesting:

Do you identify yourself as a member of a minority racial, ethnicity or tribal group in the area you live?

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 - https://github.com/publiclab/plots2/issues/4476#issuecomment-450953816 and ebarry's comment - https://github.com/publiclab/plots2/issues/4476#issuecomment-451268846.

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 notifications@github.com
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)
https://github.com/publiclab/plots2/issues/4476#issuecomment-450953816
and ebarry's comment - #4476 (comment)
https://github.com/publiclab/plots2/issues/4476#issuecomment-451268846.

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
https://github.com/publiclab/plots2/issues/4476#issuecomment-451639832,
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 :smile: )
In this case, an "audience" means the people who are reading your blog posts. They may not have all the skills or knowledge that you do. You might share some skills, but they may not be familar with your community. They could be free software contributors or they could be newcomers.

@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
Thanks for giving the opportunity

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!