Ipstenu (Mika Epstein) 11:25 pm on July 25, 2017
Tags: plugins, summit 2017 ( 5 )

Plugins Team Community Summit 2017 Recap

While a recap of our various talks (including hallway) have been collected in the link below, our primary conversations revolved around the following:

New Reviewers: There are some technical issues we’re working on that must be resolved before we can add new people. They include security ones, but also our rather archaic SupportPress tool. This is the biggest and has a lot of small steps and some weirdly large ones (like the idea of a dashboard, automated security checks, and more) so it’s not going to be anywhere near as fast as I want… Well. Release and iterate.
How to safely publicly disclose 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. closures (without dog shaming developers). This is logistically something to be concerned over, as the last thing we want to do is make WP and users a bigger target.
How to allow frameworks with the least pain for end-users as possible.

In order to meet our goals, we’re going to be discussing the improvements on many fronts at once, and I’m planing out times and dates for meetings for everyone to come and talk about one at a time. Think of it like town-halls. You can read the details of everything in the linked post:

2017 Community Summit Notes

#plugins, #summit-2017

Daniel Bachhuber 12:51 pm on July 25, 2017

WP-CLI conversations at the Community Summit

We had two WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ conversations at the Community Summit:

The future of the Package Index (notes embedded in this post)
Contributing to WP-CLI

Check out those links for the full summary. Thanks!

James Huff 10:02 am on July 25, 2017

Support Team Community Summit 2017 Summary

Getting More Support Contributors

@bethannon1 is now our official Volunteer Coordinator, and she’ll be taking point welcoming new volunteers to our support community. We have received a fair amount of negative feedback about our “somewhat robotic” handbook links for new channel joiners, so instead, Bet will now be reaching out to new joiners directly with a more personal welcome.

A new Forum Welcome (now live), which will be far less guidelines-based than the current Forum Welcome, will be a huge help here too. We will maintain a separate page for the guidelines (also now live).

Later on, we’ll be exploring adding some sort of call to join the meetings which appears 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/ users after a certain number of support replies, and also email notifications to 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./theme developers when their support forums fill up.

As for meetings, let’s open them with a note to clarify that everyone watching is welcome to participate, and on low-agenda days include community-building items like “What cool things have you done with WordPress?”

We’re taking steps to become a more international community overall, rather than separate communities of separate languages. To start off, we’ll be referring to the “English Forums” as the “International Forums” from here on out. We’ll no longer immediately redirect questions asked in other languages. Instead, try to answer them yourself in your native language if you can successfully translate the question. If you can’t do that, and the question goes unanswered for more than a day, use the pre-defined reply under “Non-English Support Request”. In the future, we’ll add language tagging once tagging is fixed so that we can tag topics without replying to them.

As for meetings, all languages are now welcome. We all know how to use translators, so we should allow everyone to participate in their own native languages. Additionally, sarcasm and cliches don’t translate well, so we should avoid those from now on.
We won’t be getting rid of specific locales, participation in the overall International Forums and meeting is only a recommendation.

@bethannon1 will also be taking the lead on organizing monthly volunteer orientations, geared as both an introduction for new volunteers and a reminder for established volunteers. They will cover a training-like Handbook walkthrough, sample questions with group answers and feedback, and an overview of cultural tone differences when it comes to English.

We’ll also be planning monthly plugin/theme support workshops, led by representatives from some very recognizable names in the WordPress community (a different one each month). The workshops will be held at a time that is comfortable for the leader and cover how they provide support for their plugins/themes. The first such workshop has been scheduled for August 23.

Support Style Guide

After a good discussion, we decided not to pursue a style guide. Instead, best practices will be conveyed as part of the monthly volunteer orientations and plugin/theme support workshops.

We also plan to encourage collaboration via SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ when an issue could be between two items (conflicting plugins and/or themes for example), and may consider exploring joining Slack as a requirement for having a plugin or theme hosted at WordPress.org.

The remainder of this session was largely a re-hash of the plugin/theme support workshops that we discussed in a previous session, including how we’d schedule them (that will be up to each person running each session) and how we’d announce them (on the applicable Make P2s and hopefully get some help from WP news sites).

