Now on stage in Halle E: @GetSource (Mike Schroder) on Decision-making in WordPress Core #wceu pic.twitter.com/GJQ0ur3kie

— Sonja Leix (@sonjaleix) June 24, 2016

It was a pleasure to have the opportunity to share with everyone there — thanks to everyone who helped out; it was an outstanding event.

@GetSource about decision making in WordPress Core development #wceu pic.twitter.com/SF104Sh0aU

— Felix Arntz (@felixarntz) June 24, 2016

You can check out the slides below:

The post Decision-making in WordPress Core Development at WordCamp Europe appeared first on GetSource.net.

Was honored to be invited to share some of my experiences with WordPress 4.5.  Thanks to the organizers and everyone who attended for a great event!

Core contributor from @DreamHost, @GetSource gives us a preview of @WordPress 4.5 at #WCSTL pic.twitter.com/yYJYHZz9fZ

— Kari Leigh Marucchi (@foundartphotog) May 14, 2016

Check out the slides here:

The post An Insider’s Look into 4.5 at WordCamp St. Louis appeared first on GetSource.net.

I’ll be posting and speaking more about my experiences with the release in the coming months, but for now, a quick thank you note.

Thanks to Adam Silverstein (Release Deputy), Mel Choyce (Release Design Lead), and all of the 298 core contributors from around the world.

Additional thanks to everyone that helps out throughout all the contributor groups in WordPress; it wouldn’t be possible without you. 

Thanks to DreamHost for donating my time to the project. Commitment to Open Source matters.

Finally, thanks to my wife Elizabeth and daughter Sofía for your unfailing love, encouragement, and support throughout the release.

The post WordPress 4.5 appeared first on GetSource.net.

The most cross-platform and standard way of doing this is with VVV — with the only problem being large download size and conference Wi-Fi. Thus, we needed a packaged way to distribute a development environment using flash drives or Adhoc networking.

If you’re in a situation where Wi-Fi won’t be a problem on contributor day, great! If you need a solution for this, read on.

Contents for Contributors

• VirtualBox Installer/Package for their platform
• Vagrant Installer/Package for their platform
• Base VVV ZIP package with Pre-Provisioned box file within

Building a base VVV package

Using a ZIP for VVV is important because otherwise the checkout will have too many files to quickly copy from a flash drive or a local. To build the VVV ZIP package, follow these steps:

• Clone VVV:

  git clone https://github.com/Varying-Vagrant-Vagrants/VVV.git

• In the newly-minted VVV directory:

  vagrant up --provider virtualbox

  This will download the box file and also download all of the dependencies upon first provision. That’s important because they’re about as large as the box file, and account for almost a gigabyte of data.

• To create a base box that includes provisioned packages, run:

  vagrant package --output vvv-contribute.box

• Minus the .vagrant directory¹, zip the folder’s contents, including the newly-minted box, using either the command line or your favorite file manager.

Contributor Steps to Get Started

• Install VirtualBox
• Install Vagrant
• Copy VVV.zip to local drive and extract
• Add pre-provisioned box to Vagrant:

  vagrant box add ubuntu/trusty64 vvv-contribute.box

• Optional, and will download, but manages hosts file:

  vagrant plugin install vagrant-hostsupdater

• Start up Vagrant:

  vagrant up --provider virtualbox

Caveats

• Once a VirtualBox base box has been added manually from a system, it can’t be automatically updated without removing it, and adding it directly from the web. This means that updates to the Ubuntu base box would need to be done manually by contributors if they want to update later.
• This will not solve all potential Windows issues. While it worked with the majority of machines, there were some Windows users who could not unzip the file with native file ZIP utility, or had other incompatibilities with Vagrant.

Feedback

Have any questions or suggestions? Let me know in the comments!

¹ Edit (05/23/2016) – Looks like Vagrant is including the user ID that created the box in a .vagrant directory, which is causing problems for contributors when starting up the box on their local machines.

The post Building a VVV Distribution for WordPress Contributor Days appeared first on GetSource.net.

A Year in Core by @GetSource #WCLAX #PointBreak pic.twitter.com/quleM3bt2G

— WordCamp Los Angeles (virtual event) (@WordCampLAX) September 27, 2015

At WordCamp LA, I had the opportunity to share a retrospective on the happenings in WordPress core throughout the last year, and a short look into a possible future for WordPress in 4.4, coming in early December!

Thanks to the organizers and volunteers for an excellent event, and to everyone who came by to learn and chat about WordPress core!

You can find the slides in PDF here, or embedded below the break:

The post A Year in Core at WordCamp LA appeared first on GetSource.net.

You can find the slides here:

The post Stress Testing and Siege at WordCamp Vancouver 2015 appeared first on GetSource.net.

The post Mizu on Christmas appeared first on GetSource.net.

WP Conspiracy. #wcvc pic.twitter.com/mZ1iJuUjjW

— Frosty aka Austin (@TheFrosty) November 8, 2014

