This is the home of the Make Community team for the WordPress open sourceOpen SourceOpen 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!
Here is where we have policy debates, project announcements, and assist community members in organizing events.
Everyone is welcome to comment on posts and participate in the discussions regardless of skill level or experience.
Get Involved
If you love WordPress and want to help us do these things, join in!
We recently posted a proposal for a speaker feedback tool to be baked into WordCampWordCampWordCamps 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 TypeWordPress 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:
Considerations
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.
Pros:
Uses existing WordPress APIs, so no need for custom data structures
Easy to extend with further features at a later date
Familiar UIUIUI 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.
Cons:
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
#2 Comments
This would involve storing the feedback as comments on the session post using a custom comment type and comment metaMetaMeta 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..
Pros:
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
Cons:
Custom comment types and comment meta have historically been tricky to work with (although I think this has been largely fixed in recent CoreCoreCore 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.
Pros:
Flexibility of building things exactly how we want it, in the most performant way possible
UI can be as optimised as possible
Cons:
Lots of development hours for planning and building
Dashboard UI would likely be unfamiliar and less predictable
Custom database tables on a large multisiteMultisiteMultisite 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.https://codex.wordpress.org/Create_A_Network. instance can be unpredictable
Questions and Feedback
With all of that in mind, please comment with your thoughts on the following:
Which data structure do you think would be a good fit for session feedback?
Is there anything further that you feel should be included in the feedback form for attendees?
In the past, the only ways we have gathered feedback from WordCampWordCampWordCamps 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:
Surveys are sent out after the event and therefore don’t usually have good response rates.
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.
The default survey does not collect very much detail about session content and presentation delivery.
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 URLURLA specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org, like <year.cityname.wordcamp.org/feedback>
The schedule page could have a ‘Feedback’ button on each displayed session.
Possible requirements worth some discussion:
Because anonymous feedback is more likely to include abuse, should the feedback tool require users to be logged in?
Should there be an automated way to report abuse to the Community Team?
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?
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?
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:
Emojis
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.
Ratings
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.
Mockups
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 WordPress.orgWordPress.orgThe 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. https://wordpress.org/ profiles
Add feedback to WordPress.tv sessions
Recommend other talks to attend (or watch on WordPress.tv) after giving feedback
Questions and Feedback
What formats of feedback should we provide (emojis, ratings, text, etc.)?
Do we encourage only positive feedback?
Should responders be logged into WordPress.org in order to leave feedback?