7:25 p.m.
On 5/20/20 3:23 PM, Marie Nordin wrote:
Hi folks!
Mindshare had our weekly meeting, and we are going to start sending
weekly updates to the list with minutes/logs and any other pertinent
updates. This is the first one to start, any feedback on what should be
included welcome.
Minutes:
https://meetbot.fedoraproject.org/fedora-mindshare/2020-05-20/mindshare_c...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-mindshare/2020-05-20/mindshare_c...
https://meetbot.fedoraproject.org/fedora-mindshare/2020-05-20/mindshare_c...
Log:
https://meetbot.fedoraproject.org/fedora-mindshare/2020-05-20/mindshare_c...
Thanks for the list update. I shared this on IRC, but thought to share
on-list too. A historical thought on a Mindshare seat for Summer Coding:
It makes sense to me as an appointed position (e.g. like Docs, CommOps,
Marketing, etc.), but it is worth pointing out that there is not *truly*
selection steps in place for how those seats are selected.
I made up my own process for how the CommOps seat was elected within the
team… I'm not sure what other teams have. I think historically, it was
whoever raised their hand first to be here.
Something to keep in mind while thinking about creating a new seat for
the Summer Coding position. There should be probably be a documented
policy on how committee seats are adjusted in Mindshare.
Not to suggest more work… but I think it is valuable work to improve
sustainability. It also adds transparency for folks on the outside about
the mysterious ways of the Mindshare Committee. :-)
--
Cheers,
Justin W. Flory (he/him)
jwf.io
TZ=America/New_York