After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 567374 - Not receiving email when someone commit
Not receiving email when someone commit
Status: RESOLVED OBSOLETE
Product: damned-lies
Classification: Infrastructure
Component: vertimus
unspecified
Other All
: Low enhancement
: ---
Assigned To: damned-lies Maintainer(s)
damned-lies Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-01-11 15:27 UTC by Milo Casagrande
Modified: 2018-05-22 12:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milo Casagrande 2009-01-11 15:27:53 UTC
Please describe the problem:
If I follow all the procedure for uploading a file with Vertimus, when a "commiter" commits the file I've uploaded, I don't receive any mail stating that the commit has been done, I need to check again the translation page.

I think it would be nice if translators receive a notification that their translations have been committed (probably even that their translation are in charge for being committed, but no committed yet), rather than checking again the website.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Claude Paroz 2009-01-16 17:11:28 UTC
In the planned workflow, this announcement is going to the team mailing list. However there is no ML configured for your team (http://l10n.gnome.org/teams/it).

Maybe we could send to the translator(s) when there is no ML infos for the team.
Comment 2 Milo Casagrande 2009-01-16 17:43:37 UTC
(In reply to comment #1)
> In the planned workflow, this announcement is going to the team mailing list.
> However there is no ML configured for your team
> (http://l10n.gnome.org/teams/it).

Oh, that's good to know: that there's no mailing list set up for my team.

I'll write in the mailing list and see what to do.

> Maybe we could send to the translator(s) when there is no ML infos for the
> team.

Anyway, sending to translators if no mailing list is set up is a good idea.

If I may suggest, as Launchpad does, let the team coordinator choose:
 - sending to the mailing list
 - sending to each individual translator
 

Comment 3 Stephane Raimbault 2009-01-20 21:51:40 UTC
For second case, sending to each individual translator

Do you want to send an email to all team members or only to concerned translators (with an action on the Vertimus page)?
Comment 4 Milo Casagrande 2009-01-20 21:54:20 UTC
In my idea, only to concerned translators.
Comment 5 Lucas Lommer 2009-02-19 00:24:41 UTC
Anyone been thinking about RSS-like stuff? Translator can receive changes/notifications via RSS.

Would be nice first reason for me to start using this technology :D
Comment 6 Lucas Lommer 2009-02-19 00:30:08 UTC
There is a RSS related bug opened as #566504
Comment 7 Petr Kovar 2009-10-05 19:26:37 UTC
May I suggest implementing a simple text entry (text field) to each module's translation page form, just like we have CC lists in each Bugzilla's bug report page? Then e.g. a coordinator could explicitly send a notification to any translator regardless of translator's current concern as Vertimus see it.

(The thing is that for the time being, the list of concerned translators gets reset after a commit action or action backup, and that prevents teams from fully implementing workflow where each translator has its own set of permanently assigned module translations. Also, in some circumstances, it might be useful to have a way to explicitly notify a [registered] user of actions, discussions etc. in a module's translation page that might be of interest to one and/or one might want to follow.)
Comment 8 GNOME Infrastructure Team 2018-05-22 12:07:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/damned-lies/issues/8.