如何參與自由軟體開發 經驗分享 By Kan-Ru Chen (陳侃如) [email_address] ICOS 2011 2011-09-11 NTU
程式有Bug或是不好用怎麼辦?
出版社排不出 Knuth 的書 於是有了 TeX
BitKeeper 死要錢 &%$#@*! 於是 Linus 寫了 git
還有很多很多類似的例子
結論
有需求(生氣)才有進步
長輩說
幹壞事是進步最大的原動力
例如: 為了抓圖學會了 perl+wget
還好我們有 Open Source/Free Software
% ls ~/src/mirror|wc -l 244
有了 Source Code 想做什麼都可以
如果...
做簡報到一半 OpenOffice.org又當啦! &%$@*!
聊天到一半... 輸入法又掛啦! &%$#@*!
不會寫程式 找別人救你
想辦法再當一次
有時候很簡單 有時候很難
紀錄流程
回報
會寫程式的人
自己動手,豐衣足食
想辦法再當一次
有時候很簡單 有時候很難
紀錄流程
回報 抓蟲
回報 (不管蟲有沒有抓到)
回報到哪?
溝通管道
Bug Tracking System
Mailing List
論壇(Forum)
IRC
語言隔閡
不用擔心
用點常識 Use your common sense
共通語言
冠C: I speak C language
爬說語(Python)嘶嘶嘶~
投PATCH問路
有時候,Patch不是目的
是溝通的方式
冠C: I speak C language
爬說語(Python)嘶嘶嘶~
只要有進步,就是好Patch!
沒什麼好害羞的!
Patch要給誰?
$ git log <file>
ChangeLog
Linux $ scripts/get_maintainer.pl
專案網頁
Bug Tracking System
Mailing List
論壇(Forum)
IRC
要有耐心
三天沒回覆很正常
一個禮拜沒更新提醒一下
一個月沒回音試試其他管道
熟悉 upstream 做事方法
說明來意
送 PATCH 不要送  tarball
注意授權方式
使用相同的風格 HACKING
測試過才送出
範例欣賞 經驗分享
Emesene http://kanru.info/blog/archives/330/
Forum vs. IRC vs. Email
Notmuch & Xapian http://thread.gmane.org/gmane.mail.notmuch.general/887
#xapian-2009-12-10 kanru>  Hi, can I assume the termlist is sorted in alphabetical  order?   ojwb>  it's sorted by byte or...
#xapian-2009-12-11 cworth>  ojwb: A notmuch user just submitted a Xapian patch that  gives a 5-6x performance for the only...
#xapian-2009-12-11 ojwb>  does it pass the testsuite?  cworth>  ojwb: I haven't checked that yet, but I can.  ojwb>  if ri...
Credits & License <ul><li>Content by Kan-Ru Chen http://kanru.info License: CC BY-NC-SA
Upcoming SlideShare
Loading in...5
×

How to join open source development

636

Published on

ICOS 2011 如何協助自由軟體開發:
提交bug、幫助除錯與測試

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
636
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

