@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.

Thanks @Johan!

@JAllemandou Some update and questions on the reportupdater:

• The docs says: “The first column must be equal to start_date parameter (consider naming it date). This is an unnecessary limitation and might be removed in the future...”. Do I need to follow this?
• As the docs say that I should put all queries and scripts in a repo, I’ve it here along with a config.yaml file: https://github.com/srish/wmcs-edits. The script takes a start and end parameter right now and outputs a wmcs_edits.tsv file. I am not sure if this is sufficient for the reportupdater or I should try to generate the output in a different format. As we are going to anyways rely on the SQL query, maybe I should not spend too much time fixing the script at this point. I am guessing that when we use the SQL query, the config.yaml should be updated to include database information.
• I'm getting setup for writing SQL query to get the data via geoeditors_daily. For reference, I’m looking at: https://github.com/wikimedia/analytics-limn-ee-data/blob/master/ee-migration/daily_edits.sql and trying to run it via beeline -f daily_edits.sql > out.txt but I’m getting the following error and not sure what I am doing wrong here:

Error: Error while compiling statement: FAILED: ParseException line 3:18 cannot recognize input near 'AS' '{' 'wiki_db' in selection target (state=42000,code=40000)
org.apache.hive.service.cli.HiveSQLException: Error while compiling statement: FAILED: ParseException line 3:18 cannot recognize input near 'AS' '{' 'wiki_db' in selection target
	at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:241)
	at org.apache.hive.jdbc.Utils.verifySuccessWithInfo(Utils.java:227)
	at org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:255)
	at org.apache.hive.beeline.Commands.executeInternal(Commands.java:989)

@Milimetric @JAllemandou Hello! Thank you both for your help. This project is a learning project for me :) So, for the pieces that are feasible to do by the folks outside your team, I would love to give a shot at them. I might be a bit slow and reach out to you via IRC for questions if that is okay with you.
Perhaps setting the ReportUpdater (I have a task for it already here T232671), or configuration file that needs to be created on Meta for generating the dashboard.

Message for Tech News:

Announced:
https://lists.wikimedia.org/pipermail/wikitech-l/2019-October/092616.html
https://lists.wikimedia.org/pipermail/wikimedia-l/2019-October/093599.html
https://discuss-space.wmflabs.org/t/outreachy-round-19-contribution-period-is-now-open/1600
https://twitter.com/mediawiki/status/1179111104657575936
https://www.facebook.com/MediaWikiProject/posts/2474841352610565

(contribution period is now open)

(contribution period is now open)

(contribution period is now open)

(contribution period is now open)

(contribution period is now open)

(created https://www.mediawiki.org/wiki/Outreachy/Round_19)

(recruited 7 projects https://www.outreachy.org/communities/cfp/wikimedia/)

Yeah, storing aggregates makes more sense than storing data per wiki. I think that’s how we were gathering data in the past via the script. I got influenced by some of the other formats in analytics/datasets. I’ve dropped a new TSV file wmcs_edits.tsv in the /srv/published-datasets/wmcs directory, the data in it looks like as shown below. The data in it shows the edits from August 2019.

(moving this to 'Backlog' as this is Epic)

(we will make this project public on Oct 1 as per Outreachy's guidelines)

(we will make this project public on Oct 1 as per Outreachy's guidelines)

(we will make this project public on Oct 1 as per Outreachy's guidelines)

(we will make this project public on Oct 1 as per Outreachy's guidelines)

(we will make this project public on Oct 1 as per Outreachy's guidelines)

Thanks everyone for your help and sorry for the delay! I took some time understanding various pieces here :)
Here is an update and some questions:
I made small changes to Bryan's script and for now added two files enwiki.tsv and fawiki.tsv to /srv/published-datasets/wmcs directory. Both these files show one-day edit data for these two wikis, including the cloud edits with timestamps.

Link to the blog post on Wikimedia Space:
https://space.wmflabs.org/2019/09/24/round-up-of-small-wiki-toolkits-at-wikimania-2019/

Thank you @Pavithraes for coming up with this idea! We can promote this idea in the next round of Google-Summer-of-Code and Outreachy!

Here it is > https://meta.wikimedia.org/wiki/Small_wiki_toolkits

Script is here T226663#5287195

Projects we've got so far: T232816, T233243

@Nuria I want to read MySQL credentials from /etc/mysql/conf.d/research-client.cnf via a script that @bd808 wrote to analyze Toolforge/Cloud VPS usage on wikis. So, for that, I need membership in the "researchers" group.

Thanks @Aklapper! Reached out to all the mentors..

Here is the email I'm planning to send to all the mentors whose project is listed on the New Developers page: