Rocio Valdivia 2:52 pm on January 26, 2017
Tags: 2017, summit 2017 ( 5 )

Community Summit 2017

The 2017 WordPress Community Summit (CS) will take place on Tuesday-Wednesday, 13-14 June, before 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 (the venue will be in the XV district of Paris).

The CS is now in the planning stages, and this site will grow in the coming weeks to include information for attendees as well as event sponsorships, agenda, etc.

Based on the feedback and discussion p2 post (https://make.wordpress.org/community/2016/11/03/wordpress-community-summit-2017/) about a new approach for the 2017 CS, these are the next steps for every make.wordpress.org contributor team.

Next Steps:

Team reps, please post the following in a comment to this post.
The deadline is March 3rd, 2017.

A list of topics/issues which are relevant for the progress of the team and 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 as a whole, prioritizing topics or tasks which are sensitive enough to specifically require in-person discussion.
A list of representatives to attend the Community Summit (not limit-determined, but please keep in mind that our venue capacity limit is of 130 attendees), with selections based on several factors, including: representation of a wide, diverse range of opinions (based on the agreed-upon topics selected by each team), diversity, inclusion, and activity of the contributors.
One or two contributors who are willing to help with the organization of the event: posts, communication, travel assistance, finding sponsors, etc. The intention of this approach is to propose a more open and team-focused Community Summit with transparent participation from all active contributors and reps of each team. This way we can hopefully anticipate barriers and cross-team difficulties that might come up, and avoid them.

Notes:

The contributors who are willing to work on the summit (referenced in #3, above) will join the WCEU team working on the Community Summit. If there are not enough contributors available to help organize, the WCEU team has volunteers available to help.
We’ll work on finding sponsors to cover travel expenses for those contributors who face financial barriers. We’ll open a call for CS sponsors in the next days.
For those teams with sub-teams, for example, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.: REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/., security, etc. the representation of these sub-teams will depend on the list of discussion topics provided by the team.
In the next days, we’ll open an application form for people who aren’t invited as contributors, but who represent other interests within the wider WordPress Community.

—
Pinging all team reps:
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): @rianrietveld, @joedolson, and @afercia
Community: @francina and @hlashbrooke
Core: @jeffpaul, @helen
Design: @melchoyce, @karmatosed, @joen, @michaelarestad
Documentation: @kenshino
Test: @designsimply
Hosting: @mikeschroder
Marketing: @rosso99
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. (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/ Site): @samuelsidler
Mobile: @astralbodies, @rachelmcr
Plugins: @ipstenu
Polyglots: @petya, @ocean90, @nao, @chantalc, @deconf, @casiepa
Support: @macmanx
Themes: @jcastaneda, @grapplerulrich
Training: @bethsoderberg
TV: @jerrysarcastic, @roseapplemedia
Cli: @danielbachhuber

#2017, #summit-2017

Jon (Kenshino) 2:29 am on January 27, 2017

Gotcha Rocio
Rian Rietveld 9:21 am on February 28, 2017
Hi Rocio,

For 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) team: @afercia, @davidakennedy), @mor10, @rianrietveld and @samikeijonen would like to attend.

Proposed topics:
- New developments for the the Editor, and how to safeguard it’s accessibility
- Join the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. discussion (if accepted) about Technology version support policies as @jorbin proposed.
- How to involve more developers in helping with the accessibility tickets
- How to proceed with the handbook.
Daniel Bachhuber 11:55 pm on March 1, 2017
Hey Rocio,

For the CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. team: @danielbachhuber, @schlessera, @miyauchi and @borekb would like to attend.

Our proposed discussion topics are:
- 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/ Package Index / future of WP-CLI packages and new feature development.
- Improving the contributor workflow, and increasing the contributor pipeline.
- Generally, how to bring the WP-CLI experience closer to people.
I’m happy to help organize the community summit as needed.
Aaron Douglas 2:01 pm on March 2, 2017
For the mobile team we have at least two people that would like to attend: @mbiais and @catehstn.

Proposed topics would be centered around:
- 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 coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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.
I haven’t verified for sure but I bet @catehstn would lend a hand with organizing as she’s amazing. 🙂
- catehstn 9:09 am on March 3, 2017
  
  Thanks @astralbodies. Happy to help 🙂
- Aaron Douglas 12:39 pm on March 3, 2017
  
  One item we would also like to propose talking about and getting some help with others on is how to increase the amount of contributors on the mobile projects.
- Aaron Douglas 4:14 pm on March 8, 2017
  
  Hopefully it’s not too late – can I nominate @kwonye as well as I know he’s going to be able to attend.
