Page MenuHomePhabricator

gonyeahialam (Gregory)
Senior UX Designer

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Saturday

  • Clear sailing ahead.

User Details

User Since
Sep 2 2021, 7:54 AM (118 w, 6 h)
Availability
Available
LDAP User
Unknown
MediaWiki User
GOnyeahialam (WMF) [ Global Accounts ]

Recent Activity

Today

gonyeahialam updated the task description for T352972: Investigate No JS implementation of a multi-step form.
Thu, Dec 7, 10:55 AM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam created T352972: Investigate No JS implementation of a multi-step form.
Thu, Dec 7, 10:54 AM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration

Mon, Dec 4

gonyeahialam added a comment to T322209: Organizers choose what information they need from participants.

The Questions for Participant section is collapsed by default because it's optional and can make the form look longer than necessary. Plus, as we add more questions, it could become the longest section in the form. An optional section shouldn't make the overall form appear more complex to users. Meeting a long-form makes users overwhelmed and discouraged from completing it.

Mon, Dec 4, 7:23 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration

Fri, Dec 1

gonyeahialam added a comment to T322209: Organizers choose what information they need from participants.
  1. Open the accordion

TTBOMK, individual form sections cannot be made collapsible; only the whole form can be made collapsible.

Fri, Dec 1, 11:48 AM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration

Thu, Nov 30

gonyeahialam added a comment to T322209: Organizers choose what information they need from participants.

Design Progress Update

Thu, Nov 30, 4:20 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam edited projects for T322209: Organizers choose what information they need from participants, added: Campaigns-Design, Campaign-Tools (Campaign-Tools-Current-Sprint); removed Campaign-Tools.
Thu, Nov 30, 3:18 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration

Fri, Nov 24

gonyeahialam added a comment to T322209: Organizers choose what information they need from participants.

Hello @gonyeahialam, I have discussed this ticket with some members of the team, and I have decided that this is a high-priority design task to work on. This is because I think this would be a very useful feature for organizers, since some organizers would not want to ask any questions (or some of the questions) to their participants. In that case, could you add this ticket into your work for this week and beyond to develop some designs to determine how we could handle a scenario in which the organizer can pick which questions are a part of the event registration form? I see that there is also a design file link in this ticket, but I'm not sure if any work has already been done. Curious to hear your thoughts; thanks!

Fri, Nov 24, 5:53 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration

Mon, Nov 20

gonyeahialam moved T343449: Add columns for non PII data on the participants tab from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Mon, Nov 20, 10:15 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.30; 2023-10-10), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Thu, Nov 16

gonyeahialam moved T346956: create the listener for the hook to add the input field from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Thu, Nov 16, 2:26 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), WikimediaCampaignEvents, Campaign-Registration

Wed, Nov 15

gonyeahialam attached a referenced file: F41507894: image.png.
Wed, Nov 15, 3:34 PM · Campaign-Registration
gonyeahialam updated the task description for T351315: Change CTA button label of EditEventRegistration page from 'Edit registration' to 'Save changes'.
Wed, Nov 15, 2:58 PM · Campaign-Registration
gonyeahialam created T351315: Change CTA button label of EditEventRegistration page from 'Edit registration' to 'Save changes'.
Wed, Nov 15, 2:43 PM · Campaign-Registration

Thu, Nov 9

gonyeahialam moved T350027: Show grant ID on Special:EventDetails for organizers from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Thu, Nov 9, 2:10 PM · MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaign-Tools (Campaign-Tools-Current-Sprint), WikimediaCampaignEvents, CampaignEvents, Campaign-Registration

Wed, Nov 8

gonyeahialam added a comment to T340115: [clickwrap] Clickwrap Agreement prompt for organisers.
  1. For the copy, go with the copy in the build.
Wed, Nov 8, 9:04 AM · Patch-For-Review, MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaigns-Design, Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Nov 2 2023