Remaining Forum Fixes

We managed to knock down our previous very large list of things we miss from bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org 1 and new things we need down to this much smaller (and far more possible to complete) list sorted by priority:

Allow moderators to add notes to users – 2272 (Finished)
All w.org users should be able to report posts or topics – 1956 (Bring back ability to add a tag (including the special “”modlook”” tag to flag issues for moderator attention) without having to add a reply, as was the case in bbPress 1. Fixing this would also allow posts in languages other than English to be specially tagged for polyglot volunteers.)
Forum RSS Feed Issues – 2204 (There are multiple issues in this ticket, MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. – please let Support know if any items should be split out into separate tickets. Especially important: include replies in RSS Feeds, include plugin & theme name in subject (as in bbPress 1). @sergeybiryukov will look into how feasible are replies in RSS re: performance.)
Add a way to sort topics in forum profiles by recent activity – 2470 (Finished)
Option to set default value of “Notify me of follow-up posts via email” in profile – 6 (Finished)
Old topics are no longer automatically closed after 1 year – 2265 (Finished)
Moving a topic from one forum to another forum results in a 500 error – 1955
Last Post ignores post status – 2043 (Finished)
Add support for custom titles on support forums – 1950 (Finished)
Moderators should have a way to edit user profiles – 1985 (Finished)
Spamming a user should flag topics and replies as spam and remove custom profile data – 1960

Ulrich 9:14 am on July 25, 2017

Theme Topics @ Contributor Day

Future of the Theme Review process & making it smoother and faster

In this session we continued the Theme Review specific discussions from the 13th of June.

The main focus was an improved review process with a new backend.
We discussed the possible changes and differences between the current and a new system:

The current Themes TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. would be replaced by WordPress.
Reviewers will no longer be assigned to themes. This means that anyone can do a followup review. The reviewer would not need to wait for the reply and would be free to review another theme meanwhile.
There will no longer be a 7 day deadline for an author to reply. The theme will wait until an update is submitted.
The reviewer would not need to close a theme as “not approved” because of minor coding errors, only if the themes are copies, spam etc.
The term queue will no longer be used. Reviewers will be able to decide if they want to review the oldest theme or any other theme.
Communication between authors and reviewers would be through e-mail.
Theme authors should have access to SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. to update their theme once it is live.
Parsing of the readme file: multiple authors, multiple screenshots etc.
There should also be standard texts for common errors, that could be added to a review.

We discussed how we can make the reviews available for anyone to read, and also where the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) review would fit in the new workflow.

Parts of the system is already in use by plugins, but it needs to be improved and completed. Once it is fully working for plugins, it will be copied over to themes. The first deadline is set to December 2017.

Another question concerned what information or feedback the theme author needs after submitting a theme. The suggestion is that instead of showing a theme’s queue position, we should show the current status (pending -awaiting review, pending -awaiting update).

Most of the points above requires the backend to be complete, but we also discussed what the Theme Review Team could do short term.

The team would need to inform theme authors about the specific format for the readme file so that it can be parsed correctly when the backend is ready. The suggested format is the current 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. readme.

We briefly discussed Theme Review requirements and the .org theme previews. It was suggested that the reviewers should allow more minor content creation and also focus more on design.

Code Automation for Themes/Plugins

