Talk:Campaigns/Foundation Product Team/Registration

From Meta, a Wikimedia project coordination wiki
← Previous Discussions Join Discussions More Status Updates →

December 2022: Release to Meta-Wiki, Feedback Request, and Office Hours[edit]

Pinging people who responded in Englishː @Din-nani1, Bobbyshabangu, Gilbert Ndihokubwayo, Alhassan Mohammed Awal, Owula kpakpo, Eric Luth (WMSE), White Orchid27, Kaffzz, Tochiprecious, Ruby D-Brown, Bachounda, T Cells, Nemo bis, Econterms, Lea Lacroix (WMDE), Esam Idris, Owula kpakpo, Ariel Cetrone (WMDC), Hogü-456, Kunokuno, OtuNwachinemere, Raggachampiongirl, Olaniyan Olushola, Pablísima, Hogü-456, Effeietsanders, Sj, Ата and Adélaïde Calais WMFr --IFried (WMF) (talk) 14:44, 5 December 2022 (UTC)Reply[reply]

Thank you @IFried (WMF), I'll attend on the 10th. Well-done on the great efforts so far. Tochiprecious (talk) 08:25, 7 December 2022 (UTC)Reply[reply]
@Tochiprecious Thank you for the kind words, and we look forward to seeing you at the office hour on the 10thǃ IFried (WMF) (talk) 21:33, 7 December 2022 (UTC)Reply[reply]

Hello, everyone! We have enabled the CampaignEvents extension Meta-Wiki, and we are now requesting feedback. You can share feedback on this talk page (we have added questions below), with an online survey, or by reaching out to any of the team members directly. Thank you, and we look forward to your feedback!

Additionally, we have upcoming office hours, which are scheduled for today and Saturday, where we wil be demoing the tool. We hope to see some of you at the office hours! If you are already on our subscription list, you will have already received an invitation to the office hours. Thank you!

@Galahmm, Adoscam, Bile rene, Modjou, Mndetatsin,, CapitainAfrika, and VALENTIN NVJ --IFried (WMF) (talk) 14:55, 5 December 2022 (UTC)Reply[reply]

Hello IFried, can you link to the landing page for the extension? Where is it made visible to Meta users? –SJ talk  07:46, 6 December 2022 (UTC)Reply[reply]
Hello @Sjǃ Hello, and thanks for the question. Regarding the landing page of the extension, do you mean this page on Regarding access to the tool on Meta-Wikiː There is the organizer side and the participant side. The organizer side is available to people who are a part of the CampaignEvents beta testers user group (which is a small group meant for an early test phase of the tool). You can see who is currently a part of the group on the V1 summary page. Right now, it's mostly Campaigns team members since we are currently conducting outreach (via office hours, a feedback form, etc) to see who wants to be a tester among volunteers. To request to join the group, you can let us know on the project talk page, V1 feedback form, or by reaching out to any Campaigns team members directly. The participant side is available to anyone on Meta-wiki who joins an event created by the test organizers. IFried (WMF) (talk) 21:32, 7 December 2022 (UTC)Reply[reply]
IFried (WMF) where might I find a list of created events? I don't know how to find anything to give feedback on. –SJ talk  22:59, 7 December 2022 (UTC)Reply[reply]
Hello @Sjǃ I don't believe any actual event pages with registration enabled have been created with the tool on Meta-Wiki yet. You can see all pages created in the Event namespace on Meta-Wiki here. I see you created a test event page, but you would need to have the organizer right to enable registration on it (let us know if this interests you). There are also some sandbox test pages that have been created, such as this page, along with test event pages created on testwiki. If it's helpful, we can add a list of some actual events that have used the event registration tool on Meta-Wiki on the V1 Summary page after they have been created. We expect people to begin creating actual event pages in the next few weeks to months, but it probably won't be immediate since someone will need to have a real event that they want to conceptualize and organize (which may take some time). We had our first office hour to demo the tool this past Monday, and we'll have our second on Saturday. After the office hours are complete, we'll be determining who wants to be a part of the beta tester user group for organizers, and then we can begin seeing some of the test events (which we can all observe, provide feedback on, etc). In the meantime, we recommend that folks check out test event pages on testwiki (which can be found by searching for pages in the Event namespace). Thanksǃ IFried (WMF) (talk) 14:20, 8 December 2022 (UTC)Reply[reply]

