TheNicksterTheNickster

Episode 25 of The SitePoint Podcast is now available! This week, Brad Williams (@williamsba) has a one-on-one chat with Matt Mullenweg, the creator of the popular WordPress blogging software.

SitePoint Podcast的 第25集現已發布！ 本周，布拉德·威廉姆斯( @williamsba )與流行的WordPress博客軟件的創建者Matt Mullenweg進行了一對一聊天。

在瀏覽器中收聽 (Listen in your Browser)

Play this episode directly in your browser! Just click the orange “play” button below:

直接在瀏覽器中播放此劇集！ 只需點擊下面的橙色“播放”按鈕：

A complete transcript of the interview is provided below.

下面提供了采訪的完整筆錄。

下載此劇集 (Download this Episode)

You can also download this episode as a standalone MP3 file. Here’s the link:

您也可以將本集下載為獨立的MP3文件。 這是鏈接：

• SitePoint Podcast #25: WordPress with Matt Mullenweg (MP3, 33MB)

  SitePoint播客＃25：WordPress與Matt Mullenweg (MP3，33MB)

面試成績單 (Interview Transcript)

Kevin: The SitePoint podcast episode 25 for Friday, August 28, 2009: WordPress with Matt Mullenweg. Hi there, and welcome back to the SitePoint Podcast: news, opinion, and fresh thinking for web developers and designers. I’m your host Kevin Yank coming to you from SitePoint Headquarters in Melbourne, Australia and I’m joined by my panel of cohosts.

凱文： SitePoint播客第25集，2009年8月28日，星期五：WordPress和Matt Mullenweg。 大家好，歡迎回到SitePoint播客：有關Web開發人員和設計師的新聞，觀點和全新思路。 我是您的主持人Kevin Yank，從澳大利亞墨爾本的SitePoint總部來找您，還有我的主持人小組。

Brad: Brad Williams from WebDev Studios.

布拉德：來自WebDev Studios的布拉德·威廉姆斯。

Patrick: Patrick O’Keefe of the iFroggy Network.

帕特里克： iFroggy網絡的Patrick O'Keefe。

Stephan: And Stephan Segraves from Houston, Texas.

斯蒂芬：還有來自德克薩斯州休斯頓的斯蒂芬·塞格雷夫斯。

Brad: Hello and welcome to the show. I’m actually running master control today and I’m joined by Matt Mullenweg of WordPress fame. Welcome to the show, Matt.

布拉德：您好，歡迎參加演出。 我實際上今天正在運行主控制，并且有WordPress名望的Matt Mullenweg加入。 歡迎參加演出，馬特。

Matt: Howdy. Glad to be here.

馬特：你好。 很高興來到這里。

Brad: Why don’t you take a second to just tell us who you are for the 1% of the people out there that don’t know.

布拉德：為什么不花一秒鐘的時間告訴我們，對于不認識的那1％的人，您是誰。

Matt: Sure. My name is Matt Mullenweg. About 6? years ago now, I started working on a project called WordPress, which is open source blogging software that since evolved to really do just about everything. You can use it for a blog, or you can power your entire web site with it. About a few years ago after that, I founded a company called Automattic which the sort of idea was it’s to bring WordPress to the world, and our biggest project is WordPress.com which gets over 200 million visitors a month.

馬特：好的。 我叫Matt Mullenweg。 大約在6?年前，我開始從事一個名為WordPress的項目，這是一個開放源代碼的博客軟件，自此演變為實際上可以做所有事情。 您可以將其用于博客，也可以使用它來驅動整個網站。 大約幾年后，我成立了一家名為Automattic的公司 ，其主旨是將WordPress推向世界，而我們最大的項目是WordPress.com ，該網站每月吸引超過2億訪問者。

Brad: That’s great. WordPress.com, that’s actually powered off WordPress MU, is that correct?

布拉德：太好了。 WordPress.com，實際上是關閉了WordPress MU的電源，對嗎？

Matt: Yup. Obviously.

馬特：是的 。 明顯。

Brad: Is it powered off the same version of MU that I can go and download or set up or is it more like customized for WordPress.com?

布拉德：它關閉了我可以下載和設置的MU的電源，還是更像是為WordPress.com定制的？

Matt: It’s basically the same. So the custom stuff that we need is obviously because it runs across more than a thousand servers and multiple data centers and everything like that, but we’ve actually open sourced I think pretty much all of our systems there. For the database, we use a class called HyperDB, which is available for anyone to download. We have a job system that we’ve released, although it’s not very well known yet. We use a memcached plug-in and a thing called Batcache for caching and those are all public and out there. The idea is that any software we develop, we want it to be available to as many people as possible.

馬特：基本上是一樣的。 因此，我們需要的自定義內容顯然是因為它可以運行在一千多臺服務器和多個數據中心以及類似的所有內容上，但是實際上我們開源了，我認為那里的所有系統都差不多。 對于數據庫，我們使用名為HyperDB的類，任何人都可以下載。 我們已經發布了一個工作系統 ，盡管它還不是很知名。 我們使用memcached插件和一個稱為Batcache的東西進行緩存，這些都是公開的。 我們的想法是，我們開發的任何軟件都希望盡可能多的人可以使用。

Brad: Going back to what you said, six years ago when you first started WordPress—and this is actually a question from one of SitePoint forum members, ULTiMATE. ULTiMATE would like to know, when you first started building WordPress, did you envision it as solely being a blogging platform or did you think it would evolve into what it kind of has now where a lot of people are using it as more of a CMS or content management system?

布拉德：回到六年前剛開始使用WordPress時所說的內容，這實際上是SitePoint論壇成員ULTiMATE提出的問題。 ULTiMATE想知道，當您剛開始構建WordPress時，您是否將其設想為僅是博客平臺，或者您認為它會演變成現在的形式，因此很多人都將其用作CMS還是內容管理系統？

Matt: It was created solely as blog platform. That was pretty much it. I had a blog I wanted to power the blog. A big thing in the software used to be how do I embed this in an existing site and at some point that switched to from how do I embed this, to how do I power my whole site with it. That actually makes a lot more sense.

Matt：它完全是作為博客平臺創建的。 僅此而已。 我有一個博客，希望為其提供支持。 該軟件中的一件大事是，如何將其嵌入到現有站點中，并在某個時候切換到如何將其嵌入到現有的站點中。 這實際上更有意義。

Brad: That really does and I think now at least in the last few years, it’s really WordPress has really evolved in the public eye as well as from just being a blog platform to really a CMS that can—it’s so extensible, it can really power anything.

布拉德：確實如此，我認為至少在最近幾年中，WordPress確實已經在公眾視野中真正地演變了，從一個博客平臺發展到一個真正的CMS，它可以—如此可擴展，它可以給任何東西供電。

Matt: Among sort of the web savvy, that’s pretty well known but the wider world in general doesn’t know that and in fact, many of our competitors say, “Oh, WordPress is good if you just want to blog, but anything more serious, you should go to X, Y, or Z…” and I obviously disagree with that.

馬特：在某種精通網絡的人中，這是眾所周知的，但是更廣泛的世界卻不知道，事實上，我們的許多競爭對手都說：“哦，如果您只想寫博客，WordPress是很好的，但是還有更多說真的，您應該去X，Y或Z…”，我顯然不同意。

Brad: Oh yeah, absolutely and working with it, I would say the same thing. Has there been any discussion in the developer chat or amongst the core developers, or just with you in general, about actually removing the blog reference from WordPress from like the different setting pages and documentation and things like that?

布拉德：哦，是的，絕對可以，我會說同樣的話。 在開發人員聊天中或在核心開發人員之間，或者只是與您一般而言，是否有關于實際上從WordPress刪除博客參考(例如不同的設置頁面和文檔等)的討論？

Matt: No. Web sites in the future, whether or not the blog is a primary part of it, most web sites are going to have a blog. I’m very much against needless abstraction.

Matt：不會。將來的網站，無論博客是否是博客的主要部分，大多數網站都會有一個博客。 我非常反對不必要的抽象。

