[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350295#comment-15350295
]
Nick Burch commented on WHIMSY-63:
----------------------------------
Details of where the date came from is on members@. Basically though, it's from
grepping the private mail archives for the account creation notices, once those
took on a common format (Subject: [NOTICE] Account created: First Last (uid)).
That means from 7th July 2004 onwards.
For those with a date currently in ldap of 20090519, but no notice email found
in private email searching, a "more likely" default of 20040701 dummy value is
set in the override file. There have been a few suggestions on ways to push
that further back working out people's actual join dates for those pre-July 04.
> 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)
