Change Details

Now that Growth features are on all Wikipedias, we can consider whether //autocreated// accounts should get them. Right now, if an account is created on wiki A (and gets the Growth features), and then the user goes over to wiki B (which creates them an account there), they don't have the Growth features on wiki B. ==== Implementation To ensure the enablement of Growth features is the same on all wikis, the easiest solution is to make use of [Extension:GlobalPreferences](https://www.mediawiki.org/wiki/Extension:GlobalPreferences). In other words, instead of enabling Growth features //locally// on account creation, we will enable the features //globally// in GlobalPreferences. That way, Growth features will either be enabled on all wikis for that user, or on none of them. On the database level, this can be done by adding rows to `centralauth.global_preferences`, using the user's global ID as `gp_user`. It seems doable via `GlobalPreferencesFactory::setGlobalPreferences`. I think we should keep the current mechanism as a fallback, in case GlobalPreferences is not available. ==== Open questions [X] How will this affect our experiments? We are only including accounts that are NOT autocreated in our analysis, so it shouldn’t impact analysis. [ ] The place where users can disable our features will move. Instead of Special:Preferences, it will be possible on Special:GlobalPreferences. Can this confuse our users? [ ] How should we handle legacy users? Should we migrate everyone to global preferences? Or should we only notify that this is an option? ==== Acceptance Criteria Given I'm logged in, When I visit another wiki and an autocreated account is made, Then the autocreated account has the same "Newcomer editor features" Preferences as currently set in the wiki where I originally registered. And autocreated accounts should NOT receive the Welcome survey.

Now that Growth features are on all Wikipedias, we can consider whether //autocreated// accounts should get them. Right now, if an account is created on wiki A (and gets the Growth features), and then the user goes over to wiki B (which creates them an account there), they don't have the Growth features on wiki B. ==== Implementation To ensure the enablement of Growth features is the same on all wikis, the easiest solution is to make use of [Extension:GlobalPreferences](https://www.mediawiki.org/wiki/Extension:GlobalPreferences). In other words, instead of enabling Growth features //locally// on account creation, we will enable the features //globally// in GlobalPreferences. That way, Growth features will either be enabled on all wikis for that user, or on none of them. On the database level, this can be done by adding rows to `centralauth.global_preferences`, using the user's global ID as `gp_user`. It seems doable via `GlobalPreferencesFactory::setGlobalPreferences`. I think we should keep the current mechanism as a fallback, in case GlobalPreferences is not available. **Autocreated accounts should NOT receive the Welcome survey.** ==== Open questions [X] How will this affect our experiments? - We are only including accounts that are NOT autocreated in our analysis, so it shouldn’t impact analysis. [ ] The place where users can disable our features will move. Instead of Special:Preferences, it will be possible on Special:GlobalPreferences. Can this confuse our users? [ ] How should we handle legacy users? Should we migrate everyone to global preferences? Should we only address this for new autocreated accounts? Should we notify legacy users that this is an option? ==== Acceptance Criteria This is a research spike that covers: - the engineering research needed to help make this work actionable. Especially determining how Growth preferences should work on Special:Preferences and Special:GlobalPreferences. - writing up subtasks to cover the work needed. Please break this work up so we can approach this in a more iterative way (and potentially only work on the lower-effort tasks if we determine a migration for legacy users is too much of an effort). In other words, likely we need separate tasks for the handling of new autocreated accounts and the handling of legacy autocreated accounts (for users with Growth features enabled).

Now that Growth features are on all Wikipedias, we can consider whether //autocreated// accounts should get them. Right now, if an account is created on wiki A (and gets the Growth features), and then the user goes over to wiki B (which creates them an account there), they don't have the Growth features on wiki B. ==== Implementation To ensure the enablement of Growth features is the same on all wikis, the easiest solution is to make use of [Extension:GlobalPreferences](https://www.mediawiki.org/wiki/Extension:GlobalPreferences). In other words, instead of enabling Growth features //locally// on account creation, we will enable the features //globally// in GlobalPreferences. That way, Growth features will either be enabled on all wikis for that user, or on none of them. On the database level, this can be done by adding rows to `centralauth.global_preferences`, using the user's global ID as `gp_user`. It seems doable via `GlobalPreferencesFactory::setGlobalPreferences`. I think we should keep the current mechanism as a fallback, in case GlobalPreferences is not available. **Autocreated accounts should NOT receive the Welcome survey.** ==== Open questions [X] How will this affect our experiments? - We are only including accounts that are NOT autocreated in our analysis, so it shouldn’t impact analysis. [ ] The place where users can disable our features will move. Instead of Special:Preferences, it will be possible on Special:GlobalPreferences. Can this confuse our users? [ ] How should we handle legacy users? Should we migrate everyone to global preferences? Or should we onlyShould we only address this for new autocreated accounts? Should we notifyy legacy users that this is an option? ==== Acceptance Criteria Given I'm logged in, When I visit another wiki and an autocreated account is made,This is a research spike that covers: Then the autocreated account has the same "Newcomer editor features" Preferences as currently set in the wiki where I originally registered- the engineering research needed to help make this work actionable. Especially determining how Growth preferences should work on Special:Preferences and Special:GlobalPreferences. And autocreated accounts should NOT receive the Welcome survey.- writing up subtasks to cover the work needed. Please break this work up so we can approach this in a more iterative way (and potentially only work on the lower-effort tasks if we determine a migration for legacy users is too much of an effort). In other words, likely we need separate tasks for the handling of new autocreated accounts and the handling of legacy autocreated accounts (for users with Growth features enabled).