Brad: With my work, I use it more as a content management system than I do blog but almost everything I launch, like you said, typically has a blog feature attached to it so I can definitely see where you’re coming from. The next question is from centered effect, and what they’d like to know is at what point would you consider WordPress to become too bloated in terms of code, or is there a point where it becomes too bloated?

布拉德：在我的工作中，我將它更多地用作內容管理系統，而不是博客，但是我發布的幾乎所有內容(如您所說的)通常都附加了博客功能，因此我絕對可以看到您的來歷。 下一個問題來自居中效果 ，他們想知道的是，您認為WordPress在什么時候變得過于腫，或者在某個時候它變得過于？腫？

Matt: Yeah, absolutely. WordPress has gotten bigger over the years but it’s been pretty much in line—I try to sort of keep it relative to sort of broadband speeds and server capacities and everything of the day. I try to keep WordPress sort of about the same I guess bloat level—would be a way to put it. In general, typically for new features, we say that’s probably not right for core, that’s something that belongs in a plug-in, and that’s one of the more difficult decisions we make day to day. The vast majority of stuff goes in plug-in. When I think something’s going to go in core, it’s either because—well it’s because it’s one of two things; the 80/20 rule—more than 80% of our audience is going to use this, or I think 80% of our audience should use this. There is sometimes some of that. Occasionally we’re ahead of the curve but more often than not, the world catches up.

馬特：是的，絕對是。 多年來，WordPress不斷發展壯大，但一直保持一致—我試圖使它相對于寬帶速度和服務器容量以及一天中的所有時間保持相對。 我試圖使WordPress保持大致相同的水平，這將是一種表達方式。 通常，對于新功能，我們通常說這可能不適合核心，這是插件中所包含的，這是我們每天做出的更困難的決定之一。 絕大多數東西都在插件中。 當我認為某種東西會進入核心時，這是因為-嗯，是因為這是兩件事之一； 80/20規則-超過80％的受眾群體將使用此規則，或者我認為80％的受眾群體應使用此規則。 有時有些。 有時我們會走在曲線的前面，但世界總是在追趕。

Brad: Absolutely. Has there ever been any talk of maybe a lighter version of WordPress that is really just kind of the bare necessities to run a site?

布拉德：絕對。 有沒有人談論過WordPress的較輕版本，實際上只是運行站點的一種必需品？

Matt: WordPress is already pretty light. Where I worry about code overhead is mostly in terms of scalability. We’ve shown that it’s actually not that hard on a single server to scale WordPress to millions and millions of pages a day, which is far more than 99.9% of web sites are ever going to get. So I feel like that sort of concern is pretty well addressed.

馬特： WordPress已經相當輕巧。 我擔心代碼開銷的地方主要是可伸縮性。 我們已經證明，在一臺服務器上將WordPress擴展到每天數以百萬計的頁面實際上并不難，這遠遠超過了99.9％的網站。 因此，我覺得這種擔憂已經很好地解決了。

Brad: I know there was a fork at one point, I think it was called LightPress, I don’t know too much about it but I remember reading about it a little bit that they forked WordPress and tried to make a lighter version. I think it’s dead in the water now though.

布拉德：我知道有一個叉子，我認為它叫LightPress，對此我不太了解，但我記得讀過一點，他們叉了WordPress并試圖制作一個更淺的版本。 我認為現在已經死了。

Matt: Yeah. And there have been probably a dozen forks of WordPress over the years. It’s just that what’s different about it, does it really matter to users? It’s hard to decide, but I don’t mind forks at all. It’s sort of the open source way, and if a fork ever came along that did something really, really cool, we’d probably look at bringing it’s functionality back in the core.

馬特：是的。 這些年來，可能有十幾個WordPress分支。 只是它有什么不同，對用戶真的重要嗎？ 很難決定，但我根本不介意分叉。 這是一種開放源代碼的方式，如果出現了一個分叉，它確實做了非常非?？岬氖虑?#xff0c;我們可能會考慮將其功能重新帶入核心。

Brad: Technically, WordPress started out as a fork, did it not?

布拉德：從技術上講，WordPress起初只是一個分支，不是嗎？

Matt: It absolutely did, yeah.

Matt：的確如此，是的。

Brad: So without forks, then there would be no WordPress, so that sounds great.

布拉德：因此，如果沒有叉子，那么就不會有WordPress，所以聽起來很棒。

Matt: And it’s a fundamental part of open source as well.

Matt：這也是開源的基本組成部分。

Brad: The next question is actually from AlexDawson, who is one of the mentors on SitePoint, and he would like to know why WordPress chose to use XHTML 1.0 as the DOCTYPE.

布拉德：下一個問題實際上是來自SitePoint的指導者之一AlexDawson，他想知道WordPress為什么選擇使用XHTML 1.0作為DOCTYPE 。

Matt: That was probably five or six years ago.

馬特：大概是五六年前。

Brad: Well, I guess maybe a more relevant question would be are there any plans now that XHTML 2.0 is pretty much dead in the water, are there any plans to look at changing that over outside of XHTML?

布拉德：嗯，我想也許是一個更相關的問題，因為XHTML 2.0幾乎已經死了，是否有任何計劃，是否有計劃在XHTML之外進行改變？

Matt: So, there are no plans for XHTML 2.0. There are some really cools features coming in what’s known as HTML 5 and that whole process, the web apps group, that I’m very, very excited about and we will continue to embrace those as they become sort of widely supported in browsers. As for the actual syntax of a code, are we going to stop self-closing BR tags and closing list items? Probably not. Even if we weren’t XHTML, it’s still like sort of the—I like the rules of XHTML and so I don’t see anything wrong with continuing that. The actual DOCTYPE isn’t as important as it used to be.

Matt：因此，沒有針對XHTML 2.0的計劃。 HTML 5中有一些非常酷的功能，整個過程(Web應用程序組)令我非常興奮，我們將繼續接受這些功能，因為它們在瀏覽器中得到了廣泛支持。 至于代碼的實際語法，我們是否要停止自動關閉BR標簽并關閉列表項？ 可能不是。 即使我們不是XHTML，也仍然有點像-我喜歡XHTML的規則，因此我認為繼續這樣做不會有任何問題。 實際的DOCTYPE不再像以前那樣重要。

Brad: I would agree with that and a lot of talk is about people focused on XHTML and now that it looks it’s really not going anywhere, is HTML 5 going to be the answer? Will they ever finish HTML 5? Who’s going to adopt it? There are still a lot of questions out there and I think over time, those will probably be answered based on how HTML 5 is adopted.

布拉德：我同意這一點，并且很多話題都集中在關注XHTML的人身上，現在看來它真的行不通了，HTML 5會成為答案嗎？ 他們會完成HTML 5嗎？ 誰將采用它？ 仍然有很多問題，隨著時間的流逝，我認為，這些問題可能會根據HTML 5的采用方式得到解答。

Matt: It’s a syntax thing; it’s not a huge deal. I’m less concerned about the answer of is XHTML the future or is it even correct to serve it without setting the application/xml whatever, MIME type and all those sorts of rules, rather than just like it’s a syntax cleaner and does it sort of force you to be a little bit tidier about your code.

馬特：這是語法問題； 這沒什么大不了的。 我不太擔心XHTML是未來的答案，還是在不設置application / xml，MIME類型和所有此類規則的情況下提供服務甚至是正確的，而不是像語法清潔程序那樣進行排序迫使您對代碼稍加整理。

Brad: And then the actual WYSIWYG editor that’s embedded in the WordPress, that doesn’t actually clean up the code so it’s specific to any DOCTYPE, does it?

布拉德：然后是嵌入在WordPress中的實際所見即所得編輯器，實際上并沒有清除代碼，因此它特定于任何DOCTYPE，是嗎？

Matt: It tries it’s darndest. It obviously can’t clean everything, it can’t fix everything but if you’re just using the editor, it will produce valid code. If you paste something in from a different web page or from Microsoft Word, again it will try to clean it up but sometimes we can’t do anything.

