Translations: Store user_id of validator/approver

[ocean90]

This would allow us to show the name of a validator in the "meta" sidebar like

[toolstack]

Seems like a good idea.

[ocean90]

Should this be a more general field which contains the user ID of the last edit? This would allow us to use it for rejects too.

Translated by: User 1
if status = current
   Approved by: last_edited_user
elseif status = rejected
   Rejected by: last_edited_user

Should this be a meta field attached to the translation or a new table column in the database?

[toolstack]

I think it should be the id of the user that made the last status change to the translation.

I'd tend to add this as a new column only to avoid another query.

[yoavf]

I'd like to move this forward - @ocean90 are you ok with an additional column?

[ocean90]

@yoavf See the related discussion on Slack. We have to make sure that all current workflows can be handled with a new column.

Maybe #209 (history/log/notes per translation) is a better idea for this?

[mhsdef]

FWIW I agree with @toolstack. AFAIK, in a normal flow, every translation requires the validation step so it seems integral to the translation record entity.

[ocean90]

Related discussion on Slack: https://wordpress.slack.com/archives/glotpress/p1464715578000943

@yoavf Let's try the additional column approach.