gonyeahialam moved T339979: Implement restriction of not being able to change the end date of events that have already ended from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Nov 2 2023, 10:48 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam moved T346845: Delete and Message participant button alignment and spacing issue from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Nov 2 2023, 10:34 AM · MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Oct 26 2023

gonyeahialam moved T346329: Update visibility rules of aggregated participant responses from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Oct 26 2023, 1:42 PM · MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam moved T349217: Disable autofocus for tab panels in Special:EventDetails from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Oct 26 2023, 1:40 PM · MW-1.42-notes (1.42.0-wmf.3; 2023-10-31), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam updated the task description for T321814: EPIC: Add Grant ID support to event registration.
Oct 26 2023, 1:35 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T346968: [EPIC] Feature Improvements to Email Participants.

UI Task in order of priority

Oct 26 2023, 12:53 PM · CampaignEvents, Campaign-Tools, Campaign-Registration

Oct 24 2023

gonyeahialam added a comment to T334761: Clickwrap Agreement.

@gonyeahialam Hello! It looks like this task is the same as T340115 at this point (in terms of the AC). I can close it, correct?

Oct 24 2023, 5:58 PM · User-Iflorez, Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T349650: Number of "No response" options in the statistics can become meaningless if participants unregister after aggregation.

@Daimona If the number of participants who answered the affiliate question or the number of responses, 20 yes 20 no, don't change after people cancel their registration, why can't we leave the 'No responses' value the same after registrations are canceled?

Oct 24 2023, 5:50 PM · Campaign-Registration, CampaignEvents, Campaign-Tools

Oct 20 2023

gonyeahialam added a comment to T348779: [EPIC] Event Invitations.

Current iteration on Event Invitation - Mobile web (Work in progress)

Oct 20 2023, 4:31 PM · Event-Discovery
gonyeahialam added a comment to T349013: For any range that starts from zero, use "Less than X".

@Daimona what do you think of using 'Less than or equal to X' for the No responses scenario you described?

Oct 20 2023, 2:53 PM · Campaign-Tools, CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T349013: For any range that starts from zero, use "Less than X".

@Daimona my recommendation was for only numbers not percentages. So we can use Less than X for numbers only

Oct 20 2023, 2:12 PM · Campaign-Tools, CampaignEvents, Campaign-Registration

Oct 19 2023

gonyeahialam closed T349209: Event invitation design exploration as Invalid.
Oct 19 2023, 3:13 PM · Campaigns-Design, Event-Discovery
gonyeahialam added a comment to T348779: [EPIC] Event Invitations.

Latest design exploration on event invitation
@ifried
Constraining ourselves to the character length limit and normal functionality of echo notifications. The echo notification could look like this:

Oct 19 2023, 3:12 PM · Event-Discovery
gonyeahialam added a comment to T348779: [EPIC] Event Invitations.

2b. For events using the Event registration tool
Event Invitations within the Event registration tool

Screen Recording 2023-10-19 at 15.46.36.gif (563×960 px, 240 KB)

Oct 19 2023, 2:52 PM · Event-Discovery
gonyeahialam added a comment to T348779: [EPIC] Event Invitations.

Design explorations

Oct 19 2023, 2:44 PM · Event-Discovery
gonyeahialam moved T345353: Participants tab - notify organisers of data retention policy from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Oct 19 2023, 2:43 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T348779: [EPIC] Event Invitations.

Design exploration

Oct 19 2023, 12:33 PM · Event-Discovery

Oct 18 2023

gonyeahialam added a comment to T345353: Participants tab - notify organisers of data retention policy.

@Daimona yes

Oct 18 2023, 1:38 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam created T349209: Event invitation design exploration.
Oct 18 2023, 1:37 PM · Campaigns-Design, Event-Discovery
gonyeahialam added a project to T346626: Event Discovery Research: Campaigns-Design.
Oct 18 2023, 1:36 PM · Campaigns-Design, Event-Discovery
gonyeahialam added a comment to T340115: [clickwrap] Clickwrap Agreement prompt for organisers.