馬特：它嘗試得最老套。 它顯然無法清除所有內容，也無法修復所有內容，但是如果您僅使用編輯器，它將產生有效的代碼。 如果您從其他網頁或Microsoft Word中粘貼某些內容，它將再次嘗試清除它，但有時我們無能為力。

Brad: I know that’s I think on the wish list of WordPress things that WYSIWYG editor has always been kind of towards the top but I think it’s an issue with any platform that you work with.

布拉德：我知道這是我所希望的WordPress清單上所希望的WYSIWYG編輯器一直都排名靠前的事情，但是我認為與您使用的任何平臺有關的問題都是如此。

Matt: WYSIWYG in general, is super hard. We just try to make it better with every release—and it has gotten better with every release, if you compare what we do now to what we had two or three years ago when it was first introduced, it’s changed quite a bit.

Matt：所見即所得，非常難。 我們只是嘗試在每個發行版中都做得更好，并且每個發行版中都做得更好，如果將我們現在所做的工作與兩年前首次發布時所做的進行比較，它會發生很大的變化。

Brad: I think it’s much more stable. I’m typically the view source kind of guy, stick with HTML but the last few versions, I have been finding myself using WYSIWYG a little bit more.

布拉德：我認為它要穩定得多。 我通常是查看源代碼的人，堅持使用HTML，但在最近的幾個版本中，我發現自己使用所見即所得的功能要多一些。

Matt: That’s actually fantastic. For me, I’ll use the WYSIWYG when I’m writing; meaning that if I’m like trying to write an essay or something meaningful, the HTML kind of mentally gets in my way. It’s not that I don’t know HTML like the back of my hand, it’s just that clutter distracts me from the words and makes it harder for me to edit my own writing and editing your own writing is already really hard.

馬特：真的很棒。 對我來說，我在寫作時會使用所見即所得。 意思是說，如果我想寫一篇論文或一些有意義的文章，那么HTML就會給我帶來麻煩。 這并不是說我不喜歡手背HTML，而是因為混亂使我分心，使我更難以編輯自己的作品，而編輯自己的作品已經非常困難。

Brad: I think everybody kind of has their own ways that they do it. I’m still used to kind of writing a hrefs and image tags and it just feels natural to me. I don’t blog quite as much as you do, or as a lot of the audience out there might, but when I do, I like to make sure it’s very clean and precise and I think viewing the code for me helps me feel that way. But the WYSIWYG editor is a great alternative.

布拉德：我認為每個人都有自己的做事方式。 我仍然習慣于編寫hrefs和圖像標簽，這對我來說很自然。 我寫的博客不如您寫的那么多，也沒有聽眾的那么多，但是當我這樣做時，我想確保它非常干凈和準確，我認為查看代碼對我有幫助方式。 但是所見即所得的編輯器是一個不錯的選擇。

Matt: I’ll often edit in the WYSIWYG editor and then before I publish, I’ll check it out in HTML.

Matt：我經常會在WYSIWYG編輯器中進行編輯，然后在發布之前，我會以HTML進行簽出。

Brad: Check out the code.

布拉德：檢查代碼。

Matt: That’s why I like the new version of WordPress because it allows you to switch between them super easily, and the cool thing about it is whatever you choose, that will be sticky so the next time you come back to the page it will default to whatever your last view was, whether HTML or WYSIWYG.

Matt：這就是為什么我喜歡WordPress的新版本的原因，因為它使您可以輕松地在它們之間進行切換，而最酷的事情就是您選擇的內容，這很棘手，因此下次您回到頁面時它將默認無論您的上一個觀點是HTML還是WYSIWYG。

Brad: That’s a great feature alright. I want to touch on WordPress and WordPress MU and I know you announced a few months ago they would be merging. I haven’t heard too much about it since, so I’m wondering if maybe you could just give us an idea how that’s progressing, any ideas of maybe the version it would be in.

布拉德：這是一個很棒的功能。 我想談談WordPress和WordPress MU，我知道您幾個月前宣布它們將合并。 從那以后，我還沒有聽到太多有關它的信息，所以我想知道您是否可以給我們一個想法，例如它的進展情況，以及可能的版本。

Matt: It’s going to be sort of around the 3.0 time line and well, kind of like I said at WordCamp we haven’t started working on it yet, so it might change as we start to work on it. Basically, the idea is that we have these two code bases; they’re 99% the same, now let’s combine them and sort of pool the development resources so we don’t have a bug tracker over there and a bug tracker over here and some developers working over there and some developers working over here. Let’s get the full sort of resources and intention and minds working on WordPress also working on MU, and I think that will improve the product quite a bit.

Matt：大概是在3.0時間線左右，就像我在WordCamp上所說的那樣，我們還沒有開始研究它，所以隨著我們開始研究它，它可能會改變。 基本上，我們的想法是擁有這兩個代碼庫。 它們是99％的相同，現在讓我們將它們組合起來，并匯總開發資源，以便我們在那兒沒有bug跟蹤器，在那兒也沒有bug跟蹤器，有些開發人員在那兒工作，有些開發人員在那兒工作。 讓我們獲得在WordPress上也可以在MU上工作的全部資源，意圖和思想，我認為這將大大改善該產品。

Brad: Oh, yeah. I couldn’t agree more. I work quite a bit with WordPress MU, and it seems there always tends to be a little bit more bugs in MU. Again, this is just my personal opinion based on watching trac and the community. It feels like MU, it doesn’t as large of a group of developers or what have you that are helping with it as WordPress does.

布拉德：哦，是的。 我完全同意。 我在WordPress MU上做了很多工作，而且MU中似乎總是會出現更多錯誤。 再說一次，這只是我基于觀看比賽和社區的個人觀點。 感覺就像MU，它不像WordPress那樣龐大，不像一群開發人員那樣，或者您在幫助它方面有什么呢？

Matt: There’s as many MU powered blogs as there are WordPress powered blogs. In fact, it’s arguable that there is even more MU powered blogs. The thing about it is that the people running them, I guess they’re really busy, so they don’t get as involved as WordPress people do.

Matt： MU驅動的博客與WordPress驅動的博客一樣多。 實際上，有更多基于MU的博客是有爭議的。 關于它的事情是，運行它們的人非常忙，因此他們不會像WordPress的人那樣參與其中。

Brad: Yeah, but combining them is going to basically eliminate that, so you basically have all the developers working on one set of code, which I think is going to make it just night and day between how it is now and how it will be in the future. So I’m really, really excited about this update. I’m looking forward to it. So that’s why I’m trying to pull some information out of you.

布拉德：是的，但是將它們結合起來基本上可以消除這種情況，因此，基本上，所有開發人員都在處理一組代碼，我認為這將使它變成現在和將來之間的晝夜工作。在將來。 因此，我對此感到非常興奮。 我對此很期待。 這就是為什么我要向您提取一些信息。

Matt: Cool. You should get involved.

馬特：太酷了。 您應該參與其中。

Brad: Yeah, actually I have been getting involved in WordPress. I would say I guess I’m one of the people I’m talking about. I work more on the WordPress side than I do MU but you’re right, I probably should be more MU involved.I want to talk about WordPress.org a little bit, the actual web site. Now I know recently you released or you launched the commercial themes page. It got a lot of press, a lot of buzz, a lot of people talking and I think it’s a great feature, and I think that was kind of the general consensus. Are there any plans to do the same for plug-ins and have a commercial plug-in section that essentially just kind of promotes those commercial plug-ins that are GPL compliant?

布拉德：是的，實際上我一直參與WordPress。 我會說我想是我正在談論的人之一。 我在WordPress方面比在MU方面做得更多，但是您是對的，我可能應該更多地參與MU。我想稍微談論一下WordPress.org ，即實際的網站。 現在我知道您最近發布了或您啟動了商業主題頁面。 它引起了很多媒體的關注，嗡嗡聲，很多人在談論，我認為這是一個很棒的功能，我認為這是普遍共識。 是否有任何計劃對插件做同樣的事情，并有一個商業插件部分，其本質上只是在推廣那些符合GPL要求的商業插件？

