Will stamps be applied for all email notifications and reasons for the recipient to receive them, so as to fix T6297: Maniphest email notification doesn't say why I'm receiving it?

Indeed I'm not confused about that. That's why I pointed out that giving money in return for no right/expectation to anything, AKA donating, is usually something done towards non-profit entities with certain requirements, not for-profit entities.

Sorry, I'm unable to answer your question because I have no idea how you could compare development support to hosting services, or equity to donations.

If I read this correctly, people would pay a certain amount regularly without any certainty or reasonable expectation to have any of the fixes or support they care about. Instead they'll need to rely on the resident haruspex to assess what they're embarking on.

The most important aspect in flexibility is the ability to support all locales. MediaWiki uses a system largely based on PHP's date() for historical reasons, see Language::sprintfDate().

Likewise, when importing, I don't know how to unescape $.

(Self-reminder of the downstream report: https://phabricator.wikimedia.org/T624#2606686 .)

If you don't like the @mention-implies-CC behavior

Was rendering disabled altogether? https://secure.phabricator.com/diffusion/P/browse/master/README.md shows up as a mere textarea.

I've not looked into the details of the implementation you started, but because it's gettext I thought maybe some links wouldn't harm:

• https://blogs.gnome.org/mclasen/2016/07/21/using-modern-gettext/
• http://nedohodnik.net/gettextbis/
• http://laxstrom.name/blag/2013/11/20/review-of-gettext-pot-file-format/

I don't see how Herald rules are related to the provided "example use case"

Another example use case: the ability to perform advanced searches based on report history criteria and to send "whines" (as on bugzilla) is needed for any project that wishes to join https://bestpractices.coreinfrastructure.org/ , namely the criteria:

The project MUST acknowledge a majority of bug reports submitted in the last 2-12 months (inclusive); the response need not include a fix.
The project SHOULD respond to most enhancement requests in the last 2-12 months (inclusive). The project MAY choose not to respond.

You should be able to just use a library for this. MediaWiki uses https://www.mediawiki.org/wiki/CLDRPluralRuleParser , see https://doc.wikimedia.org/CLDRPluralRuleParser/master/ for documentation (integration example: https://gerrit.wikimedia.org/r/#/c/240643/ ).

My primary concern here is that I strongly dislike adding options to the product

I do have reasons to believe the is a problem: Google doesn't index most of phabricator.wikimedia.org maniphest reports. This makes a lot of sense because there is no HTML entry from which one could reach all reports; most links are hidden behind JavaScript pagination or manual fiddling.

It's not: the column has a name, position, history, configuration (e.g., maximum points), and triggers

I think this bug was unnecessarily morphed into something unrealistically complex. Deletion of workboards would solve most issues and it would be easy to address

it's intentional that users (including administrators) can not permanently destroy data

by setting some limit (default e.g. 0) on the pieces of information one can destroy. If the workboard has all items in a single column, its information content is 0.

This report lacks a use case explaining why status columns are useful. Just saying.

Herald wouldn't help Wikimedia at all, as we're not able to use it.

When I type a project or user name, I expect the dropdown not to suggest things I already added.

T6943 is the task you'll likely want to follow.

Thanks, good thing I added "AFAICS". ;-) Then the only missing parts are notifications and diffing (optionally, also a direct link to the diff e.g. from "Edited"). Diffing is partly covered by T4961.

Removal of comments is not the only issue: editing of comments

• is not publicly logged AFAICS,
• shows no diff.

An attacker who managed to get access to a very active account of an issue tracker would be able to delete substantial portions of the issue tracker without anyone noticing or being able to revert.

I know what Excel is; but I'm not aware of a definition for the "Excel spreadsheet" term. Any format that Excel can write? read? The Excel flavour of CSV? xls, xlsx, xlsm?
If you know a definition, it would be a useful addition to https://en.wikipedia.org/wiki/Microsoft_Excel#File_formats

I would guess that most users of OpenOffice know that they can open Excel spreadsheets,

Thanks for taking the time to write it down, that's very useful.

I didn't propose adding any list. The comments were expressed as generic. If this guide is about the "When", can a similar guide be created with the "What"? Otherwise, if collating the information in question is not considered interesting, is there a wiki where to collect links to scattered place currently containing it?

Ok, following your request: please integrate the diff https://secure.phabricator.com/transactions/detail/PHID-XACT-TASK-4qse7yakd4fvs45/ because it contains important information that I wish I had known before filing tasks. The text comes from comments by maintainers at T6297, T6309; copying it here makes it easier to reference (I have to link one thing instead of 6 comments) and will hopefully save you from repeating the same things again on countless other tasks.

Err, I just pasted what you folks said

In T6309#79515, @epriestley wrote:

This software is also not targeted at consumers or the public at large. It is targeted at professionals in software fields and adjacent fields.

If I look at https://secure.phabricator.com/settings/panel/emailpreferences/ , this seems rather easy conceptually: there is already one row (and selector) for each possible event, they only need to be "exploded" by the possible relations one can have to the event: Actions x {I made it; or not} x {I'm author of the task/whatever; I'm subscribed to it; I'm assigned to the task; I'm backer of the fund proposal; ... }. You already have the first two combinations, just need the latter.

I understand the constraints and that's the very reason I didn't (yet) split this up more: this is a feature request that can be satisfied on a "best effort" basis, doing what's easy and letting the rest be. I could make a rank of those 15 headers and 3*2 footers but the reality is that whatever portion of those gets fixed I'll be happier.

Well, why not implement all that bugzilla has? Is any of that especially difficult? I could break this down into headers and body footer, if that helps. Do you need a rationale for each header? (That was an email from herald, but those from "normal" relations to the tasks look the same. Unless no herald rule applies for the action, in which case maybe no X-Herald-Rules header will be added at all?)

qqq context documentation is helpful, but not really needed [...]

In T3102#18, @epriestley wrote:

• Implement Project/Repository relationships

Generally, I think the hired Language Admins provided the highest quality, consistency

Facebook's inline translation system is interesting: is there anything I can read on it, particularly on efficiency for translators and accuracy? I've got mixed feedback from Facebook translators and the translations I see in Italian are sometimes less than optimal. AFAICS it values quantity over accuracy (with only 50–100 languages translated though), correct?

Ok, it seems quite some work is needed on Phabricator's end before we can even start. On the bright side, you don't have previous work to trash.

A link to the l10n files would be handy