Bonjour à tous! Nous avons activé l'extension CampaignEvents Meta-Wiki, et nous demandons maintenant des commentaires. Vous pouvez partager vos commentaires sur cette page de discussion (nous avons ajouté des questions ci-dessous), avec un sondage en ligne ou en contactant directement l'un des membres de l'équipe. Merci, et nous attendons vos commentaires avec impatience!

De plus, nous avons des heures de bureau à venir, qui sont prévues pour aujourd'hui et samedi, où nous ferons la démonstration de l'outil. Nous espérons voir certains d'entre vous aux heures de bureau! Si vous êtes déjà sur notre liste d'abonnement, vous aurez déjà reçu une invitation aux heures de bureau. Merci!

What Wikimedia chapters, affiliates, or user groups are you a part of, if any?[edit]

FR: De quels chapitres, affiliés ou groupes d'utilisateurs de Wikimedia faites-vous partie, le cas échéant ? SW: Je, wewe ni sehemu ya Shirika lipi la Wikimedia, washirika au vikundi vya watumiaji, kama vipo? AR: ما هي فصول ويكيميديا​، الجهات الشقيقة، أو مجموعات المستخدمين التي تنتمون إليها، إن وُجِدت؟

Greetings, admin. I am a member of the Tyap Wikimedians User Group. Kambai Akau (talk) 12:04, 4 October 2023 (UTC)Reply[reply]

What Wikimedia events do you typically organize each year?[edit]

FR: Quels sont les événements Wikimedia que vous organisez habituellement chaque année ? SW: Ni matukio gani ya Wikimedia huwa unaandaa kila mwaka? AR: ما هي فعاليات ويكيميديا ​​التي تنظمونها عادة كل عام؟

Do you want to be a test organizer and use the event registration tool in a real event on Meta-Wiki that you organize? If yes, please let us know in the section below![edit]

FR: Voulez-vous être un.e organisateur.trice test et utiliser l'outil d'inscription aux événements dans un événement réel sur Meta-Wiki que vous organisez ? Si oui, faites-le nous savoir dans la section ci-dessous ! SW: Je, ungependa kuwa muandaaji wa majaribio na kutumia zana ya usajili wa tukio katika tukio halisi kwenye Meta-Wiki ambalo unaandaa? Ikiwa ndio, tafadhali tujulishe katika sehemu iliyo hapa chini! AR: هل ترغبون أن تكونوا منظمين للاختبار وأن تستخدمو أداة تسجيل الفعالية في تنظيم فعالية حقيقية على ميتا ويكي؟ إذا كانت الإجابة بنعم ، يرجى إخبارنا بذلك في القسم أدناه!

Greetingsǃ I would like to be a test organizer and use the event registration tool in an event we are currently planning coming up soon. Kambai Akau (talk) 12:00, 4 October 2023 (UTC)Reply[reply]

If you answered “yes” to the last question, do you want any help from our team with creating or managing your event? If yes, what would you want help with, exactly? If you don’t know yet, that is also okay![edit]

