Closed
Bug 1359033
Opened 7 years ago
Closed 3 years ago
[notifications] Fix sending new string notifications
Categories
(Webtools Graveyard :: Pontoon, enhancement, P2)
Webtools Graveyard
Pontoon
Tracking
(Not tracked)
RESOLVED
MOVED
People
(Reporter: mathjazz, Unassigned)
References
Details
There are a few cases when we send new strings notifications but we shouldn't, and vice versa. We do not send notifications, but we should: - If new symmetric (bilingual) file is enabled for a locale (e.g. in Mozilla.org), we should notify contibutors of that localization about new strings. Currently we don't send any notifications when such event occurs. We do send notifications, but we should not: - If we not only add new strings, but also pretranslate them in repository using existing translations (e.g. on merge to Firefox Beta or when files are moved in the l10n repo on merge day), we shouldn't notify project contributors about them. - If source strings are different depending on locale (e.g. Mozilla.org or Engagement), we should send notifications only to contibutors of locales for which the new strings were added. Currently we notify all project contributors, even if new strings are only enabled for a handful of locales. - If a project is private, we send new string notifications to all translation authors within that project. That doesn't sound wrong on a first look, but if the project had been public in the past and is not private, there might be false positives among the recipients. So we must only send notifications to users that have access to the project at the time of sending a notification.
Reporter | ||
Updated•7 years ago
|
Summary: Fix sending new string notifications → [notifications] Fix sending new string notifications
Comment 2•3 years ago
|
||
*This bug has been moved to GitHub.* *Please check it out on https://github.com/mozilla/pontoon/issues.*
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → MOVED
Updated•3 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•