Summary: Women in WordPress

Attendees: Cátia Kitahara (discussion leader), Erica Varlese, Helen Hou-Sandi, Aaron Jorbin, Sara Cannon, Christine, Amy Hendrix, Andrea Rennick, Rachel Baker, Mika Epstein, Matt Mullenweg, Siobhan, Jane Wells

It’s not just a WordPress problem, but more men and women working in tech. Only 12 out of 100 women here. There are more women involved, how do we get them here? Don’t want to feel like we’re here just because we’re women.

Follow the ADA initiative, get more WCs to follow the guidelines and everything they set up for events.

There’s a tendency for women to do lots of work but not call attention to it; don’t brag about it. “I’ve been told I was bragging and it was unseemly and it was coming across as too manly.” To be noticed in WordPress has been to keep people from knowing I was a women for as long as possible.

What I’m hearing from other women is they don’t think they’re smart enough; even though they’re doing amazing work, they feel like outsiders. Lots of women in themes or design who actually do development say they’re not a developer.

Some stories of being treated badly in tech support when they found out they were a woman. It’s also a big problem that women stereotype and mistreat other women in professional situations. But if people don’t know you’re a woman, it doesn’t encourage other women to get involved. Work twice as hard, half the credit, and 100% of the blame.

Zero-tolerance for people with bad manners. If you can’t respect everyone you’re not welcome in the community. Etiquette file used to be linked from forums. WP forums used to have a reputation of being a bit of a snakepit. Justin Tadlock of “what was the first question you asked on the forums?” Many were what we would now see as dumb questions. You can’t know what you don’t know. The moderators have changed their attitude, to not just keep off spam but really to set a good example.

There’s a 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. Code of Conduct. For website we prefer to be positive rather than “don’t don’t don’t.” Can we shift this conversation from what other people do wrong to what can we do right? Changing other people is futile. What kind of example can I set? Might need to put more effort into remembering to project, and be confident.

Something I’ve noticed with WordCamps I’ve attended is most of the people that apply to speak are male and on the developer track. Big opportunity. Need to reach out extra to include women speakers. Demographics of wordpress.orgWordPress.org 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. https://wordpress.org/ visitors are 61% male, 39% women — for users of WP software it’s probably more even. This event (summit) skews more developer-y.

I feel pressure to speak in the developer track, but I would rather go outside of my comfort zone for a user track presentation to set that example for the community at large. If we had more women involved there wouldn’t be that pressure. Women say no to speaking invitations more than men for tech conferences. Goes back to safe zone issue, stranger danger fear. Division of household duties can make it harder for a woman to go.

Every session doesn’t need to be the latest and greatest, some users just want to know how to edit CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site.. Make it less intimidating to contribute. We get a lot of the same people giving similar presentations. Some of the exclusion isn’t necessarily gender but disposition, even the women we get tend to be a lot more assertive.

Not just having a hack day, but a contributing to WP day, rename hack day as contributing day? Lisbon had translation group, support group, documentation group, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. group. Cross-functional groups means that a lot more can get done, than if it was just isolated developers, designers, or users.

The learning curve of WP isn’t straight, it’s easy easy easy BOOM.

I think it’s hard to learn to public speak well, I struggle with it and I’ve been doing it for four years. It’s a difficult skill, and is something above and beyond just having normal confidence. A mentorship program — a huge help is teaching, when you start teaching it goes a long way to being more comfortable.

Give positive reinforcement especially when code or anything is shared. Maybe it could be important to have some numbers, from the survey or something to have more what our baseline is and track our progress (or regression) over time.

Action item: ask for gender on survey? Don’t want to put the question in people might not want to identify. Maybe on .org profiles? Male, female, a LGBT dropdown, I don’t want to say. Important for moderators on forums to make the forums a safe space, IRC, TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. Also important for WCs and meetups. There’s always that weird guy at a meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. 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 meetup.com will help you find options in your area..

I put a code of conduct in the badges for WCSF 2011, and everyone knows there’s a standard of behavior. OS Bridge has a great thing attached to their CoC that you could nominate people that are super-inclusive and recognize them publicly. Defcon had red cards, yellow cards, green cards. There are two types of people when it comes to code of conduct, those who don’t think it’s needed and have never dealt with it, and those who have dealt with it.

Proactive program to reach out to middle and high school programs for girls and women into the community, particularly on the engineering side. What are some things we could do to reach out to that group? Lots of non-profits and groups focused on this. When my kids were 12 we taught them HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. and CSS.

