We will check in on this in a few days
Fri, Mar 5
Thu, Mar 4
Will need to merge PR first
Wed, Mar 3
Tue, Mar 2
Mon, Mar 1
Sharing the blueprint per our team meeting https://image-suggestion-api.toolforge.org/?doc
Sat, Feb 27
Fri, Feb 26
Just wanted to update this task with a note. We recently received another request about this.
@Dbrant shared this helpful context on Android:
There's nothing "structured" about [accessing archived talkpages]. A user can put a link to their archived talk pages on their main talk page, or they may not. They can put a link to the archives inside a template at the top of the page, or not. If they put it in a template, the app won't display it, similarly to mobile web: https://en.m.wikipedia.org/wiki/User_talk:Jimbo_Wales.
Thu, Feb 25
We can use the same langauge.
Looks good, I'm moving this to ready for release until we have regression testing.
After talking to @ppelberg I'm going to decline this task for now. Sending people to webview isn't ideal and the impact of people replying at the bottom isn't very different than what is happening on mobile web.
Wed, Feb 24
Editing Tenure is a bucket in Turnilo, not sure how we are recording that information.
Based on the[[ https://docs.google.com/spreadsheets/d/1N_PAVerw0AO-GWdGwEnLd2DhLkB_kvkVMxAqbeEb56A/edit#gid=0 | validation document ]], my first list of languages we should be deliberate in getting translations in for the copy as early as possible include:
Tue, Feb 23
Hey @Dbrant we got the following questions about the above schema:
- Is instrumentation related to the editor tenure missing in the draft scheme because it will be found in existing instrumentation or via username?
- Is the lang identifying all the different languages the app is set to, or only the 1st app language or device language? For example, someone might speak Danish natively and have that set as the primary language, but also may have added English and Chinese as additional languages?
Ok @schoenbaechler is finishing up the designs so I am increasing the priority of this. After the offsite it should increase to high.
Mon, Feb 22
Thu, Feb 18
Tue, Feb 16
Thu, Feb 11
Marking this as low until we Robin finish designs
I agree it is worth the tradeoff and also would prefer taking the approach listed by Robin
Wed, Feb 10
Talked to Robin and he agrees
@Dbrant helped me sort out having the latest version of alpha and it works on alpha and in production. This is good to go.
Tue, Feb 9
Accidentally unassigned @Sharvaniharan 😆
Move subject line to the left and bottom. Do it like the Contributions page.
From @Miriam :
The image is not depicting the subject of the article The image is of very low quality The image is relevant, but we would not use it on our Wiki There is not enough metadata to understand the goodness of the image match I am not expert enough on the article subject to judge the goodness of the image match The image is just a placeholder for missing images The image is not available I did not understand the task
We are not going to prioritize this at the moment but it isn't completely off of the table. The team is having discussions about the future and strategy of the app. In a world where Editing is a priority on the app we can see instances of leveraging such a feature. As for right now there isn't enough evidence to prioritize it given the social implications and technical workload.
Mon, Feb 8
In our Board Refinement meeting we discussed converting to webview in instances that we take users out of the app, once we do that it should fix this case.
I've added details to this. We won't need to look at this for a month in a half so 3 release cycles.
Sun, Feb 7
We have answered all of the questions in this task so we can close it out