Proposal Update: Speaker Feedback Tool

We recently posted a proposal for a speaker feedback tool to be baked into 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. sites. The proposal included some ideas and mockups, with a call for feedback, suggestions and questions. Thanks to @adityakane, @imath, @andreamiddleton, @hlashbrooke, @karmatosed, @iandunn, @mrwweb, @dimensionmedia, @samsuresh and @wpfangirl for their input on that post.

Based on the feedback from that post, we have some more refined mockups to share with you, courtesy of @karmatosed. In addition to that, we are looking for input on the data storage method here, so check out the mockups and details below.

Front-end views

Initial view before selecting a talk to give feedback on:

Full form view after selecting a talk:

Dashboard views

The following mockups are based on the idea that we would store the feedback in a new custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept. with each feedback item being a separate post in that type.

List table view of feedback items in the dashboard:

Single view of the feedback post in the dashboard:


The main decision that needs to be made at this stage is regarding how the feedback data will be stored. The three options are:

#1 Custom post type

This would appear as shown in the mockups above. Feedback would be stored in individual posts within a new custom post type.


  • Uses existing WordPress APIs, so no need for custom data structures
  • Easy to extend with further features at a later date
  • Familiar UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.


  • Some WordCamp sites could get thousands of feedback items for a single event, this could slow everything down and make for a very tedious UI to look through for feedback items.
  • Individual feedback items would require a click through to a new page in order to view them


