Hard to fully express my enthusiasm for this next iteration of the business I started 12+ years ago and my fondness for my new business partners. 🎉🥳🍾. I’ve used so many apps they’ve built - their work sold me on buying Warby Parker glasses. My thoughts in the linked post.

RT @greyd_suite: What do @automattic's “Big Sky,” agency busywork, and AI’s future in WordPress have in common?.In episode #9 of Greyd Conv….

RT @brover: Catching up on @TheWPMinute and enjoyed this conversation with @jakemgold, particularly from 30:34-37:26, on the topic of FSE a….

My favorite part of this new e-commerce solution from our team - an easy way to order swag or branded gifts for clients or partner without having to carry and manage an inventory internally (which is even messier when sending sized apparel). 😎.

RT @Press__Conf: 🔧 Panel Announcement! 🔧.“Navigating the Future of WordPress in Digital Agencies” brings together powerhouses @kimberlylipa….

RT @markjszymanski: LIVE at 3 PM EST today!. WP Towhnall w/ @jakemgold, Founder of @10up . If you're a freelancer or agency owner, you're n….

RT @Press__Conf: 📢 We're excited to share @jakemgold will be taking the stage at #PressConf in April!. 📍 Tempe, AZ….

Every election, when it's time to study the California ballot propositions, @CalMatters is an absolutely indispensable resource. Very proud to also work with this scrappy, high quality publisher at @10up + @Fueled on select projects.

Sometimes it’s the little, fun projects that spark the most inspiration and joy. 🧙.

RT @joemcgill: So cool to see what this little @10up + WordPress Performance team project is growing up to be.

I'll be there!.

Some good, detail oriented policy thinking from @Dries - leader of @drupal CMS - around "maker-taker" problems in open source. I'm still hung up on how you "implement a fair and objective system for tracking . contributions" in such a big market, though.

I am still hopeful for the future of #WordPress, and would like to believe that one positive outcome today, a silver lining of lawyers being involved, can be the emergence of a long absent clarity and framework for OSS trademarks and licensing.

Call me a policy wonk, but I think this dialog is bigger than WP and suffers from vague appeals to ideology, rather than specific, practical policy making. Let's make WP & OSS durable against market forces & greed - to do so we need clarity, compromise, and specificity.

If we do introduce an "OSS tax", contribution or licensing, how would it work? Can we audit contribution? Can we force private revenue disclosure? Should it be a marginal tax, so tiny startups & SMBs aren't scared off? Can we do so without greatly impeding market share growth?.

I'd love to hear trademark licensing experts weigh in. What's a typical royalty? What's considered fair use in software? Are there legal / trust implications if the trademark holder is also a competitor?.

How adjacent does the OSS use have to be for it to "count"? Should @wpengine (or 10up?) also pay a licensing fee to PHP? MySQL?? Apache? Linux?? Perhaps only if you sell *the* OSS as a core value prop? What if you *use* it extensively, but don't make it core to your marketing?.

A more useful conversation for the entirety of OSS might be "how would that work, *exactly*, and what would be fair?" Is it 8% or revenue, as @photomatt proposes? Is it Five for the Future-like, as somewhat narrowly defined today? Do sponsorships - also marketing - count?.

A licensing system, preferably non-profit centered, with the option of fees (a tax) or volunteerism (labor contribution), strikes me as a reasonable way to help sustain popular OSS. It's certainly better than the "switching to closed" several others have taken (eg Elastic).

We think contribution to an open web is a vital core value at @10up. I never could have bootstrapped 10up with the moats, licensing fees and lack of freedoms of closed platforms. Heck, websites as a market only exist because of open, free technologies and standards. We owe this.

Regarding the dispute between WP Engine, Automattic, and WP org, I'd love to see a *far* more specific, far less binary dialog about structural contribution, licensing & OSS health. Let's imagine - what exactly would more specific, fair terms look like - beyond just #WordPress?.