User Details
- User Since
- Nov 1 2021, 4:22 PM (223 w, 8 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- CMelo (WMF) [ Global Accounts ]
Yesterday
3 new charts added to this superset dashboard:
https://superset.wikimedia.org/superset/dashboard/615/?native_filters_key=iypqHB0qc3wbsB7Qyhuc7NzJ1H-LisSyJlhKDNguYGvGnJhZus47UupX4IG5K_Q0
Tue, Feb 3
Mon, Feb 2
Sun, Feb 1
Thu, Jan 29
Tue, Jan 27
Decisions made about the proposals:
Thu, Jan 22
ceeg_event BIGINT UNSIGNED NOT NULL, -- References campaign_events.event_id
Shouldn't it be ceeg_event_id, as it is for other tables like: ce_event_wikis -> ceew_event_id, ce_event_topics -> ceet_event_id
Wed, Jan 21
Yes, make sense thanks @JFernandez-WMF and @Daimona
+1 to what Daimona said, and:
Dec 18 2025
I see, I suppose something like that would work, although it looks very complex. Maybe it would be possible to simplify by putting all goals in disjunctive normal form (for example), so we don't have to store operators; it still looks quite complex, but maybe that's just me not having a clear enough picture.
Hi @Daimona I will move it to product sign-off, thanks for looking into it.
Dec 16 2025
We decided in today’s meeting to leave it as it is. This means that if the user has only one contribution to delete and deletes it, we will not automatically remove the “Actions” column. However, it will no longer be visible after refreshing the page if there are no contributions left to delete, which is the current status quo.
Dec 12 2025
Done, but for
Priority 3: Breakdown of association methods (i.e., number of post-publication adds, manual adds, manual removes) - may or may not be possible - we can look and see
- To get the number of post-publication adds, manual adds, is not possible because there is no way to differentiate them.
How would that work? For example, how would it represent the JSON blob I put as an example in T407028#11402480?
Thanks @vaughnwalters and @Daimona, I was able to reproduce it now, I created a patch to fix it, will move this task to code review
The investigation looks good to me, thanks @MHorsey-WMF
Dec 10 2025
Thanks for the detailed analysis — this all sounds good. I just have one concern regarding the JSON blob approach. Because of the limitations you mentioned, I would prefer *not* to store goals as JSON blob data.
Dec 9 2025
Nov 19 2025
Nov 18 2025
Nov 17 2025
We do need a database change: event-specific opt-out can’t rely on global user preferences because they only store fixed per-user keys, not per-event state. To persist “don’t show the post-edit modal for this event” we have to extend CampaignEvents data, e.g. add a boolean field like cep_hide_post_edit_modal to ce_participants. That keeps the flag scoped to each participant/event pair and lets us query/update it alongside other participant metadata.
Nov 14 2025
Nov 13 2025
Nov 12 2025
I did some tests on having more than one pagination in the same special page, I created a POC, and sounds to work, so I would like your feedback to see if it could be a possible implementation.
Nov 11 2025
Hi @vaughnwalters, I have tested it on the maser branch, and I was not able to reproduce it anymore, I think this was fixed in some of the other tasks we did, let me know if you can still reproduce it, thank you!
Just as a note, we decided that the max per page limit will be changed from 50 to 500.
cc: @ifried
Nov 7 2025
Nov 5 2025
Hi @ifried I added a tooltip for when the user mouse over the trash icon, I just added it to the AC, and would like to confirm with you if this is ok.
What I added to the AC was:
- And the icon has a tooltip with the message "Remove contribution" on mouse over
Nov 4 2025
Oct 31 2025
Oct 30 2025
Hi @ifried ,
Following up on our backlog refinement discussion where we decided to set the pagination limit to 50 for now, due to performance issues:


