<epriestley> qgil: the ALLCAPS one is runtime-generated. We only have English other than that (src/infrastructure/internationalization/translation/PhabricatorEnglishTranslation.php). You can run bin/i18n extract to extract strings from the codebase, but it doesn't dump them out in a common format yet.

It seems there is some basic information in https://secure.phabricator.com/diffusion/P/browse/master/src/docs/contributor/internationalization.diviner

@Swidmann: Thanks for looking into this! If there's anything you need help or input with, please let us know here!

Typeahead works perfectly, sure.

Estimation feels impossible because we're not yet running Phab in production (so feedback base is very limited), but I expect quite some users to be confused by drag'n'drop only (until they somehow manage to discover that other ways are available).

@demo: "Resumable / Chunked file upload" sounds like one potential solution to a problem, but there is no problem described in this task. Can you please explain which problem you'd like to see solved?

This is how a board looks like when you change white-space: nowrap, to normal, showing the full titles of cards:

aik099: Sounds like a topic for a separate ticket?

I see, and having the option to use comment 0 as an "updated description of the task in one single place" instead of having to read 40 followup comments makes a lot of sense.
Might just be an issue of different social expectations and how much a reporter considers a task summary and description "her/his own". For example, I'd expect a MediaWiki user who started a discussion thread to be rather disturbed if somebody else edited their initial posting.

Can the possibility to delete be restricted by a policy? For instance, only admins can delete. The fact that all users can delete their own posts kept me thinking. MediaWiki and Bugzilla users cannot do this (in the first case you can revert, in the second case comments are not editable). There is the theoretical case of the upset volunteer that one evening decides to start deleting their own contributions. I will leave that to @aklapper because he has seen enough to write a couple of books.

Using the Orca 3.10 screenreader, the spoken output is "Calendar beta link" so this sounds like a bug in JAWS to me.

This might work for the time being - no stats, but I guess it happens once or twice a month that I (or other WMF Bugzilla admins) need to hide a comment or hide/delete an attachment.

The usefulness of proposed duplicates really depends on the search algorithm used in the backend, and I don't know enough neither about Bugzilla's nor Phabricator's so I cannot judge if Bugzilla's duplicate search is good or bad, as I miss comparisons.
It's hard to gather data here which isn't just anecdotes unfortunately.

As Phabricator allows a task to be part of more than one project, a user can create a ticket with 'Projects' set to 'Foobar' (as that's the codebase) and also 'Security' (as it's a vulnerability s/he reports).
We'd want to make sure that the access settings for 'Foobar' wouldn't "leak" the information in the ticket and that the access rules of the "more restrictive" project are applied to the task, I guess.

Thanks for elaborating! So let's keep this ticket refering to the wording of the search option; and I'll investigate making our instance use ElasticSearch.

Anything that supports stemming would help. I need to find "delete" and "deleting"/"deletion" when searching for "delet"; or "duplicate" and "duplication" for "duplicat", because users use different forms of words in ticket trackers.

Hmm, how do I find out how old a Phab checkout is (in this case the one on wmflabs.org)? Any way I can see a revision ID?