I was thinking how to track diversity in our events. Then I thought that a question like gender was covered in the survey for newcomers. Then I thought whether we should align the questions of the survey with the questions to newcomers in events, or ask them to take the survey there right away.

Basically, consistency of information requested to newcomers online (surveys) and offline (events).

Helpful would be to get the following information for Wikimedia / Wikimania Hackathon 2017:

• No of newcomer sign ups
• From the sign ups, how many did we identify as newcomers
• From the ones we identified as newcomers, how many provided (or we managed to collect) Gerrit / Phabricator / Github username

Github username would help us only if someone has some concept how to track activity. I don't... :)

Anyone who has access to the "Vienna Newcomers: TC" GDoc and "Wikimania Hackathon Newcomers" GDoc could do that. From a quick look:

• Vienna 2017 No of newcomer sign ups: 40 lines
• Montreal 2017 No of newcomer sign ups: 77 lines

• From the ones we have some information available to track, how many contributed code before, during or after the event
  • Code activity (if any) of new developers from Wikimania hackathon since August and Wikimedia hackathon since May (similar to the table in T170495#3434359)

I started that in T175854.
If they contributed code a long time before, are they still newcomers? Or does that rather imply "do not consider them newcomers"?
How is "Code activity" defined exactly, as I cannot say "We saw 12 code activities"? Did you mean how many newcomers? How many code change proposals?

+1 on Quim's comment on consistency of offline vs online.

In T175886#3607524, @Aklapper wrote:

If they contributed code a long time before, are they still newcomers? Or does that rather imply "do not consider them newcomers"?

If they consider themselves as newcomers then yes.. iterating over the list if we end up identifying some as not then we rule them out.

How is "Code activity" defined exactly, as I cannot say "We saw 12 code activities"? Did you mean how many newcomers? How many code change proposals?

For the first report, for code activity, I was referring to code changes proposed. So rather than how many times code changes were proposed we measure whether or not there was a code change proposed ( we apply this equally to before, during and after the event)

+1 on Quim's comment on consistency of offline vs online.

+1

Good news - I believe I will be getting a list of "no-shows" for the Montreal hackathon in the next few days so we can makes sure we are not tracking people who did not arrive.
As long as I get this information by then I think we will have pretty accurate date for the number of newcomers that actually attended our last two hackathons.

@srishakatux: Could you clarify what else is wanted here / when this task is "resolved"?
Looking at the current task description:

• No of newcomer sign ups

(So far) We did not use that in the New Developers Quarterly Report and I don't see why we should.

• From the sign ups, how many did we identify as newcomers

We decided that in T176137#3661459 and have put those numbers into the New Developers Quarterly Report.

• From the ones we identified as newcomers, how many provided (or we managed to collect) Gerrit / Phabricator / Github username

Unclear underlying problem. (Note that for some folks I could find them via their email address or real names instead. Also see "disclaimer" in T163440#3663058.)

• From the ones we have some information available to track, how many contributed code before, during or after the event

Unclear underlying problem. For "the full calendar quarter after the quarter in which the event took place", see queries/numbers in T163440#3663058.

In T175886#3606979, @Qgil wrote:

Basically, consistency of information requested to newcomers online (surveys) and offline (events).

@Qgil: That could / should be a separate / dedicated task to potentially sync event registration forms with online survey forms, I'd say?

In T175886#3665707, @Aklapper wrote:

@srishakatux: Could you clarify what else is wanted here / when this task is "resolved"?

I don't think we need anything more here, what metrics we are showing for Outreach events in the report and the method we are following to obtain it is what we have agreed on gathering for the next report as well, anything additional in the task is no more useful.

Feel free to close this task!