The purpose of this page is to determine whether a new use case for a "static datetime" should be implemented. Please add anything you think helpful for deciding the issue. Please vote below on the proposal.
What we're NOT talking about
The normal use for dates in Tiki, where dates represent a single point or period of time, which is then represented in the timezone applicable to the user, is not under discussion. Tiki already has a method of handling this case, which is used to organize meetings, etc. so that everyone knows when a single event is actually happening regardless of timezone.
What we ARE talking about
The new use case under discussion is to represent the same date and time of day, regardless of the timezone. So this is not a single point or period of time, but actually 24 different times (one for each offset from UTC). This would be used to represent when a holiday starts, for example. New Year's Day starts on January 1, 20XX at 00:00 hours in each time zone, so the later the timezone, the later the holiday starts.
How it would need to work
The date could be stored as a UTC time stamp like all other dates, but there would need to be a flag to tell Tiki that this date needs to be interpreted differently than the normal use case, i.e., to not treat it as a single point in time but rather as the same date and time of day for every timezone.
This will need to be rolled out in several places - trackers, calendar, articles & blogs (which can be published in the future) and perhaps others.
The need to flag this use case will be the weak point of implementation and could more easily lead to bugs. On the other hand, it would seem to be a basic function to be able to show a static date and time (like a holiday).
Vote on the proposals
| Accept | Undecided | Reject |
|---|---|---|
| 3 | 0 | 0 |
|
| Accept | Undecided | Reject |
|---|---|---|
| 0 | 3 | 0 |
|
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}