Matt: Probably not in the near term. Honestly, there’s not that many people asking for it. It’s really just been like one or two people and they’re asking a lot but it’s not that many in terms of number of folks versus the themes page where there is a ton of folks… I think themes are a little bit different from plug-ins in terms that… a theme is more like the basis for designing your web site and it’s kind of the building block, where a plug-in is often just one smaller part of it. So honestly I feel like there’s a better commercial case for themes than there is for plug-ins.

馬特：短期內可能不會。 老實說，沒有多少人要求它。 確實只是一個或兩個人，他們問了很多，但就人數和主題頁面而言，并不是很多，那里有很多人……我認為主題與即插即用有點不同ins的意思是……主題更像是設計網站的基礎，并且它是構建模塊，在其中插件通常只是其中的一小部分。 所以說實話，我覺得主題的商業案例比插件的商業案例更好。

Brad: Yeah, I would agree. That was actually the follow up I had to that is it feels like that’s kind of the mindset of everyone, that commercial themes are accepted and kind of understood by the community; whereas commercial plug-ins are almost frowned upon. If I were to release a plug-in and charge for it, more people would almost probably tell me that I shouldn’t do that, even if it’s still GPL compliant.

布拉德：是的，我同意。 實際上，這是我必須采取的跟進措施，這就是每個人的心態，商業主題被社區接受并被社區所理解。 而商業插件幾乎不受歡迎。 如果我要發布一個插件并為其付費，那么即使它仍然符合GPL標準，也可能會有更多的人告訴我我不應該這樣做。

Matt: And it would also be more likely that someone would create a good free alternative, where with design that’s less likely to happen.

馬特：而且更有可能有人創造出一個不錯的免費替代品，而這種設計不太可能發生。

Brad: That’s exactly right. Maybe I’m the same way, I come across a plug-in that costs money and chances are you’re right, there is a free alternative out there that’s going to do something similar or very close to that functionality.

布拉德：完全正確。 也許我是用同樣的方式，我遇到了一個花錢的插件，而您是正確的機會，那里有一個免費的替代方案，可以做類似或非常接近該功能的事情。

Matt: Most features for WordPress start as plug-ins first. So if all plug-ins were to be commercial, that would seriously inhibit because even though they’d be GPL, the guys obviously would want us to put functionality in WordPress and that would seriously inhibit, I think, the growth of WordPress.

Matt： WordPress的大多數功能都首先從插件開始。 因此，如果所有插件都是商業化的，那將嚴重地抑制，因為即使它們是GPL，他們顯然也希望我們在WordPress中添加功能，而我認為這將嚴重地抑制WordPress的增長。

Brad: Some plug-ins warrant a price tag, some of the more complex e-commerce forms, things like that… those plug-ins if you look at the source behind them, there’s a lot of work that has been put into plug-ins.

布拉德：有些插件需要標價，有些更復雜的電子商務形式，諸如此類……如果您查看插件背后的源代碼，那么插件中已經做了很多工作ins。

Matt: It’s not a function though of the amount of work because obviously there’s a lot of amount of work put into WordPress.

馬特：雖然工作量不大，但這并不是一個函數，因為顯然WordPress中有很多工作要做。

Brad: True. That’s a very good point and ultimately, it’s everyone’s decision on how they want to release that. I’m a big…

布拉德：是的。 這是一個很好的觀點，最終，這是每個人對如何發布它的決定。 我很大...

Matt: I like to say that best things in life are free.

馬特：我想說，生活中最好的東西是免費的。

Brad: Hey, WordPress is a great example of that. I’m a big fan of GPL and I like to see things that released GPL. I really don’t have a problem if people pay or ask for money for certain things.

布拉德：嘿，WordPress是一個很好的例子。 我是GPL的忠實擁護者，我喜歡看釋放GPL的事物。 如果人們為某些事情付款或要錢，我真的沒有問題。

Matt: Also, if you look at the direction of the commercial theme page, they’re not really charging for the downloads, less and less; they’re more charging for the support and the customization and work around it. I think plug-ins totally can go that direction as well.

馬特：此外，如果您查看商業主題頁面的方向，他們并沒有真正為下載付費，而且越來越少。 他們需要為支持和定制支付更多費用，然后再進行解決。 我認為插件也完全可以朝這個方向發展。

Brad: Yeah, that’s actually a great business model and I know a few plug-ins like that that go that way. I think the e-commerce plug-in is one of them. The download is completely free and then if you want support, you pay for that. I think that’s probably a good business model for plug-in developers to look towards. WordPress 2.8.4 recently came out and I have a couple of stats here I want to throw at you on version releases. So bear with me here. So WordPress 2.7 came out December 10, 2008 and exactly two months later, WordPress 2.7.1 came out to the day. The WordPress 2.8 came out on June 11th and exactly two months later to the day, WordPress 2.8.4 came out. Basically, 2.8 had four minor releases in the same time that 2.7 had one minor release; so I’m curious, what happened with 2.8? Was there a lot functionality that just wasn’t quite ready to go out the door? Maybe you could explain kind of the difference there.

布拉德：是的，這實際上是一個很好的商業模型，我知道有一些類似的插件可以這樣。 我認為電子商務插件就是其中之一。 下載是完全免費的，然后如果您需要支持，則需要付費。 我認為這可能是插件開發人員可以考慮的良好商業模式。 WordPress 2.8.4最近問世了，我在這里有一些統計數據，我想向您介紹版本發布。 所以在這里忍受我。 因此WordPress 2.7于2008年12月10日發布，恰好兩個月后，WordPress 2.7.1正式發布。 WordPress 2.8于6月11日發布，而恰好兩個月后的今天，WordPress 2.8.4正式發布。 基本上，2.8具有四個次要版本，而2.7具有一個次要版本； 所以我很好奇，2.8發生了什么？ 是否有很多功能還沒有準備好推出？ 也許您可以解釋那里的區別。

Matt: It’s actually the opposite. If we were doing a bug fix release, like 2.7.1 was, it probably would have been the same amount of time because the releases were similar in terms of quality and bugs that made it through but the four releases for WordPress thus far for 2.8 had been security fixes. So those are things that rather than if it’s a bug, we pull them all up and we get like a whole bunch of them fixed and it’s more a matter of time, like we sort of aim for release one to two months later after the main one. If it’s a security fix, we’re trying to get a release out the door as soon as humanly possible, right? Because otherwise, blogs are in danger and that something could happen to your site, or to your content or anything. So it’s sort of our responsibility, our obligation to get a release out the door as soon as possible. When we find a security issue that’s serious, like that one with 2.8.4, where someone could remotely reset your password; as much as I hate doing a ton of releases, it’s the right thing to do.

馬特：事實恰恰相反。 如果我們像2.7.1那樣進行錯誤修復，那么可能會花費相同的時間，因為這些版本在質量和錯誤方面都差不多，但是到目前為止，WordPress的四個版本為2.8是安全修復程序。 因此，這些事情不是將其全部歸結為bug，而是將它們全部拉高，我們將它們修復了一整堆，這只是時間問題，例如我們打算在主要版本發布后一到兩個月發布之一。 如果這是一項安全修復程序，我們正在嘗試盡快將發布發布出去，對嗎？ 因為否則，博客將處于危險之中，并且您的網站，內容或任何內容可能會發生某些事情。 因此，這是我們的責任，我們有義務盡快將產品釋放出去。 當我們發現嚴重的安全問題時，例如2.8.4中的那個，有人可以遠程重置您的密碼。 盡管我討厭做大量的發行，但這樣做是正確的。

