Meeting Summary for February 20, 2014

Full meeting transcript:

This week’s focus was WordCamps/conferences. Bolded subjects link to the point in the chat transcript when we started talking about it.

WordCamp organizer hangouts: We’ve held 4 orientation hangouts now, and while they have generally been successful, we agreed to make a few changes. First: schedule some topic-specific hangouts about things like budget, CampTix, tools, and video. Second: record one baseline hangout every month (and transcribe it) or so for those who can’t join but focus on more interaction between organizers and community team members. Andrea clarified about whether the hangouts are intended just for new WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. organizers: they’re intended for everyone, as repeat organizers will benefit from hearing about tools and practices that have been adopted since they organized last.

WordCamp Tools: It was agreed that new page templates for the WordCamp Base theme are always welcome, and that it might be nice to have more options for ways to display speakers, sessions, etc. Then we moved along to identifying other tools we might need/use for WordCamps.

Newsletters: All chat participants who’ve used a third-party tool for WordCamp newsletters said they had used MailChimp. There was concern about the security of attendee data when we use third-party tools, and general discussion about how WordCamps use newsletters as well as other methods of communicating important information with attendees (email, posting to the site, SMS). We agreed we should start with a list of the specific needs that we’re currently using third party tools to meet; WordCamp organizers can post those lists to the community site.

Accessibility: WordCamp sites should be accessible, and right now they’re not, very. @jenmylo suggested we ask the AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( team to review the themes in play as base themes, and fix those themes based on their advice; she also suggested we create a guide of baselines for CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. accessibility (contrast, etc) so organizers can meet those guidelines. I’ll post to the Accessibility P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at to ask for help.

#meeting-notes, #wordcamps