How to join open source development

  1. 1. 如何參與自由軟體開發 經驗分享 By Kan-Ru Chen (陳侃如) [email_address] ICOS 2011 2011-09-11 NTU
  2. 2. 程式有Bug或是不好用怎麼辦?
  3. 3. 出版社排不出 Knuth 的書 於是有了 TeX
  4. 4. BitKeeper 死要錢 &%$#@*! 於是 Linus 寫了 git
  5. 5. 還有很多很多類似的例子
  6. 6. 結論
  7. 7. 有需求(生氣)才有進步
  8. 8. 長輩說
  9. 9. 幹壞事是進步最大的原動力
  10. 10. 例如: 為了抓圖學會了 perl+wget
  11. 11. 還好我們有 Open Source/Free Software
  12. 12. % ls ~/src/mirror|wc -l 244
  13. 13. 有了 Source Code 想做什麼都可以
  14. 14. 如果...
  15. 15. 做簡報到一半 OpenOffice.org又當啦! &%$@*!
  16. 16. 聊天到一半... 輸入法又掛啦! &%$#@*!
  17. 17. 不會寫程式 找別人救你
  18. 18. 想辦法再當一次
  19. 19. 有時候很簡單 有時候很難
  20. 20. 紀錄流程
  21. 21. 回報
  22. 22. 會寫程式的人
  23. 23. 自己動手,豐衣足食
  24. 24. 想辦法再當一次
  25. 25. 有時候很簡單 有時候很難
  26. 26. 紀錄流程
  27. 27. 回報 抓蟲
  28. 28. 回報 (不管蟲有沒有抓到)
  29. 29. 回報到哪?
  30. 30. 溝通管道
  31. 31. Bug Tracking System
  32. 32. Mailing List
  33. 33. 論壇(Forum)
  34. 34. IRC
  35. 35. 語言隔閡
  36. 36. 不用擔心
  37. 37. 用點常識 Use your common sense
  38. 38. 共通語言
  39. 39. 冠C: I speak C language
  40. 40. 爬說語(Python)嘶嘶嘶~
  41. 41. 投PATCH問路
  42. 42. 有時候,Patch不是目的
  43. 43. 是溝通的方式
  44. 44. 冠C: I speak C language
  45. 45. 爬說語(Python)嘶嘶嘶~
  46. 46. 只要有進步,就是好Patch!
  47. 47. 沒什麼好害羞的!
  48. 48. Patch要給誰?
  49. 49. $ git log <file>
  50. 50. ChangeLog
  51. 51. Linux $ scripts/get_maintainer.pl
  52. 52. 專案網頁
  53. 53. Bug Tracking System
  54. 54. Mailing List
  55. 55. 論壇(Forum)
  56. 56. IRC
  57. 57. 要有耐心
  58. 58. 三天沒回覆很正常
  59. 59. 一個禮拜沒更新提醒一下
  60. 60. 一個月沒回音試試其他管道
  61. 61. 熟悉 upstream 做事方法
  62. 62. 說明來意
  63. 63. 送 PATCH 不要送 tarball
  64. 64. 注意授權方式
  65. 65. 使用相同的風格 HACKING
  66. 66. 測試過才送出
  67. 67. 範例欣賞 經驗分享
  68. 68. Emesene http://kanru.info/blog/archives/330/
  69. 69. Forum vs. IRC vs. Email
  70. 70. Notmuch & Xapian http://thread.gmane.org/gmane.mail.notmuch.general/887
  71. 71. #xapian-2009-12-10 kanru> Hi, can I assume the termlist is sorted in alphabetical order? ojwb> it's sorted by byte ordering (which means unicode code point ordering the utf-8) ojwb> but not by any collating order which your language might have ojwb> so, sort of yes kanru> thanks ojwb> for example, in german I believe the &szlig; character should sort as if it were &quot;ss&quot; kanru> at least it's sorted, that's enough
  72. 72. #xapian-2009-12-11 cworth> ojwb: A notmuch user just submitted a Xapian patch that gives a 5-6x performance for the only performance bug we're hitting notmuch (Xapian defect #250): http://notmuchmail.org/pipermail/notmuch/2009/000886.html cworth> I guess I should go add that to the defect page... * ojwb sighs at the first hunk ojwb> yes, attach it to the ticket ojwb> I think richardb has been looking at that recently too cworth> ojwb: Added. cworth> ojwb: I haven't actually looked at the patch. Is it bad? ojwb> well, the first hunk contains only whitespace changes AFAICS ojwb> which is never a good sign ojwb> rather odd setting of cmp to -2, 0 or 2 ojwb> it's probably along the right lines cworth> Oh, right. Not a clean patch. cworth> ojwb: Gotta be sure you don't get &quot;too close&quot; to 0 with a value like 1 or -1, you know? cworth> ;-) cworth> ojwb: Anyway, I hope it leads to a proper upstream patch soon.
  73. 73. #xapian-2009-12-11 ojwb> does it pass the testsuite? cworth> ojwb: I haven't checked that yet, but I can. ojwb> if richardb isn't working on it after all, I'll happily review the patch [...] kanru> oh.. hi :) kanru> that patch is against 1.1.3 aka svn branch ojwb> kanru: cool kanru> it passed the test suite ojwb> excellent kanru> rough but works :) cworth> kanru: Oh, hi! I should have noticed you in here. :-)
  74. 74. Credits & License <ul><li>Content by Kan-Ru Chen http://kanru.info License: CC BY-NC-SA
  75. 75. OpenOffice.org template by Raphaël Hertzog http://raphaelhertzog.com/go/ooo-template License: GPL-2+
  76. 76. Background image by Alexis Younes “ayo” http://www.73lab.com License: GPL-2+ </li></ul>
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×