[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021486#comment-16021486
]
Sebb commented on WHIMSY-63:
OK, fixed.
The dates should appear in the file shortly
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021444#comment-16021444
]
Sebb commented on WHIMSY-63:
It would be very easy to add the date to the existing file, though of course it
would get somewhat bigger.
Given that there are already optional entries in the output, I would hope that
adding a new field won't cause any problems.
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021363#comment-16021363
]
Nick Burch commented on WHIMSY-63:
--
The use case is to power http://community.zones.apache.org/map/years/ without
needing lots of manual work to update
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021349#comment-16021349
]
Sebb commented on WHIMSY-63:
I am curious to know what the use case is?
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021345#comment-16021345
]
Nick Burch commented on WHIMSY-63:
--
Adding to the existing file is fine with me, I have a feeling someone somewhere
wasn't so sure, but it was a while ago and I might be confusing it with
something else related...
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021336#comment-16021336
]
Sebb commented on WHIMSY-63:
Doesn't look like it.
The overides are in the file
https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob;f=lib/whimsy/asf/person/override-dates.rb;hb=HEAD
and the data is applied in ASF::Person::createTimestamp():
https://gitbox.apache.org/repos/asf?p=whimsy.git;a=blob;f=lib/whimsy/asf/person.rb;hb=HEAD#l89
However there does not seem to be a JSON file that includes the createTimestamp.
At present public_ldap_people.json only includes:
- id
- name
- URLs
- fingerprints
- noLogin
Is there a need for the overrides to be available separately?
It might make sense to add createTimestamp to the existing output.
> 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
> Components: PublicData
>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.15#6346)
[jira] [Commented] (WHIMSY-63) Provide a feed of account creation dates with corrected data
[
https://issues.apache.org/jira/browse/WHIMSY-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16021244#comment-16021244
]
Nick Burch commented on WHIMSY-63:
--
Did we ever add a generated json file to expose this? (A quick grep suggests
not). If not, any thoughts on what to call the file, so I can add it?
> 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
> Components: PublicData
>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.15#6346)
RECOVERY: whimsy.apache.org (whimsy.apache.org (https)) is back up!
Hi there! The service at whimsy.apache.org (whimsy.apache.org (https)) seems to be back in working order. With regards, Ping My Box - https://www.pingmybox.com/
ALERT: whimsy.apache.org (whimsy.apache.org (https)) is DOWN!
Hi there! The service at whimsy.apache.org (whimsy.apache.org (https)) appears to be down from multiple locations around the world. The exact error is: Error component: response Error code: Internal Server Error or equivalent bad message received: HTTP/1.1 400 svn iclas ["svn: E175002: Unexpected HTTP status 400 'Bad Request' on '/repos/private/!svn/rvr/76850/documents/iclas'"] Debug output: [Tue May 23 09:25:17 2017]: Initialising socket [Tue May 23 09:25:17 2017]: Looking up hostname whimsy.apache.org... [Tue May 23 09:25:17 2017]: Connecting to 54.91.229.41:443 [Tue May 23 09:25:17 2017]: Connected, sending HTTPS payload. [Tue May 23 09:25:17 2017]: Analyzing server certificate [Tue May 23 09:25:17 2017]: Saving certificate data [Tue May 23 09:25:17 2017]: Reading response header from server [Tue May 23 09:25:17 2017]: Caught exception: Internal Server Error or equivalent bad message received: HTTP/1.1 400 svn iclas ["svn: E175002: Unexpected HTTP status 400 'Bad Request' on '/repos/private/!svn/rvr/76850/documents/iclas'"] With regards, Ping My Box - https://www.pingmybox.com/