We haven’t had too many issues, mostly language based or language in a presentation, not usually downgrading but more objectifying from a sexual level. It’s the subtle things as much as the obvious things. We’ve also gotten feedback on women speakers who are too flirty or cutesy when presenting, not professional enough. When I see those turned away I introduce myself first to the person who was snubbed, say “probably just didn’t see you” and then re-get the speaker or person and say “this person was waiting for you and you didn’t notice them can I introduce you? This is so-and-so and from this town and really enjoyed your presentation.”

Be super-encouraging. Action item: should be everyone here should find a woman in their local community that really knows their stuff and get them to present at a local meetup.

Growth and Marketing

Note: These discussion notes are from the team reps summit the weekend before wpcsWordPress Community Support A public benefit corporation and a subsidiary of the WordPress Foundation, established in 2016..

WordPress is successful because it’s seen as friendlier than competitors. Homepage is old, but still better than Joomla, PHPNuke, etc in how we talk about ourselves. It’s more challenging than ever, though, because saying wp can do anything is not super compelling — people don’t relate to it. Specific uses — I want a site for my bakery, for my book club — are better. How do we reach constituencies, how do we keep our percentages up, how do we market to developers and overcome the perception there that wp is lame, and evangelize to people who would work in app platforms. What would help?

WordPress.orgWordPress.org 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. https://wordpress.org/ needs a facelift. Not just design, but content like /about. Old features (post revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.) are listed instead of cool stuff that is newer. Marketing the features is a good step.

Let’s have each area of wp (via contributor groups) give a synopsis to promote their section. Rep will say what is awesome about their app/section/teams, and we’ll compile them all to make a new about/features page.

The Showcase is kind of tired. It should answer the question of what wp can do. Entries should become case studies. Who worked on this site, what plugins and themes are used, is there anything special about it, interviews with stakeholders on the experience of making this site with WordPress, etc.

Let’s put videos of people using wp on home page. Show them customizing a theme, writing a post. Make the video a hero, and cycle through different videos so they are short and consumable. But before we decide how to do it, we need to decide what we are about.

What makes developers gravitate to other platforms?  We need to answer that question up front and use content to convince them to use wp.

When wordpress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ put more features on the home page, fewer people signed up. Many use it because someone told them to. Anything that slows down their getting set up is a risk.

A lot of people/devs initially hear from someone else what to use. Having a page that compares the systems would be cool. We’d need to keep up with other projects to keep info current. Let’s have an email address for if info on that page is out of date.

Our tone is playful and irreverent; we don’t pretend the rest of the world exists (a la apple/slate). We even thank Movable Type and Drupal on the about page for inspiration.

Which issues do we need to convice devs on, vs which things do end-users care about? We need separate convincing paces, not overwhelming info on one. Two home pages/landing pages, a developer portal.

Jekyll has been taking off. jQuery uses wp for everything, but if they hadn’t always used us, they would likely be on githubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ pages on jekyll. Making wp sexy enough for devs to use is important. Caching — not great on wp, but good on jekyll. Devs need scaling info.

We focus on ease of use and SEO for users. Focus on security, deployment/staging, APIs, etc for devs. We should promote examples of cool devs/projects using wp (like jquery, nasa, math blogs).

What about how to market to non-traditional blog users? Corporate, etc.

Hello world is the first post. Make the default view clearer that it’s not just a blog. They may not know where to go next to make stuff in their site. New user panel is going toward that (that’s a breakout discussion). Important to make sure the support materials don’t lose the threads started in the marketing. Make priorities clear. Jetpack is an attempt at unified marketing, user experience, and support.

We should also make sure people are in the right place. “I just want to get started” — Direct them to the right host.

When they’re on .org, we convince them to look into something, but then they have to pick a host. What if we could do the install while right on .org, create hosting account, site title, etc. The nice part about passing off early is that user associates early with the third party, but we can ameliorate that with language and branding within the ux flow. We could improve the conceptualization of .com/.org/host/etc. We could email them — communications could change to tell them the host vs .org usernames etc. Whatever we do, should be careful not to confuse .com/.org more than it already is.

We’ve talked before about using .org as a dashboard. We could theoretically check the login against their site.

Let’s get back to marketing and come back to NUX as breakout. Use best practices based on .com that hosts should follow.

Events. Booth at bridal conference, comic-con, auto shows, outreach at non-tech events. More wp illuminati speaking at dev conferences (not WCs). Need to get Events on .org site instead of on separate domains.

