Ready to get started?Download WordPress

WordPress Community Summit 2012

Recent Updates Toggle Comment Threads | Keyboard Shortcuts

  • mitcho (Michael Yoshitaka Erlewine) 1:40 am on December 10, 2012 Permalink  

    WordPress Global Communities 


    Andrea Middleton, Takayuki, Remkus, Katia, Eric Mann, Viper, Ze, Xavier, Scribu, JJJ, mitcho (notetaker), Jorge Bernal, Scott, Tenpura

    Discussion Notes

    The first suggestion for visibility of WordPress as a global solution was to create something like global.wordpress.org, which doesn’t exist right now. Its objectives would be to present how WordPress exists around the world, where the latest localized versions are available and who is involved in which language.

    The user profile issue was raised and explained where we’re at by JJJ: it’s originally a project of Automattic, uses BuddyPress and the profile page information is pulled in by feeds. He also mentioned that it’s slow and prone to crashes.

    The idea is that all activity, including posts in international forums, translation work and event organizing should go into the wordpress.org profiles.

    Zé noted that we are on hold as far as new international forums are concerned until we can figure out how to integrate bbPress (plugin) into the Rosetta sites.

    The problem isn’t just one of profiles, however.

    There is often the need for a visitor, beginner or not, to be able to look at one of these regions/countries where multiple languages exist, and see what the status is and what the community is like. Right now, if you want to know who’s the Russian person in charge, you have no idea.

    Also, translators sometimes feel left out of some decision-making in core, despite being often (if not always) the first contact in local communities. According to Xavier, one of the issues is that many documents (such as WordCamp guidelines, handbooks and so on) are in English.

    Translations need to be recognized as equally valuable contributions to core. Some formal liaison maybe necessary; in fact some language communities already have unofficial leaders and liaisons with core or even Andrea. One question was raised if one problem might be that there needs to be an “owner” of a language/local community? Some places have that, others don’t.

    Following that, the suggestion was made to have group profiles by region. Zé mentioned that it might not be feasible, as the relationship between languages and countries is not one-to-one, nor is it one-to-many, but rather many-to-many. It would be better to have profiles searchable by region and language.

    This all could be helped by having a place for communities to live inside of WordPress.org, as opposed to meetup.com or other solutions. JJJ mentioned that BuddyPress could be used for this.

    Rosetta sites: Even though WordPress.org (in English) is now sexier, and the roadmap seems to say that it’ll be even more so, Rosetta sites are three years behind. Cátia made it clear that it is very important to give more freedom to Rosetta administrators; it can be frustrating to not be able to do what you want.

    As the discussion veered towards languages, Zé reminded that communities can be different things and most of the time are actually a mix of countries speaking the same language, different languages spoken in the same country and so on. This is not clear to visitors right now. As an example, the ISO code for Georgian inside Georgia (the country), is not the same as the code for Georgian spoken outside the country. This could mean two language communities and one country community ir any combination of those.

    Historically, however there seem to be not many formal connections between various communities in different varieties of the same language, e.g. Portuguese from Portugal and Portuguese from Brazil.

    Finally, many of the community sites are not on the WordPress.org infrastructure. They may even look like they are, but their domain is mapped. However, to be able release a language pack (and core upgrades), they need to be on xx.wordpress.org (Rosetta).

    Forums (or maybe even a P2?) for language/translations, per locale, would be a good place to have discussions for that community. Also, those contributions could feed into a user’s profile. Xavier warned that many communities have totally different sites, and this content archive is important.

    Cátia asked the question about the Foundation and transparency and representing WordPress inside a community; what should a community leader do if people don’t follow guidelines? Are there “semi-official” capacities in different places? There seem to be none. Andrea said that right now, in core, we have a team rep system, which is transparent, but none of these people then represent the foundation. A community leader/rep’s importance is determined by the time he puts in, and the better he becomes at his tasks, i.e. “if you’re here (at the summit), it’s because you are perceived as a leader”.What about a team rep system around communities or languages?

    Zé suggested there should be a global/international P2/make/forum site, written in English, but global. A place where polyglots can voice their opinions on the global reach of WordPress and how to make it more visible. The Polyglots P2 is not the place to do that as it is where Nacin and Zé deal with technical issues and fix various stuff.

    The kinds of questions discussed there should be, for instance:

    • How do we make reps in a region legitimate?
    • Viper: What happens if a community ends up creating a fork? A different looking site?
    • How do we reach out to those communities and make them more legitimate?
    • How do we make reps in a region legitimate?
    • Should we implement voting per language community like for the other team reps? (Cátia and Remkus noted that voting might be different for other cultures)

    The general consensus:

    • Having profiles and a make/global site is a good start
    • The other stuff is more about the particular community itself
    • Communities need to be made visible and open
    • Transparency is important
    • “This is how I got to be Nacin” would be very helpful for local communities/international contributors


    • There were lots of discussions of where international conversations occur, about transparency, and on how to get involved.
    • Profile integration and a make/global, or similar, were seen as a good start
    • There should be more discussions about community structure and legitimacy

    Action Items

    • Create make.wordpress.org/global
    • In the long-term: beef up profiles to show who is active in language communities and region communities

    (if people want to talk about technical stuff, they should talk to @JJJ)

  • George Stephanis 7:49 pm on December 3, 2012 Permalink
    Tags: a11y, accessibility, eu, standards   


    In Attendance:

    • Aaron Jorbin
    • Emil Uzelac
    • Kevinjohn
    • Amy Hendrix
    • Michael Fields
    • Dave Martin
    • Jake Goldman
    • Isaac Keyet
    • George Stephanis (note taker)

    Discussion Notes

    Kevinjohn brought up the initial concern that, in the EU, some groups can’t use WordPress, as it hasn’t met some accessibility requirements for a few releases now — but we’re close.  Have to meet AAA standards for EU.

    How’s the back-end for accessibility? Jorbin brought up that he, Nacin, and Koop sat down with a blind user and did accessibility testing of post screen — everything was properly set up except for the post box itself.

    (aside: question of if we should / how we could make it easier for front-end users to be accessible is nipped in the bud for later discussion)

    Amy Hendrix brought up the question of new accessibility tests for themes — which is a work in Progress

    What is the accessibility group? http://make.wordpress.org/accessibility/

    Aaron Jorbin pointed out that we should get accessibility experts more involved in WordPress. By bringing the accessibility community into the WordPress community, we all benefit.

    One of the challenges is that it is hard for much of the core team to test accessibility patches do to them not having copies of accessible technology software. A good deal of the software is commercial (or only runs on one operating system) and few people have copies to test patches against.

    (aside: someone pointed out that it would be nice to automate patch applying by generating trunk installs on the fly and applying patches to them, to enable less-technically-minded people to contribute to testing.  Perhaps on wpusertesting.com or similar?)

    We need to migrate from being reactionary to proactive!  While there are a couple patches for 3.5, we may need a set of guidelines for a11y standards, the same way that we have php and css guidelines.

    It would be very useful to add a high-contrast theme for the admin UI.

    We also need to emphasize the reasons to focus on accessibility — better SEO results and marketing, for one. The W3C has an article on the web accessibility business case.

    (aside: could we possibly include an API for toggling high contrast mode on or off?)

    It would be nice if TwentyThirteen was designed accessible as a number one priority, but how do we get there? We need someone to take responsibility.

    Isaac Keyet mentions that mobile apps are mostly compliant, but it’s more dependent on the platform that you’re on.

    Drupal contacted the governments and asked what they needed to do to become fully compliant. We need to get data / feedback that lists what we have already, and what we need to be properly up to spec.

    Standards — which ones should we focus on? There are multiple options.

    Checklists to compare patches against would be really helpful! Accessibility is much more than that, but it’s a tool that could help devs not as familiar with Accessibility. Not a solution.

    Should we add a `not-accessible` or `needs-accessibility` tag in trac? These could make it easier and puts accessibility on the same level as UI or UX. It’s not a feature, it’s a core asset.

    We need more accessibility talks at WordCamps … bring accessibility into the popular mindset.


    • Add a section to the Handbook.
    • Add in some requirements for patches that they be tested against accessibility guidelines.
    • Need someone to take ownership for things going forward.
    • Page on .org talking about what certifications we meet.
    • Challenge TwentyThirteen to be designed with accessibility as it’s number one Priority.

    Action Item:

    We want to add WordPress.org/accessibility which will be a one stop shop for successes we’re having and ways people can get involved. This is partially inspired by The Drupal Accessibility Page.

    • Joseph Karr O'Connot 11:32 pm on December 3, 2012 Permalink

      It is wonderful to read the notes from this discussion. Continuous improvement of accessibility is needed and this post points to that being a reality. Thank you all very much for making this a priority, it is much appreciated.

    • Kevinjohn Gallagher 1:44 am on December 4, 2012 Permalink

      The big thing for me is to put accessibility (and usability) at the forefront of UI decisions.

      This was a great discussion, but to took a while to get past the “but we fixed that in 3.5″ viewpoint, without realising that it’d had been broken since 3.3 beta 1. 3.5 isn’t out yet, so it’s been a while year of being broken!

      WP iterates so fast, and thats awesome, but it also comes with a huge risk that we focus on “cool looking stuff” over accessible features :)

    • Graham Armfield 8:47 am on December 4, 2012 Permalink

      This is excellent news. Just to echo what Joseph said – continuous improvement is vital – we can’t afford to stand still. Drupal have had a strong focus on a11y for some time now and substantial improvements have been made.

      I also agree with Kevinjohn, accessibility needs to be fully at the forefront of UI decisions and design. Designers and developers all need to understand what accessibility means and the benefits it brings.

      There have been many positive steps taken in the admin area in 3.5 but there is still much to do.

      I’m happy to play a part where I can.

  • Helen Hou-Sandi 7:21 pm on November 23, 2012 Permalink  

    Education and Training Discussion 

    Note: These discussion notes are from the team reps summit the weekend before WPCS.

    Have made a lot of headway with Core Handbook, internal training documentation. Codex mixes dev and user materials – needs work.

    Where do we put these materials? Anybody can write to the Codex; issues like voice consistency, information accuracy. Support Handbook in progress: http://make.wordpress.org/support/handbook/. Someday it will be Learn WordPress (learn.wordpress).

    Next steps: get it right. Get videos. Get screenshots. Get more bodies. Move from overviews to specific items/features.

    Core Handbook idea: interview people who committed/contributed their first patch and review what they did or didn’t know or needed to know based on information in the handbook. To discuss more: onboarding core contributors.

    Better documentation

    What’s changed in a cycle. Development/code comments → commit message → new developer API announcement/tutorial → to-user announcements → support documentation → tutorials. Better changelog tracking – plain (user-facing) English!

    Official API documentation site. Special doc style for actions/filters (needs loooots of bodies to write code docs). Developer portal.

    Huge part of education is the transition from being a user to getting into development.

    Better incorporate high quality content from WordPress.tv. Virtual “WordCamp Ignite” – flash talks.

    Beyond Documentation

    New user workshops. New developer workshops. Workshops! We’re not bad with 101 (new and non-technical users) and 401 (established developers), but not so much with 201 (power users) or 301 (beginning developers). Workshops would help, perhaps “pre-packed” materials that can be shipped out for use.

    Courseware plugin (Stas) as training support on .org is a long-waiting idea. What would curriculum/syllabus be? Who would teach it and where? Libraries, meetups, etc. Example teachers/classes: Austin meetup, Lorelle, Boone. Would need a person to collect/collate/review exemplar syllabi, etc.

    Quizzes – how well do you know WordPress? Don’t want to go down the path of certifications, but self-testing, maybe as auxiliary helpful material for vetting Happiness Bar volunteers and WordCamp speakers.


    More standardized “Happiness Bar” (in-person at-event help). What are issues – naming (confusion about what it is), nobody goes, misinformation being given as help. Volunteers should be scheduled on skill/specialty + time – a volunteer per area per time. How do you point a user, who might know where their problem lies, to the best fit for help?

    Ask speakers to volunteer at the Happiness Bar (opt-out, of course). “I’m interested” on your .org profile – WordCamp speaking, helping at a Happiness Bar, etc. Exit survey for Happiness Bar users.

    Hack Days should include more than core or code contribution – also documentation and support, especially for tasks that really need bodies. How about a Happiness Day / WordPress Study Hall?

    Action items

    • Learn WordPress: Call for curricula and volunteers to review curricula.
    • Move materials over from handbooks (“final resting place” –Mika). Need to find Learn.WP structure idea that already exists somewhere, or do it again.
    • Exit survey for Happiness Bar users.
    • A better default name for the Happiness Bar.
    • andrea_r 10:25 pm on November 23, 2012 Permalink

      “Quizzes – how well do you know WordPress? Don’t want to go down the path of certifications, but self-testing, maybe as auxiliary helpful material for vetting Happiness Bar volunteers and WordCamp speakers.”

      I *love* this idea.

  • Jen Mylo 7:57 pm on November 21, 2012 Permalink  

    Growth and Marketing 

    Note: These discussion notes are from the team reps summit the weekend before wpcs.

    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.org needs a facelift. Not just design, but content like /about. Old features (post revisions) 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.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 github 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.

    • Andrea Rennick 9:43 pm on November 21, 2012 Permalink

      WordPress: Your site, your way.

    • Simon Wheatley 10:46 pm on November 21, 2012 Permalink

      Specific uses — I want a site for my bakery, for my book club — are better.

      I think this kind of approach could help us breach the gap in perceived ease of use between something like Tumblr and WordPress. One hit install: everything for a particular constituency. I guess the trick is choosing the constituencies, and then being appropriately opinionated.

  • sara cannon 7:36 pm on November 21, 2012 Permalink
    Tags: Education, Meetup, WordPress Meetup Groups   

    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 Meetup Groups Present:

    Sara Cannon – WordPress Birmingham Meetup, WordCamp 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 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 source 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.


    • 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.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 trac, so we need to educate our groups on core development. Meetups gives people an avenue to talking about new core features.

    Two great Meetup Ideas from DC: 1) “My favorite plugin” lightening talk. 2) Upgrade-a-thon!

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

    • Adam W. Warner 8:12 pm on November 21, 2012 Permalink

      Good stuff. I organize our Sarasota Meetup group and would be happy to be involved on the .org side of things as well.

      One method that we’ve started to use to get the shy ones involved is to try and get a different presenter at the end of each Meetup for the following Meetup…or at least to throw out some preso ideas for others to grab onto.


  • Ipstenu (Mika Epstein) 7:30 pm on November 21, 2012 Permalink  

    Summary: Non Code Contributions to WordPress 

    Attendees: Ryan Imel, Sara Cannon, Brandon Dove, Andy Stratton, Tom Willmot, Siobhan, Ryan Duff, Lisa Sabin-Wilson, Justin Sainton, John Hawkins, Andrea Rennick, Mika Epstein

    The main issue was that if you want to find who contributes to core, it’s easy, but meetups/wordpcamps/etc are unlisted, and there are no acknowledgement for loads of work.

    There’s no credits page for non-coders (and coder is really an iffy term, since help-doc edits get listed). Possible suggestions of things to add/pull from:

    • In the help tabs or on the .org credit page, below rockstar
    • Ticket submitters should be listed in the credits page (if they forget to credit/prop you, you’re forgotten. Sad Elf)
    • UI Props – Workups/Wireframes don’t get props
    • Automated culled list – anyone who commented/contribed on a ticket that was picked up and added to this release “These people were involved”
    • From the Make Blogs – Pull Recent RockStars too

    Make credit page less of people who WROTE code.

    • - Here are the code leaders
    • - Here are the codex leaders
    • - Here are the support leaders

    Remember that profile pages don’t show codex, so seeing who wrote a page isn’t all that helpful for most.

    Lower the wall for new non-code-contrib

    • Identify these barriers
    • Terminology?
    • Meetups – joint project to contribute a codex page/handbook
    • Mentorship
    • ties in with fixing profiles
    • Bring in codex edits to profiles.wordpress.org
    • List Meetups etc ‘Where I help’ on the profile page
    • WordCamps I’ve been at, spoken at, organized
    • How do we validate ‘I organized this meetup’
    • Tie in wordcamp.org data to validate
    • Plugin that adds data to extended profile – speaker-CAMP-YEAR etc etc

    WordCamp categorize role

    Self Assessments

    • I’m awesome at….
    • I’m good at ….
    • I’m okay at …
    • Please don’t ask me about …


    • Design standard format for handbooks
    • CORE
    • User Guide
    • Theming Best Practices
    • Plugin Best Practices
    • WordCamp Organizers
    • Meetups
    • Teaching WP

    Action Items

    • * Improve profiles to include more (@JJJ)
    • * Change Credits to recognize the non-coders (people who submit tickets, contrib to discussion, user manuals, make-people)
    • * Offline Activities (Meetups and WordCamps) — SEPARATE INSTALL, will have to wait, but it’s on the radar

    TO DO


    • - Make a post on /support about the handbooks/documentation

    MIKA (trac tickets)

    • Improve credits
    • Add a link in the welcome screen or about page to ‘How to contribute’

    There’s a codex template that you can use to indicate a stub, write up how to edit

    Rewrite the main page of Codex to an intro

  • Andrea Middleton 6:40 pm on November 21, 2012 Permalink
    Tags: contributor groups, team reps, teams   

    Team Reps 

    Note from Jane: These notes are from the team rep summit that happened the weekend before #wpcs. More information about the outcome of this talk will be posted soon to wordpress.org.

    How were people chosen to be team reps?

    Every contributor group were surveyed (via p2 and/or mailing list) to choose team reps (primary and backup). The UI team was slightly different in that the group was not very active at that time, so the responses were low, but the selection was Jane and Helen as second. Since Jane was organizing it, Helen was chosen as a Core team rep, and the UI team had devolved into mostly CSS (dev), no UI team reps were assigned.

    Core devs have team reps including long-time core committers, highly experienced devs with commit access, experienced devs without commit access, and devs new to contributing. This overweighted the team rep group in favor of core devs. Also, since people were voted in, roles have changed. Agreed to reduce the number of core dev reps to two, just like all other groups.

    Sometimes roles change (like Mika, who’s been working on plugins as well as support). People should, ideally, just be responsible for one thing. How regularly should we revisit who the reps are? Should we time it with release cycle, or make it time-based? 6 months, timed with calendar, not release cycle seems most attractive.

    After the summit, Jane will post about another voting round – whittle down the core dev reps, revisit UI/events/etc, and announce the new round of elections.

    Term limits. Is it best to switch team reps every term? This can be a good way to encourage people in your team to step up. Another idea is to have a team rep and a rep-in-training, so that the alternate rep can be learning and training before they take on the team rep responsibilities.

    Do you lose team rep status based on poor performance? If team reps miss weekly updates or monthly chats, should they be asked to step down? Alternate reps should represent the team if a team rep can’t make a monthly hangout or weekly update. If the whole team can’t post/represent for 2 weeks straight, then they need to re-assess the reps.

    What teams are light and need to be recruited for? Mobile, international, accessibility, and security (new team!).

    Are there any teams we don’t have that we should? WordPress.org team (Meta) for sure. UI could use more designers. Support could use more people and documentation writers. It would be a good idea to make documentation a separate group.

    Agreed to close voting on December 14 for the next round of team reps to start on January 1, allowing for a 2-week orientation and training/getting up to speed.

    It needs to be emphasized to the community that the team rep position is more about communication and project management, not necessarily prestige. Let’s keep assessing our processes and structure, and make iterative improvements.

  • Jen Mylo 4:08 pm on November 19, 2012 Permalink  

    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 API
    • Git mirrors for open source parts of the 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.

    • Brian Layman 4:54 pm on November 19, 2012 Permalink

      Just on the subject of food:

      One of the things that impressed me that I didn’t think of during the survey was how you accommodated specific dietary needs by supplying the vegetarian meals and gluten free products. You made an effort to attend to people’s needs and that was not something that everyone does even if they are aware there may be a need…

      From my personal perspective, I’m just not sure how you could have done better than a free, all you can eat incredibly good BBQ followed by a free all you can eat crab shack!

    • Kevinjohn Gallagher 10:56 pm on November 19, 2012 Permalink

      I have a #wpcs review half written for a blog post once this “world tour” ends (#wpcs kicked off a 4 week stint circling the globe twice), but I really wanted to comment on this (as someone’s already emailed me about it, laughing at what answers they THINK I gave).

      For the record, I loved #wpcs, and thought the great massively outweighed the “not great”, but there were certainly somethings I think we should take on board as feedback, even if we don’t action all of them :)

      I should also note that in many places in the survey the options were Fantastic, Good and Poor. There were a few instances where I really wanted an “ok” box. Maybe it’s semantics, but there’s a large difference between Good and Poor. Poor has such negative connotations, and I’d hesitate to say that anything was “poor”, but there were two occasions where I didn’t feel “good” was my opinion. Also, without being able to give a weighting to the questions as to their relativity to my outcomes or enjoyment, my survey probably read far more negative than my good opinion of the event.

      ### Monday

      Having it on a Monday was a challenge.

      • Travel on a Sunday is more difficult that at other times
      • Trying to juggle work with no wi-fi
      • People are more accepting of a Friday off work than a Monday
      • It meant *having* to miss work, it removed the option or ability to plan around it.
      • It cost more in terms of flights (flying on a Thursday instead of a Saturday would have saved me 30% off the cost of travel)

      ### Tybee

      I felt that Tybee was a poor choice of location – and this coming from a man in love with Georgia. Being near a hub is really a must for any for of international event. Taking 5 different flights to get to Savannah was just painful; but the worst of it was to be in London’s Heathrow, and still take 3 flights to get where we were going was a bit much.

      I totally understand having it US-based, but any of the major coastal cities/hubs would have made travel infinitely easier for those of us not in the US.

      I think this one got a lot of “Good” votes because “ok” wasn’t available as a choice.

      ### Tybee Chapel

      Having the event in “different” venue was great. I loved the premise, and I took a butt-load of pictures of the chapel; but it had issues as a venue. Bathrooms were mentioned, and for those of us hard-of-hearing, 70 people chatting about 6 different topics within 5square meters was incredibly difficult.
      (again, this is maybe just me, and thats cool, but being fairly-deaf and with so many wonderful accents in the room, i couldn’t attend a “table discussion” that was next to more than 1 other table).

      I think this one got a lot of “Good” votes because “ok” wasn’t available as a choice.

      ### The Wi-fi

      The Wi-fi was an issue, but y’know, it’s always an issue at conferences ;-)
      There was nothing that Jane or anyone else could have done about it.

      That said, it was really disappointing at lunch to sit next to two US based folks, who were on Facebook/amazon respectfully while I couldn’t connect to answer work emails. Limited wi-fi is one thing and couldn’t be helped, but it was disappointing that some folks didn’t only use it when needed. (Just my 2cents as someone paying $5/Mb on my phone while in the US)

      ### Many wished they’d stayed longer.

      I sure did.

      I just about missed my flight because I was so engrossed in a conversation with JJJ that I forgot to ask for Jane’s help in getting a taxi on time.

      I feel if I’d have known the plan for the week, and the plan for the “actual day” a little more, I would have stayed an extra night.

      ### Advanced Knowledge

      I’m one of the folks who would have loved some more advanced knowledge – which is not to say I amn’t aware of how much work Jane was doing to get this thing going!

      But not being a developer (so unable to talk about the specifics line of code or trac ticket that conversations sometimes went to), and with a lot of discussion-points being subjective; I would have loved to have been able to prepare some data/slides/examples for which to articulate what I was trying to say in some of the discussions.

      I’m not saying I wanted to stand up and present ( people would only throw things ;-] ), but there were some discussions where I felt a little unprepared and/or disappointed I couldn’t boot up my laptop and show my example to help further the amazing discussions that were going on :)

      In part this is probably my fault as well, WordPress is my hobby and my side-business, I love it, but it’s not my day job – so maybe everyone else felt totally prepared and had all the data they needed at their fingertips.

      ### Advanced planning

      From “welcome” to first discussion was just over 2 hours.

      Unconference is fine, heck its a really good format for this, but if we would have asked folks to come up with (or even submit) topics before hand we could have done a fair amount of the “Nacin board” planning in advance.

      Which is not to say we couldn’t have added more in the morning, but I wonder how many of the 60 people that stood up knew what they wanted to talk about that subject prior to arriving that morning. I’d guess a large percentage.

      Adding another row of “sessions” (9.15 – 10am) would have been far more beneficial in my opinion.

      ### Matt’s talk

      I’ve always liked Matt from afar, and liked him even more in person (it’s the hair I think, it’s v pretty). But this was very much a “state of the word” type talk, nd thats very cool, but we had one of these just 2 months ago.

      ### “It’s ok, we’re fixing that…”

      I heard this a lot through out #wpcs. And thats great, it really is, but it was used as a shield to not discuss how we got to the place where an intervention was needed – so we wouldn’t fall into the same trap again.

      ### Presumption that we knew each other

      I know that most of you know each other, which is awesome, but some form of “ice breaker” would have made the world of difference for me.

      ### Cupcakes

      I’ve lost about 5 inches off my waist this year, including the amount I lost for #wpfit, pretty much only by avoiding sugar; but my Lord those cupcakes were to die for. I had 5 :(
      I’d come back to Tybee just for one of them !

      Anyway, thats my two cents, I’ll talk more about the GREAT stuff in my blog post when I return.

  • Matt Mullenweg 3:59 am on November 16, 2012 Permalink  

    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 WordCamp 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.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 CSS. 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, core 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, Trac. Also important for WCs and meetups. There’s always that weird guy at a meetup.

    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 HTML 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.

    • Cátia Kitahara 2:42 pm on November 17, 2012 Permalink

      May I add a new action item here? I think this one is very opportune and much more effective right now as a real action we can accomplish in a very short ammount of time: I propose WordPress Foundation participates in the Gnome’s Outreach Program for Women internships. What do you think of it?

      • Amy Hendrix (sabreuse) 4:12 pm on November 21, 2012 Permalink

        Great program – but I’m not sure if they’re still taking on projects for this round, since they’ve already started taking student applications. Might be something to make a point of for next year’s internships?

      • Jane Wells 4:16 pm on November 21, 2012 Permalink

        It’s too late to get in on Gnome, and we need to build our mentorship group and materials first so that when we do partner with other programs we can be successful. Cátia, the outreach for women will be happening officially through the community outreach contributor group we just started. You should join us! http://make.wordpress.org/community

        • Cátia Kitahara 4:45 pm on November 21, 2012 Permalink

          I’ve talked to them and it seems it’s still possible to join the program, but I agree with Jane, we need to get our side organized before we do it. But it’d be awesome if we were able to join this program or other similar to that in the near future.
          I wasn’t aware of this new group. I’ll join u and keep this conversation there. Thank you!

    • Vinicius Massuchetto 11:19 pm on November 17, 2012 Permalink

      I must point that it’s freaking awesome to see this discussion in the WordPress community.

      In the Brazilian WordCamps we’ve seen a lot of woman trying to learn and get involved, but still, they are related to WordPress in a more ‘peripheral way’, they don’t contribute and get in touch with the community often. I would be very happy to see the community discussing any criteria to measure woman presence around WordPress, and maybe start specific programs to increase their participation.

    • DocX 5:15 pm on November 21, 2012 Permalink

      if every women like Benazir Bhutto then this world would be different.. more attractive :)

      • Jane Wells 5:34 pm on November 21, 2012 Permalink

        Commenting on women’s attractiveness in a professional environment is one of the problems we want to address… even when it’s complimentary, it’s out of place.

    • Manuel Schmalstieg 6:32 pm on November 22, 2012 Permalink

      As a fresh WP meetup co-organizer, aiming to help building a healthy local WP community, it’s great to see this topic adressed. Also by some incredible coincidence, gender imbalance at tech conferences is the topic of the latest A List Apart issue: http://www.alistapart.com/articles/universal-design-irl/

  • scribu 8:01 pm on November 15, 2012 Permalink  

    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 Multisite:

    1. a network of independent sites (like 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.


    • domain mapping in Core
    • 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 UI for users that haven’t activated their accounts yet
    • settings API that works for network admin
    • default WP_ALLOW_MULTISITE to true

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

    • Ron Rennick 8:05 pm on November 15, 2012 Permalink

      wp-login.php was also mentioned along with wp-signup.php & wp-activate.php

      • scribu 8:25 pm on November 15, 2012 Permalink

        Yeah, but it’s not really a multisite thing.

    • Ipstenu (Mika Epstein) 10:19 pm on November 15, 2012 Permalink

      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.

      That’s an interesting statement. Do you mean there are too many use cases to come up with ‘common’ APIs? Because there are too many difference use cases for WordPress, but we can provide people with easier tools to meet those cases. The two primary use cases (free and controlled) is a good start, but maybe we need to reach out and get a better list?

      default WP_ALLOW_MULTISITE to true

      Speaking from support? Please don’t do this. The hurdle of people having to do that actually weeds out folks who shouldn’t be using Multisite. It’s certainly easier now, but that extra step isn’t a bad thing. What’s the reasoning behind changing that?

      • scribu 7:50 am on November 16, 2012 Permalink

        I guess I didn’t phrase it properly. Yes, there might be common use cases that would make sense to have in Core, but we just don’t know about them, so some kind of survey would be good.

        It’s certainly easier now, but that extra step isn’t a bad thing. What’s the reasoning behind changing that?

        There was a question: why is it so hard to set up Multisite? I tend to agree that enabling WP_ALLOW_MULTISITE by default should be accompanied by more profound improvements. Here’s a memorable quote from JJJ during that talk:

        Until we take the bullets out of the gun, we’re going to keep the safety on.

        • Ipstenu (Mika Epstein) 3:33 pm on November 16, 2012 Permalink

          Yes, thank you JJJ ;) that was what I was worried about too.

          If we can make it easier … Okay, I say that and I totally feel that Multisite, the basics, is easy, but it goes back to what you said about too many use cases. The ones for Single WP are well worn paths, for the most part, and when someone comes up with the wild and wooly, they accept that they need to make their own trail. Multisite is all new paths. I have a blog post in draft, about why it’s so damn hard to find the right plugin for Multisite :/

          After 3.5 goes live, a think a survey to sort out what people want in Multisite, coupled with looking at the multisite plugins that are highly used, should be in order.

          (I wanted to come to this talk, but it was opposite another one I wanted to go to, so Multisite lost, since I knew I could just pester Ron later ;) )

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc