That totally makes sense. I thought that doing this task in a separate branch is a best practice, but your concern is 100% correct, and I agree with merging PRs directly into the main branch.

Nice proposal, @Rohitverma9625

Good proposal @Akul-Tyagi

About the tests, I wonder if it may be better to try TDD approach rather than adding them post the migration. What do you think @Neeldoshii / @VoidRaven-18 ?

Good proposal @VoidRaven-18

Just a few minor comments on the project description:

In T332956#8751749, @Kartikay1412 wrote:

Thank you so much for the detailed feedback @Kaartic, I'll make the changes accordingly. Also, is the current upload mechanism via File Upload API already?

It seems good for a start, overall.

@Kartikay1412 would be able to mention what you plan on doing during the community binding period?

@Kartikay1412 You would need to elaborate a bit more on your proposal. Do checkout the details mentioned in this wiki page. You could also checkout other proposals for the project in Phabricator to get an idea on the structure of a good proposal.

Hi Priyank! Sorry about the delay. I'm out of station on a commitment and hence finding lesser available time than usual for this week.

In T332513#8717401, @PriyankShankar wrote:

Unfortunately, I have not raised any pr's to the commons app repository.

In T292543#8597029, @Ladsgroup wrote:

They should be visible in the deployment calendar: https://wikitech.wikimedia.org/wiki/Deployments

I suggest adding a final tech news saying this won't be announced anymore and users could see some short read-only times in 7AM UTC in Tuesdays and Thursdays.

The issue mentioned here does appear fixed in mobile web. But as noted in the task description the issues appear not to be fixed in the mobile app (v2.7.50391-alpha-2022-01-14) yet. So, re-opening the task.

Just wanted to note that I announced this read-only to the following wikis: enwiki, commons, tawiki, tawiktionary, tawikiquote, meta-wiki (linking the changes for easy reference).

I'm not sure if I experience the ambiguity as I'm a non-native speaker. A comma before "... in the last 30 days" would've avoided the confusion I guess.

Strange observation. I saw the "You've been logged out" pop-up today when I was initiating a search:

Apparently, I'm still observing this in my Android 5.1.1 device using v2.7.50334-alpha-2020-11-11 of the app. So, I'm reopening it.

In T263046#6491623, @Jgiannelos wrote:

@Kaartic can you still reproduce this issue with your device?

I just tried on a Firefox for Android 68.12.0esr and couldn't reproduce the issues described in this task and T240883. The editor works fine. I didn't observe any weird behaviors. So, I believe the fix works.

In T35805#6361151, @JMinor wrote:

No longer valid

Compatibility matrix template has been officially bumped.

Space has been canceled

Was the removal from a description a request to opt out of this change or is this a mistake?

Done in tawikipedia. Ref: https://ta.wikipedia.org/w/index.php?title=Main_Page%E0%AE%AE%E0%AF%8D&type=revision&diff=2992950&oldid=2984893&diffmode=source

This is likely never going to happen as Nearby has been removed from the app. So, closing. Feel free to re-open if this is not correct. :)

In T255742#6235684, @Whatamidoing-WMF wrote:

Every time you switch back and forth, an additional set of colons is inserted.

In T248594#6233882, @ppelberg wrote:

able you to share a link to documentation where the cases in which people will be prompted to complete a CAPTCHA when using the Reply tool?

On Android, truncate the description at two lines in order to easily scan list items and to keep it consistent with the rest of the app.

In T254287#6222190, @Jdlrobson wrote:

thank you @Kaartic for your help!

(note: can you actually save a reply?)

Just an FYI. I just opened topics about this in the tawikipedia, tawikiquote and tawiktionary talk pages.

I will add, however, that when performing a search in Mobile Web, there doesn't seem to be any constraint on the description length:

IIUC, this was created based on the feedback given by a user in the mobile-l mailing list: https://lists.wikimedia.org/pipermail/mobile-l/2020-May/010720.html

In T183859#6174714, @matmarex wrote:

2. Make it difficult to discard edits
   
   The default option selected in the "Are you sure?" modal is "Discard edits". To make sure users don't lose their edits easily wouldn't it be better to choose "Continue editing" by default ?

(This problem was reported again in T249880)

In T151302#6168716, @Aklapper wrote:

Cannot reproduce anymore in a small window with Firefox 76 on desktop - when I open a new dropdown the other open one closes here.

Ok, done! I've posted the reminder at enwiki VPT.

I'm a little confused about the approximate duration of the operation. This task says the read only time would be around 30 minutes. The other one related to this (T251982) says the read-only time would be around 15 minutes. Which one should I trust?

In T251985#6148701, @Trizek-WMF wrote:

@Kaartic, I know that you are very efficient at posting reminders on wikis! :) Have you already posted some reminders on English Wikipedia?

In which version is this supposed to be fixed? I still observe the issue mentioned in the description in 2.7.50317-alpha-2020-05-15.

I'm facing this again. I observe a pattern, though. It seems to be happening after I log in for a few times in other devices/browsers.

Yeah, log in to Commons beta is possible using the Commons Android app (beta flavour). Thanks for fixing this 😄

In T244951#5875336, @Urbanecm wrote:

I'm confused. The task talks about Commons, and links to enwiki's login form?

I can confirm this. I observe the same behaviour as described in the task description.

Also, SSL server test seems to be a lot happier (A) than before (B). Though I notice that it shows "No" near OCSP stapling now. Is this intentional?

@Krenair As of now, I can confirm that this is fixed in both Firefox on Windows and the commons beta app. Thanks a lot for fixing this! 🙂

According to SSL server test it already expired (at Feb 05 09:00:00 UTC 2020), ...

Personally, I like Option 1 to be chosen as there would be enough space for two icons in desktop and I like to see them separately.

Just wondering, how long would the temporary solution work? I think that's the same as the answer to the question: How long is the stapled response valid?

Previously notices were accessible via the overlay that opened when you clicked the icon however this was intentionally broken to separate mobile and desktop experiences more cleanly.

the title does? "It should be possible to access notices in Minerva desktop without adding a new icon"

Though the description doesn't explicitly mention that notices are not accessible in desktop, they do seem related.

I reported this earlier. You can find the response I got at T244089#5843531

Yeah, I can confirm that the beta site is now accessible again in my desktop. The issue faced in the commons app also seems to be gone now. Thanks for the quick fix! :-)

I just checked and this seems to be happening only for notices and not for alerts. I'm able to see the unread notices from other wikis in my mobile but not in desktop.

👍

This is a duplicate of T232275 which has already been fixed.

I can't reproduce this in Firefox 72.0.2 on Windows 10

I can't reproduce this in Firefox 72.0.2 on Windows 10. Though, we're facing an issue in the Wikimedia Commons Android app in which we're unable to connect to the Commons beta cluster. It might be due to the OCSP stapling issue. Link to the issue.

This does look fixed. But I came across another issue with search in the History page. I've filed it as T242142.

There is nothing in the JSON output of https://api.github.com/orgs/wikimedia/repos that indicates whether a Github repository has been forked ...

As far as I checked this does look fixed i.e., the "Reference Previews" beta feature is enabled when the "Automatically enable all new beta features" option is enabled. Thanks for fixing this!

IIUC, after the change setlang would change the preferred interface language of a user permanently when they accept the change. In that case I think the following string communicates that very well.