James Huff 6:47 pm on March 2, 2017
For the Support Team: @macmanx, @clorith, @bethannon1, @zoonini, @cristianozanca, @sergeybiryukov, @imazed, @tnash, and @hardeepasrani would like to attend.

Topics we would like to propose and/or participate in:
- 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.
- Create a common style guide (best practices) that can be used across all forum languages.
- Improved management of contributors with time to spare.
@clorith and @bethannon1 have offered to lend a hand with organizing the summit.
Tammie Lister 7:07 pm on March 2, 2017
For the design team we’d like the following people to attend (they span across design areas and interests): @michaelarestad, @karmatosed, @mapk, @folletto, @empireoflight, @sonjanyc, @saracannon, @liljimmi, @ashleighaxios and @joanrho.

Representative to help with organising summit: myself (@karmatosed).

The topics we want to discuss are:
- 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?
- Impact: How can WordPress impact the greater design community?
- Tammie Lister 7:22 pm on March 2, 2017
  
  It’s worth adding to the above, that as focus leads are already included in invites, we did not include designers who are in that group. However, the following people are very important for us to have included in the design team discussions:
  
  @melchoyce, @joen, @matias.
Ipstenu (Mika Epstein) 11:35 pm on March 2, 2017
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 Directory Team

Attending: @ipstenu @otto42 (possibly @samuelsidler @dd32 and @tellyworth …)

Topics:
- Tools plugin devs need to manage their plugin
- Tooks plugin devs need to manage reviews and support (crossover with forums)
- How to effectively handle contributor days
- Dependencies and libraries – can we save WP from DLL Hell? (crossover with coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team)
- Safely and responsibly improving communication of closed plugins (crossover with the 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. and security team)
- Marketplace plugins
Coordinating… I guess it’s me, since no one else volunteered. We’re a really small team 🐹
Francesca Marano 7:03 pm on March 3, 2017
The Community team selection board has been hard at work, reviewing topic proposals and coming up with a roster of people that we feel could be candidates to participate in a number of discussions.

We received a lot of proposals and we wish we could say “Yes!” to everything and everyone, but alas, space is limited and time too.

We came up with a list of 18 people that we would like to be considered for the Community Summit; please note, this is not a formal invitation, but more of a wishlist of potential attendees. We’ve also included an incomplete list of people who will be there with other teams, but we’d still value input from.

Topics
- Global involvement
- WordCamps & Money
- Marketing & Engagement
- Paying for speaker travel
- Regional camps
- Improving deputy training
- CoC and harrassment reports
- Supporting other event types
People (in alphabetical order)
- Aditya Kane (@adityakane)
- Andrea Middleton (@andreamiddleton)
- Arnstein Larsen (@arnsteinlarsen)
- Cami Kaos (@camikaos)
- Courtney Patubo Kranzke (@courtneypk)
- Dee Teal (@thewebprincess)
- Emanuel Blagonic (@emanuel_blagonic)
- Hugh Lashbrooke (@hlashbrooke)
- Ibon Azkoitia (@ibonazkoitia)
- Ivan Kristianto (@ivankristianto)
- Jenny Wong (@miss_jwo)
- Kevin Cristiano (@kcristiano)
- Maja Benke (@travel_girl)
- Mayuko Moriyama (@mayukojpn)
- Rafael Funchal (@rafaelfunchal)
- Roberto Remedios (@remediosgraphic)
- Rocío Valdivia (@_dorsvenabili)
- Thabo Tswana (@thabotswana)
People from other teams

There are a number of people whose input we’d greatly value, but who are already being invited by other teams:
- Dion Hulse (@dd32; coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., 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.)
- Josepha Haden (@chanthaboune; training)
- Morten Rand-Hendriksen (@mor10; 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))
- Pantip Treerattanapitak (@inmok; polyglots)
- Sami Keijonen (@samikeijonen; accessibility)
- Taco Verdonschot (@tacoverdo; polyglots)
- Ulrich Pogson (@grapplerulrich; theme review team)
- Jenny Wong
- Mayuko Moryama
Thank you!
- Francesca Marano 7:30 am on March 6, 2017
  
  Also Jon @kenshino will be there and his input will be valuable to our discussions.
Samuel Sidler 10:22 pm on March 3, 2017
The 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. team is very much a “service” team, in that we build the features and products that other teams request and need. Thus, we don’t have a long list of topics that our team should drive. That said, this year, we have one major topic that we’d like to discuss in-person, specifically with the #polyglots, #docs, and #support teams:
- Translation of documentation on 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/, including developer hub and (the future) help hub.
For this topic, and for other topics wherein other teams will want us to participate, the following active contributors to the meta team (based on commits and props over the past year), have been nominated to attend (note that some of these individuals will be on the lists of other teams): @coffee2code, @coreymckrill, @dd32, @iandunn, @jmdodd, @mapk, @obenland, @ocean90, @pento, @samuelsidler, @sergeybiryukov, @tellyworth.