@ifried The message here is Wikimedia specific "In accordance with the Wikimedia foundation's terms of use", we will need a generic version.

Oct 18 2023, 1:35 PM · Patch-For-Review, MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaigns-Design, Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T348338: Make the two sections in the Enable Registration form to be in a single rectangle.

@Daimona In the future, the form may become longer and will need to be further broken down into more sections. It would be cluttered to have many such rectangles. We can explore this at that time or if another need requires it.

Oct 18 2023, 10:00 AM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T345353: Participants tab - notify organisers of data retention policy.

Data retention information icon is in focus (see outline around the element) any time the user clicks on the Participants tab from another tab

That's the default behaviour in OOUI where it auto-focuses the first clickable element of each tab when you select that tab. We can disable that if we want to.

Oct 18 2023, 9:50 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam moved T347587: Display original data collection text if and only if Participant Questions not enabled from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Oct 18 2023, 9:02 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents

Oct 17 2023

gonyeahialam added a comment to T348338: Make the two sections in the Enable Registration form to be in a single rectangle.

That's how the standard form sectioning works, each section is put inside those rectangles. We could have a rectangle for the whole form, but that's only available when the form itself has a legend, which it doesn't in this case.

Is this task blocking the release?

Oct 17 2023, 2:04 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam attached a referenced file: F37933904: Screenshot 2023-10-03 at 12.45.14 PM.png.
Oct 17 2023, 2:02 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam attached a referenced file: F37933915: Screen Recording 2023-10-03 at 1.05.26 PM.gif.
Oct 17 2023, 2:01 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T340115: [clickwrap] Clickwrap Agreement prompt for organisers.

@ifried The message here is Wikimedia specific "In accordance with the Wikimedia foundation's terms of use", we will need a generic version.

@MHorsey-WMF What terms of use will the generic version be linked to since the one currently linked is Wikimedia's?

@gonyeahialam The text is inconsistent with regular styling, the light grey is usually reserved for disabled text or help text. can we agree that it will not be grey and instead the standard black?

The color I am using is the color for subtle text #54595D/Gray600/Base 20. The disabled color is #72777D/Gray500/Base30. But since this text is for an action and clickable you can go ahead to use the standard black (#202122/Gray700/Base10) so it is not confused as disabled.

Oct 17 2023, 1:58 PM · Patch-For-Review, MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaigns-Design, Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Oct 13 2023

gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

@gonyeahialam: I have updated the copy for grant ID based on the fact that we will be asking for numbers only. Here is my suggestion; what do you think?

"If this program or event is supported by a grant from the Wikimedia Foundation, please provide your Grant ID, which you can find in the Grantee Portal (Fluxx).
Please enter the numbers and dashes in your grant ID, but exclude the letters. For example, if your grant ID is G-1111-1111, please enter 1111-1111."

Oct 13 2023, 5:57 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T346329: Update visibility rules of aggregated participant responses.

Yes @ifried @vaughnwalters I agree we should follow the same format. I mentioned it above in T346329#9188346:

Any range, whether it is for the options or 'No response' that starts from zero as in <5 or 0 ≤ x ≤ 8 we use Less than 5, Less than 9(or whatever the number is)
If the lower range is above zero as in 8 ≤ x ≤ 16 we use Between 8 and 16

Oct 13 2023, 5:52 PM · MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T340115: [clickwrap] Clickwrap Agreement prompt for organisers.

@gonyeahialam The AC says that this will appear when enabling registration, but does not specify if it should appear when EDITING registration. If the organiser does not accept the agreement initially, should it show on the edit form for them?

Oct 13 2023, 2:53 PM · Patch-For-Review, MW-1.42-notes (1.42.0-wmf.4; 2023-11-07), Campaigns-Design, Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Oct 10 2023

