Change Details

**Type of activity:** Unconference Session **Main topic:** https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Useful,_consistent,_and_well_documented_APIs == The problem == People tracking the generation of dumps of all sorts for our wiki projects must either screenscrape https://dumps.wikimedia.org/backup-index.html, check the dumpsruninfo.txt file in the directory for the dump of the particular wiki on the given date, or, in the case of other sorts of dumps, check directory listings via the web to see what's going on. With the rewrite of the dumps, we have the opportunity to include a monitoring/stats API from the start of the design. == Expected outcome == * List requirements for a monitoring/stats API for all forms of dumps; what do users need? * Review internal WMF projects that may have code or data we can reuse * Discuss and compile a list of third-party software that could be adapted for our use * Put together a roadmap of timetable/tasks for implementation for use with the Dumps 1.0 (current infrastructure) == Current status of the discussion == Starting it now. Note that I can't dedicate coding time to this now as I am working on another piece of the rewrite this quarter. == Links == * This task is part of T128755 scheduled for work during the quarter Jan-Mar 2017.

==Session title== An API for monitoring dumps of WMF wikis ==Main topic== [[ https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Useful,_consistent,_and_well_documented_APIs | Useful, consistent, and well documented APIs ]] ==Type of activity== Unconference Session ==Description== %%% === 1. The problem === People tracking the generation of dumps of all sorts for our wiki projects must either screenscrape https://dumps.wikimedia.org/backup-index.html, check the dumpsruninfo.txt file in the directory for the dump of the particular wiki on the given date, or, in the case of other sorts of dumps, check directory listings via the web to see what's going on. With the rewrite of the dumps, we have the opportunity to include a monitoring/stats API from the start of the design. === 2. Expected outcome === * List requirements for a monitoring/stats API for all forms of dumps; what do users need? * Review internal WMF projects that may have code or data we can reuse * Discuss and compile a list of third-party software that could be adapted for our use * Put together a roadmap of timetable/tasks for implementation for use with the Dumps 1.0 (current infrastructure) === 3. Current status of the discussion === Starting it now. Note that I can't dedicate coding time to this now as I am working on another piece of the rewrite this quarter. === 4. Links === * This task is part of T128755 scheduled for work during the quarter Jan-Mar 2017. ==Proposed by== [[ https://www.mediawiki.org/wiki/User:ArielGlenn | Ariel Glenn ]] ==Preferred group size== The more the merrier ==Supplies needed== An easel with white paper or a whiteboard, with markers ==Interested attendees (sign up below)== # Add your name here

**Type of activity:**==Session title== An API for monitoring dumps of WMF wikis ==Main topic== [[ https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Useful,_consistent,_and_well_documented_APIs | Useful, consistent, and well documented APIs ]] ==Type of activity== Unconference Session **Main topic:**==Description== https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Useful,_consistent,_and_well_documented_APIs%%% ===== 1. The problem ===== People tracking the generation of dumps of all sorts for our wiki projects must either screenscrape https://dumps.wikimedia.org/backup-index.html, check the dumpsruninfo.txt file in the directory for the dump of the particular wiki on the given date, or, in the case of other sorts of dumps, check directory listings via the web to see what's going on. With the rewrite of the dumps, we have the opportunity to include a monitoring/stats API from the start of the design. == === 2. Expected outcome ===== * List requirements for a monitoring/stats API for all forms of dumps; what do users need? * Review internal WMF projects that may have code or data we can reuse * Discuss and compile a list of third-party software that could be adapted for our use * Put together a roadmap of timetable/tasks for implementation for use with the Dumps 1.0 (current infrastructure) === 3. Current status of the discussion == === Starting it now. Note that I can't dedicate coding time to this now as I am working on another piece of the rewrite this quarter. ===== 4. Links == = * This task is part of T128755 scheduled for work during the quarter Jan-Mar 2017. ==Proposed by== [[ https://www.mediawiki.org/wiki/User:ArielGlenn | Ariel Glenn ]] ==Preferred group size== The more the merrier ==Supplies needed== An easel with white paper or a whiteboard, with markers ==Interested attendees (sign up below)== # Add your name here