FR: Si vous avez répondu "oui" à la dernière question, souhaitez-vous que notre équipe vous aide à créer ou à gérer votre événement ? Dans l'affirmative, pourquoi voulez-vous de l'aide, exactement ? Si vous ne savez pas encore, c'est également possible ! SW: Ikiwa ulijibu "ndiyo" kwa swali lililopita, je, unahitaji msaada wowote kutoka kwenye timu yetu kuhusu kuundaa au kuratibu tukio lako? Ikiwa ndio, ungetaka msaada wa nini hasa? Ikiwa bado hujui, hiyo pia ni sawa! AR: . إذا أجبتم بـ "نعم" على السؤال الأخير، هل تريدون أي مساعدة من فريقنا في إنشاء أو إدارة الفعالية الخاصة بكم؟ إذا كانت الإجابة بنعم، فما المساعدة التي تريدونها، بالضبط؟ إذا كنتم لا تعرفون، فلا بأس بذلك أيضًا!

Do you think this event registration system will improve your workflows and processes, as an event organizer? Why or why not?[edit]

FR: Pensez-vous que ce système d'inscription aux événements améliorera vos flux de travail et vos processus, en tant qu'organisateur.trice d'événements ? Pourquoi ou pourquoi pas ? SW: Je, unafikiri mfumo huu wa usajili wa matukio utaboresha utendakazi na michakato yako, kama mratibu wa tukio? Kwa nini ndiyo au kwa nini hapana? AR: هل تعتقدون أن نظام تسجيل الفعاليات هذا سيحسن سير العمل والعمليات لديكم، بصفتكم منظمين للفعاليات والحملات؟ لِما و لِما لا؟

Do you think you are more likely to organize events in the future, if you have the event registration tool? Why or why not? If not, what other tools would you need to be more likely to organize events?[edit]

FR: Pensez-vous être plus susceptible d'organiser des événements à l'avenir, si vous disposez de l'outil d'inscription aux événements ? Pourquoi ou pourquoi pas ? Si non, de quels autres outils auriez-vous besoin pour être plus enclin à organiser des événements ? SW: Je, unafikiri kuna uwezekano mkubwa wa kupanga matukio katika siku zijazo, ikiwa una zana ya usajili wa matukio? Kwa nini ndiyo au kwa nini hapana? Ikiwa sivyo, ni zana gani nyingine ungehitaji ili uwe na uwezo zaidi wa kuandaa matukio? AR: هل تعتقدون أنه من المرجّح أن تنظمون فعاليات مستقبلا، إذا كانت لديكم صلاحيات أداة تسجيل الفعاليات؟ لِما ولِما لا؟ إذا لم يكن الأمر كذلك، ما هي الأدوات الأخرى التي تحتاجونها لتكونوا فاعلين أكثر في تنظيم الفعاليات؟

What is your favorite thing about the event registration tool? Why do you like it?[edit]

FR: Qu'est-ce que vous préférez dans l'outil d'inscription aux événements ? Pourquoi l'aimez-vous ? SW: Ni jambo gani unalopenda zaidi kuhusu zana ya usajili wa tukio? Kwa nini unaipenda? AR: ما هو الشيء المفضل لديكم في أداة التسجيل في الفعاليات؟ لماذا أعجبتكم؟

How can we improve the event registration tool? What features or changes would you like to see in a later version of the tool?[edit]

FR: Comment pouvons-nous améliorer l'outil d'inscription aux événements ? Quelles fonctionnalités ou modifications souhaiteriez-vous voir apparaître dans une version ultérieure de l'outil ? SW: Tunawezaje kuboresha zana ya usajili wa tukio? Ni vipengele au mabadiliko gani ungependa kuona katika toleo lijalo la zana hii? AR: كيف يمكننا تحسين أداة تسجيل الفعالية؟ ما الميزات أو التغييرات التي تتمنونها في الإصدار القادم من الأداة؟

After we complete the event registration project, what organizer features or tools would you like us to work on next?[edit]

FR: Une fois que nous aurons terminé le projet d'inscription aux événements, sur quelles fonctions ou outils de l'organisateur.trice voudriez-vous que nous travaillions ensuite ? SW: Baada ya kukamilisha mradi wa usajili wa tukio, ni vipengele au zana zipi za mratibu ungependa tuzifanyie kazi tena? AR: بعد الانتهاء من مشروع التسجيل في الفعالية، ما هي ميزات المنظم أو الأدوات التي تريدوننا أن نعمل عليها بعد ذلك؟

