Tim Parenti as backup TZ Coordinator?
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily. Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
On 2020-05-20 16:03, Paul Eggert wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
++
+1 On 5/20/20 6:03 PM, Paul Eggert wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
-- Kenneth Murchison Senior Software Developer Fastmail US LLC
On 2020-05-21 06:03:45 (+0800), Paul Eggert wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
+1 Great idea. Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
On 5/20/20 3:03 PM, Paul Eggert wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
I haven't actually worked with tzcode or tzdata in over 15 years, but it is a topic that still interests me, so I am still here. If my opinion counts for anything, +1 alan
Paul Eggert said:
I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
I don't have any specific opinions about Tim, but succession planning is a good idea and I'm glad to see it's happening here. -- Clive D.W. Feather | If you lie to the compiler, Email: clive@davros.org | it will get its revenge. Web: http://www.davros.org | - Henry Spencer Mobile: +44 7973 377646
+1 On Wed, May 20, 2020 at 6:04 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
On Wed, May 20, 2020 at 6:04 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
Another +1 from me, FWIW. +--------------------+--------------------------+-----------------------+ | Paul Goyette | PGP Key fingerprint: | E-mail addresses: | | (Retired) | FA29 0E3B 35AF E8AE 6651 | paul@whooppee.com | | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette@netbsd.org | +--------------------+--------------------------+-----------------------+
On 20 May 2020, at 23:03, Paul Eggert <eggert@cs.ucla.edu> wrote:
Tim Parenti's recent emails to the list reminded me that I'd long been meaning to nominate him to be my backup as TZ Coordinator. We should have a backup in case I am no longer available due to retirement or whatever, not that I'm planning to retire any time soon. I would like to start by giving him commit privileges to the development repository on GitHub, so that his contributions can become part of releases more easily.
Tim has been a longtime and substantial contributor to tzdb, as evidenced by his detailed and careful patches. Although he's mostly worked in the tzdata area, he's also proficient on the code side, as his recent patch proposals demonstrate. He and I have corresponded by email about this and he's indicated his willingness to take on the responsibility. I'd appreciate reactions to Tim's offer to be backup; please respond within the next week.
+1 jch
Last month I proposed Tim Parenti as a backup coordinator and the consensus was pretty much unanimous. He is now listed as a collaborator for committing to the development repository. The idea is that he can circulate patches on this mailing list and commit them directly, in the style that we've used in the past for patches from me. I'd like to thank him again for volunteering, and am looking forward to more patches from him.
This is great news. Thanks for stepping up, Tim! -Matt ________________________________ From: tz <tz-bounces@iana.org> on behalf of Paul Eggert <eggert@cs.ucla.edu> Sent: Thursday, June 25, 2020 3:23:24 AM To: Time zone mailing list <tz@iana.org> Subject: Re: [tz] Tim Parenti as backup TZ Coordinator? Last month I proposed Tim Parenti as a backup coordinator and the consensus was pretty much unanimous. He is now listed as a collaborator for committing to the development repository. The idea is that he can circulate patches on this mailing list and commit them directly, in the style that we've used in the past for patches from me. I'd like to thank him again for volunteering, and am looking forward to more patches from him.
This has now been made official by the Internet Engineering Steering Group. Thanks again for volunteering, Tim.
participants (12)
-
Alan Perry -
Brian Inglis -
Clive D.W. Feather -
Guy Harris -
John Haxby -
Ken Murchison -
Matt Johnson-Pint -
Michael H Deckers -
Patsy Griffin -
Paul Eggert -
Paul Goyette -
Philip Paeps