Tue, Nov 19
It has no active users at the moment and has been broken for months. However, I would like to re-activate it for further reporting exploration and prototyping. It may now be possible to replace it with calls to the API (which didn't have all the necessary info and/or wasn't stable when the code was originally written), but that would be a significant refactor. If there's a quicker fix for the dump, it would be more helpful sooner to have the dump back.
Tue, Nov 12
Any suggestions on how to proceed? There is no specific deadline, but I would like to have some Phlogiston results for consideration in the next few weeks.
Oct 25 2019
Aug 22 2019
Wikimedia Foundation (https://wikimediafoundation.org/) → Technical Blog
Aug 21 2019
title, subtitle and description
Aug 20 2019
Jul 31 2019
passing to Greg for step 2, configuring the blog and vanity name.
Decide on a public pretty domainname for these more public/promoteable/cacheable tech blog posts (and if it's the legacy techblog.wikimedia.org instead of a fresh name, decide how we're handling historical redirects or whatever. (who's deciding, or was it decided?))
Jul 22 2019
a) didn't need Ariel; could run it myself
b) couldn't run it very easily due to officewiki config et al
c) fixed the problem manually
Jul 17 2019
Jul 1 2019
Jun 20 2019
Jun 18 2019
Jun 16 2019
sounds reasonable to me. Would it have to be both sub-projected and re-named to fully prevent conflict? Something like:
May 20 2019
I have a video of the bug, but this Phabricator instance won't take an upload. Is this appropriate for Commons?
May 1 2019
Works, thank you.
Apr 30 2019
Mar 28 2019
Mar 20 2019
Feb 7 2019
Dec 17 2018
Dec 16 2018
The new production server has been set up and is populating. The remaining server on eqiad, phlogiston-3, can be removed. All phlogiston services are running on eqiad1-r, and there is no possibility of data loss if phlogiston-3 is removed.
Dec 13 2018
Dec 5 2018
Dec 3 2018
Nov 26 2018
Status update: New Dev server has been set up; everything works except for a few R commands that perhaps have been deprecated or changed. They have been deprecated.
Nov 11 2018
Oct 25 2018
Oct 22 2018
Sep 27 2018
meanwhile I could kick off the report for you on dev so you don't have to wait for a resolution to access.
You can connect to other Cloud VPSes through the bastion?
- Try phlogiston-2.phlogiston.eqiad.wmflabs (because that's what's shown on https://tools.wmflabs.org/openstack-browser/project/phlogiston, although the phlogiston-2.eqiad.wmflabs version works for me)
Does your access work? If so, could you please close this task?
Sep 25 2018
Access is granted. Please let me know if you get stuck on gaps in the documentation.
Can you say more about what kind of report? Phlogiston can be complicated to work with; would you like to meet with me or @MBinder_WMF to discuss what you need and set it up together?
Sep 4 2018
Aug 24 2018
@MBinder_WMF this is one of the known, unfixed data quality bugs
Aug 14 2018
Tasks that are Done at the start of the status report and Done at the end of the status report are omitted (or else all resolved tasks would be on every status report). This includes tasks that are open in the middle of the report period but not the start or end.
Aug 9 2018
works on dev and prod.
Aug 8 2018
Categorize as Toolhub Milestone 2 all tasks that are:in project FY2018-19 and that are descendents of a task tagged Category whose title includes the text Toolhub Milestone 2
Is it safe to assume this is a unique data error? Not sure what else to do.
New board for FY19 milestones: https://phabricator.wikimedia.org/project/view/3256/
The first rule was catching everything, I think, and not leaving any tasks for the "Doing Test T174183" rule to operate on. I moved that rule (and the "Tracking" rule) higher, and it appears to work.
Aug 7 2018
Aug 6 2018
Jul 31 2018
Jul 30 2018
shrunk README to point to wiki instructions
Jul 27 2018
was handled at centralized level.
This is by design. There is a "last quarter" link that goes back 3 months further. See T175621: Phlogiston "show hidden" report should go back as far as possible for a feature request to address going back even further.