Re: 5.12 release: congratulations and post-mortem

Paul Brown <[email protected]>
Newsgroups gmane.comp.kde.events
Organization KDE e.V.
Message-ID <2604680.dqGaXg2SEI__4770.53902945972$1517938378$gmane$org@linux-lpbb>
On Tuesday, 6 February 2018 16:54:19 CET Nate Graham wrote:
> Congrats on a fantastic release of Plasma 5.12 everybody! People are
> really gonna love it.
> 
> The release process was a bit rockier than expected, and I thought I
> might do a post-mortem to see how we can make the next one smoother:
> 
>.
>.
>.
>
> Thoughts?

- Create teams with a clearly designated team leader for tasks that are 
currently done by one person to avoid bottlenecks and delays.

I'm thinking of video-creation, social-media post creation, announcement 
composition, etc. Like that, you alleviate the workload of the team leader 
with researchers and "elves" than can create assets needed for the completion 
of the task.

Also, if the team leader, God forbid, should become unavailable for any 
reason, the rest of the team can pick up form where the team leader left off 
and deliver.

- Establish strict deadlines for suggested changes to media (texts and videos) 
and strictly stick to said deadlines.

[EDIT: Ivana has also suggested this, but here are my thoughts too.]

So when the next-to-last draft of the announcement text or the video is done, 
it is submitted to the peers. Peers then have say, 48 hours or whatever to 
suggest/request changes.

Once the window for requests is closed only proofreading and minor corrections 
should be allowed. 24 hours before the release, no changes should be allowed 
at all.

This would avoid the last minute hacks that are so error prone, as well as the 
"too many chefs" syndrome, that leads to everybody trying to push their own 
preference on the media.

This requires that all media is available quite in advance of the launch. But 
this should be the norm anyway.

Paul
-- 
Promotion & Communication

www: http://kde.org
Mastodon: https://mastodon.technology/@kde
Facebook: https://www.facebook.com/kde/
Twitter: https://twitter.com/kdecommunity
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCAAdFiEEoXbL8WR1l3/5c867NTv7CdPS2FoFAlp55yoACgkQNTv7CdPS
2Fph6wf/UfuugUizMHB3Gjx/+L8mEtZxmTFVTgYIoXNNPEnsZL+c0y6ZqA+ApkKn
i43Az6JuScBhtPMQun33ufirDo87e1oGPYiVlrePy9wJpxePFPtVwSxuUR5UDXF8
gTLikLR2FzpbMCcF18n8Avz3HLureROAMBxkvwjMO9BWHa6jU4IURvTMrdJQssd9
XZAxi1lBeeRvrlQgmZhfqMY9Tho5fgpmGINeHacd2ruaWBeVDRQa9ZrGYNFiaA4T
v7sVj5DKaBx/gWBZZBKYYT6eaKRFrI3Jb9+fnpo6cQxVbB0shkFLK0NqZHOYsTjM
EzcoYj4YAJRm2i037MdJnZ9s280LLA==
=pfPM
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.