PHPCSPHP Code Sniffer PHP Code Sniffer, a popular tool for analyzing code quality. The WordPress Coding Standards rely on PHPCS.’s problem requires certain functions and it can’t handle that.
Theme Check doesn’t have unit tests, so it rewrote it.
Dream: Checkboxes show green, yellow or red. Showing a theme/plugin health. Some required, some not.
Rank according to severity of issues.
Some people are overwhelmed with the requirements to be a TRT volunteer.
Humans would still be used to help with the quality of themes, but just from more people, not just contributors.
Three contexts: when developing, on upload, and continuous.
False positives are an issue at times.
Could be one backend, multiple front ends.
TagTag Tag is one of the pre-defined taxonomies in WordPress. Users can add tags to their WordPress posts along with categories. However, while a category may cover a broad range of topics, tags are smaller in scope and focused to specific topics. Think of them as keywords used for topics discussed in a particular post. errors so they’re suppressed if it’s not really an issue.
Local tool would help with false positives.
People could check in code, and when it passes, it could be made public to other people.
Huge opportunity for educating on best practices.
WordPress coding standardsWordPress Coding Standards The Accessibility, PHP, JavaScript, CSS, HTML, etc. coding standards as published in the WordPress Coding Standards Handbook. May also refer to The collection of PHP_CodeSniffer rules (sniffs) used to format and validate PHP code developed for WordPress according to the PHP coding standards. could be a check, but not required.
Plugins/Themes could include their own checks. Would need to be limited.
Checks could give compatibility for PHP7, etc.
Same check for WordPress versions. Knowing whether code generates warnings or errors would be helpful.
Searching for 500 errors.
Ticker for themes being activated WITH 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 errors.
This could improve directory interfaces for plugins and themes.
Can plugins be easily transferred. Need to know the expectations and norms. This way, plugins and themes could be more cared for.
Up to versions run now to tell people that’s not up to date, and it helps with updates.
Could be checks for mobile, etc. to push better themes to the top.
Probably need to start small. Up to checks and go from there.
Locally first, plugin, then server everywhere.
Reduce amount of manual checks for accessibility checks.
TRT is working on a lot of tools to start solving some of this.
Visual regression testing in themes has helped some developers.
Starter theme content could help with regression testing. What would be done with the differences? Users might want to know this.
Do the easy stuff first.

Rocio Valdivia 6:56 pm on July 24, 2017

Community Summit 2017 recaps will be posted here soon

As a few weeks have passed since Community Summit 2017, we’ve gathered some notes of the discussions that took place during the Summit (although we haven’t received notes of all discussions yet).

We’ve sent the notes we received so far to the respective team leads, and asked them to publish a post with their recaps on this make/summit p2 blog (if you haven’t being pinged already, this means that we haven’t received notes related to your team’s topics).

The Community Summit team would like to ask the team leads for the following:

A) If you haven’t published already a recap in your team’s p2:
Please publish a p2 post on this make/summit blog with a recap of all the discussions related to your team at the Summit.

B) If you have published already a recap in your team’s p2:
Please publish a p2 post on this make/summit blog with a link to that published recap.

Pinging some team reps who attended:
Rian Rietveld: @rianrietveld – 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)
Daniel Bachhuber – @danielbachhuber – CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.
Jonathan Desrosiers and Adam Silverstein – @desrosj @adamsilverstein – CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
Mike Schroder – @mikeschroder – Hosting
Jon Kenshino – @kenshino – Docs
Cate Huston – @catehstn – Mobile
Mika Epstein – @ipstenu – Plugins
James Huff – @macmanx – Support
Ulrich – @grapplerulrich – Themes
Tammie Lister – @karmatosed – Design
Francesca Marrano and Hugh Lashbrooke – @francina @hlashbrooke – Community
Petya Raykovska – @petya – Polyglots

Note: If you’re not an Author in this p2 already, please 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.” @andrescifuentesr or @milana_cap and they will give you access to it.

Thank you all! 🙂

Jenny Wong 8:08 am on June 13, 2017

2017 schedule

Please use this link to find the schedule for the two days.

https://docs.google.com/spreadsheets/d/1uTJKx31elVdYvbROUpadA7RCA41qWMq4TegCbItoRkg/edit?usp=sharing

Remember NO posting of anything such a pictures, notes or conversations on any social media.

Milana Cap 12:01 am on June 10, 2017

WordPress Community Summit 2017: Final list of topics

The 2017 WordPress Community Summit (CS) in Paris (Tuesday, June 13th – Wednesday, June 14th) is less than 5 days away and here is the final list of topics submitted by teams.

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

How can we increase JavascriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com contributions to Core?
What should be Core’s technology support policy (especially related to deprecating support)?
How can we better project manage contributors efforts in Core?
How can we improve the on-boarding experience for new contributors?
How can we improve the Security process from report through triage through disclosure? – (Security)