This would involve storing the feedback as comments on the session post using a custom comment type and comment metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress..


  • Uses existing WordPress APIs, so no need for custom data structures
  • Easy to extend with further features at a later date
  • Familiar UI (this would use the edit-comments.php template in the dashboard
  • Dashboard comments view allows for full feedback content to be viewed in the list table, without a new page load
  • Feedback is effectively a comment, so this would be a logical way of storing the data


  • Custom comment types and comment meta have historically been tricky to work with (although I think this has been largely fixed in recent CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. releases)

#3 Custom database table

This would involve writing a custom data structure in custom database tables – the exact data structure and dashboard UI would still need to be planned out.


  • Flexibility of building things exactly how we want it, in the most performant way possible
  • UI can be as optimised as possible


  • Lots of development hours for planning and building
  • Dashboard UI would likely be unfamiliar and less predictable
  • Custom database tables on a large multisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. instance can be unpredictable

Questions and Feedback

With all of that in mind, please comment with your thoughts on the following:

  1. Which data structure do you think would be a good fit for session feedback?
  2. Is there anything further that you feel should be included in the feedback form for attendees?

#proposal, #speaker-feedback, #tools

Proposal: Speaker feedback tool

In the past, the only ways we have gathered feedback from 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. attendees about a speaker session was to use a survey/poll or collect feedback at the event via paper forms.

There are a few problems with these approaches:

  1. Surveys are sent out after the event and therefore don’t usually have good response rates.
  2. The more time that has passed since an attendee has seen a session, the less detail they might remember, which makes the feedback less precise.
  3. The default survey does not collect very much detail about session content and presentation delivery.
  4. Feedback shared in hard copy isn’t easy to share with speakers (so they can grow their skills) or track (so the organizers can compare year to year).

This is a proposal that we build a special speaker-feedback tool to collect attendee feedback that solves those problems.

Goals of the tool:

  • Collect feedback for individual sessions during the event.
  • Provide easy access to feedback to the WordCamp organizers and speakers.

Where could it live?

  • The feedback tool could be accessed at an easy-to-remember URLURL A specific web address of a website or web page on the Internet, such as a website’s URL, like <>
  • The schedule page could have a ‘Feedback’ button on each displayed session.

Possible requirements worth some discussion:

  1. Because anonymous feedback is more likely to include abuse, should the feedback tool require users to be logged in?
  2. Should there be an automated way to report abuse to the Community Team?
  3. Would it be helpful for organizers to be able to edit the text-based feedback, so as to remove abuse, slang terms, confusing content, and/or to correct spellings before sharing with speakers?
  4. Should there be a way for the feedback to be made public, and if so, should it show up anywhere other than in the comments on each individual Session?
  5. Should there be a way to export the feedback, and should feedback be included in a requested privacy export?

Feedback Formats

Feedback could be given in a few different ways – either on their own or as a combination:


  • Pros: Simple, standardized way of showing how an attendee felt about a talk. Encourages positive feedback.
  • Cons: Could come at the expense if useful critical feedback.


  • Pros: Can be provided quickly. Usually allows for more accurate sentiment toward speaker sessions.
  • Cons: Can be easily skewed either way. Lower ratings without proper feedback are not very useful.

Free text

  • Pros: Would encourage attendees to be more thoughtful. Should provide more actionable feedback for speakers.
  • Cons: Some attendees will not be willing to provide more lengthy feedback, or they may take a longer time to submit it.


Here are some very early speculative mockups thanks to @karmatosed

Version One

Version Two

Possible Future Additions

  • Feedback content could be added as “testimonials” for sessions
  • Allow speakers to add feedback to their The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. profiles
  • Add feedback to sessions
  • Recommend other talks to attend (or watch on after giving feedback

Questions and Feedback

  1. What formats of feedback should we provide (emojis, ratings, text, etc.)?
  2. Do we encourage only positive feedback?
  3. Should responders be logged into in order to leave feedback?

#proposal #tools

Proposal: clearer WordCamp and WordPress chapter meetup logo guidelines

There have always been some casual recommendations  for how the WordPress logo should be incorporated into logos for WordCamps and WordPress chapter meetups, but we’ve never really had an open discussion about it. Following, you’ll find a proposal from Mel Choyce, Kjell Reigstad, Sarah Semark, Mark Uraine, and Tammie Lister for how the WordPress logo should be used for official events of the WordPress open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. project. Please read through the guidelines, and share your feedback and concerns in a comment on this post.

The following pages provide some important context on the WordPress logo, logotype, and the WordPress trademarks

You don’t need to use the WordPress logo.

While you are free to include the WordPress logo, or reference the W, in your logo, you don’t need to do so.


The WordPress logo has two variants.

If you do use the WordPress logo, know that it comes in two variants: W Mark and Simplified

W Mark
W Mark

Here are some examples of the variants in use:

Say “No!” to the Fauxgo.

If you are using the WordPress logo in your 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. logo, please make sure you are using the correct WordPress logo. 

The correct logo has a higher cap height, and rounded serifs:

Don’t change the logo.

Do not:

  • Remove the ring around the logo.
  • Cut or splice the logo.
  • Skew, distort, or add 3d effects to the logo.

Don’t use the Dashicons logo icon.

The Dashicons logo icon is specifically designed for use at smaller sizes; do not use it for your WordCamp logo. Instead, use the official logo files.


Ensure that the logo has sufficient contrast.

Your logo should have sufficient color contrast to pass AA guidelines for text. You can check your design using a tool like Stark (for Sketch) or Logo Rank.

Design your logo in black & white first.

Designing your logo first in black & white is a good way to ensure that your logo will communicate effectively without color. We recommend designing your logo first in black and white, and then adding color near the end of the process.


When designing your logo for digital devices, it’s good practice to use the RGB (red, green, blue) color model. When preparing your logo for print, use CMYK (cyan, magenta, yellow, black). Screens differ from tangible paper products by emitting light instead of absorbing light. For this reason, RGB values work as additive colors for the screen and CMYK values work as subtractive colors for print.


Typography should be easily readable.

Your WordCamp name is one of the most important pieces of information, so make sure people can read it! Generally speaking, it’s best to use a relatively simple typeface without a lot of flourishes. This ensures that text is readable even at very small sizes, or when printed on a badge of which attendees may only catch a brief glimpse.

Avoid using Mrs Eaves.

Mrs Eaves is the WordPress brand typeface. It’s best to avoid using it for your WordCamp to avoid confusion with the WordPress brand.


Consider a range of users when designing.

When designing your logo, think about users who may have trouble reading or parsing your logo. Ensure your text is readable and color contrast is sufficient. It’s good practice to design your logo first in black and white, to ensure that those with color blindness are still able to understand your logo. (See also the color and typography sections.)

Ensure your logo is appropriate for all audiences.

A WordCamp is welcoming to everyone. Part of ensuring a safe, welcoming, and inclusive environment is ensuring that your logo (and other materials) are family-friendly. This means that logos should contain:

  • no sexually suggestive imagery
  • no profanity
  • nothing that would constitute implied or explicit exclusion of a group
  • no characterizations of a minority group in your area

Context and Formats

Ensure that your logo is recognizable in a wide range of contexts. 

WordCamp logos typically appear in many different places: on top of websites, on shirts and merchandise, stickers, in social media, signage, etc. Ensure that your logo is adaptable enough to be recognizable and readable in all of these contexts. Your logo should be flexible enough to work when it appears on a giant presentation screen, but also when it appears in a tiny social media icon.  

Provide the final logo in a variety of file formats for different uses.

The logo should be in a scalable vector format (Sketch, Figma, and Illustrator all produce vector graphics). The final file should also be available in the following formats:

  • .svg (preferred) or other open scalable graphics format (.eps)
  • .png (with a transparent background)

Provide the final logo in a variety of color formats.

To ensure maximum compatibility with different usage contexts, the recommended color formats for the logo are:

  • black & white
  • RGB (screen)
  • CMYK (print)
  • Pantone (print, optional)


Please share your thoughts on the proposed guidelines and how best to share them moving forward. 

#design, #meetups-2, #proposal, #wordcamps

Proposal: how to use this blog for discussions – Update

Hi Team!

In June 2018 I wrote a proposal to create some guidelines for posting on this blog and how to use it also for project management.
At the time I made the mistake of mixing up two topics on the same post, so today I am writing an updated proposal only for the first part.

Guidelines to post on the Community Team blog

I reviewed the document that I wrote a year ago. It’s open for comments, awaiting for your feedback!

Categories and Tags

A bit messy to say the least.

I did try to make sense of the categories. There were 24 initially: I deleted the ones that are not used and added one (Documentation) to post about changes in documentation, text of 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. websites, MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area. pages, HelpScout replies.

The tags situations is worse: we started with 401, I deleted all the empty ones, but I think there is ample space for making this better.

For this part of the project, I am looking for volunteers to help out: information architects, SEO experts, where are you?

Where we could put the guidelines

  • Welcome Box
  • Sticky box in the blog, very short so it doesn’t push the rest of the content too much below the fold
  • New pages related to the Welcome Pack, a project that I will pick up in the next few weeks.

Want to help make the blog better?

Please comment on the document and on this post before July 31st

And if you are an Information Architect or a SEO expert, help us make the categories and tags system more efficient so people can actually find what they are looking for!

Thank you!

#blog-posts, #proposal

Sourdough: The Local-Community Starter Kit (proposal)

Local WordPress communities could benefit from having access to a basic business infrastructure that enables ongoing, non-event community activities. A local-community starter kit like this could serve as a catalyst to further democratize WordPress community organizing.


We recently launched a non-event-specific WordPress community entity in Seattle. Modeled on similar initiatives in Kansas City and Portland, we felt the need for a virtual destination for our community that wasn’t tied to the and 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. event-management systems.

Members of our community rounded up a long-ago-registered domain name, found a web host, created a MailChimp mailing list, and launched a simple website that 1) guides folks to our local WordCamp, MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on will help you find options in your area., and SlackSlack Slack is a Collaborative Group Chat Platform The WordPress community has its own Slack Channel at sites and 2) offers a sign-up for the new Mailchimp list.