Is there anything else you would like to share? Please let us know![edit]

FR: Y a-t-il autre chose que vous aimeriez partager ? N'hésitez pas à nous le faire savoir ! SW: Je, kuna kitu kingine chochote ungependa kutushirikisha? Tafadhali tujulishe! AR: هل هناك أي شيء آخر تودون مشاركته؟ فضلا لا تترددوا في إبلاغنا عنه!

November update on test wiki release[edit]

The team has just released the event registration tool to testwiki and testwiki2 (see November 3 update for details). This is in addition to the previous V0 release to the beta cluster. We are now planning to release the event registration tool to Meta-wiki soon. You can see the release schedule for details. Please share any feedback you have below, or you can check out our older discussions for context. Thank youǃ --IFried (WMF) (talk) 16:08, 3 November 2022 (UTC)Reply[reply]


Where are the logs of changes to events kept? — xaosflux Talk 02:29, 8 November 2022 (UTC)Reply[reply]

Hello @Xaosfluxǃ For event pages, they are normal wiki pages, so the normal rules for watching and monitoring them apply. As for actions specific to event registration, we have not implemented logging yet, but we imagine that logging would be very useful to some Wikimedians. Do you agree? We would love your feedback. Right now, we have created tickets to implement the following logging in the futureː log when registration enabled (T321018), log when registration disabled (T318160), and log when someone registers publicly for an event (T321019). We have also shared this explanation in our user guide (see FAQ section). Thank you in advanceǃ IFried (WMF) (talk) 14:27, 8 November 2022 (UTC)Reply[reply]
@IFried (WMF) Thank you, basically if changes can be made, for transparency changes should be recorded - especially if a change can be made by more than one person. For example, if I kick someone out of an event, it should be logged that X removed Y from event N or the like. If someone edits an event, what it was and how it got there would be useful as well. For example, if I change the campaignevents-edit-field-meeting-url a history of that should be made. Almost all processes that happen on-wiki are normally expected to have full transparency and accountability. An example I'm thinking of is SecurePoll, notice logs such as this one. If the actual event data was stored in a page (like a .json page) that would provide the accountability, if it is being stored in a bespoke database, more logging may be the best solution. Thoughts? — xaosflux Talk 14:39, 8 November 2022 (UTC)Reply[reply]
@Xaosflux Thanks for the reply and explanationǃ Your reasoning makes sense, and it's completely understandable that people would want some sort of logging of changes related to event registration that can be publicly displayed, like other actions performed on the wikis. For this reason, the team is currently exploring what options are available. So far, we have identified two potential paths. The first option is to record changes in SpecialːLog, and we have already written tickets for this work, as shared in my previous comment. If we choose to take this path, it would be high-priority for the team to work on soon. The second option is to investigate if we can display registration changes in the event page history (see T322657 in Phabricator). The first option (logging in SpecialːLog) would be most likely to be quicker and easier to implement, but it would record single actions rather than providing a more detailed history of changes like one can see in a page history. The second option (display changes in event page history) is still undetermined in terms of effort and scope (one of our engineers has just started looking into it), but we can provide updates when we know more. It should be noted that we can also implement both solutions; it doesn't have to be a choice of just one. So, for example, we could implement logging in SpecialːLog first, and then incrementally build out support for the page history, if it is indeed a larger amount of work that would take time. With all that being said, we'll share an update on this project page when we know more. In the meantime, we would love your feedback and thoughts on this topic and how and we're thinking about it, along with anything else related to the project. Thank you again for taking the time to share your thoughts with usǃ IFried (WMF) (talk) 13:53, 9 November 2022 (UTC)Reply[reply]
Thank you for the update! — xaosflux Talk 14:22, 9 November 2022 (UTC)Reply[reply]