gonyeahialam closed T346627: Event Discovery Survey as Resolved.
Oct 10 2023, 10:58 AM · Event-Discovery
gonyeahialam closed T346627: Event Discovery Survey, a subtask of T346626: Event Discovery Research, as Resolved.
Oct 10 2023, 10:58 AM · Campaigns-Design, Event-Discovery
gonyeahialam updated the task description for T346627: Event Discovery Survey.
Oct 10 2023, 10:56 AM · Event-Discovery
gonyeahialam moved T347065: Release the email participants feature from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Oct 10 2023, 10:53 AM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam closed T346628: Event Discovery Comparative Analysis as Resolved.
Oct 10 2023, 10:20 AM · Event-Discovery
gonyeahialam closed T346628: Event Discovery Comparative Analysis, a subtask of T346627: Event Discovery Survey, as Resolved.
Oct 10 2023, 10:20 AM · Event-Discovery
gonyeahialam updated subscribers of T346628: Event Discovery Comparative Analysis.
Oct 10 2023, 10:18 AM · Event-Discovery
gonyeahialam updated the task description for T346628: Event Discovery Comparative Analysis.
Oct 10 2023, 10:17 AM · Event-Discovery

Oct 9 2023

gonyeahialam added a comment to T347065: Release the email participants feature.

I don't know if you have already identified it but I think I may have found a bug. @vaughnwalters
What happens when an organizer tries to send a message of less than 10 characters? @Daimona

Oct 9 2023, 6:37 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam updated the task description for T321814: EPIC: Add Grant ID support to event registration.
Oct 9 2023, 4:38 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

image.png (899×1 px, 145 KB)

Oct 9 2023, 4:34 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

Okay, update :) I spoke with @cmelo and it is a very small amount of work to allow organizers to provide the full grant ID, so we will not require the organizer to add only the last 8 digits. This means the designs can stay the same and the organizers can add in the full grant ID. cc @gonyeahialam and @Rmaung

Oct 9 2023, 4:33 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

@ifried
We would need to modify the description/helper text above to clearly inform organizers to only input the numbers.
If organizers are not used to using the numbers alone, the chances of the organizers making mistakes will increase

Oct 9 2023, 3:26 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T347065: Release the email participants feature.

@vaughnwalters
Is "Event details: Sandbox/VWalters..." the email subject?

Oct 9 2023, 12:55 PM · Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

Hi @ifried and @gonyeahialam I would like to check with you on the grant ID format we will ask the organizer to provide, for what I saw in the designs on the tasks, it says:

e.g. G-RF-1201-3302

But I remember we mention that we would be asking only the digits, so it would be only:
e.g. 1201-3302

So I am wondering if we will really be asking the full grant ID, if we do, we will need to update T346956 AC, also it adds a small complexity on the code which is make a regex to remove the "G-RF-" before sending it to be validated, because the API only accept the digits like "1201-3302"

Oct 9 2023, 12:17 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration

Oct 6 2023

gonyeahialam moved T339978: Inform organizers about the data retention policy for participant questions from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.

@Daimona Can't the two sections be inside a single rectangle/border, instead of rectangles around each section?

That's how the standard form sectioning works, each section is put inside those rectangles. We could have a rectangle for the whole form, but that's only available when the form itself has a legend, which it doesn't in this case.

Oct 6 2023, 5:36 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam created T348338: Make the two sections in the Enable Registration form to be in a single rectangle.
Oct 6 2023, 5:34 PM · CampaignEvents, Campaign-Tools, Campaign-Registration

Oct 4 2023

gonyeahialam added a comment to T339978: Inform organizers about the data retention policy for participant questions.

@vaughnwalters Can I see the screenshot of the full form?

@gonyeahialam I had to zoom out to see the whole form but here it all is together.

Screenshot 2023-10-03 at 12.45.14 PM.png (1×2 px, 295 KB)

and here's a gif of it:

Screen Recording 2023-10-03 at 1.05.26 PM.gif (1×3 px, 2 MB)

Oct 4 2023, 10:40 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