Design

Onboarding: How do we recruit and attract new designers to WordPress?
Retention: How do we retain new designers?
Process: How do we communicate a unified design process to contributors?
Collaboration: How do we work with other WordPress teams to supply design assistance? – (All)
Impact: How can WordPress impact the greater design community?

Mobile

WP 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. & the mobile apps
Possibly the new core blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor experience and how it can work with the upcoming Aztec native iOSiOS The operating system used on iPhones and iPads. & Android editors – (Core)

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)

New developments for the the Editor, and how to safeguard it’s accessibility – (Core)
Technology version support policies – (Core)
How to involve more developers in helping with the accessibility tickets
How to proceed with the handbook
Considering the shift towards JS-based interfaces, we should consider to review and update the accessibility coding standards

Polyglots

Increase outreach (Rosetta sites outreach, jump starting and upgrading our locale sites to best fit the community) – (Community)
Local contributor days – (Community)
Global contributor days (translation days)” – (Community)
Improvement of translation and communication tools 2.0 (we’ve already got the first phase of this going with the O2s, GlotPress improvements, etc) – (MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.)
Cross locale PTEs implementation discussions – (Meta)
Translating documentation (already mentioned above)” – (Meta)
New General Translation Editors onboarding/ Mentorship program and new translation contributors onboarding plan
Polyglots Leadership team growth plan in underrepresented regions

Support

Continue 2015’s discussion about how to make/keep the support community welcoming and open, while at the same time encouraging quality replies.
Go through the remaining items on the lists of known issues and requested enhancements. – (Meta)
Create a common style guide (best practices) that can be used across all forum language.

Themes

How we improve the leadership of the TRT team?
How can we encourage and enable more people to lead new projects?
What is the vision and goals of the team?
What is the future of the theme review team, can we change it to become the Theme Team and be more involved in theme related activities like improving the theme directory or the theme developers handbook? – (Meta, Docs)
Future of the theme review theme and making it smoother and faster
How we can encourage creative designs and how to stop more of copy themes which can just be child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/

Docs

Game Plan for recruitment
Onboarding Plan
State of Doc Team’s own documentation
DevHub and Helphub Translation
Clear way of contributing to specific parts of documentation
Helping other teams with their documentation – (All)
Discuss opportunities for leadership and retainment of contributors to ensure longevity of Docs Team goals

Community

Paying for speaker travel – following on from our existing discussion and reaching a consensus.
Regional camps – following on from our existing discussion and reaching a consensus.
WordCamps and Money – discussing guidelines for responsible use of funds and clearly outlining what will and will not pay for. Also looking at how this affects in-kind types of sponsorships.
Code of Conduct and harassment reports – Establishing a plan for training for organisers on how to deal with CoC violations, as well as reviewing the CoC to be more inclusive (possibly to be concluded at Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/).
Marketing & Engagement – discussing a general marketing plan for 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. and meetups, especially to engage people outside of the WordPress bubble – (Marketing)
The 80/20 rule for local/international speakers – this is a sticking point for many camps and it will be worth defining what we mean and where the line is for this.
Communication tools for WordCamp organisers – discussion on how to handle third party newsletter tools/services and how organisers can more effectively communicate with their community.

Plugins

Tools 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. devs need to manage their plugin – (Meta)
Tools plugin devs need to manage reviews and support (crossover with forums) – (Meta, Support)
How to effectively handle contributor days
Dependencies and libraries – can we save WP from DLL Hell? (crossover with core team) – (Core)
Safely and responsibly improving communication of closed plugins (crossover with the meta and security team) – (Meta, Security)

Training

None

WordPress Community Summit 2017: Attendees and Agenda Summary

The 2017 WordPress Community Summit (CS) is almost here. It will take place on Tuesday, June 13th and Wednesday, June 14th, the two days before contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/ at 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. Europe in Paris, France. All attendees should have received an email with venue and other important details. If you haven’t received such an email, or if you’re not able to attend, please let us know asap at community@wp-europe.org