Some members of the community immediately raised concerns about the ongoing administration and governance of the new entity:

  • Who controls the domain-name registration?
  • Who has access to the website? and how do they decide which level of access other users have?
  • Who pays for the web hosting?
  • Who owns the email list?
  • Which email addresses are associated with the community’s social-media account logins and who has access to them?
  • Where do we deposit the check when a local sponsor offers to support the entity?
  • What is the entity, legally? We all know what a “community” is, but goverments and tax collectors don’t recognize it.
  • Ours is a friendly, professional, and responsive community, but what if an account holder became incapacitated? what if a key community leader moves? what if a bad actor were to get control of an account login?

These are all valid concerns, but they need not prevent a local WordPress community from creating a new entity alongside the current Meetup and WordCamp programs.


I propose exploring the feasibility of a WordPress Community Support-backed program (tentatively called Sourdough) that would provide support for the creation, development, and administration of a very basic local WordPress community infrastructure.

Much of the proposed technical and administrative infrastructure already exists as support mechanisms for the current WordCamp and Meetup community-event programs. But there would be some additional development and, possibly, staffing needs, hence the request for WordPress Community Support help.

Like any good program, Sourdough introduces at least one new acronym, the LCO, Local-Community Organizer (or LOCO, if we want to allude to the sometimes crazy-making nature of community wrangling).

