<!doctype html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><div dir="auto">Hi Paul<br><br>I understand that LA is interested in capital cities right now, so it would be Brisbane target than Sunshine Coast.<br><br>Anyway I fully agree with you. Sustainability of EO is the key.<br><br>Regards, <br>Arjen.</div><br><br><div class="gmail_quote"><div dir="auto">On January 21, 2025 2:21:05 PM GMT+10:30, Paul Wayper via linux-aus <linux-aus@lists.linux.org.au> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<p>Hi all,</p>
<p>Picking up a bunch of ideas that we talked about in the LA
meeting.</p>
<p>I think the main thing we should be looking at is: how do we
build a sustainable, maintainable process for running Everything
Open conferences.</p>
<p>One idea I'd like to see is a essentially a sub-committee formed
from people who plan to run upcoming EO conferences. Some jobs,
like venues and dinners, need to be people in the location of the
next conference. Some, like treasurer and sponsorship and
volunteer coordinator, could be longer term roles with people that
could be elsewhere. Some might be an 'apprentice' or 'learner'
role - e.g. the chair for EO27 might be an assistant chair for
EO26.</p>
<p>I'm aiming for continuity, maintainability, and long term
knowledge retention.</p>
<p>I'm interested in running EO26 in Canberra; I know Arjen is
interested in EO26 on the Sunshine Coast. We don't need to fight
over this :-) I think it's more useful for us to get together and
form a group that can run EO and then work out what teams and
venue options might be available.</p>
<p>What do people think of those ideas so far?</p>
<p>Hope this helps,</p>
<p>Paul<br>
</p>
<br><p>Message protected by MailGuard: e-mail anti-virus, anti-spam and content filtering.<br><a href="https://www.mailguard.com.au/mg">https://www.mailguard.com.au/mg</a></p>
<br><a href="https://console.mailguard.com.au/ras/29vfj4MlCs/6AatmoSgLycpkR8SzKzIql/-2.8">Report this message as spam</a>
<!-- MailGuard Message ID: 678f1c20f96644 - use this number for reporting -->
<br> <br></blockquote></div></body>
</html>