Brad: Yeah, absolutely. That was kind of an interesting bug. I think everyone—obviously, I probably shouldn’t be laughing about it—but I think everyone had a little bit of fun with that, resetting all of their friends’ passwords.I think it is great that you guys take security very seriously. I know anytime I talk to someone about open source that’s not familiar with open source, that’s the first question out of their mouth. How is that secure if someone can see my source code? How do I know my web site is secure? And I think the way you do release things right when security vulnerabilities are found, kind of proves how serious you do take security with your software or with WordPress and the open source. Hats off for that. It actually begs a good question. I was kind of following the story when the bug came out, or the vulnerability and it was widely reported that the way that it was reported to WordPress as being a bug was actually a blog post that basically said, “Here’s how you exploit this vulnerability.” What would you recommend as a proper way to submit a security vulnerability rather than just blog about for the whole world to see? Is there a better method that people should use?

布拉德：是的，絕對。 那是一個有趣的錯誤。 我認為每個人(很顯然，我可能不應該為此而笑)，但是我認為每個人都對此感到有點樂趣，重置了他們所有朋友的密碼。我認為你們非常重視安全性，這是很棒的。 我知道我每次與不熟悉開源的人談論開源時，這都是他們的第一個問題。 如果有人可以看到我的源代碼，那將有多安全？ 我怎么知道我的網站是安全的？ 而且我認為，當發現安全漏洞時，您發布事情的方式是正確的，這可以證明您對軟件或WordPress和開放源代碼的安全性的重視程度。 為此致敬。 這實際上是一個好問題。 我很在意這個錯誤或漏洞發布的故事，據廣泛報道，向WordPress報告它是一個漏洞的方式實際上是一篇博客文章，基本上說：“這就是您利用此漏洞的方式。” 您會提出什么建議，作為提交安全漏洞的適當方法，而不僅僅是博客，讓全世界看到？ 人們應該使用更好的方法嗎？

Matt: Well, so every other release of 2.8 and generally every security release we’ve done in the past few years, it’s been prior to the announcement of the vulnerability. What most responsible security researchers do is they’ll contact the vendor—in case us—and we have sort of open email address where anyone can email us anything and we follow up on every report pretty seriously. We research it, we verify it, we get a fix in and we do a release and then they announce it a couple of days later. This gives everyone a chance to upgrade and everything, so everyone’s most protected. Because their benefit is really to—the notoriety for having found an issue, they don’t really benefit from zero-day exploits or a bunch of blogs getting messed up. So that’s how most of the time it works. In this particular case, we found out at the same time as everyone else, which is not ideal, which is one of the reasons why we sort of had to burn the midnight oil to get a fix out there.

馬特：嗯，所以2.8的每個其他發行版以及我們過去幾年中完成的每個安全發行版，在發布此漏洞之前就已經存在。 最負責任的安全研究人員所做的是，如果有我們的話，他們將與供應商聯系。我們擁有一個開放的電子郵件地址，任何人都可以向我們發送電子郵件，我們會認真對待每份報告。 我們研究它，驗證它，得到修復，然后發布，然后幾天后他們宣布。 這使每個人都有機會進行升級和所有操作，因此每個人都受到最大的保護。 因為他們的利益確實是對(發現問題的臭名昭著)，所以他們并沒有真正從零日漏洞利用或一堆博客陷入混亂中受益。 這就是大多數情況下的工作方式。 在這種情況下，我們與其他所有人同時發現了這是不理想的，這就是為什么我們不得不燃燒午夜的石油才能解決問題的原因之一。

Brad: You guys did have a fix out fairly quickly. I think it was discovered and a new version of WordPress were released on the same day if I’m correct, maybe the next day.

布拉德：你們確實很快就解決了。 我認為它是被發現的，如果我正確的話，可能會在第二天就發布WordPress的新版本。

Matt: Yeah, I think it was next day. We had the fix in within a few hours because it was a relatively simple fix but even with a simple fix, even if only a small amount’s changed, you’ve really got to dig in to see if there are other parts of the code that are affected by a similar problem… does this fix break anything else? We kind of have to do a very accelerated QA cycle. But it’s pretty good. I’m actually very proud of how Ryan and the other lead developers responded to this.

馬特：是的，我想是第二天。 我們在幾小時內就收到了修復程序，因為它是一個相對簡單的修復程序，但是即使有一個簡單的修復程序，即使只有很小的改動，您也必須深入研究一下代碼中是否還有其他部分受到類似問題的影響...此修復程序是否可以解決其他問題？ 我們有點必須加快質量檢查周期。 但這很好。 實際上，我為Ryan和其他主要開發人員對此做出的回應感到非常自豪。

Brad: Yeah, I was amazed at how quick it was. In fact, somebody actually released a plug-in (the name is escaping me, I’ll look up their name and put it in the show notes [It was Will Anderson. —Ed.])—released a plug-in to patch the vulnerability as well. So even in that short amount of time where it existed, there was a plug-in you could download to patch it too. And that kind of speaks highly of the WordPress community in general, is how everyone kind of pulls together when something like this happens, figures it out, figures out how to patch it, gets it up there, releases the version, releases plug-ins; so it feels like everyone kind of has each other’s backs.Enough tech questions. I’ve got of couple personal questions here and then we’ll wrap it up. I know you’re a busy guy, so not too personal. Alex Dawson again, he’d like to know what favorite social network is outside of any kind of WordPress product?

布拉德：是的，我對它的速度如此之快感到驚訝。 事實上，實際上有人發布了一個插件 (這個名字在逃避我，我將查找他們的名字，并在顯示注釋中寫上[這是Will Anderson。- Ed。])-發布了一個補丁進行修補漏洞。 因此，即使它存在的時間很短，也可以下載一個插件來修補它。 總體上來說，這種方式在WordPress社區中具有很高的評價，那就是當發生這種情況時每個人如何團結起來，弄清楚，弄清楚如何打補丁，安裝它，發布版本，發布插件。 ; 因此感覺每個人都有彼此的后盾。足夠多的技術問題。 我在這里有幾個個人問題，然后我們將其總結。 我知道您是個忙碌的人，所以不要太私人。 亞歷克斯·道森(Alex Dawson)再次，他想知道任何一種WordPress產品之外最受歡迎的社交網絡是什么？

Matt: Hmm. A good question.

馬特：嗯。 一個好問題。

Brad: Are there any social networks that you check daily, Facebook, or MySpace, or anything like that, Twitter?

布拉德：您每天都在檢查社交網絡，Facebook或MySpace或類似的Twitter嗎？

Matt: I don’t check any of them daily and I also don’t really consider Twitter a social network. For me, Twitter is sort of like a stream of stuff that I dip in and out of occasionally. It doesn’t really connect me to people anymore than anything else. I guess the social network I use the most is Facebook. I have just always been really impressed with their products and developments, the way they innovate, the way the sites… I get the impression that they’re really obsessed about speed because the site is often very, very fast. It just has a lot of really elegant features on there. I’ve always taken inspiration from Facebook and honestly, that’s where most of my friends are.

馬特：我每天都不會檢查其中的任何一個，也不會真正將Twitter視為社交網絡。 對我來說， Twitter有點像是我偶爾會涉足的東西。 它并沒有真正將我與其他人聯系起來。 我猜我最常使用的社交網絡是Facebook 。 他們的產品和開發，他們的創新方式，網站的方式給我留下了深刻的印象，我的印象是，他們對網站的速度非常著迷，因為網站通常非常非?？?。 它只是那里有很多非常優雅的功能。 我一直從Facebook那里獲得靈感，說實話，這是我大多數朋友所在的地方。

Brad: I think all of my friends migrated to Facebook too and I don’t think I know anybody on MySpace anymore.

布拉德：我想我所有的朋友也都遷移到了Facebook，而且我不認識MySpace上的任何人。

Matt: Yeah, same here. I think I have a MySpace profile but I haven’t looked at in years. What that changed for me was—the primary thing that started getting on MySpace was spam. I think it’s interesting how of much of an Achilles heel spam is for these networks.

馬特：是的，這里也是。 我想我有一個MySpace個人資料，但多年以來都沒有看過。 對我來說改變的是–開始在MySpace上使用的主要內容是垃圾郵件。 我認為對于這些網絡而言，有多少跟腱垃圾郵件很有趣。

