Beautiful summary, Flavio, especially the points about creating new PTL's.
It's the bus-number argument: How many people have to get hit by a bus for
the project to falter? It's best to have a backup.
Also: Being a PTL is a full-time job.
>From working with current and former PTL's, I've noticed
Very well said. Thank you for this.
Kevin
From: Flavio Percoco [fla...@redhat.com]
Sent: Wednesday, September 09, 2015 8:10 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [all] Something about being a PTL
Greetings,
Next week many
Greetings,
Next week many folks will be running for PTL positions and I thought
about taking the time to dump[0] some thoughts about what being a PTL
means - at least for me - and what one should consider before running.
Since the audience I want to reach is mostly in this mailing list, I
Flavio, thanks for sending this out. I agree with everything you've written
below. Having served as PTL for 3 cycles now, I can say it's very
rewarding, but it's also very exhausting and takes an incredibly thick skin.
Before jumping in and throwing your hat into the ring (especially for a
large
+1 Fantastically well said. I'd encourage all current and potential PTLs to
take these words to heart.
> I believe it's safe enough to say that you'll have to spend 60% to 70% of
your time upstream, assuming the porject is a busy one.
The busier the project, the closer to 100% this becomes. For