We would like to remind all teams and contributors the purpose and goal of the Community Summit:

“The main purpose of the summit is to move the WordPress project forward before and after the event, with the event being a milestone in a larger set of work.

With this main goal in mind, we’ll touch base with all team reps to figure out which of the topics proposed can be handled beforehand, and come up with topics that would be:

1) of importance to the project as a whole

2) would benefit from cross-team collaboration

3) will leave us in a better position than when we started”

How Attendees Were Selected

Unlike WordCamps or Contributor Days, the Community Summit has limited capacity both because of the venue size and the type of work that is required. The list of nominations was reviewed by a committee composed of experienced contributors, chosen for their broad overview of the project and its community: @aaroncampbell @petya @chanthaboune @helen @ipstenu and @_dorsvenabili

The committee reviewed the list of nominated contributors that we received from the original call for nominations (more info on the process and criteria).

In voting on each person, we kept several things in mind:

Active contributions to 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/ project and that specific team
Influence/reach in the broader WordPress ecosystem (not just within WordPress.org)
Employer (to prevent an overwhelming presence by one or few select companies)
Location (to have a decent international contingent and not be solely US-focused)
Differing Points of View (to ensure minority voices can be heard)

Attendees

The list of attendees was formed from all those who were invited and confirmed their attendance:

@afercia @rianrietveld @davidakennedy @mor10 @samikeijonen

CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.

@schlessera @borekb @danielbachhuber @miyauchi

Community

@andreamiddleton @andrescifuentesr @iaaxpage @mbigul @courtneypk @thewebprincess @jennybeaumont @emanuel_blagonic @francina @mayukojpn @hlashbrooke @ibonazkoitia @miss_jwo @kcristiano @lanche86 @travel_girl @markgazel @imath @paolal @remediosgraphic @sptorabi @_dorsvenabili @mahype @thabotswana @00sleepy @xibe

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

@adamsilverstein @boonebgorges @chriscct7 @desrosj @dd32 @iseulde @flixos90 @jjj @joehoyle @joemcgill @joen @johnbillion @kadamwhite @matt @marcs0h @matveb @voldemortensen @azaozz @swissspidy @rmccue @stevenkword @westonruter @peterwilsoncc @codebykat

Design

@empireoflight @folletto @michael-arestad @melchoyce @saracannon @sonjanyc @karmatosed @liljimmi

Docs

@atachibana @kenshino @milana_cap

Hosting

@aaroncampbell @andrewtaylor-1 @ddsucurinet @joostdevalk @mikehansenme @mikeschroder @stephdau

MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.

@tellyworth @coreymckrill @pento @iandunn @obenland @mapk

Mobile

@catehstn @mbiais @kwonye

Plugins

@ipstenu @otto42

Polyglots

@glueckpress @chiragpatel @carl-alberto @ocean90 @imnok @lasacco @openstream @petya @tacoverdo @vannkorn

Support

@bethannon1 @cristianozanca @imazed @macmanx @clorith @sergeybiryukov @zoonini

Themes

@acalfieri @grapplerulrich @sakinshrestha @ionutn @poena

Training

@wpaleks @chanthaboune

Summary of Community Summit Agenda

Day 1 (Tuesday, 13 June):

Individual team and cross-team discussions* which need in-person discussions

Day 2 (Wednesday, 14 June):

Continuing cross-team discussions*

Writing recaps for the make/summit p2 blog

Proposed Discussions

A few months ago, each team proposed topics that need in-person discussion ( List of proposed topics ). If teams need to amend or update their list, post any changes as a comment, please. The deadline is Friday, June 9th, at which point we will close comments and publish the list of topics for WordPress Community Summit 2017.

Travel Assistance Program Applicants

All guests, selected for the travel assistance program have been contacted via email by the organizing team, who will follow up in the next few days. Thanks so much to all our sponsors for making this Travel Assistance program possible!

#attendees, #summit-2017

Andrés Cifuentes 1:47 pm on May 16, 2017

The Community Summit Travel Assistance program still needs your support

There are less than 30 days until the 2017 WordPress Community Summit, and we are still looking for your support with the Summit’s travel assistance program.

