- Check in on Ed's progress on the membership database
- Talk about AGM resolutions (bank card / constitution / committee stacking)
- Post-RailsCamp update
- Was the RailsCamp inventory tracked?
- Did we find a volunteer for the developer survey?
- How did we go with adding articles to the app?
- Bank Card resolution - Secretary + Treasurer to have access to bank card details + reissue the card in the organisation's name.
- Annual statements for 2013, 2014 and 2015 - Ryan
- Permissions on Slack, Google & 1Password - Lauren
- Streamlining onboarding process - Lauren
- Goals for the coming year - Lauren
- Membership database - Tom
- Communication & Infrastructure - Andre
My proposed goal for the term: Communication and Infrastructure.
Why?
My original goal for the term (as Lauren knows) was to restructure Ruby Australia to minimise operational overhead and increase community involvement. No matter how much I want it to happen it is doomed to fail, as there are missing fundamentals. I want to run while we are still crawling.
I want to focus during my term on providing infrastructure for the community. In my opinion the core of our community is communication and I'd like to focus solely on that. This is an ongoing problem which I was observing for years.
Good communication is the base of any community. It is the glue which holds everything in place and doesn't allow to fall apart.
Unfortunately communication in a community suffers from diffusion of responsibility. It's everybody's responsibility and as a result it's nobody's responsibility.
That's why I believe RubyAU should take leadership on improving communication within organisation and the community as a whole.
"Communication" might not sound as obvious goal for RubyAU, but with all my experience and knowledge I can't think of anything more important than it.
"Communication" is a big project but to give you some perspective, there are three parts to it: ref
Why should you trust me?