Program Components

The components of the proposed basic infrastructure:

  • a new role – Local-Community Organizer – much like current event-organizer roles; vetting for this role could be fast-tracked for existing Meetup and WordCamp organizers
  • a community email address (one address for all social-media and other account logins) accessible both to the Local-Community Organizer(s) and to super-admins at WordPress Community Support
  • a domain-name registration service
  • website hosting
  • a mechanism for granting access to the community’s website, email list, Slack administration, and social-media profiles to vetted community members (such vetting could be administered by the LCO at the local level)
  • access to WordPress Community Support’s money-handling capabilities for receiving sponsor funds and paying vendors
  • a virtual inventory system (could be as simple as a Google Docs sheet) to track swag, lanyards, print collateral, and other community property, which may reside in many different physical locations

A deluxe version of the infrastructure might also include:

  • a PO box or mailing service to give the community a physical address
  • a small storage facility for leftover swag, print collateral, etc., which could also serve as a receiving facility for exhibitor shipments to WordCamps and other local events
  • a group password manager like LastPass or 1Password to more precisely and securely grant and control access to community accounts

Program Benefits

Benefits to the local community:

  • one-stop shopping for local event and other community information
  • creates a portal for recruiting into the local WP community members of the broader local community (articles on how to get involved, what WordPress is, what a WordCamp is, what happens at meetups, etc., examples of which could be collected and shared at
  • cross-promotion opportunities for existing community event programs
  • ability to build an opt-in email list of local community members who are interested in both current and future WordPress-related events, activities, and announcements
  • ability to showcase community members on the community website (directory or similar non-promotional listing, equally accessible to all community members)
  • non-promotional community blogging on topics of interest to the local community
  • create a community legacy archive documenting the background and history of the community and sharing its lore – sort of like the old “newspaper of record”
  • ability to engage event-averse introverts with a way to virtually and anonymously participate in the community
  • create virtually accessible local special-interest groups for folks not mobile enough to travel to meetups and other events (kids, seniors, disabled, etc.)
  • virtually augment the new physical Community Bazaar presence at WordCamp US
  • maintain a minimal community presence if there are not currently active Meetups or other events

Benefits to WordPress Community Support:

  • similar community-building and -nurturing benefits as existing event programs
  • proactively and preemptively manage potentially messy issues around account access and other local community-resource stewardship issues


I know how stretched for time community members are, so not expecting immediate action. I just want to get this idea out there and see what even-better ideas folks in the community might have on this subject.


Slight change in Office Hours time

UPDATE: The poll is now closed and the Tuesday/Thursday Office Hours time is now going to be 9:00 UTC (1 hour later than previously held). The sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. is updated with the correct info.

We currently hold Office Hours at the following times:

  • Mondays & Wednesdays at 22:00 UTC
  • Tuesdays & Thursdays at 8:00 UTC

As the bi-monthly Community Team chat falls at the same time as the Thursday Office Hours, we are considering moving the time of the Tuesdays & Thursdays session by 1 hour in order to help us be more effective. This time slot for Office Hours is designed to conveniently serve people in the EU and Asian time zones, so with that in mind, would either of the following times work for those of you spread across Africa, Europe and Asia:

  1. Tuesdays & Thursdays at 7:00 UTC (1 hour earlier)
  2. Tuesdays & Thursdays at 9:00 UTC (1 hour later)

I’m leaning towards option #2 as #1 will be very early for Western Europe, but I’m not sure how this would affect those further East, so please use the quick poll here to vote and weigh in with your comments on this post if you have anything further to add.
#meetings #proposal

X-posting Proposal: WordPress Community Conduct…

X-posting Proposal: WordPress Community Conduct Project
Please read + comment on the original post.

Proposal: WordPress Community Conduct Project