Should have autocomplete for the timezone[edit]

The dropdown is extremely(!) long. Would be very useful to have some autocomplete. For example: after typing "War" I should see a short list with at least "Europe/Warsaw" as one of the suggestions. Nux (talk) 15:14, 8 November 2022 (UTC)Reply[reply]

@Nux Thank you trying out the tool and for sharing your feedbackǃ This is a sensible request, since we also think there can be user experience improvements to the time zone selector dropdown. This is the same drop-down that is also displayed in Preferences > Appearance when the user selects their preferred time zone on the wiki. For this reason, any improvements to the time zone selector would be a more generalized Mediawiki request that is beyond our team specifically. If you would like to see changes to the time zone selector, one option is to write a ticket in Phabricator, so perhaps someone can pick up the work now or in the future. Meanwhile, there are some options already available with the current time zone selector that can help the user. First, there is basic autocompletion for continent (so, if you type the first few letters of a continent, it should bring you to that continent's section). Second, the continents are listed in alphabetical order, followed by the countries in alphabetical order, so there is a standardized logic applied. Third, the top section of the selector has options for the wiki default time zone, UTC offset, or browser time zone of the organizer. The organizer may pick one of these options in many cases, all of which are easier to access. With all that being said, we still think this is a useful feature suggestion, so we encourage you to bring this up in a Phabricator ticket if you would like to see these changes made. Thank you again for your feedbackǃ IFried (WMF) (talk) 16:50, 9 November 2022 (UTC)Reply[reply]
OK, added to phab: Filtering (combobox) for choosing timezone. Nux (talk) 23:20, 9 November 2022 (UTC)Reply[reply]
Thank youǃ IFried (WMF) (talk) 13:46, 10 November 2022 (UTC)Reply[reply]

End date should have start date in the calendar[edit]

Would be nice to have a start date selected in the calendar. In jQuery UI this is resolved by setting minimum date on the 2nd control. jQuery UI date range example. Nux (talk) 15:18, 8 November 2022 (UTC)Reply[reply]

Hello @Nuxǃ Thank you for bringing up this point. We have a ticket for this (see T305706 in Phabricator), and we can make this change in the future. Much appreciatedǃ IFried (WMF) (talk) 20:21, 9 November 2022 (UTC)Reply[reply]

Limitations for registrations[edit]

There appear to be no restrictions / requirements for users registering for an event.

I think it would be wise if you could set a limit on the minimum number of global edits per account. For example, a minimum of 100 global edits to be able to register. Or the minimum age for a global account.

Also when I remove a user there seem be no consequences. The user is not really banned as he can simply re-register. The user should not be able to re-register without some kind of action of organiser(s). Nux (talk) 15:32, 8 November 2022 (UTC)Reply[reply]

Thank you for this feedback, @Nuxǃ In this comment, you provided two different suggestions, which I will address separatelyː
  1. You recommended that we set a minimum number of edits before someone can register for an event as a participant. This is an interesting idea, but it goes against the research we have collected from our communication with organizers, as well as research conducted by other teams (for example, see Movement Organizers Study), which confirms that many organizers either target or at least include wiki newcomers in their events. Some organizers even explicitly even say "no experience necessary" on their event pages (for example, you can check out this event page). During these events, organizers often provide training to newcomers and hands-on support. For these reasons, we don't think it makes sense to explicitly exclude newcomers from event registration. However, if you think it may be useful for organizers to have an optional feature in the future that only allows people to join their events if they have a certain number of edits, that could perhaps be a feature request for us to consider, but we would need to learn more. In particular, why would an organizer want to impose this restriction? Have we seen organizers advocate for this restriction before? How would the restriction be determined?
  2. You recommended that, when someone is removed from an event by an organizer, the organizer should have the ability to prevent the user from registering again. We agree. For this reason, we have created a ticket (T322659) to look into how we can implement this feature improvement in the future.
Thank you again for your feedbackǃ IFried (WMF) (talk) 20:41, 9 November 2022 (UTC)Reply[reply]
Yes, I have been to events that welcome newcomers (and I understand your concern), but I would also not like to impose requirements on the number of edits for all events. I'm not talking about strict, static requirements here. I would see this as one of the options for the event. Each organizer would then be able to decide.
It is slightly different with the requirement to have an account for a certain number of days. With very open events you might want to lift this requirement, but I think 7 or 14 days would be a reasonable default. This has to do with being kicked out of the event and with security. If you can create a new account and sign up right away, kicking out of the event doesn't make much sense. The user might create another account and re-register. The other part of this is security or confidentiality of links. If everyone can sign up at any time, why do you even bother to hide links in the event description? Even in this early demo you did hide the links in events. I assume this was due to concerns about some kids using links to bomb video chats or something like that. If there are no limits then you can create an account and harvest these links in minutes (harvest from all events). Nux (talk) 23:44, 9 November 2022 (UTC)Reply[reply]
Thanks for clarifying, @Nuxǃ The fact that this would be an optional feature for organizers makes sense. It also makes sense that the participation criteria could vary (such as the number of edits, the number of days since the account was created, etc), although such variation would increase the scope and complexity of this potential feature. This is the first time we have heard this request, so we would like to see if other people consider it high-priority and/or suggest similar features before delving into potential planning. This will help us understand the context and options better, as well as the level of user need among organizers. In the meantime, we have taken note of this request, and we'll monitor if we hear the same request from other people in the coming months, as we release the CampaignEvents extension to Meta-wiki, conduct various outreach initiatives (like our upcoming community office hours), and then begin planning for the next phase of feature enhancements. So thank you again for this suggestion and clarification, as well as the many helpful insights you have shared overall on this talk pageǃ IFried (WMF) (talk) 14:08, 10 November 2022 (UTC)Reply[reply]

Timezone not visible in details[edit]

Seems like timezone is not visible. I assume the time is converted and displayed as local to the user. Even if so, it would still be good to display that timezone. It would be more obvious. I'm not sure if it takes timezone from my computer or from my wiki-preferences (or from wiki-site settings). Nux (talk) 15:43, 8 November 2022 (UTC)Reply[reply]

Thanks for bringing this up, @Nuxǃ We just released time zone support on the event pages on the beta cluster (see this event page as an example), and it will be released to testwiki and test2wiki by the end of the next week. As for the rules for how the time zone is displayed, here is what we have implementedː
  • For in person events, we display the event time zone that was specified by the organizer when they configured registration.
  • For online and hybrid events, we display the event time zone that is set up in the user preferences of the participants for logged in users, and we display the wiki default time zone for logged out users.
Thank you againǃ IFried (WMF) (talk) 20:50, 9 November 2022 (UTC)Reply[reply]
Sounds great! Thanks for your all this information 🙂 Nux (talk) 23:46, 9 November 2022 (UTC)Reply[reply]

Some way to display registration box below some other text[edit]

One more thing 🙂. Not sure if that would be very useful, but I think it might be useful sometimes to put registrations below some template with navigation etc. Maybe a magic word like for TOC?

See for example Wikidata event of WMPL. There is a template above and some text and a list below. I've tried to re-create that in A test event in new system. I guess it looks acceptable, but I think it would look better if the registration would be below the navigation. Nux (talk) 16:01, 8 November 2022 (UTC)Reply[reply]

Thanks for bringing up this feature request and providing an example of what you mean (and even creating a test eventǃ). This may be something that we explore in the future, but we would need to look into it after we implement some more core event registration and management features that are higher priority, such asː an automatic confirmation email after the participant registers (which the engineers are working on now), integration with the Programs & Events Dashboard (which the engineers will be working on soon), along with other tasks. For us to understand this request better, we would love to get some more information and context from you on it. Why would you prefer the navigation below the navigation? And how do you usually set up navigation? Do you have any recommendations or ideas for how the event registration header could be configured during the process of setting up navigation? Thanks in advance, and we look forward to your responseǃ IFried (WMF) (talk) 20:54, 9 November 2022 (UTC)Reply[reply]
@IFried (WMF), no problem. This is actually a navigation template from Polish Wikipedia which is used in WMPL (charter) events and some less official ones. The navigation template is a actually a community effort (I've only helped with CSS). So this is a real thing already used a few dozen of times probably and with some enhancements along the way. Or in short: it is quite mature.
Having said that I think navigation might have more sense on top partially because this is how we are used to do it. You can see for example:
Wikipedia:Wikiolimpiada 2021
Wikipedia:Wikipedia bez barier 2021
Wikipedia:Miesiąc ukraiński w Wikipedii
Wikipedia:WikiWalentynki 2022
Wikipedia:(Nie)znane kobiety Wikipedii 2022
Wikipedia:CEE Spring 2022
There are two... or three people I think that take care of this most of the time. But I think this year WMPL helped in writing this down somewhere...
In retrospect, I think the navigation is at the top, because then the header doesn't move. When you switch between subpages, the navigation stays in the same place (more or less). So it's easier to browse through all the subpages. Nux (talk) 00:09, 10 November 2022 (UTC)Reply[reply]
@Nux Thanks for the reply and explanationǃ We have created a ticket to investigate implementing support for this feature request in the future (see T322863 in Phabricator). I don't know when we can work on the investigation, but it will be on our radar and, when we do have updates, we'll share it in the Phabricator ticket. Thank you for bringing this topic to our attentionǃ IFried (WMF) (talk) 16:14, 10 November 2022 (UTC)Reply[reply]

Comment mesuré les objectifs d'un Event ?[edit]

Bonsoir la team, j'espère que vous allez bien!

Je veux savoir si l'utilisation de cet outil va exclure (ou rendre moins important) l'utilisation du Tableau de bord d’événement?

Si oui, comment doit-on mesuré l'implication des participants et aussi mesuré les goals d'une activité? VALENTIN NVJ (talk) 19:47, 8 December 2022 (UTC)Reply[reply]

Bonjour @VALENTIN NVJ, merci pour votre question! Non, nous ne voulons pas que l’outil d’inscription exclue ou rende moins important le tableau de bord d’événements. En fait, nous espérons le soutenir et le renforcer en créant une intégration entre l’outil d’inscription et le tableau de bord d’événements. Le but est de synchroniser les listes de participants entre les deux plateformes. Vous êtes invité à suivre ce travail ici:
Hello @VALENTIN NVJ, thank you for your question! No, we do not want the registration tool to exclude or make less important the Programs & Events Dashboard. Instead, we hope to support and strengthen it by building an integration between the registration tool and the Programs & Events Dashboard. This way, participant lists can be synchronised between the two platforms. You are welcome to follow this work here: LDelench (WMF) (talk) 16:48, 24 January 2023 (UTC)Reply[reply]

Open questions as an organizer For event registration system[edit]

1. I think is a good proposed system for creating and managing event registration. It offers benefits like streamlined management, but it may have disadvantages related to adaptability. 2. Your proposed participant registration experience seems convenient since it provides a straight forward information. For instance instead of participants providing their usernames manually it log them in automatically but it could lack personalization compared to our current system. 3. Building an MVP is a good approach to start. Focus on core registration functionality first. 4.The first version should include event creation, participant registration, and basic communication tools. 5.Typically, I send campaign details like sessions date and time via email. 6. Please prioritize the mobile version of the registration system since it prioritize simplicity, ease of yes and some participants may not have laptops and desktop computers. 7. No additional comments at the moment.