In addition to WCs and meetups, educational events, local wp training.

A friendly face can overcome a lot of difficulties and make up for anything confusing at in-person events.

How do we tap into local groups to evangelize?

Something to remember (as we talk about guidelines for official meetups and WCs) is  that people with less desirable practices/intents are still getting people on WordPress. Look at Thesis.

Re WCs, some people still think ,”Isn’t it kind of cheap?” so it’s not taken as seriously.

How can we make WCs more unified? What’re the important common threads to ensure?

We should start doing video testimonials/commercials. WP “rockstars,” celebs who love WP, average people.

Where do we go after the home page? Where are people going on the site? Top pages on .org  are: home, themes, download, plugins, support, codex for installing wp.

Should there be marketing for mobile apps? Yes. Let’s get them on the Download page at least.

Action item: Each team comes up with one great thing about wp that is a marketing blurb. One sentence per team, to be used in new features page.

What the Meetup?

Attendees: Aaron Jorbin – Notes, Sara Cannon – Leader, Erica Varlese, Lisa Sabin Wilson, Ryan Duff, Ryan Imal, Brandon Dove, Dre Armeda, Michael Torbert, Jane Wells, Andrea Middleton, Remkus

Brief Chat about the different MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. 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 meetup.com will help you find options in your area. Groups Present:

Sara Cannon – WordPress Birmingham Meetup, 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. Birmingham
Although the WordCamp is large, the meetup group is tiny. 12 regular ~30 – over 300 for WordCamp (destination conference in the south: people travel) Wants to learn how to expand and have good programming

Brandon Dove – WordCamp Orange County, OC WP Meetup
Active contributor – virtual and in person meetup – 2 meetups a month (1 dev, 1 user) – active members 150 – regularly 40-50 people. Their events are live streamed, have different people and interests, and is free, not run through the Foundation / Meetup.com. They use a private Facebook group (must be accepted and verified) and have found that people are more active in conversation on Facebook is better then in person. Anyone that asks gets answers quickly. In Brazil – private Facebook is more active for support than forums.

Ryan Duff – Harrisburg PA Meetup
The area has a lot of back and forth & can’t get any traction. There is one meetup group in the area that does well becouse it moves it around. The area that the airport serves is 6-8 cities each with their own identity. People won’t get in the car and go far if there is weather – he sometimes has problems getting anyone to come. He knows there are WordPress users in the area: but might only get 5 maybes: people can’t commit. He uses meetup.com – but believes geography is the biggest challenge & persistance is the problem.

Aaron Jorbin – One of the organizers of the DC meetup.
DC has about 1,100 members who meet once a month with between 70 and 100 people at all meetups. Occasionally they partner with the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php group. They made the decision to be a user group, so keeps it pretty user-centric. If it’s something that’s more dev-centric they partner with the PHP group rather than fill their meetups with it. There is not yet a WordCamp, but they do host an annual 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. barbecue.

Ryan Imel – Fort Wayne Meetup
Fort Wayne is similar to Birmingham – 10 to 15 people that regularly come – He’s been working on getting more organizers and that has been great for the group.

Lisa Sabin Wilson – Milwaukee Meetup, former 2x WC Chicago organizer
They host about 25 to 30 people. Milwaukee used to be a very Drupal city, but now it is getting more diverse – tehy have 4-5 organizers and around ~100 people at the WordCamp. WordPress is getting bigger and bigger each year.

Erica Varlese – NYC – not an organizer but interested in helping more.
NYC has diverse topics and is large and can be overwhelming. When they had the large WordCamp in 2009 – it was big and helped really grow the community.

Michael Torbert, Raleigh Meetup & WC Organizer
They use Meetup.com. They have 600 in the online meetup group roster: but 1/2 never have been.  Between 30 to 40 people will attend each meetup. When Jane was there it was very popular and they had to turn people away because the venue was too small. They usually have 2 meetups a month. One is classroom “teaching” oriented and the other is at the semper fi lounge and is networking oriented.

Dre Armeda – WordCamp San Diego
He is starting a group in Riverside since he moved inland – So Cal is popular and there are many meetup groups going on there.

Andrea Middleton – Portland
She doesn’t lead the meetup, but helps with organizing WordCamp – not very active in meetup (time/day of meetups).