This year we are expecting contributors coming from Zimbabwe, Thailand, Costa Rica, Philippines, USA and all over the world. Most event costs for the 2017 WordPress Community Summit are being paid for by 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. Europe 2017 (Thank you WordCamp Europe!!), however we still need to focus all our efforts on raising the remaining funds for the summit’s travel assistance program to ensure we can bring these active contributors together.

So far, we have received a great support from the community. However we still need an extra push to guarantee the success of this program.

If you’d like to sponsor the Community Summit, check out the Call for Sponsors and sign on as a sponsor. We will be more than happy to get back to you with all details.

Thanks for being the part of the WordPress Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Project!

Andrés Cifuentes 4:27 pm on May 8, 2017

Community Summit 2017 Sponsors

The WordPress Community Summit only works because of the participation of our amazing community members. This year we are expecting contributors coming from Zimbabwe, Indonesia, North America, Japan and all over the world.

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. Europe covered mosts of the costs for the 2017 WordPress Community Summit (Thanks so much!), however we also needed to raise money to subsidize travel expenses for some of our community volunteers who don’t get paid for their work on WordPress and/or whose travel expenses are significantly higher than those living in Europe.

The following people sponsored this Summit and helped to build the future of WordPress Open SourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. Project.

Sponsorship Levels

Gold

Bluehost has been a WordPress partner since 2005 and powers over 1 million WordPress sites worldwide. Their objective is to help customers, whether novice or pro, create a thriving online presence at an affordable price. With a team of in-house tech experts available 24/7, Bluehost dedicates time and resources to providing the best support and services in the industry. Join millions of other site owners and see what Bluehost can do for you and your online presence.

Bronze

Human Made is a globally distributed WordPress development agency specialises in high-end WordPress development and consultancy for enterprise & big media.

Our knowledge of WordPress is extensive: many humans have been involved with the WordPress open source project for years, some since its very inception. Individually, we are skilled developers, driven project managers, dedicated account managers, organised event planners, and insightful product makers. Together, we are a friendly, enthusiastic, and approachable team, dedicated to finding problems, big or small, and doing what we can to fix them.

Since 1997 DreamHost has helped individuals, small businesses, entrepreneurs and developers the world over bring their dreams to life on the Internet. From domain registrations to traditional web hosting and highly-optimized managed WordPress hosting, more than 400,000 customers trust DreamHost to be their online home. DreamHost supports the WordPress project and community with dedicated resources and a passionate team. Packed with excellent value, DreamHost is a great place to launch a blog, website, or online application into the stratosphere!

At YITH we develop innovative WordPress themes and plugins for WooCommerce based sites. For years our philosophy has been based on simplicity and effectiveness as basic concepts required in any professional online business.

Our crown jewel, that makes us proud, is our high-quality support service, through which we take care of our customers day-by-day, never as a number, but as people with faces, names and a personal history that we deeply care for.

Individual

Ahoy! We are the pirates from ThemeIsle who believe that WordPress themes don’t need to be boring. That’s our primary motto and we’re doing everything we can to prove it—starting from our involvement in the community to developing Zerif Lite, one of the most popular themes out there.

SiteGround is a leading hosting provider internationally recognized for their unique approach to hosting. With a focus on performance, security and unmatched customer service, they provide solutions to protect your website from hacks and invented new technologies that can make your website run over one hundred times faster.

WP Site Care was founded in 2012 and was started with the focus of helping high profile bloggers and small business succeed online. We offer support and maintenance services for WordPress, along with a lot of other odds and ends. Our goal is to make sure you’re working on the business that you love, while we lift the technical burden behind the scenes. For less money than one part-time employee, you can have the technical expertise of our entire team, whenever you need help most. We’d love to talk more if you need a technical team that truly cares about the success of your business!

Thanks again to all these amazing companies who are contributing to the future of WordPress and its Open Source community!
We still haven’t covered the whole Travel Assistance Program, so if you’d like to sponsor the 2017 WordPress Community Summit, check out the Call for Sponsors and sign up. We will be more than happy to get back to you with all details.