On this meta page for grants you can view the icons currently used-- I think it would make sense to mirror the one used for the grantee portal ("Add ltr") but if that presents an issue I think the star would be a safe choice.

Oct 4 2023, 10:34 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration

Oct 3 2023

gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

I am working on adding Grant ID to event details but I am a bit stuck on finding the most appropriate logo. @ifried would like your feedback on the logo.

Event details tab.png (899×1 px, 113 KB)

Oct 3 2023, 6:04 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T339978: Inform organizers about the data retention policy for participant questions.
Oct 3 2023, 5:39 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam updated the task description for T321814: EPIC: Add Grant ID support to event registration.
Oct 3 2023, 9:20 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam updated the task description for T339979: Implement restriction of not being able to change the end date of events that have already ended.
Oct 3 2023, 9:17 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

I think this text is confusing, since "past" and "future" are not defined: "Past event dates cannot be changed to future dates to protect participant data." We can rewrite it to something like: "The event has ended, so you cannot change the event dates to future dates. This restriction protects participant data." This is lengthier, but perhaps more helpful in actually conveying the behavior to organizers. What do you all think? Curious to hear other opinions, especially from @gonyeahialam.

Oct 3 2023, 9:11 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T343449: Add columns for non PII data on the participants tab.

@cmelo 80vh is good.

Oct 3 2023, 8:56 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.30; 2023-10-10), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Sep 28 2023

gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

@ifried Does the last AC "The grant ID should not be displayed in the event page user interface. It should only be viewable in the organizer view when configuring or editing registration." also mean that the GrantID wouldn't show up in the organizer view of the event details page?

Sep 28 2023, 8:40 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam updated the task description for T321814: EPIC: Add Grant ID support to event registration.
Sep 28 2023, 8:31 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

I have updated the design to include the correct format of the grant ID as a placeholder text in the form field "e.g. G-RF-1201-3302". @ifried Can the acceptance criteria be updated to include this?

Sep 28 2023, 8:30 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration

Sep 25 2023

gonyeahialam added a comment to T322332: Participants can provide optional PII info when registering for an event (MVP).

@gonyeahialam: This task can be closed, right?

Sep 25 2023, 9:07 AM · Campaigns-Design, CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

@ifried what is the reason for this AC "The grant ID information should be entered as freeform text"? Does the GrantID have a fixed format?

Sep 25 2023, 9:04 AM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T346329: Update visibility rules of aggregated participant responses.