Jane Wells – Tybee Island, these are her people
Before coming to Tybee: She was in NYC  and before that in SF – She organized WordCamp Savannah. There was no Savannah meetup group. She talked to group about hosting it, and then after a year just said screw it and started one Meetup.com and got 15, then 30, then 45. At the same time she started a  meetup group on Tybee, with about the same number of people at each. The first one had 12 people show up (tybee), 8 or 9 (Savannah). The first meetup was about what the meetup should be: they decided to have multiple types of meetups: 1 night, no presentations, just coworking. They wanted to grow the people doing stuff and not just be people showing up to learn. They also have one at lunch time and demo what they are doing or watch a wordpress.tv video and then talk about it. The WordCamp really inspired people in Savannah, that is how most people learned about WordPress.

Discussion:

  • Meetup.com helps with publicity and drawing a larger untapped audience in some areas
  • Sandwich boards outside helped bring people in.
  • Putting up signs just helped bring people in.
  • Outside the US/Canada primarily doesn’t use meetup.com, they use FaceBook.
  • Centralizing the events will help know what else is going on.

We have a resource for WordCamps, we don’t have resources for meetups. Want to bring more stuff over to WordPress.orgWordPress.org 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. https://wordpress.org/ and make it more visible. Surface Meetups on WordPress.org so if we know your zip code, we can show on the page when the next meetup in your area is.

One challenge of being a very successful meetup is the need to divide things up. If there are 800 people, you are basically cattle moving between rooms. 300 is the highest comfortable size for a WC. Multiple WordCamps in a year.

Challenge: What are we going to talk about at the meetup? What kind of programming do we need to have? One answer is to Skype in a group to talk about the things that you don’t know. Have a pre-recorded presentation and a google hangout.

In one meetup, when it started there were 3 presenters — they were the experts. All of the attendees are presenting regularly: but some are not as experienced as others, so sometimes there are issues with consistency of quality. Challenge: Getting locals over the fear of public speaking, upping the quality of presentations.

There should be a good ratio of local and non-local speakers. If someone is not an expert, but they have the time to give the presentation, w can get them in touch with people who have given similar presentations for help.

Challenge: Some leaders are not well versed in teaching new, new, new people how to use WordPress. Are there resources or ways to teach that? We need to share curriculum. Or have a “WordSchool” focused on teaching new people. Or just suggestions for WordPress news to share each month: A sales flyer.

Challenge: Not everyone pays attention to tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/., so we need to educate our groups on coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development. Meetups gives people an avenue to talking about new core features.

Two great Meetup Ideas from DC: 1) “My favorite pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party.” lightening talk. 2) Upgrade-a-thon!

ACTION ITEM: make.wordpress.org/events – get organizers to start writing best Meetup practices.

#education, #meetup, #wordpress-meetup-groups

Summary: Multi-language Plugin(s)

Re the action for me (Simon Wheatley) to 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. my multi-language pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. as part of the “i18n improvements” session.

The Babble multi-language plugin we wrote for and used on Free Speech Debate, is now available on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ at https://github.com/simonwheatley/babble. The plugin handles translating posts in all post types and terms in all taxonomies, though the translation of terms badly needs a workflow. Translation of widgets and menus is currently not covered by the plugin, and in the future I’d like to see a much more “work queue” style system for the translation teams in the various languages.

Please feel free to comment, raise issues, fork, submit pull requests, etc.

If you like the approach of using custom post types and taxonomies to store the translations, it’s also worth looking at the Multi-Language Framework plugin by HackLab.

Post-event Survey Results

63 people responded to the post-event survey. Wish it had been more, and I’ve left the survey open if any participants want to fill it in now, but here are the results as they stand.

Some quotes that represent the majority of the overall feedback:

“Having the smaller groups made it possible to actually have more than a passing conversation with people. I truly feel as though I got to know these people.”

“It was absolutely incredible to be in the same place as all the attendees, a real and genuine thrill and honour.”

“[I] have a lot more momentum to move forward with getting involved than I had previously.”

“Really good to get together in person and discuss all the things that tend to go unsaid or have never been verbalized at all.”

And now, the actual survey results!

Overall, how would you rate the community summit?
Fantastic; exceeded my expectations — 71%
Good; met my expectations — 29%
Poor; didn’t live up to my expectations — 0%

What was the main thing you wanted to accompish by attending the summit?
Most answers here centered around meeting people face to face and building stronger bonds than have been built online, and increasing communication. Second runner up was around figuring out how to contribute something valuable to WP and/or get more contributors interested in specific areas (i18n, etc).

