User Details
- User Since
- Mar 15 2024, 2:51 PM (116 w, 4 d)
- Availability
- Available
- LDAP User
- Antonkokhwmde
- MediaWiki User
- Anton Kokh (WMDE) [ Global Accounts ]
Today
- Testing by activating a policy on staging
- The dialog: implement the more flexible solution right away (depending on which policy is active vs. the user is on); update the behavior requirement when only 1 policy gets accepted
- Remove mentions of the "active" flag for now
- ToU and HP links in the dialog pointing to the currently active policies
- Just UI lockdown, no API lockdown
Yesterday
Included the changes approved by @Alice.moutinho into the design
Regarding using dates for version identifiers: in the database, feel free to identify them as you prefer. In UI (the version list) - please keep them identified by effective date (+ 'Upcoming version' for future versions).
Per new rollout plan, this should remain stalled until we ship the first batch of stories. I will move it back to another board, so it's not confusing
Product-wise, I don't see a need in a sign up limit.
Mon, Jun 1
Fri, May 29
Thu, May 28
Instances won't be suspended for not accepting Terms of Use.
Instead, they will be suspended through the hosting policy suspension workflows (the manager won't be able to submit the instance for review unless they accept the new policies)
A suggestion from the refinement feedback to be reviewed by the designer.
@Alice.moutinho , are you OK with this solution?
Sigh, since the full rework of the plan, the whole hierarchy is messed up, I will fix it now
Tue, May 26
Closing ticket, because managers on old policies won't be able to create instance (or do anything else in the profile, other than accepting the new policies)
To be estimated after a proper tech breakdown
Wed, May 20
Tue, May 19
reported, thank you!