Edited to add: I am happy to help with the organization.
Sara Rosso 10:50 pm on March 3, 2017

For the Marketing team, which is incredibly new and starting to gain momentum, we don’t have any specific conflicts or issues to resolve – please note that I’m not saying we don’t have a ton of work to do nor are there things we could be doing better – but given the focus of the Summit to focus on issues & conflicts which need in-person discussions/resolutions, it’s best if we give more room to other teams and issues this time around.

The building and doing more part of marketing will happen as usual during 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. and in our 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/./weekly meetings. They’re broken down by subgroup! Please join us :slightly_smiling_face: https://make.wordpress.org/marketing/2017-slack-meeting-schedule/

With that being said, I’d LOVE it if some of the teams here could discuss how to better utilize and work with all the wonderful marketing volunteers to make marketing more part of the project flow. Marketing the Community is off to a great start & working well with the Community team, but Marketing to End Users, Marketing to Developers, and Marketing to Agencies & Clients could have more ties to groups like Training, Documentation, CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., and others.
- Nirmal Desai 7:23 am on March 9, 2017
  
  I am interested to be part of the summit for Marketing to End Users & Marketing to Agencies & Clients .
  - Sara Rosso 2:16 pm on March 9, 2017
    
    Hi Nirmal, we chatted a bit in .org 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/. but due to the reasons above marketing won’t have a dedicated session at the summit but we’ll definitely want to keep working on things 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.!
Ulrich 7:23 am on March 4, 2017
For the Theme Review Team

The topic that we would like to discuss are:
- 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?
- 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/..
We have also a few projects that we would like to work on together, also in preparation for the 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://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. at WCEU.
- A set of good slides on the introduction to theme reviewing that can be used for contributor days
- Improving the documentation so that it is clearer and easier to understand
- Work on improving the theme author and reviewer experience by analysing the whole theme review process.
- Improving the review process and focus on quality and good codes
Possible candidates are: @grapplerulrich, @poena, @sakinshrestha, @cristianozanca, @acalfieri, @ionutn
Petya Raykovska 11:30 am on March 4, 2017
Polyglots teamPolyglots Team Polyglots Team is a group of multilingual translators who work on translating plugins, themes, documentation, and front-facing marketing copy. https://make.wordpress.org/polyglots/teams/. list of reps and topics

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

I see @mayukojpn and @sergeybiryukov have already been nominated as part of other teams, I’d just like to say that they are essential for most of the Polyglots discussions we’d like to have.

Topics

Polyglots team & community team topics:
- Increase outreach (Rosetta sites outreach, jump starting and upgrading our locale sites to best fit the community)
- Local contributor days
- Global contributor days (translation days)
Polyglots team & 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. team topics:
- Improvement of translation and communication tools 2.0 (we’ve already got the first phase of this going with the O2s, GlotPress improvements, etc).
- Cross locale PTEs implementation discussions
- Translating documentation (already mentioned above)
Polyglots Processes
- New General Translation Editors onboarding/ Mentorship program and new translation contributors onboarding plan
- Polyglots Leadership team growth plan in underrepresented regions
- Chirag Patel 7:55 am on March 6, 2017
  
  Thank you @petya
Mike Schroder 7:20 am on March 5, 2017

Hi Rocio,

For the Hosting team, I’d like to nominate @boogah, @aaroncampbell, @lukecavanagh, and @mikeschroder (myself) to attend.

In addition to the hosting topic below, these suggested folks would be good to have for coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. related conversations, including the one regarding 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/preface.php./technology adoption.

The Hosting team is fairly new, and most of the current concerns are being handled within the group publicly/over the web, and do not need in person communication.

We have only one separate topic suggestion (from @aaroncampbell):
“How can the Core Security Team work better with hosts? During the 4.7.2 release, our interactions with hosts were drastically expanded, but I would love to continue to pave a path between core security and hosts”

For this topic, it’d be good to also invite a few representatives from the security community. From hosts who are currently involved, @rawrly, @mhildum, and @vortfu are a few good options. From the WP security space, @dcid would be a good option. I’m open to suggestions on folks who would be good to invite from outside the WP space.

I’m willing to help organize as necessary.
- Luke Cavanagh 1:53 am on March 6, 2017
  
  @mikeschroder
  
  Thanks for the nomination recommend, I think @mikehansenme would be a better option for the hosting team, since I will not be attending 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.