Was that achieved?
Yes, completely — 62%
Partially, but there are still open issues — 37%
Nope, not at all — 2% (that’s 1 person out of 63)
Most of the comments noted that if the goal had not been completely achieved, progress was being made as a result of the summit discussions and would hopefully achieve it soon.

The one person who said “Nope, not at all” had this primary goal: “I wanted to hear, discuss, dissect, and propose high level solutions to places where WordPress isn’t a market leader; especially outside of the US.” I’ll follow up with this person to get more feedback on why they think this goal wasn’t achieved.

The unconference format was new to many people. Had you ever participated in an unconference before?
No, this format was new to me — 44%
Yes, I was familiar with this format — 38%
Yes, but previous unconferences were more like regular presentations, not discussions — 17%

What did you think of the unconference format as it was used here?
Fantastic; exceeded expectations — 68%
Good, met expectations — 27%
Poor, didn’t meet expectations — 5%

Which discussion groups did you participate in?
Fairly even listing of all the discussions.

Of the discussions you participated in, which was the best/most useful, and why?
This was pretty evenly distributed, and looking at who chose which topics, they were the ones closest to their original goals.

Many people had informal discussions in between sessions. Were any of your informal discussions about a topic that didn’t make it onto the unconference board that you think belonged there?
Most of the answers to this question were actually sessions, just ones that the respondent didn’t attend. Ones that weren’t on the board:

  • EU Cookie Law
  • WordPress failing to break into Enterprise, Education and Government.
  • Settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.
  • GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/ mirrors for 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. parts of the WordPress.orgWordPress.org 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. https://wordpress.org/
  • GlotPress release milestone/features.
  • BuddyPress

What did you think of the size of the summit (about 100 participants)?
Perfect size — 95%
Too big — 5%
Too small — 0%

How many participants did you interact with by the end of the summit?
I met most, but not all — 63%
I met many people, but probably fewer than half the people there — 32%
I met everyone — 3%
I didn’t meet that many people — 2%

How many people (ballpark) did you meet in person for the first time?
Mean: 35
Median: 30
Mode: 20
High Number: 99
Low Number:0

How many people did you meet that you hadn’t even encountered online before?
Mean: 14
Median: 10
Mode: 10
High Number: 40
Low Number: 0

Were there any people you really wish had been there to represent a specific point of view?
Everyone mentioned by name had been invited to the summit, but didn’t ultimately attend for one reason or another.

How do you feel about the duration of the conference?
Too short — 71%
Just right — 29%
Too long — 0%
Most comments said 2 days would be good, with informal days optional afterward.

How long did you stay in town?
Three+ extra days — 30%
One extra day — 29%
Just Sunday — Tuesday — 22%
Two Extra days — 19%
Many wished they’d stayed longer.

What did you think of Tybee Island as the location?
Good; met my expectations — 48%
Fantastic; exceeded expectations — 44%
Poor; did not meet my expectations — 8%
46 comments on this one. A number of people (esp int’l) thought we should have gone to a hub city instead for easier travel, though most liked the actual place in terms of being there. Others thought the semi-remoteness helped make the event better, citing accidental meetings, restaurant take-overs, and cottage shares as positives. Overall thread noted a more retreat-like atmosphere and fewer distractions was good. May want to try a hub city next time and compare.

What did you think of the venue (Tybee Island Wedding Chapel)?
Good; met my expectations — 67%
Poor; did not meet my expectations — 17%
Fantastic; exceeded expectations — 16%
Comments cited that the downstairs area got too noisy, more bathrooms would have been good, and that the wifi issue was lame (most acknowledged that it wasn’t a dealbreaker since we were doing all discussions). Note: I followed up with the venue owner afterward. They apparently did get 3 access points to carry up to 180 simultaneous connections as requested, but had not installed them. Hmph.)

What did you think of the food?
Pizza at Huc-a-Poo’s
FANTASTIC — 25%
GOOD — 67.31%
POOR — 7.69%

Coffee/muffins before start
FANTASTIC — 52.46%
GOOD — 47.54%
POOR — 0%

BBQ Lunch
FANTASTIC — 59.68%
GOOD — 33.87%
POOR — 6.45%

Dinner/Party at Crab Shack
FANTASTIC — 44.44%
GOOD — 47.62%
POOR — 7.94%

Should we make this a regular event?
Yes, definitely — 90%
Maybe, depends on details — 10%
Nope — 0%

