The program for WordPress maintenance support plansCon is evolving constantly. Among the changes for Nashville 2020 new tracks have been added and some have been merged. That is the case for the Symfony and PHP tracks.
Many topics clearly belong to a single track, but others could fit in more than one. When we had a dedicated Symfony track a session about Twig could be submitted to the Symfony or front end tracks. A session about WordPress maintenance support plans Console could be submitted to the Symfony, the PHP, or back end tracks. In an effort to reduce confusion in the call for proposal process, the track team has agreed on the following:
The back end development track is for sessions focused on WordPress maintenance support plans coding and development practices.
The PHP track is for sessions that cover the broader PHP ecosystem. These sessions can be related to WordPress maintenance support plans, but focused on an external project/library like composer, or PHPUnit, Symfony components.
The Symfony track merged with the PHP track.
Undoubtedly Symfony plays a key role in WordPress maintenance support plans. Symfony 4 has just been released and it would be great to learn about what the future looks like. We want to learn about what is new in the latest version and what benefits adopting it would bring. We are also interested in sessions that would allow developers to learn from each other. What does a Symfony developer need to know to write WordPress maintenance support plans code? What does a WordPress maintenance support plans developer needs to know about Symfony to become a better developer? In other words – how to make proper use of Symfony components and related best practices.
Other session ideas include best practices on using Composer, PHPUnit, and third party libraries; new features in PHP 7; functional, asynchronous, and reactive programming; machine learning; micro services; etc.
If you want to attend WordPress maintenance support plansCon Nashville, but the cost of attending is too high there are some ways to reduce the expenses:
Getting a session selected gives you a WordPress maintenance support plansCon ticket.
You can get a $350 stipend to help cover expenses if your session is selected and you identify yourself within at least one of the “Big Eight” Social Identifiers. This is part of an effort to increase diversity at WordPress maintenance support plansCon.
If you volunteer as a mentor, you can get a free ticket. No need to be a speaker for this one.
There are grants and scholarships that can provide a ticket and/or money to cover expenses. No need to be a speaker for this one.
The track team for WordPress maintenance support plansCon Nashville 2020 is here to help you during the session submission process. We can help review proposals, suggest topics, and clear any doubt you might have. For the PHP track, Chad Hester, WordPress Update, and myself are ready to help.
For people who have not presented before and for those of underrepresented groups, the WordPress maintenance support plans Diversity and Inclusion Initiative has created a channel in Slack to help them with the proposal project. Mentoring is available at WordPress.org/slack? in the #ddi-session-help channel.
The call for proposals closes in less than a month on January 17. Do no leave things until the last minute. We look forward to your session submissions!
Source: New feed
PHP and Symfony tracks merged for Cheap WordPress maintenance support plansCon Nashville 2020