Brad: Back in MySpace’s heyday, you’re right you would get 10 … well you probably got thousands, but I would get 10 or 15 friend requests a day and they’re all these half naked girls that I’ve never seen before. You’re not my friend.

布拉德：回到MySpace的鼎盛時期，您說的很對，您會得到10…好吧，您可能會得到成千上萬，但我每天會收到10或15個朋友請求，而這些都是我從未見過的半裸女。 你不是我的朋友

Matt: What always fascinated me about that was how good the targeting was. So because they had sort of information about you on your profile, if you were Catholic, the spam would be Catholic, from a Catholic girl. If I was in San Francisco, the spam would come from Oakland. I mean they really—it was interesting and they would be in a similar age range and everything like that. So I found that really fascinating how highly targeted the spam became. You could tell how effective it was by looking at the profile and seeing how many friends they had, right?

馬特：一直令我著迷的是定位的出色程度。 因此，由于他們在您的個人資料中擁有關于您的某種信息，因此，如果您是天主教徒，則垃圾郵件將是天主教徒，來自一個天主教徒女孩。 如果我在舊金山，垃圾郵件將來自奧克蘭。 我的意思是他們確實如此-這很有趣，而且他們的年齡范圍也差不多，而且類似的年齡。 因此，我發現這真的使垃圾郵件的針對性變得非常有趣。 通過查看個人資料并查看他們有多少朋友，您可以判斷出效果如何，對嗎？

Brad: Yeah, absolutely.

布拉德：是的，絕對。

Matt: Sometimes I’d get a spam, I’d look at the profile and it would have 40,000 friends, so obviously it works.

Matt：有時候我會收到垃圾郵件，我查看一下個人資料，它將有40,000個朋友，因此顯然可以。

Brad: Something’s working. Did you take that knowledge back and kind of go back to akismet which is your comment spam filter and kind of include that knowledge that you learned from you saw in akismet.

布拉德：某些東西在起作用。 您是否把這些知識帶回去了，又回到了akismet ，這是您的評論垃圾郵件過濾器，并且包括了從akismet中看到的知識。

Matt: You know I can’t talk about how akismet works.

馬特：您知道我無法談論akismet的工作原理。

Brad: I had to ask. Speaking of Facebook, I got another question that’s kind of related by Divisive Cotton, and apparently they’re making a film about Facebook and about the founder Mark Zuckerberg. What Divisive Cotton wants to know is if they were to make a film about WordPress, what actor would you like to play you?

布拉德：我不得不問。 說到Facebook，我又遇到了一個與Divisive Cotton有關的問題，很明顯，他們正在拍一部關于Facebook和創始人馬克·扎克伯格的電影。 分裂棉花想知道的是，如果他們要拍一部關于WordPress的電影，你想扮演什么演員？

Matt: Obviously Brad Pitt.

馬特：顯然是布拉德·皮特。

Brad: Is it because his name Brad?

布拉德：是因為他叫布拉德嗎？

Matt: Actually, when I’m overseas sometime people say I look like Tom Cruise which I don’t see but sometimes people see it. They never say that in America. In America, there was this actor, I think his name might actually be Matthew (I’m going to have to look it up), I want to say he was an actor on Kids In The Hall… oh, Dave Foley. He was also on the show I used to watch a ton called NewsRadio, which I really enjoyed and people tell me I look like Dave Foley. So maybe Dave Foley, although I guess he’s getting older now.

馬特：實際上，當我有時在國外時，人們說我看起來像湯姆·克魯斯，雖然我沒看到，但有時人們看到了。 他們從來沒有在美國這么說。 在美國，有一位演員，我想他的名字實際上可能是馬修(我得去查一下)，我想說他是《大廳里的孩子們》的演員……哦，戴夫·弗利。 他也參加了我以前看過的一集名為NewsRadio的節目，我非常喜歡，人們告訴我我看起來像Dave Foley。 所以也許是戴夫·弗利(Dave Foley)，盡管我想他現在正在變老。

Brad: You do kind of look like Dave Foley. I know exactly who this guy is now. Everybody listening, go look up pictures of Dave Foley.

布拉德：你看起來像戴夫·弗利。 我確切知道這個人是誰。 大家都在聽，去查找Dave Foley的照片。

Matt: So one of those.

馬特：所以其中之一。

Brad: That’s great. So who knows, one day they might have “WordPress: The Movie”, playing Matt Mullenweg played by Dave Foley.

布拉德：太好了。 誰知道呢，有一天他們可能會飾演Dave Foley飾演的Matt Mullenweg的“ WordPress：電影”。

Matt: And the love interest will definitely be either Megan Fox or Corinne Bailey Rae.

馬特：愛情的興趣絕對是梅根·?？怂?Megan Fox)或科琳·貝利·雷(Corinne Bailey Rae)。

Brad: Or both. You travel a lot to WordCamps all over the world, you’ve been all over the place; what’s your favorite place to visit or the favorite place that you visited in your travels. You can say New?Jersey if it’s New?Jersey, I mean, I won’t hold offense to that because I live there.

布拉德：或者兩者都有。 您到世界各地的WordCamp旅行很多，您去過各地。 您最喜歡去的地方是什么？旅行中最喜歡去的地方。 您可以說新澤西州，如果它是新澤西州，我的意思是說，我不會因為自己住在那兒而感到冒犯。

Matt: I’ve never really traveled before. In fact, I hadn’t really left Texas for a good chunk of my life. The past two years, I’ve literally been to every corner of the world. I think I’ve gone to like maybe six continents in the past eight months. It’s just been all four corners. It’s not that one is better or worse than the other; it’s just really different. The thing I love, like what makes me like a place versus not, is the people who I’m interacting with there.Typically, when I go to a WordCamp, I’m hanging out with WordPress users and the local hosts and everyone like that, and so it’s kind of actually a really neat way to get to know some place. Sometimes I’ll go to a city and not even visit any of the any landmarks or the tourist stuff or anything; I’ll just be hanging out with the WordPress users in that community at their favorite bars or their favorite restaurants or things like that. I actually really like that, because, ultimately, although I’m a photographer and I take a ton of pictures, when I travel, what I tend to like to take pictures of is the small stuff the light posts, the graffiti on the wall, things like that—I feel it really gives character, the murals in Philadelphia. When I was in Sydney, the Sydney Opera House blew me away. It sort of makes you appreciate the wide variety of just people and places, and geography, and everything all over. This weekend, I was in New Zealand and, man, that is a pretty place. I think it’s really, really beautiful. We bought a company in the north of Ireland in a place called Sligo, which I had never heard of before in my life. I think it’s one of the most beautiful places I’ve ever been.

馬特：我以前從未真正去過。 實際上，我并沒有真正離開得克薩斯州。 在過去的兩年中，我確實去過世界的每個角落。 我想在過去八個月中，我已經喜歡了六大洲。 到處都是四個角落。 不是說一個人比另一個人更好或更壞。 真的不同。 我喜歡的東西(例如讓我成為一個地方而不是一個地方)是與我互動的人。通常，當我進入WordCamp時 ，我會與WordPress用戶，本地主機和每個人一起閑逛這樣，所以實際上是了解某個地方的一種非常巧妙的方法。 有時我會去一個城市，甚至不去參觀任何地標，旅游景點或任何東西。 我將與該社區中的WordPress用戶在他們最喜歡的酒吧或他們喜歡的餐館之類的地方閑逛。 我實際上真的很喜歡，因為最終，盡管我是一名攝影師并且要拍照很多，但是當我旅行時，我更喜歡拍照的是燈柱上的小東西，墻上的涂鴉。 ，像那樣的東西-我覺得它確實給人以特色，費城的壁畫。 當我在悉尼時，悉尼歌劇院讓我震驚。 它使您欣賞各種各樣的人和地方，地理位置以及所有事物。 這個周末，我在新西蘭，老兄，那是一個漂亮的地方。 我認為它真的非常美麗。 我們在愛爾蘭北部的一個叫Sligo的地方買了一家公司，這是我一生中從未聽說過的。 我認為這是我去過的最美麗的地方之一。

