Open dgilge opened 6 years ago
Ahm ... I think I didn't get it. Can you play through an example?
Sure…
Does that help?
Okay.
A) When is a translation complete? How can we tell? Do we use an algorithm (probably very hard) oder do we let the user tell us (probably chaos)? My answer: we don't ... we don't want to know if a paragraph is completely translated. The users will vote it, and they only vote for completed translations.
B) Do we really want to make it thus complex? What have we to loose if we set one expiration time (30 min). Once the user is familiar with the concept of our history he will expect that such long periods of inactivity will generate a new record and that's it. In fact, I assume the user would be surprised that the next day his edits will still go to his history record the day before (howbeit, this can be communicated through ui)
C) What I want to say is: If we set only one 30 min time we only loose disc space (and probably not a lot), but we gain a less complex system. I don't see this complexity necessary here.
A) Actually this is another topic, but here are my thoughts. We plan a status bar and I think it's better to show the completion more accurately than just by "has the translated segment any content". And I think we should ease contributors as much as possible. My plan is to count the words or characters, multiply it with a language specific factor, compare it with the original, admit some tolerance and determine completion.
B) You're probably right. It might not be intuitive.
C) I was thinking about this feature because I don't know any platform where your contributions are "auto commited" and you don't have a chance to change that. I.e. you always decide when to publish something. I don't know how users like our concept. (I personally don't like a half completed contribution to be published.) Therefore I wanted to compensate that somehow. But I think we just use the 30 min for now and we will see how users feel about it. (Maybe we could also implement a feature that you can delete historical records with incomplete translations for contributors how care in the future, we will see.)
A) That is quite smart actually. B) Yes C) I see your point. That is a user testing issue then. Let's use 30 min and see how people respond.
I thought about the time a user has to undo (i.e. remove) their changes and when a new historical record is created after several edits because I wasn't satisfied with the ideas so far. Finally I came up with this:
As a result we have two periods. What do you think? (@lhermann I'd insert both expiry dates in the history API and according to the user who requested it if you like.)