[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349606#comment-15349606
]
Sebb commented on WHIMSY-63:
----------------------------
Tricky choice.
The file is already one of the larger ones.
However using a separate file will increase the overall download size (local
storage will also be affected, at least temporarily) unless Whimsy creates a
new file with all the data in it.
I suppose it depends on how many consumers of public_ldap_people.json will want
the additional info.
Note: since the joining date is not the same as createTimestamp I think we
should use a different name; also there's no need for any time information in
the field. This would reduce the size somewhat.
> Provide a feed of account creation dates with corrected data
> ------------------------------------------------------------
>
> Key: WHIMSY-63
> URL: https://issues.apache.org/jira/browse/WHIMSY-63
> Project: Whimsy
> Issue Type: New Feature
> Reporter: Nick Burch
> Attachments: override-dates.json
>
>
> As discussed on INFRA-12008, the earliest {{createTimestamp}} in LDAP is
> 20090519, which corresponds with when the full LDAP import happened. This is
> problematic for things like the {{projects.a.o}} timeline +
> {{accounts-evolution.json}} data, and for the ComDev locations map over time.
> As Infra feel that maintaining the corrected creation date in LDAP isn't a
> core need, and it would be very painful to fix the current data, we should
> instead have Whimsy publish a fixed list. This would read the
> {{createTimestamp}} from ldap, and apply a correction for most (but not all)
> 2004-2009 accounts based on account creation notices. (We can potentially
> extend it later for pre-2004 accounts too)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