Brad: We have a lot of developers and designers that are part of SitePoint?and the community and if anyone’s interested in getting involved with WordPress, where should they start, what’s the best way so someone can really start getting involved with WordPress?

布拉德：我們有很多開發人員和設計師都屬于SitePoint和社區，如果有人有興趣參與WordPress，他們應該從哪里開始，什么才是使人們真正開始參與WordPress的最佳方法？

Matt: It’s interesting; there is a space for almost every skill. Where I actually kind of got started with B2, which was the predecessor to WordPress, was in the forums. At the time, I didn’t really know much about programming. Actually, I was just learning. I was actually a SitePoint user in 2002, and I actually learned a lot of the early page B and C assessment stuff I knew from SitePoint. I think my username is allusion, like a literary allusion.

馬特：這很有趣。 幾乎所有技能都有一個空間。 我實際上是從B2開始的，那里是WordPress的前身。 當時，我對編程并不了解很多。 實際上，我只是在學習。 我實際上是2002年的SitePoint用戶，實際上我從SitePoint中學到了很多早期的B和C頁評估知識。 我認為我的用戶名是典故 ，就像文學典故一樣。

Brad: We’re going to have to look at your first post now and see what it was.

布拉德：我們現在必須看看您的第一篇文章 ，看看它是什么。

Matt: That’s probably super embarrassing.

馬特：這可能真讓人尷尬。

Brad: Oh, mine are awful.

布拉德：哦，我的太可怕了。

Matt: I was just learning, and so even though I didn’t know a ton, I was able to help people who knew even less. No matter how little you think you know, there is always someone else out there who is just getting started earlier than you. Actually, I learned a ton through that. I probably learned more through helping people, or like tech support and things like that, than I ever did from any of the books or web sites I read. That’s where I got started and then over time, I branched into contributing and filing bugs and writing my own code and everything like that. That was a pretty natural progression. We also have spaces for people to contribute. Let’s say you’re good at writing prose or poetry, but not code; we have haikus … did you see the new Automattic homepage?

馬特：我只是在學習，所以即使我一點也不懂，我仍然能夠幫助那些了解甚少的人。 無論您認為了解多少，總會有其他人比您更早開始。 實際上，我從中學到了很多東西。 我可能通過幫助人們，喜歡技術支持之類的東西比從我閱讀的任何書籍或網站中學到的更多。 那就是我開始的地方，然后隨著時間的流逝，我開始致力于貢獻和提交錯誤，以及編寫自己的代碼和類似的東西。 那是自然而然的進步。 我們也為人們提供了貢獻的空間。 假設您擅長寫散文或詩歌，但不擅長編碼。 我們有haikus…您看到新的Automattic主頁了嗎？

Brad: I did, it’s completely haikus. It’s great.

布拉德：我做到了，完全是hai句。 這很棒。

Matt: That was just kind of fun. I was having fun one night. We have a new WordPress handbook, which is basically a way for—we’re trying to write like an open source WordPress book. There’s the Codex where there’s all sorts of different documentation for people. There is mailing lists where any number of issues come and go. Almost whatever the thing you enjoy doing is, there is a way to do it as part of WordPress.I believe it was President Obama who said when we hitch ourselves to something greater than just us, that’s when we sort of find happiness and satisfaction, and that’s totally what I found as well. I was sort of years as basically a solo web developer, and the thrill of working in an open source community and some of the shared ownerships—like we’re all in this together—it’s kind of like an Amish barn raising. You build something with each other that’s far greater than you ever could have built yourself or any of the people… it’s greater than the sum of its parts. And that’s actually pretty fun. It’s also a fantastic learning experience where, in the WordPress’ case, you have the opportunity to interact with, my opinion, some of the best PHP coders in the world, people who have dealt with sites that get 15-20 million page views a day, which is more than most of it.There’s not a ton opportunities to do things like. I mean, it’s not like you can go in and hang out with the Facebook developers or anything like that. Outside of Wikipedia, it’s hard to think of another project like it. I think it’s a good opportunity for folks as well.

馬特：那只是一種樂趣。 我有一個晚上很開心。 我們有一本新的WordPress手冊，從根本上來說，這是一種方法-我們正在嘗試像開源WordPress書一樣編寫。 在食典中 ，人們可以找到各種不同的文檔。 有郵件列表 ，其中出現了許多問題。 無論您喜歡做什么，幾乎都有一種方法可以作為WordPress的一部分。我相信正是奧巴馬總統說，當我們向自己超越自己的目標邁進時，就是在那種時候找到幸福和滿足感，這也是我發現的全部。 我基本上是一個單獨的Web開發人員，幾年來，在開放源代碼社區和一些共享所有權(如我們都在一起)中工作的快感，就像是阿米什人的谷倉籌集活動。 彼此之間構建的東西比您自己或任何人所能構建的東西要大得多……它大于各個部分的總和。 這實際上很有趣。 這也是一種奇妙的學習體驗，在WordPress的情況下，您有機會與世界上一些最好PHP編碼器進行互動，這些人與處理過15-20百萬頁面訪問量的網站一天，這比大部分時間都重要。做類似事情的機會不多。 我的意思是，這并不是說您可以加入并與Facebook開發人員一起閑逛或類似的活動。 在Wikipedia之外，很難想到另一個類似的項目。 我認為這對人們也是一個很好的機會。

Brad: Oh, yeah, absolutely. I’ve been working with WordPress for a few years now and just this past year really, I’ve really got involved in the IRC chat. There’s a whole under Freenode if you join WordPress or WordPress-dev where are the core devs hang out—I’ve learned a lot just by sitting in those rooms and like you said, helping other people that knew less than me and then learning from people that knew more than me. There is a lot of people in there that know more than me. I feel like I’ve doubled what I know about WordPress just in the last year of just hanging out in that room and talking WordPress.

布拉德：哦，是的，絕對。 我已經使用WordPress已有幾年了，而實際上在過去的一年中，我真的參與了IRC聊天 。 There's a whole under Freenode if you join WordPress or WordPress-dev where are the core devs hang out—I've learned a lot just by sitting in those rooms and like you said, helping other people that knew less than me and then learning from people that knew more than me. There is a lot of people in there that know more than me. I feel like I've doubled what I know about WordPress just in the last year of just hanging out in that room and talking WordPress.

Matt: Wow, that’s a fantastic story. I guess it works.

Matt: Wow, that's a fantastic story. I guess it works.

Brad: I’m always in WordPress chat, so if you’re ever trying to find me, I’m usually in there. The dev chats now are Thursdays.

Brad: I'm always in WordPress chat, so if you're ever trying to find me, I'm usually in there. The dev chats now are Thursdays.

Matt: Yes, that’s another great way to get involved. We have sort of a weekly developer chat, sort of just a way for us to talk about where WordPress is and sort of figure out who is going to work on what for the next release. If you’re a developer and you want to get involved at a higher level or maybe have someone mentor you through a feature or something like that, the weekly chats are a great place. I think right now they’re on Thursdays. They used to be on Wednesdays. They might move around in the future.

Matt: Yes, that's another great way to get involved. We have sort of a weekly developer chat , sort of just a way for us to talk about where WordPress is and sort of figure out who is going to work on what for the next release. If you're a developer and you want to get involved at a higher level or maybe have someone mentor you through a feature or something like that, the weekly chats are a great place. I think right now they're on Thursdays. They used to be on Wednesdays. They might move around in the future.

Brad: Even if you’re just watching, a lot of times, I just sit in there and watch; if nothing else, you can kind of see the cool new features that are coming up for WordPress.Matt: Yeah, you’ll know it before all your friends.

Brad: Even if you're just watching, a lot of times, I just sit in there and watch; if nothing else, you can kind of see the cool new features that are coming up for WordPress. Matt: Yeah, you'll know it before all your friends.

