Sat, Oct 17
Mon, Oct 12
Thu, Oct 8
Wed, Oct 7
Mon, Oct 5
maybe try using https://flask-sqlalchemy-session.readthedocs.io/en/v1.1/
or diy with https://flask-sqlalchemy-session.readthedocs.io/en/v1.1/
Fri, Oct 2
Thu, Oct 1
Sep 28 2020
Sep 25 2020
Sep 23 2020
@Envlh do you use a dockerize image of mysql 8, or install it from package, or use a general cli-installer?
Sep 22 2020
Sep 13 2020
remaining items here: https://docs.google.com/document/d/1aXaeyL6sTWYVAs6lrgAnC9N2bvYwB5OBsjDZp6rVnBs/edit
Sep 12 2020
Definite requirement: transform KPI table from long to wide
Definite requirement: updated schema
- Can you explain the KPI quadruple loop is to generate every possible metric, is that correct? https://framagit.org/wikimedia-france/denelezh-core/-/blob/master/scripts/import.php#L113
- Which parts are slow?
- Which parts are you unhappy with?
Sep 11 2020
Definite requirement: Backfiller
Whatever the future schema is, allow previous data from WHGI and Denelezh to be filled in retroactively.
Definite Requirement: include whgi-needed data
Sep 10 2020
Sep 8 2020
Sep 4 2020
@Aklapper this project is funded now, and has a new name 'humaniki' . Can you help me set-up a new tag or board to start tracking its progress? I'm not sure what level of organization is appropriate. I want to model out the technical development, as well as take user feedback, and bug reports. Thanks.
Dec 19 2019
I just got an alert that the disk space was at 100%.
Aug 26 2019
Thanks for writing. Yes, as you noticed there are many confounding factors. The original Teahouse paper showed a retention improvement of heuristics-vs-control, so that side is "proved" (although a replication would always be great). As for AI-vs-control (not AI-vs-heuristics), I did have a plan for how to do that. Since I was to invite no more than 150 users per day, I tried to tune the threshhold of the model to invite about 150 user per day, but on days that had more positives than that I gave those users the status "overflow", that is would-be-invited. I planned to use theses as a control for AI-vs-control. I see that I had 4,281 overflows and 8,223 invited, so I'm hoping we will have enough statistical power.
Aug 18 2019
- create draft domain schema
@Envlh and I decided to make a roadmap for a "new" tool that would combine the best features of our 2 tools, and make a common platform to de-duplicate engineering effort.
Aug 9 2019
Jun 26 2019
Jun 25 2019
Jun 24 2019
Thank you for reporting @kai.nissen . Yes I will take a look. This is not WMDE problem. The essence of what happened was that I cloned the WMDE-fundraising-style "at the very top" banner, but at the last moment some central-notice admins on Meta did not want that very bold style, so I converted the CSS to be in the standard banner position. This banner's run ends in 12 hours. So won't push a fix in time, but for the next civilservant banner we will fix. Thanks for your attention everyone and especially @Tacsipacsi for uploading screenshots.
Jun 23 2019
Jun 7 2019
Am I correct in thinking that CentralNotice banners that are displayed organically, that is not via the &banner= url parameter, will not give the CSP error? Otherwise this probably would have popped up sooner, right?
I find the CSP error happening diferently on different language Wikis. Errors on
May 16 2019
Thank you @Andrew !
Apr 28 2019
Hello @Krenair ,
Thanks for your response:
Apr 25 2019
Hello @bd808 , I would prefer to get the VPS if possible. The reason being is that our stack is built on top of mysql8, and I'm not sure what issues lie ahead with using the Maria-DB per-tool instances . Our stack was built 2-years ago without toolforge compatibility in mind. I appreciate your response that it would be possible to run toolforge, and was going to roll-up my sleeves to try just that, until I saw your response about approval in the WMCS meeting. Here is another argument I would make for needing the VPS: (A) if our experiment is successful ("does nudged-thanking improve editor retention and performance?") then we would convert the experimental software to be a tool that would run for all users, which definitely need lots of disk for cacheing, probably necessitating a VPS. Otherwise, if (B) the experiment is not successful we would just spin down the VPS anyway.