I gave a satirical talk called “Connect the Dots” at WordCamp Ventura about the WordPress community and its connections, whose slides you can see below.

Yes, it’s silly. Yes, I hope you enjoy it. I’ll post a link to the video when it lands on WordPress.tv.

If you’d prefer a download, you can find the PDF Here.

Have a favorite WordPress conspiracy theory?  Feel free to share it below!

The post Connect the Dots at WordCamp Ventura 2014 appeared first on GetSource.net.

Below, you can find the slides and code for my talk on the Heartbeat API for WordPress.

.@GetSource, showing us how to make WordPress honk with the heartbeat API at #wcnyc pic.twitter.com/IwyRKZm4V2

— K. Adam White (@kadamwhite) August 3, 2014

In this presentation, I also included a sample for a custom WordPress API endpoint (hat/tip Ryan McCue) for causing the WordPress admin to honk via a GET request (which is decidedly unRESTful, but equal to the way the Tesla Model S API works). I then provided this URL to the audience prior to discussing the code for much hilarity.

So @GetSource made a custom endpoint with the Heartbeat API to honk a horn in his presentation at #wcnyc: http://t.co/llFoO3e3uR

— Brian Krogsgard (@Krogsgard) August 3, 2014

Luckily, @getsource used heartbeat #wcnyc pic.twitter.com/IkLAzj18cE

— Brent Shepherd (@thenbrent) August 3, 2014

https://twitter.com/alpha1beta/status/496018182571048960

The code’s after the break. But think twice about deploying it on a production server, since it allows others to annoy you with unauthenticated requests. The JSON REST API plugin is required prior to the JSON API’s introduction in WordPress Core itself.

You can download the slides in PDF, and see the slides inline from Speaker Deck below.

<?php
/*
	Plugin Name: Heartbeat Honk
	Description: Honks WordPress' Horn using Heartbeat
	Author: Mike Schroder, Ryan McCue
	Version: 0.1
	Author URI: https://www.getsource.net
*/

add_filter( 'json_endpoints', function ( $routes ) {
	$routes[ '/honk_horn' ] = array(
		function () {
			$count = get_option( 'wc-heartbeat-honk', 0 );
			update_option( 'wc-heartbeat-honk', $count + 1 );
			return array( 'result' => true );
		},
		WP_JSON_Server::READABLE
	);
	return $routes;
} );

add_filter( 'heartbeat_received', 'wc_heartbeat_honk', 10, 3 );
function wc_heartbeat_honk( $response, $data, $screen_id ) {
	$do_honk = get_option('wc-heartbeat-honk', 0 );

	if ( $do_honk ) {
		// Add data in an unique array key -- prefix!
		$response['wc-heartbeat-honk'] = $do_honk;
	}

	delete_option('wc-heartbeat-honk');

	// If the above conditions aren't met,
	// we still pass along the existing $response.
	return $response;
	 
}

add_action( 'admin_enqueue_scripts', 'wc_heartbeat_honk_script_enqueue' );
function wc_heartbeat_honk_script_enqueue( $hook_suffix ) {

	// Make sure the JS part of the Heartbeat API is loaded.
	wp_enqueue_script( 'heartbeat' );

	// Output the JavaScript we need.
	add_action( 'admin_print_footer_scripts', 'wc_heartbeat_honk_js', 20 );
}

function wc_heartbeat_honk_js() {
	$honk_audio = plugins_url( "car-honk.mp3" , __FILE__ );
	?>
	<script>
	jQuery(document).ready( function($) {
		$(document).on( 'heartbeat-send.wp-heartbeat-honk', function( e, data ) {

			window.wp.heartbeat.interval(5);

		// Listen for the tick custom event.
		}).on( 'heartbeat-tick.wc-heartbeat-honk', function( e, data ) {
			// Double-check we have the data we're listening for
			if ( ! data['wc-heartbeat-honk'] ) {
				return;
			}

			var honk = new Audio('<?php echo $honk_audio; ?>');

			for ( var count = data['wc-heartbeat-honk']; count--; count > 0 ) {
				honk.play();
			}
		});

		// Initial connection to cement our new interval timing
		window.wp.heartbeat.connectNow();
	});
	</script>
	<?php
}

The post Heartbeat + WP REST API at WordCamp NYC appeared first on GetSource.net.

Thanks to the organizers for the opportunity, and everyone who showed up to listen to me speak very rapidly about polling awesomeness.

As of WordPress 3.9, the heartbeat api is no longer experimental. Use it in your plugins, but only in the admin. – @GetSource #wcsea

— Aaron Jorbin (@aaronjorbin) June 28, 2014

You can download the slides in PDF, and see the slides inline from Speaker Deck after the break.

This is just an introduction — For a deeper dive, check out this talk that was done in a longer form, and has example code attached.

If you have any questions, comment here, and I’ll happily update the post with further info!

The post Heartbeat API Jumpstart – WordCamp Seattle 2014 appeared first on GetSource.net.