Brad: Last question. What’s next for WordPress? What’s down the future towards this year, may beginning of next year, what can we expect from WordPress?

Brad: Last question. What's next for WordPress? What's down the future towards this year, may beginning of next year, what can we expect from WordPress?

Matt: Hopefully WordPress 2.9 and WordPress 3.0.

Matt: Hopefully WordPress 2.9 and WordPress 3.0.

Brad: With the WordPress MU integration, of course.

Brad: With the WordPress MU integration, of course.

Matt: There is three things really on my mind a lot right now. One is WordPress as a platform. It’s now well north of 5,000 plug-ins available for WordPress. There’s at least that many themes everywhere around the Web. How do all those interact with each other, how do you stay up to date, how do you manage conflicts when you upgrade, how do you make sure everything is compatible? These are kind of tough problems, and so we need to figure all that out because you as a user, upgrading should be a one-click button and you should never worry about it. All of your plug-ins, everything in your site should just work, and that’s the goal of WordPress; it should just work. You should never have to think about it. If you have to think about, we failed as developers.Two is around media. I think I might have more photos on my blog than any WordPress user in the world more photos in WordPress. I obviously use that functionality a lot but in addition to photos, how we’re going to be interacting with audio and video and really rich media because I think that’s becoming a more important part of just the Web experience, especially as broadband and everything increases, which somewhat like Moore’s Law gets better every year.And then finally, sort of different content around the Web. Just me: I use Twitter, I post photos to Flickr, I have two or three blogs, I do a lot of things around the Web. Is it possible—I don’t know the answers to this—but is it possible for sort of WordPress to bring all that in and sort of archive it for me and maybe present it in a unified view and become sort of my ultimate profile or ultimate homepage. This is something that I don’t think we’ve figured out yet. I don’t know what that’s going to look like.I think that WordPress provides a really good base for it and most importantly, although a lot of these services are fantastic, often they are proprietary. In fact, none of the ones I’ve just mentioned are open source. I would really like all the data, from my heart and soul and blood, sweat, and tears that I pour into all these services to belong to me, because right now according to their web sites in terms of service and everything, it sort of belongs solely to them. And who knows; I like Facebook today, but if it’s get bought by News?Corp and merged with MySpace, I probably won’t. I’d like a way to sort of take my data out and just sort of have it on a domain that I own and software that I own and control as well and open source is really the only true example of software freedom. So, I’m thinking about that. It’s kind of bounced around in my head.

Matt: There is three things really on my mind a lot right now. One is WordPress as a platform. It's now well north of 5,000 plug-ins available for WordPress. There's at least that many themes everywhere around the Web. How do all those interact with each other, how do you stay up to date, how do you manage conflicts when you upgrade, how do you make sure everything is compatible? These are kind of tough problems, and so we need to figure all that out because you as a user, upgrading should be a one-click button and you should never worry about it. All of your plug-ins, everything in your site should just work, and that's the goal of WordPress; it should just work. You should never have to think about it. If you have to think about, we failed as developers.Two is around media. I think I might have more photos on my blog than any WordPress user in the world more photos in WordPress. I obviously use that functionality a lot but in addition to photos, how we're going to be interacting with audio and video and really rich media because I think that's becoming a more important part of just the Web experience, especially as broadband and everything increases, which somewhat like Moore's Law gets better every year.And then finally, sort of different content around the Web. Just me: I use Twitter, I post photos to Flickr, I have two or three blogs, I do a lot of things around the Web. Is it possible—I don't know the answers to this—but is it possible for sort of WordPress to bring all that in and sort of archive it for me and maybe present it in a unified view and become sort of my ultimate profile or ultimate homepage. This is something that I don't think we've figured out yet. I don't know what that's going to look like.I think that WordPress provides a really good base for it and most importantly, although a lot of these services are fantastic, often they are proprietary. In fact, none of the ones I've just mentioned are open source. I would really like all the data, from my heart and soul and blood, sweat, and tears that I pour into all these services to belong to me, because right now according to their web sites in terms of service and everything, it sort of belongs solely to them. And who knows; I like Facebook today, but if it's get bought by News Corp and merged with MySpace, I probably won't. I'd like a way to sort of take my data out and just sort of have it on a domain that I own and software that I own and control as well and open source is really the only true example of software freedom. So, I'm thinking about that. It's kind of bounced around in my head.

Brad: It sounds like we have a lot of cool things to expect out of WordPress over the coming years and it will probably be surprising and amazing all at the same time, I’m sure.

Brad: It sounds like we have a lot of cool things to expect out of WordPress over the coming years and it will probably be surprising and amazing all at the same time, I'm sure.

Matt: The final thing – if you haven’t, if you’re a WordPress user or especially if you’re a developer, you should check out two things. One is VideoPress, which is our new plugin for doing video. It’s really slick, it does really nice video. Two is BuddyPress, which is sort of a social layer on top of WordPress that allows you to create social networks, profiles, all the things you’d expect on a traditional social network, but you can integrate it really nicely with your existing blog or web site or network.

Matt: The final thing – if you haven't, if you're a WordPress user or especially if you're a developer, you should check out two things. One is VideoPress , which is our new plugin for doing video. It's really slick, it does really nice video. Two is BuddyPress , which is sort of a social layer on top of WordPress that allows you to create social networks, profiles, all the things you'd expect on a traditional social network, but you can integrate it really nicely with your existing blog or web site or network.

Brad: BuddyPress is pretty exciting and especially anyone that’s used it, it’s an awesome, awesome package that fits right on top of WordPress MU. As I understand it, once they merge, it will also kind of merge right into working with regular WordPress as well. That’s going to be great. I think it’s really going to explode BuddyPress. Definitely check out BuddyPress if you haven’t.Matt, I really appreciate you taking time. I know you have a crazy busy schedule and taking the time to have a chat with me, I really, really do appreciate. I’m sure everybody listening does as well.

Brad: BuddyPress is pretty exciting and especially anyone that's used it, it's an awesome, awesome package that fits right on top of WordPress MU. As I understand it, once they merge, it will also kind of merge right into working with regular WordPress as well. That's going to be great. I think it's really going to explode BuddyPress. Definitely check out BuddyPress if you haven't.Matt, I really appreciate you taking time. I know you have a crazy busy schedule and taking the time to have a chat with me, I really, really do appreciate. I'm sure everybody listening does as well.

Matt: Thank you.

Matt: Thank you.

Brad: Thanks, and that ends another episode of the SitePoint Podcast.

Brad: Thanks, and that ends another episode of the SitePoint Podcast.

Kevin: And thanks for listening to the SitePoint Podcast. If you have any thoughts or questions about today’s interview, please do get in touch. You can find SitePoint on Twitter @sitepointdotcom and you can find me on Twitter @sentience. Visit sitepoint.com/podcast to leave a comment on the show and to subscribe to get every show automatically.We’ll be back next week with another news and commentary show with our usual panel of experts. The SitePoint?Podcast is produced by Carl Longnecker and I’m Kevin Yank. Bye for now.

凱文：感謝您收聽SitePoint播客。 如果您對今天的采訪有任何想法或疑問，請保持聯系。 你可以在Twitter上找到SitePoint @sitepointdotcom ，你可以找到我的Twitter @sentience 。 Visit sitepoint.com/podcast to leave a comment on the show and to subscribe to get every show automatically.We'll be back next week with another news and commentary show with our usual panel of experts. SitePoint播客由Carl Longnecker制作，我叫Kevin Yank。 暫時再見。

Thanks for listening! Feel free to let us know how we’re doing, or to continue the discussion, using the comments field below.

謝謝收聽！ 歡迎使用下面的評論字段讓我們知道我們的狀況，或者繼續討論。

翻譯自: https://www.sitepoint.com/podcast-25-wordpress-matt-mullenweg/

總結

以上是生活随笔為你收集整理的SitePoint播客＃25：WordPress与Matt Mullenweg的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。