Page MenuHomePhabricator

Ask for feedback before deleting a WB instance to ask "why"
Open, Needs TriagePublic

Description

We want to understand who's interested in Wikibase Cloud and who is not, and how we can improve, to continously develop our platform. A good source of information is the moment someone decides to the delete their Wikibase: Is the product not suitable for them? Why? Is it missing core functionality? What? Is it not meeting their needs? Why? etc. etc.

image.png (2×1 px, 527 KB)

Link to figma

AC:

  • Responses are stored and can be accessed as a file (similar to implementation of conversion metrics (i.e. a csv that can be downloaded)
  • the download should only be visible to internal users. this should be done by marking some wikibase cloud accounts as WMDE users
  • Update button components to current design (see figma)

Event Timeline

Charlie_WMDE updated the task description. (Show Details)
Charlie_WMDE subscribed.

Before we pick this up please do a quick investigation to find how many wikis are deleted each month by unique real (not WMDE employee users) actually delete their Wikis

Tarrow changed the task status from Open to Stalled.Jan 31 2024, 12:13 PM
Charlie_WMDE changed the task status from Stalled to Open.Feb 16 2024, 12:34 PM

after finding out that we have had deletions of unique users in the 10s in the past months, I would like to proceed with this ticket. therefore I have unstalled it and moved it back up in the todo column

Charlie_WMDE renamed this task from Add an additional field to deletion to ask "why" to Ask for feedback before deleting a WB instance to ask "why".Feb 21 2024, 12:21 PM

@Charlie_WMDE we heard form the grapevine that we're fine for this data to all be exposed publicly; is that right? Our technical implementation of it somewhat depends on this. For example, if we add this to the conversionMetrics "anyone" could then see the reason a user deleted a site; maybe that's desired but we wanted to check you were aware that is the case.

Tarrow changed the task status from Open to Stalled.Feb 22 2024, 2:36 PM
Charlie_WMDE changed the task status from Stalled to Open.Feb 26 2024, 11:28 AM
Charlie_WMDE updated the task description. (Show Details)

Hey Rosalie,

thank you for sharing the link.

Here are my remarks:

  1. The delete button has not been updated (see last AC)
  2. The style of the heading doesn't look right. I couldn't figure out what you used, but it is supposed to be an h5
  3. The style of the subtitle doesn't look right. it's supposed to be "subtitle 2" i can not make out what you used there.
  4. the free form text field is not the same styling of the component as in figma
  5. There are a lot pf spaces between components that are not in the designs, for example between all the checkboxes and between the text input label and the text input field
  6. The "delete Wikibase" button has no padding to the left and is touching the border of the card

I did not check the functionality of the card at this stage. I'm happy to do that in a second interation.

For all the specs, please refer to the figma file and swtich to "dev mode" to see all the component names and properties and specs. Thanks!

@Charlie_WMDE What are some attributes we want in the csv file?. Fo now I have this 'domain_name', 'wiki_deletion_reason', 'wiki_creation_time', 'wiki_deletion_time'
Also do we want all WMDE accounts to have acces to the csv or some specific emails?

Hey @Rosalie_WMDE thanks for asking! I'm sorry for not including these details in the ticket in the first place.

The attributes you picked already sound great!

My suggestions:

  • how many other instances does the cloud account associated with that wiki have at time of deletion
  • how many edits did the instance have at time of deletion
  • how many entities did the instance have at time of deletion
  • how many pages did the instance have at time of deletion
  • how many user accounts did the instance have at time of deletion

let me know if any of these are not possible. thanks!

no, not all WMDE accounts should have access. only specific emails. for now i would say the engineers, conny, anton and I should have access. thanks!