Also one more thing, which could maybe be addressed in a follow-up task. "less than 5" is not capitalised as per T336855. Instead, "Between X and Y" is capitalised. I think we should be consistent here. (I would personally vote for capitalising everything, but I don't feel strongly about it; what I do feel strongly about is consistency).

Sep 25 2023, 8:53 AM · MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents

Sep 22 2023

gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

@ifried
The error message due to the Flux API ('There was an issue with validating the grant ID. Please try again later.') isn't clear enough on the next steps for the user. Should they pause filling it and come back later to try again? Do they clear the field, submit the form, and come back to edit it and see if the ID goes through? This can leave the user frustrated.
A better message might be:
There was an issue with validating your Grant ID. You can try submitting the form again in a few minutes. If the issue persists, you can still submit the form without a Grant ID and add it later by editing the event details.

Screenshot 2023-09-22 at 19.01.19.png (728×1 px, 131 KB)
This gives options on how the user can proceed

Sep 22 2023, 6:04 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T321814: EPIC: Add Grant ID support to event registration.

Yes. it can be the last field in the Event details section of the form. I can work on it next.

Sep 22 2023, 5:12 PM · WikimediaCampaignEvents, CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@Daimona The predefined error message shows when you submit the form and not when the field turns red immediately after you enter a future date.

Yes, you're right, and I think showing the message immediately could be a potential improvement for MW core's date widget. However, given that:

  • We already have an error message showing (after you submit the form)
  • You already see a notice informing you that future dates cannot be selected
  • You have to enter the date manually for this scenario to happen
  • The field turns red
  • It may not be easy to turn the notice into an error

Could we just leave it as a notice for now, to keep things simpler?

Also, the pre-defined error message is for when you input an earlier date. I don't think there is one for when you input a future date

There is one:

image.png (159×1 px, 29 KB)

Sep 22 2023, 4:06 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents

Sep 21 2023

gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@Daimona The predefined error message shows when you submit the form and not when the field turns red immediately after you enter a future date.
Also, the pre-defined error message is for when you input an earlier date. I don't think there is one for when you input a future date

Sep 21 2023, 4:33 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T346329: Update visibility rules of aggregated participant responses.
Sep 21 2023, 4:25 PM · MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T346329: Update visibility rules of aggregated participant responses.

Thank you so much, @Htriedman! It's great to hear that you like this idea, so we'll go ahead and implement it. We really appreciate your help on this topic!

And @Daimona, thank you for thinking this through & coming up with a new idea!

As a next step, @gonyeahialam, do you have a recommendation for the best way to represent the range (such as 8 ≤ x ≤ 16 in the example shared above)?

Sep 21 2023, 4:16 PM · MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@Daimona suggests we disable future dates in the calendar picker instead and show a notice message explaining why always. This prevents the user from making the error in the first place.

My question is: If the user enters the dates directly without using the calendar picker what happens?
Perhaps we turn the notice into an error message.

In that case, the field outline becomes red. If you try and submit the form, you get a predefined error message. This can be tested on beta by manually entering a date in the past (the only difference is in the wording of the error message when the date is in the past vs future). I'm not sure if we would be able to replace the predefined error message in this scenario. Maybe we could have our notice remain a notice, in addition to the predefined error?

Sep 21 2023, 3:51 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents

Sep 20 2023

gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@Daimona suggests we disable future dates in the calendar picker instead and show a notice message explaining why always. This prevents the user from making the error in the first place.

Sep 20 2023, 1:53 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@Daimona suggests we disable future dates in the calendar picker instead and show a notice message explaining why always. This prevents the user from making the error in the first place.

Sep 20 2023, 1:47 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T346848: Validation / decrementing counter when approaching maximum characters in Message tab.

Decision(Design/Eng Meeting): Remove the limit from the message body and keep 200 character limit on the subject

Sep 20 2023, 1:45 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam moved T326619: Implement participant selection logic and interface from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Sep 20 2023, 8:28 AM · MW-1.41-notes (1.41.0-wmf.26; 2023-09-12), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam moved T326413: Implement front end module for participant email, compatible with current tab layout from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.

Since separate tickets have been created for the changes, I am moving this to product sign-off.

Sep 20 2023, 8:27 AM · MW-1.41-notes (1.41.0-wmf.22; 2023-08-15), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

Yeah, I hear you, @gonyeahialam. I was basically trying to do a few things to improve the sentence, which were:

  • change from "can't" to "cannot" (since "can't" is a bit informal)
  • change from "the future" to "future date," since I thought it was a bit more clear
  • change "ensure participant data safety" to "protect participant data" since I found it a bit more accurate & clear

Do you agree with any of the choices I made above?

If yes, what do you think of this rewritten version (see below)?:

"Past event dates cannot be changed to future dates to protect participant data."

Sep 20 2023, 8:23 AM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents

Sep 19 2023

gonyeahialam added a comment to T345200: "Organized by" and "Timezone" text in the more details dialog should match the design.

Also, the title in the build says Multiple organisers, the title is supposed to be the event name

In F37097121, "Multiple organizers" is literally the name of the event.

Sep 19 2023, 1:46 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam updated the task description for T345200: "Organized by" and "Timezone" text in the more details dialog should match the design.
Sep 19 2023, 12:21 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam added a comment to T345200: "Organized by" and "Timezone" text in the more details dialog should match the design.

Also, the title in the build says Multiple organisers, the title is supposed to be the event name

Sep 19 2023, 12:20 PM · CampaignEvents, Campaign-Tools, Campaign-Registration
gonyeahialam moved T345310: Improvements for "has email" column in EventDetails from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Sep 19 2023, 10:01 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaign-Registration, CampaignEvents
gonyeahialam added a comment to T326619: Implement participant selection logic and interface.

The AC in this task is met, but there are a few UI issues, and if these should go in another ticket I can make that instead:

  1. The search bar is in a different place now than where it is in the comp. Is this intentional?

The build is correct. This page was updated for the Participant questions feature/tasks.

  1. The Message participants button should be disabled (gray button) if the organizer does not have an email. The tool tip copy is correct, but right now it is on click of the button - @gonyeahialam can you clarify if this tooltip should appear on click or on hover of the disabled button?
compbuild
Screenshot 2023-03-17 at 11.53.53.png (2×3 px, 385 KB)
Screenshot 2023-09-18 at 7.39.34 PM.png (760×1 px, 119 KB)

If we leave the button disabled then the tooltip will only show on hover. However, we can leave it as it is in the build where the button isn't disabled and the tooltip shows on click.

  1. The To message participants... warning should go above the Recipients / Add recipients button
compbuild
image.png (1×2 px, 134 KB)
Screenshot 2023-09-18 at 7.45.31 PM.png (1×1 px, 155 KB)

Yes, it is above. The warning is a central warning for the whole page.

  1. The Delete and Message participants buttons have a slight vertical alignment issue. When inspecting it you can see where it is off:
Screenshot 2023-09-18 at 9.05.09 PM.png (96×570 px, 13 KB)
Screenshot 2023-09-18 at 8.56.59 PM.png (104×594 px, 15 KB)
  1. The Delete button and the Message Participants button should not have any space between the buttons.
compbuild
Screenshot 2023-09-18 at 9.03.35 PM.png (100×652 px, 23 KB)
Screenshot 2023-09-18 at 9.05.09 PM.png (96×570 px, 13 KB)

Yes, the buttons are together, the component is called a ButtonGroupWidget (destructive and progressive ButtonWidget)

Sep 19 2023, 9:56 AM · MW-1.41-notes (1.41.0-wmf.26; 2023-09-12), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam moved T336855: [IMPLEMENTATION] Front end: Show aggregate data to organizers after the event is over from Design Sign-Off 🖌️ to Product Sign-Off on the Campaign-Tools (Campaign-Tools-Current-Sprint) board.
Sep 19 2023, 8:53 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration

Sep 18 2023

gonyeahialam added a comment to T336855: [IMPLEMENTATION] Front end: Show aggregate data to organizers after the event is over.

Looks good, passing this back to design sign off:

Screenshot 2023-09-18 at 12.01.18 PM.png (300×1 px, 47 KB)

Sep 18 2023, 5:51 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Campaign-Tools (Campaign-Tools-Current-Sprint), CampaignEvents, Campaign-Registration
gonyeahialam added a comment to T339979: Implement restriction of not being able to change the end date of events that have already ended.

@gonyeahialam & @cmelo, what do you think of the following update to the copy (see below). Do you think it's a bit more clear to readers? Let me know what you think!

"Past event dates cannot be updated to a future date in order to protect participant data."

Sep 18 2023, 4:51 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam updated the task description for T339979: Implement restriction of not being able to change the end date of events that have already ended.
Sep 18 2023, 12:18 PM · MW-1.42-notes (1.42.0-wmf.2; 2023-10-24), MW-1.41-notes (1.41.0-wmf.29; 2023-10-03), Campaign-Tools (Campaign-Tools-Current-Sprint), Campaigns-Design, Campaign-Registration, CampaignEvents
gonyeahialam created T346628: Event Discovery Comparative Analysis.
Sep 18 2023, 12:01 PM · Event-Discovery
gonyeahialam created T346627: Event Discovery Survey.
Sep 18 2023, 11:59 AM · Event-Discovery