Change Details

NOTE: This ticket has incomplete sections as we aren't quite ready for a performance review yet, but would like to get the task on your radar sooner rather than later. We expect the product to be ready for review at **the end of Q4 (June, 2022)**. #### Description We are creating an on-wiki registration system for campaigns in the Wikimedia movement (e.g. Wiki Loves Monuments, WikiGap, #1Lib1Ref, etc.). For this iteration, we are focusing on the campaign's organisers' experience of creating/editing registration, as well as for participants' experience to sign up for campaigns. Please find user flow here: for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.gc6f75fceb_0_10 | campaigns organisers ]], and for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.g105a8dd60ad_0_52 | campaigns participants ]] Additional references: - [[ https://meta.wikimedia.org/wiki/Campaigns/Foundation_Product_Team/Registration | Documentation on MetaWiki ]] - [[ https://docs.google.com/presentation/d/1WZNaAjvSotCSMn6Mifoo4bLZf-fwXOXfGs5-9LuAbmk/edit#slide=id.g10d8d924887_0_0 | MVP architecture diagram ]] #### Preview environment > 🚧 Will share link once we have deployed to beta 🚧 //(Insert one or more links to where the feature can be tested, e.g. on Beta Cluster.)// Hosting the changes on Beta Cluster is a requirement prior to performance review. Please ensure that the feature can be used directly on the link(s) provided, without any data entry such as having to create an article. Any sample content needed should already be present. If the changes cannot be hosted on Beta Cluster, explain why and provide links to an alternate public environment instead where the Performance Team can also SSH into. Links to code only is insufficient for a performance review. #### Which code to review Code repository is hosted on: https://gerrit.wikimedia.org/g/mediawiki/extensions/CampaignEvents #### Performance assessment > 🚧 Will provide more details later 🚧 Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? - Are there potential optimisations that haven't been performed yet? - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]].

NOTE: This ticket has incomplete sections as we aren't quite ready for a performance review yet, but would like to get the task on your radar sooner rather than later. We expect the product to be ready for review at **the end of Q4 (June 2022)**. #### Description We are creating an on-wiki registration system for campaigns in the Wikimedia movement (e.g. Wiki Loves Monuments, WikiGap, #1Lib1Ref, etc.). For this iteration, we are focusing on the campaign organisers' experience to create/edit registration, as well as for participants' experience to sign up for campaigns. Please find user flow here: for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.gc6f75fceb_0_10 | campaigns organisers ]], and for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.g105a8dd60ad_0_52 | campaigns participants ]] Additional references: - [[ https://meta.wikimedia.org/wiki/Campaigns/Foundation_Product_Team/Registration | Documentation on MetaWiki ]] - [[ https://docs.google.com/presentation/d/1WZNaAjvSotCSMn6Mifoo4bLZf-fwXOXfGs5-9LuAbmk/edit#slide=id.g10d8d924887_0_0 | MVP architecture diagram ]] #### Preview environment > 🚧 Will share the link once we have deployed to beta 🚧 //(Insert one or more links to where the feature can be tested, e.g. on Beta Cluster.)// Hosting the changes on Beta Cluster is a requirement prior to performance review. Please ensure that the feature can be used directly on the link(s) provided, without any data entry such as having to create an article. Any sample content needed should already be present. If the changes cannot be hosted on Beta Cluster, explain why and provide links to an alternate public environment instead where the Performance Team can also SSH into. Links to code only is insufficient for a performance review. #### Which code to review Code repository is hosted on: https://gerrit.wikimedia.org/g/mediawiki/extensions/CampaignEvents #### Performance assessment > 🚧 Will provide more details later 🚧 Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? - Are there potential optimisations that haven't been performed yet? - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]].

NOTE: This ticket has incomplete sections as we aren't quite ready for a performance review yet, but would like to get the task on your radar sooner rather than later. We expect the product to be ready for review at **the end of Q4 (June, 2022)**. #### Description We are creating an on-wiki registration system for campaigns in the Wikimedia movement (e.g. Wiki Loves Monuments, WikiGap, #1Lib1Ref, etc.). For this iteration, we are focusing on the campaign's organisers' experience ofto creatinge/editing registration, as well as for participants' experience to sign up for campaigns. Please find user flow here: for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.gc6f75fceb_0_10 | campaigns organisers ]], and for [[ https://docs.google.com/presentation/d/1qHuSEiO_ouRFLy6KEQ1LYEC140nqVZeMuH9i_fhAZZo/edit#slide=id.g105a8dd60ad_0_52 | campaigns participants ]] Additional references: - [[ https://meta.wikimedia.org/wiki/Campaigns/Foundation_Product_Team/Registration | Documentation on MetaWiki ]] - [[ https://docs.google.com/presentation/d/1WZNaAjvSotCSMn6Mifoo4bLZf-fwXOXfGs5-9LuAbmk/edit#slide=id.g10d8d924887_0_0 | MVP architecture diagram ]] #### Preview environment > 🚧 Will share the link once we have deployed to beta 🚧 //(Insert one or more links to where the feature can be tested, e.g. on Beta Cluster.)// Hosting the changes on Beta Cluster is a requirement prior to performance review. Please ensure that the feature can be used directly on the link(s) provided, without any data entry such as having to create an article. Any sample content needed should already be present. If the changes cannot be hosted on Beta Cluster, explain why and provide links to an alternate public environment instead where the Performance Team can also SSH into. Links to code only is insufficient for a performance review. #### Which code to review Code repository is hosted on: https://gerrit.wikimedia.org/g/mediawiki/extensions/CampaignEvents #### Performance assessment > 🚧 Will provide more details later 🚧 Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? - Are there potential optimisations that haven't been performed yet? - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]].