What suggestions do you have for improving the event in the future?
Most comments were around scheduling a 2nd day, talking more about topics and format in advance, and location. Overall people seemed very happy with the event.

Summary: Multisite Roadmap

Participants: Ronnie Burt, James Mowrey, Jake Goldman, Ron Rennick, Frederick Townes, Andrew Nacin, John James Jacoby, Pippin Williamson, Ptah Dunbar, Scott Taylor, Ryan Boren, Cristi Burcă, Peter Chester.

The roadmap so far has looked like this:

3.0 – initial WPMU merge
3.1 – a proper network admin area
3.5 – several enhancements (no more ms-files.php, being able to install MS in a subdirectory)

There was a big gap between 3.1 and 3.5.

There are two main, competing usecases for 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. Advanced Administration Handbook -> Create A Network.:

  1. a network of independent sites (like wordpress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/)
  2. a small number of tightly controlled sites

Since the first case is the original reason why Multisite was created, it covers it pretty well. It doesn’t do so well in the second case. To separate the two use-cases, we could have a “controlled network” flag: when set, automatically enable all themes on all sites etc.

The main problem is that it’s hard to share data between sites in a network. We have switch_to_blog(), which is faster in 3.5, but still needs caching around it.

The consensus was that there are too many different use cases right now. At this point, the best solution for developers is to build their own APIs; custom global database tables are fine.

Wishlist:

  • domain mapping in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • multi-network support in Core
  • enable-disable (not activate) plugins per site, similar to themes
  • revisit register_update_hook()
  • wp-signup.php and wp-activate.php should become theme templates and/or forms
  • admin 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. for users that haven’t activated their accounts yet
  • settings APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. that works for network admin
  • default WP_ALLOW_MULTISITE to true

Action item: set up team for Multisite component and triage existing multisite tickets.

Summary: Core UI team discussion

Participants: Helen Hou-Sandi (leader), Dave Martin, Sara Cannon, Drew Strojny, Tom Auger, Ronnie Burt, Andy Peatling, Amy Hendrix (note taker)

Notes:

General question for contributors : how did you get started, were there pain points, things they wish had been there; for non-contribs: what would help you get started?

  • One person got derailed by figuring out the step after the dev chat — what’s already being worked on, make a commitment to an initiative but then what’s the communication channel?
  • overlapping efforts can be discouraging
  • we need to be better at keeping ALL discussions public (IRC or make/ui) instead of falling back to private conversations
  • we aren’t always good at saying “this is what we’re currently working on”
  • lone dev still happens
  • suggestion for newer contribs: get comfortable with IRC, learn to use the bots (the .tell command is brilliant!), ask in public rather than one person’s email.
  • Goal: get better at building small teams that play on individual strengths
  • Dave: works for Automattic, wanted to contribute, but found it super-intimidating even as an experienced dev + Automattician.
  • We can keep a list of who’s working on what projects (Make P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org is important for this, not just IRC convos), what issues are being worked on, what needs help
  • Helen: wants to improve weekly posts on make/ui – combine with meeting notes – what we did this week, what has new patches, what needs work, what to do this week

Discussed improving the wp.org site. Challenge: how to open-source portions of things (not just a 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. group challenge); we want better design and feedback for .org, but currently the workflow is that one person (Otto, Nacin, Scott) gets a request and might have time to implement it.

