(not sure we need these statistics in the near future so I'm declining this task)

(not sure we need these statistics in the near future so I'm declining this task)

Detailed notes

Ahha, I see! So may be then, we should display the date in the queries as YYYY-MM and for that change SELECT $1 .... to SELECT substr('$1', 1, 7) everywhere. Perhaps, filenames could be:

@mforns So, I see data corresponding to two dates: 2019-11-01 and 2019-10-01 meaning for the month of September and October only and we are missing for November right now.

@mforns Thanks a lot for making all the changes and sorry for causing trouble :) I just refreshed the dashboard with new data and all looks good to me except one thing that we don't see the November data in the query results. Is there a reason for it?

@Aklapper I'm willing to co-mentor this task with @Apap04! I think this task can be about updating documentation on existing tools on that page, and researching for new tools and adding their information as well. I think we can remove the conclusion part from the task as different tools serve different purpose, so asking to suggest one tool may not make sense. I can help import the task on the GCI site!

@Aklapper thanks for pointing that, I've made minor changes in both venues :) Take a look and if you are happy with the description, please help publish the task!

@mforns @JAllemandou when will I see the files in here https://analytics.wikimedia.org/published/datasets/periodic/reports/metrics/wmcs/? I see there is one already there, not sure if I added it.

@Urbanecm I currently see this task marked as "MORE DETAIL REQUIRED" on the GCI site. Could you share more what is missing?

Thanks @JAllemandou! I've changed the table name in the queries and made the changes to the patch. I've also tested the queries with the new table. It looks good to me :) For the record, here is the comparison now between data via Bryan's script and hive queries for the month of November:

Updated https://www.mediawiki.org/wiki/Outreachy/Round_19#Recommended_steps_for_accepted_interns and sent the email below to all our accepted interns:

Hello ...,
Greetings! First of all congratulations on getting accepted to the Outreachy program with Wikimedia :)
Next, we have prepared a list of recommended steps for you to consider between now and the internship period kick-off. Though these steps are not mandatory, once the internship period starts, we would expect from you to:

• Write bi-weekly reports
• Stay up-to-date with your goals as outlined in the timeline
• Communicate regularly with mentors and keep them updated on your progress and challenges
• Submit evaluations on time
• Attend any program-related meetings we host
• Follow any guidelines we share to involve you in our community and process

Wikimedia administrators will be using Zulip to share announcements and opportunities for participating in various Wikimedia activities. We will use the #outreachy19 stream for all communications.
Although we hope this never happens, if, for some reason, you feel like there is a problem between you and your mentor, please contact me directly on Zulip via @Srishti Sethi.
We’re so proud of your contributions to our community so far, welcome aboard, and wish you a pleasant time working with Wikimedia!
Cheers,
Srishti

@JAllemandou this is perfect! :) Let me know when I can query the new data from the table (or if there is a test table that I can play with), I will then modify this patch accordingly.

@JAllemandou WOW! I'm guessing that the edits in different cuc_type categories are all mutually exclusive, assuming that if I add the different cuc_type edits for a wiki, I get a number very close to Bryan's. Not sure what 142 category is, it is not in here https://www.mediawiki.org/wiki/Manual:Recentchanges_table#rc_type. I don't have a strong opinion on whether or not we should report the remaining cuc_type to the table, what are your thoughts? Do you want me to check with someone from the Cloud Services team on this?

Imported here https://codein.withgoogle.com/dashboard/tasks/5294456337596416/.

Imported here https://codein.withgoogle.com/dashboard/tasks/6309589708963840/

Imported here https://codein.withgoogle.com/dashboard/tasks/6039185547329536/

