[Linux-aus] Recent mailing list discussions

[Joel Addison]

> On 16 Oct 2022, at 17:34, Simon Lees via linux-aus <linux-aus at lists.linux.org.au> wrote:
> 
> Hi,
> 
> On 10/16/22 12:03, Kathy Reid via linux-aus wrote:
>> On 16/10/2022 11:32 am, Simon Lyall via linux-aus wrote:
>>> I am reminded of a discussion a few months ago where one of the PGSD told off the rest of the list for not volunteering to help, when there had been no indication that any help was needed or welcome. 
>> As the "teller-offerer" referenced above, I offer the following:
>> "There were no bids received for LCA2023."  - Russell Stuart, this list, previously.
>> Call for bids for a hybrid conference for LCA2023, April 2021 by Sae Ra Germaine, published to this list.
>> https://lists.linux.org.au/pipermail/linux-aus/2021-April/023729.html
>> "Ways to help Linux Australia", in "What does Linux Australia do all year?", a presentation at LCA2022 by Sae Ra Germaine and Julien Goodwin, Council Members of Linux Australia 2021-2022
>> https://youtu.be/ektSl_d0F6Q?t=1504
>> "We have unfortunately relied on a small pool of return volunteers to help run conferences, be part of sub-committees, be on Council but we need to do more and we need to do better. Burnout is all too common in our industry and we must do our best not to add burden onto our volunteers giving us what precious time they have left for us. There will always be a component of variable capacity amongst Council and it’s subcommittees. We will take what we can get from people to help us but we need to recognise that we are human, we are volunteers, balls will be dropped and you know what. That is completely ok."
>> - President's Report by Sae Ra Germaine, Linux Australia Annual Report 2021-2022 pp. 7-8
>> https://linux.org.au/wp-content/uploads/2022/01/annual-report-2022-combined-hires.pdf
>> ---
>> The "PGSD" are burning out. They've taken measures, admirably, to reduce that burn out, such as reshaping a hybrid conference to be manageable while safeguarding the community's health, and STILL deliver, with the best of intent, for this community. And what do they get for their efforts? The threads on this list that accuse of them of a lack of transparency. That accuse of them of betraying the values of the organisation they're pouring their unpaid *free* time into.
>> At the risk of this being branded another "telling off" - and echoing Matt Cengia's very wise words - if you don't like how things are run, or what is being done, then:
>>  * Stand for LA Council at the next AGM
>>  * Volunteer on a Subcommittee of LA Council.
>>  * Stand up a Subcommittee for an alternative event, and run the Event
>>    That You Want To See Happen.
>>  * Volunteer with Everything Open, when the Calls for Volunteers comes
>>    out.
>> But let's stop adding work, noise, cognitive load, and emotional labour to the people who are actually getting stuff done. Because these threads are not worthy of their time, their efforts and their energy *in service* of this community.
> 
> While I agree with much of the sentiment here having spent several years on boards of various open source projects i've learned that as much communication as possible is key, while understanding that sometimes there are very good reasons not to communicate certain things.
> 
> My perception (and therefore I presume others) based off the communication we've received this year, especially the thread in June was that everything was ok and lca 2023 would be happening somewhat as previously. As such I found the announcement of a new but similar seeming conference with a different name and format and no mention of LCA somewhat a surprise as it seems did many in the community.
> 
> Personally I believe that we probably wouldn't have been as much of a shock / surprise to people if there had been a much earlier announcement maybe once the proposal was accepted, along the lines of As we have received no expressions of interest to host LCA 23, we are now looking at holing a conference with similar goals but a different structure and in a different time frame if anyone would like to help being involved in organising please reach out to us. Maybe even asking for feedback then wading through the inevitable flamewar to see if there is a consensus from most parts of the community (Unfortunately I know how unpleasant this step can be and can understand why people may not really want to do it).
> 
> Finally I have the greatest respect for everything the board is doing as someone who's been on a board that oversees other conferences and communities I know the work and effort required, if there were more hours in a day LA is something i'd certainly contribute more too but as i've learned over time there is only one of me and I need to choose which projects get my time very carefully.
> 
> Anyway if nothing else I hope its something people can learn from, I look forward to hopefully seeing you all in person or online at EO
> 
> Simon



Thank you for your points Simon. I agree we could have done some things differently, and hindsight helps immensely with that.

The announcement timing overall was later than we would have liked, but was done as soon as we knew everything was in place to proceed. Booking venues takes a while to sort out, and my responses earlier in the year about having details soon was because I thought we were close to the end of the process, but as happens there were further changes that needed to be made on a number of occasions before everything was locked in. The last thing we wanted to do is announce the conference and then run into an issue meaning we couldn't follow through.

Just like many people in the community, the Council is comprised of members who are all very busy. We worked as fast as we could to get everything planned out ready to announce. We've done the first part now, and the team is now getting on with the job of opening the Call for Sessions. 

We look forward to seeing you at Everything Open, in person or online.

Joel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.org.au/pipermail/linux-aus/attachments/20221016/ced8e746/attachment.html>