This is also a challenge for the team’s work in general – we have a huge range of things we touch (graphic design, UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. design, user testing, front-end engineering, 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). (https://en.wikipedia.org/wiki/Accessibility), QA), and people with a lot of different skillsets. How can we get better granularity, and get better at breaking things down?

  • work iteratively! (this is a comfort level thing as well as a project management thing) — don’t work for a month getting something perfect, be comfortable submitting something that’s partway there but will still need more.
  • question about dealing with ticket “ownership” – do you jump in on something that people are already working on and risk stepping on toes? or do you avoid it when it might need more people working on it?
  • Make sure to give props/recognition for everyone (including non-coders)

We should have guidelines – but as general principles, almost like mission statements, rather than strict checklists. This is also useful as a decision-making tool for handling UI questions/requests.

Challenge: we don’t have a committer in our group, and have to get the attention of one that isn’t fully involved in what we’ve been discussing. We sometimes land things prematurely, back out, things get in that we didn’t intend… looks bad, breaks our processes.

Reaching out to new contribs and non-developers:

  • can we use Make P2 to post specific patches for discussion requests?
  • can we find one-hour tasks? matchmakers? people like to be asked.
  • dedicate time to training contributors (maybe in office hours?) – how to use trunk, make/apply patches, etc.

A lot of non-developers have been interested in UI work but get scared off by technical aspects OR stick around for discussing mockups but then leave at feature freeze when there doesn’t seem to be as much place for designers etc. Those would be good times to work on improvements outside the specific release – ongoing tasks, wp.org improvements

Lightning round: One improvement wanted per participant:

  • curated list of things to work on x2
  • public posting of the scope of the group
  • clarity about communication channels, who’s on what
  • channels for non-devs. we have a lot of connection to (design, a11yAccessibility 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). (https://en.wikipedia.org/wiki/Accessibility), …)
  • testable patches
  • manage TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. better – use keywords, use them consistently (needs-ui-testing)?
  • ways to attract & keep non-developer contributors
  • preplanning for future projects (even after feature freeze – discussion dies when the feature is done or the mockup discussion is wrapped up)

Action item:

  • Review + publish a version of the contributing to UI doc in the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contributor handbook (draft, can be abbreviated for now)

Summary: Engaging / Retaining New Community Devs

Merged discussions:

  • I can’t get no traction: how community devs can get involved in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. culture without giving up their day jobs? – Jonathan Davis
  • State of the idea of Component Leaders – Konstantin (?)
  • How to help contributors in a good way 3.4-ish – Marko H
  • What can we do to better engage/retain new contributors? – Tom Auger

Attendees

  • Jonathan Davis (discussion leader)
  • Peter Chester
  • Chris Olbekson
  • William Davis
  • Aaron Campbell
  • Chris Jean
  • Marko Heijnen
  • Scott Taylor
  • Michael Pretty
  • Jon Cave
  • Ryan McCue
  • Nikolay Bachiyski
  • Justin Kopepasah
  • Simon Wheatley
  • Kailey Lampert
  • Konstantin Kovshenin
  • Brad Williams
  • Mike Hansen
  • Ptah Dunbar
  • Tom Auger
  • Alex King
  • Andy Peatling
  • Andrew Norcross
  • Helen Hou-Sandi

Many conversations carry on for a long time with no end in sight.

One of the problems is that code is often too toxic to proceed. Toxic code can be addressed by unit tests

One of the problems is that you submit a ticket and it just dies.

How should the process of contributing work? Trac? It’s hard to figure out who’s who on Trac. Once you know it’s easier to move tickets through.

Tickets die if coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. devs don’t buy in to tickets. It takes persistence and day job time to get your work pushed.

There’s a difference in motivation of fun vs. business. How do we support customer driven, time sensitive contributions?

Is that the right motivation? Dangerous to promise/use contributions as leverage with clients.

There are detailed tickets that are awesome and perfect. And other times when the detailed ticket is hopeless and instantly denied.

It would help if Trac profiles had ‘specialties’ so that people who are specialized in areas get routed.

Nacin: We used to have component owners, but found that this stifles contribution. I’d like to discuss building teams for components. This would help for quick response to tickets.

How do you fix a stalled ticket? Communication is key. Even if the communication is “we’re looking into it”. If UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. / 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. are your blockers, we do bug scrubs in IRC so we can move tickets forward regularly.

Nacin: We have the weekly project chat, but it’s designed for status checks and not ‘come with your ticket’. The key now is, come into IRC and pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” someone. You don’t have to ping me directly, just drop a ticket and see who chats:

I didn’t even know this stuff. It should be more clearly written out. Each P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org needs the essential info at that top of the page.

I’d like to see more chatter from us on IRC. We need to reference the IRC chat in tickets.

  • Biggest change for me was subscribing to Trac emails.
  • How many emails?
  • A lot.
  • That doesn’t seem realistic as a solution.
  • It gives you a better perspective of how much is happening and where.

We’re all contributors. We have limited time. Spending it licking a firehose is maybe not the most effective way to use our time. I think we need to know where our tickets / components are going.

For every ticket that needed a patch, there is a difficulty. First time contributors, start with ‘easy’ tickets. This made it very easy to do your first contribution.

I don’t think the problem is finding a ticket, it’s getting the ticket you want to get passed.

What about a signal that is basically, “I’m new here, I want to submit a patch. Can someone hold my hand?”

What can we accomplish in the near term?

  1. P2s need headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. with info about how to get involved.
  2. Dev handbook needs to be more prominent including how to submit a patch.
  3. Come up with an ideal flow to eventually be a roadmap to better Trac/submission/patch process

Triaging tickets could be a perfect medium task. How do we define triage? This is a bit more modular issue.

  • Bug reporting
  • Enhancement / Feature requests
  • Bug gardening

Action Item: P2s need header with info about how to get involved

Missing Discussion Notes

Hi everyone. Now that everyone has recovered from the summit (and/or the subsequent trip to Pressnomics) it’s time to follow up on all our promises to each other at the summit. To that end, we’re trying to get all the discussion group notes posted and action items coordinated. There are some discussions that don’t seem to have any notes:

  • The Downside of Theme Customizers and PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party. Options Screens: Oversimplification
  • WordPress.orgWordPress.org 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. https://wordpress.org/ Profiles and Transitioning to bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org 2.X
  • What challenges do people face with release schedules and management?
  • Education Tools

If you were in one of these discussions and would be able to produce a summary of who was there and what was discussed (and what the action item was), that would be outstanding.

I’ve drafted a page of collected action items from the discussions. This is basically a public draft right now, covered in notes for follow-up, but I wanted to make it public sooner rather than later so that it’s clear we are actually following up on things. Once the working notes are cleared off and people are assigned to follow up on various things, I’ll add the page to the nav of this site.

Summary: Let’s improve the Codex

Participants: Andrea_R, Siobhan, Kailey, Dougla, Syed, Erica

Nobody loves the codex.

The codex is not useful if it doesn’t have good documentation

There are people in charge of the codex?

People are afraid or don’t feel competent enough to contribute? We need to reduce fear?

Some people are working independently and reverting changes.  It’s hard to know what people are doing. Some changes are reverted, which is a bit strange and worrisome.

The codex was put in place but simply exploded and lost it’s usefulness.

It would be great to split it from user to developer.

Things are wrong with the codex:

  • New users get freaked out by code
  • The structure of the pages needs to re-done.
  • Examples are needed. Functions, and code snippets.
  • Examples are sometimes wrong and poorly documented.
  • Notes in code would make it easier for people to understand.

Documentation can be quite varied, It tries to teach and also documents.

The search needs to be done all the time because of lack of organization.

the way the codex is indexed in Google, it’s loaded as secured and often breaks in Chrome.  Can we look into fixing the canonical links so there’s no SSLSSL Secure Socket Layer - Encryption from the server to the browser and back. Prevents prying eyes from seeing what you are sending between your browser and the server. Link.

We should have a user manual for beginners.

The front page needs to be re-organized. User vs Dev.

The front page could be mocked-up quite easily.

Who are the people who are responsible for the Codex. Who are these independent people.

Some stuff is not documented and need more work.

Every release, there should be new pages that get set up for them.

Perhaps a mentorship program could be put in place, so that more people contribute.

The Codex is huge. Right now, we’re just doing damage control.

People are paid to work in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but why not have fundraising for finding a way to take responsibility for that?

A reward or recognition function should be put in place so that people are rewarded for contributing.

If there’s a person paid to edit, then who is in charge, and can others still contribute?

The multilingual stuff is very spotty and translation is very difficult.

One suggestion is how to tackle this. A suggestion is to just start from scratch and present it a better way,

The relationship between the writers and developer needs to be improved.

Core developers need to check the box “needs codex”.

Should we allow video in the codex? The videos need to be stripped down and can not be branded.

@Rarst has come up with Query post — which could work for the Codex.

Separating the documentation and removing the function. Better search.

Visualization for loops and all sorts of diagrams could be brought in.

Glossary – The codex has one but it’s not done right. We would then need 2 glossaries, one for users, one for devs.

Users, learners, developers

Sorting using taxonomyTaxonomy A taxonomy is a way to group things together. In WordPress, some common taxonomies are category, link, tag, or post format. https://codex.wordpress.org/Taxonomies#Default_Taxonomies. and alphabetized.

Media Wiki for developer docs

WordPress could be used for developers.

It would be nice if you could check a box, user and only see the user stuff. Vice versa.

The user guides and theme handbook could be phased out for users.

The user guides are web based only from now. If it’s turned into a pdf, it should be timestamped and updated on a regular basis.

The user manual could be added to the dashboard.

A roadmap for the codex should be put in place.

The codex is lacking in best practice information. security, apis, themes, etc…

The codex needs to be inter-inked to all the various handbooks.

Action Item: 

Road map for the Codex.