Thanks, @JAllemandou, for recognizing the missing piece in the data! The plan sounds good to me. Looking at the possible rc_type, my interpretation is that we would need the data unfiltered as all the fields in there seems relevant. But, Bryan may have been able to say more on this and he is currently on a very long vacation :(

Imported here https://codein.withgoogle.com/dashboard/tasks/5704741141610496/

@mforns Thanks! I've made minor changes in response to the code review to the queries. Also, rounding off the percent to 3 decimals now in all the queries which also resolves the issue with exponential values.

(there is nothing more left to do here)

(thanks @Milimetric for the ping on this! )

@mforns @JAllemandou Would it be possible for one of you to review the patch and give feedback? I've made the necessary changes to the scripts to adhere to the data format here that we are using for the first version of the dashboard: https://wmcs-edits.wmflabs.org

Talked with IndicTechCom + CIS (India) today! They are very much interested in coordinating the workshop sometime in April. The next steps would be finalizing dates/venue and funding process to follow. Also, to talk with technical contributors from the region and do some research to understand their needs that would help us develop the workshop curriculum.

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Thanks for creating a proposal! As we are past the deadline, if you would like us to consider your proposal for review, please move it to the submitted column. Thank you!

Developer-Advocacy Hi team - here we have the first version of the dashboard: https://wmcs-edits.wmflabs.org with help from Analytics folks :)

Here it is https://wmcs-edits.wmflabs.org with help from @Milimetric :)

This was very helpful! I put three different files each for a separate view here https://analytics.wikimedia.org/published/datasets/periodic/reports/metrics/sri-test/, and I'm happy with the dashboard dashiki gives with this data: For example, the timeseries view looks like:

Update > I have the config here https://meta.wikimedia.org/wiki/Config:Dashiki:WMCSEdits, and I can use it to generate a dashboard with the layout of type tabs and some not-so-accurate/old data locally.
Out of three views (hierarchical, dygraphs-timeseries, and tabular), I am only able to get the tabular one working as of now. For dygraphs-timeseries, I am guessing that the data format needs to be something like in all_sites_by_os_family_percent.tsv here https://analytics.wikimedia.org/published/datasets/periodic/reports/metrics/browser/ (wikis in columns and not in rows)? Is that right, or is there any workaround for this?

Thank you both for your helpful reply! We discussed the two possible layouts in our meeting and agreed that:

• Ratios/percentages are what we would like to visualize, particularly the % of edits across all wikis monthly.
• If not all for all wikis, definitely for wikidata, enwiki, dewiki, commons and others that we see as indicators of general trends (to begin with).

Met with the Wikimedia Amical project coordinator for an initial meeting. We discussed the goals of the workshop and logistics. They think that conducting a technical workshop will be a good idea, and they will be sharing it with the rest of the group members in the next monthly meeting. Soon after the meeting, sometime in early December, they will follow-up with us for the next steps.

@Milimetric I looked into the supported layouts and visualization a bit https://wikitech.wikimedia.org/wiki/Analytics/Tutorials/Dashboards#Supported_layouts_and_visualizations. It seems to me that the most relevant layout for wmcs visualization would be the metrics-by-project layout like in https://analytics.wikimedia.org/dashboards/vital-signs or https://page-creation.wmflabs.org.

@srodlund will be coordinating/leading/planning this session and I will be one of the participants of this session.

( the recent changes should have fixed this problem, also available for quick review here: https://github.com/wikimedia/labs-tools-gerrit-newcomer-bot/commit/c36ed4a4e32317c75c9ed5edbc5a39ec20618e54)

@mforns for the documentation sake, I've filed this task :) You can share related updates here.

@bd808 The bot is working fine! So that means explicitly calling the venv's python3: exec ${VENV}/bin/python3 watch_newcomers.py was the key here. Do we consider this issue as resolved then?

I am currently investigating the possibility of running the workshops with/for:

• Indic-TechCom
• Wikimedia Amical
• Africa Wikimedia Developers Project
• Wikimedia Asia Oceania project
• Wiki Movement Brazil User Group

(to coordinate with @srodlund)

Sent the email to Wikitech-I asking for new projects for New Developers guide https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092662.html.

@Anomie Is there anything remaining to be addressed before the patch opened by @jeropbrenda to address this issue can be merged?

(thanks to @jeropbrenda for working on the API overview pages as part of Outreachy internship! )

@jeropbrenda could this task be a microtask or part of the Outreachy project T232816? What do you think?

Thank you @JAllemandou and @mforns for your helpful reply :)

@matmarex this happens if you first go into source editing mode and then switch back to visual editing without making any changes.