編輯“WordPress:Mailing List Summary”

This content seems stale.? And it is a result when searching for "mailing list". Moved under WAKELESS for him/her to decide/update  
- [[WordPress:User:Foolswisdom|Foolswisdom]] 21:14, 4 Sep 2006 (GMT)

內容看起來過時了？這是搜索"郵件列表"時，出現的結果。Moved under WAKELESS 讓他/她決定/更新- [[WordPress:User:Foolswisdom|Foolswisdom]]2006年9月4日，21：14（格林尼治標準時間）

=== TODO List ===

=== TODO 列表 ===

This is a list that pretty much everyone on the list has agreed should be done.

幾乎列表上的所有人都同意完成列表。

* the_content filters. The way they work seems a little bit inconsistent with the_excerpt and the_content, also the way they currently work it makes it a little bit harder for alternative input formatting. One of the suggested solutions is to not filter everytime the post is viewed, but store the filtered output. Michel Fortin has a discussion of the difficulties he had [http://www.michelf.com/weblog/2005/wordpress-text-flow-vs-markdown/ here].

* the_content filters。這些filters的運行方式與the_excerpt和the_content的運行方式似乎有點不一致，而且這些filters當前的運行方式，使得使用另外的輸入格式變得較為困難。一種建議的方法是不要在每次瀏覽文章的時候，都過濾文章，而且儲存已過濾的輸出內容。Michel Fortin在這里討論了他在[http://www.michelf.com/weblog/2005/wordpress-text-flow-vs-markdown/ 這里]遇到的問題。

* '''Theme browser.''' The theme browser has been implemented, though all the themes are very similar in terms of layout. ''Some alternative's (three column layouts) would be appreciated.''

* '''主題瀏覽器。'''雖然就布局而言，所有的主題非常相似，主題瀏覽器已經運行。''一些其它的方法 (三欄布局)更合適。''

=== Current Work ===

=== 當前工作 ===

* '''Compose screen.''' There has been some changes made recently to the compose screen, there has been mixed reactions to how it currently works. Final verdict should probably wait till it's smoothed out. General consensus is that there are definitely ways to improve the existing (1.5) screen.

* '''寫作界面。'''寫作界面最近發(fā)生了一些變化，寫作界面當前的運行方式出現了一些混合的反響。只有平穩(wěn)過渡后，才有有最終的判斷。一般認為有方法，能夠改善當前（1.5）界面。

* '''User Permissions'''. There has been some pretty major changes to the whole User Permissions going on, this involves plugin-editable user-roles and capabilities. (Ryan and Owen have been mainly involved) Links: [[WordPress:User:ringmaster/Capabilities_Classes|Incomplete spec]] and [http://asymptomatic.net/wp/2005/07/11/1747/permission-change-overview-in-16/ more complete spec]

* '''用戶權限'''。當前的用戶權限發(fā)生了一些主要的變化，包括可以編輯插件的用戶角色和權限。(只要涉及到Ryan和 Owen) 鏈接：[[WordPress:User:ringmaster/Capabilities_Classes|還未完成的spec]] 和[http://asymptomatic.net/wp/2005/07/11/1747/permission-change-overview-in-16/ 更多完成的 spec]

* '''Plugin De-activation'''. There has been discussion and a couple of patches regarding a plugin deactivation hook.

* '''Plugin De-activation'''。關于插件停止運行hook，有相關的討論和補丁。

* '''Improved Image Handling'''. Owen has revealed that he has a patch waiting in the wings with lots of crazy cool image/upload changes. This involves, while posting uploads, automatic thumbnail generation and the removing of the upload tab. He also revealed that this is going to tie in with the user permissions changes, allowing sandboxing of users into their own folder or letting them access a public folder.

* '''已改善的圖像處理'''。Owen透露他有個待用的補丁，擁有許多神奇的圖像/上傳更改。這包括，發(fā)表上傳內容的時候，自動生成縮略圖，并且移除上傳圖標。他還透露，這個補丁功能會隨著用戶權限的變化而變化，使得用戶的sandboxing進入用戶自己的文件夾或者允許用戶訪問公共的文件夾。

=== Recently implemented (from dev list) ===

=== 最近執(zhí)行 (來自 dev列表) ===

* '''New Wiki Tech List.''' A new email list http://lists.automattic.com/mailman/listinfo/wiki-tech was created for wordpress related wiki technology.

* '''新的 Wiki 技術 列表。'''一個新的電子郵件列表http://lists.automattic.com/mailman/listinfo/wiki-tech為wordpress相關的技術創(chuàng)建。

* '''1.5.2 or on to 1.6.''' It looks like the next major version released will be 1.6, a fair amount of major work has been started. (Obviously this has no actual bearing on what will necessarily happen)

* '''1.5.2 或者直到 1.6。'''1.6好像是將要發(fā)行的新的主要版本，許多主要的工作已經開始展開。（當然，對于真要發(fā)生的事，沒有多大真正的影響）

* '''XMLRPC.''' Changes have been made to xmlrpc due to certain security vulnerabilities being  brought to light. There ended up being a point release to resolve these problems.

* '''XMLRPC.'''因為暴露了一些安全隱患，xmlrpc發(fā)生了變化。最終，可能要發(fā)行新的版本解決這些問題。

* '''High-performance wordpress'''. There has been discussion about how to work with sites requiring high performance wordpress installations. This will pretty much just end up being a document here on the codex to point people to. Draft here: [[WordPress:User:Ringmaster/WordPress_in_High_Traffic|Ringmaster/WordPress_in_High_Traffic]].

* '''High-performance wordpress'''。有關于怎樣與那些高性能的wordpress站點合作的討論。最終，codex上會提供文檔，供人們查閱。這里有草稿：[[WordPress:User:Ringmaster/WordPress_in_High_Traffic|Ringmaster/WordPress_in_High_Traffic]]。

=== Shelved Threads ===

=== Shelved Threads ===

  This is stuff that the conversation has been shelved on. This has no bearing on whether or not it will be implemented or not. I'm not fully up to date on the threads so can't summarise it too well. If I get some time, I will go back and try and bring it up to date.
  
  這是談話的焦點問題。不管是否有主題，影響不是很大。我沒有完全地跟上最新的主題因為不能夠很好地總結主題。如果某天我得到了一些主題，我會返回，并且試圖更新主題。

  This was copied straight out of an email that Matt posted.

  這完全復制自Matt寫的電子郵件。

* Let's whip WYSIWYG (asking for suggestions)
* getSelection Workaround (still unanswered)
* Making it better (community feedback on some criticism)
* Pingback block-level awareness (request for code)
* Category project (request for code volunteers)
* XUL Hackers (request for volunteers)
* '''Importer updates.''' Matt asked for assistance for some housekeeping to be performed on the importers, it's possible that this might be a good way for someone to give ongoing contributions.


* Let's whip WYSIWYG (尋求建議)
* getSelection Workaround (仍然沒有回答)
* 將其變得更好(團隊對一些批評的反饋)
* Pingback block-level awareness (需要代碼)
* 類別 project (需要代碼志愿者)
* XUL Hackers (需要志愿者)
* '''Importer 更新。''' Matt請求幫助維護importers ，這是一些人參與貢獻的好機會。