Jeffrey Paul 3:15 am on March 6, 2017
Hola Rocío!

The following are the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. team’s proposed topics:
- 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 (especially related to utilization of the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think “phone app” or “website”) can communicate with the data store (think “database” or “file system”) https://developer.wordpress.org/rest-api/.)?
- 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?
The following are the Core team’s proposed invitees:
Leads & active committers (in alphabetical order): @aaroncampell, @adamsilverstein, @afercia, @azaozz, @boonebgorges, @dd32, @drewapicture, @flixos90, @iseulde, @jeremyfelt, @jnylen, @joehoyle, @joemcgill, @johnbillion, @jorbin, @mark, @matt, @melchoyce, @michael-arestad, @mikeschroder, @nacin, @obenland, @ocean90, @pento, @peterwilsoncc, @rachelbaker, @rmccue, @sergeybiryukov, @swissspidy, @westonruter

2017 focus leads: @joen, @kadamwhite, @matveb

Additional nominees, including self-nominations (in alphabetical order): @celloexpressions, @chriscct7, @danielbachhuber, @desrosj @ipstenu, @jjj, @logankipp, @petya, @rianrietveld, @samuelsidler, @stevenkword, @voldemortensen

(@helen and @jbpaul17 have indicated they cannot attend this year, but would otherwise be included in this list.)

Gracias,
Jeff.
- Jeffrey Paul 3:30 am on March 6, 2017
  
  That’s @aaroncampbell & @jnylen0 above.
- Mike Schroder 9:59 pm on March 6, 2017
  
  What should be CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s technology support policy (especially related to deprecating support)?
  
  I think that @joostdevalk would be helpful for this conversation, in particular relating to the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. upgrade push he’s working on.
Jon (Kenshino) 6:51 am on March 6, 2017

Hiya,

The documentation team remains focused on projects it started years ago at the first community summit.

However, this year we are deeply aware of the limitations of our team at managing contributors, in part stemming from a lack of process and in part from a lack of a system (software) to do so.

Below are a list of topics we’re gonna work on

1. Game Plan for recruitment
2. Onboarding Plan
3. State of Doc Team’s own documentation
4. DevHub and Helphub Translation
5. Clear way of contributing to specific parts of documentation
6. Helping other teams with their documentation

Some details are available here https://make.wordpress.org/docs/2017/02/19/summary-for-documentation-team-meeting-february-16/

In addition, the documentation team will be part of 2 major topics that is relevant across the WordPress Teams

1. Improved management of contributors with time to spare:
https://make.wordpress.org/core/2017/02/23/planning-for-community-summit-2017/#comment-32191

2. Communicating changes to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
https://make.wordpress.org/core/2017/02/23/planning-for-community-summit-2017/#comment-32196

@kenshino, @drewapicture, @milana_cap, @atachibana are slated to attend

In addition, we are hoping that the attendees nominated by other teams will join us in discussions as well

@carl-alberto @samuelsidler @adamsilverstein @clorith @rianrietveld @hardeeparasni @mapk

This is by no means an exhaustive list, please feel free to contact @Kenshino to suggest topics or nominate someone (or yourself) to the summit
- Jon (Kenshino) 7:49 am on March 7, 2017
  
  @kenshino @milana_cap and @atachibana will volunteer to be part of the Summit Team
Rocio Valdivia 9:31 am on March 7, 2017

Thank you very much to all team reps! 🙂
We’ll get in contact very soon with all the people who has stepped up for organizing the CS for the next steps.
The final list of topics and attendees will be posted in this p2 on March 15th.
Jerry Bates (jerrysarcastic) 8:31 pm on March 9, 2017

Adding here (a bit late) that similar to the Marketing team, for the WordPress.tv team we don’t have any specific topics or conflicts that would need in-person discussions/resolutions, so it makes sense for us to also give space to other teams to discuss the issues we are facing.

We do of course have issues that we are working to solve around improving the submission rate/volume for videos on our site, as well as technical challenges in submitting content that usually involved many gigabytes of data, but I don’t think those will be solved via discussion at the CS.

We wish you all the best!
bethsoderberg 2:36 pm on March 10, 2017

The training team is not proposing topics this year. @chanthaboune will attend as our proxy rep and we’d also like to nominate @wpaleks to attend and participate in the conversations that are related to the training team.
Rocio Valdivia 6:03 pm on March 15, 2017

Update: We’re working on the post with the final list of topics and attendees, this will be posted in this p2 not later than March 24th.

Comments are closed.

Next Steps:

Notes:

Share this:

Site resources