1. The document discusses how to get involved in open source software development by sharing experiences contributing to projects. 2. It encourages contributing by reporting bugs, submitting patches, communicating respectfully through various channels, and being patient as maintainer responses can sometimes take time. 3. Examples are provided of productive contributions the author has made to various open source projects through patching, testing, and discussion on mailing lists and IRC.

1. 如何參與自由軟體開發 經驗分享 By Kan-Ru Chen (陳侃如) [email_address] ICOS 2011 2011-09-11 NTU

2. 程式有Bug或是不好用怎麼辦？

3. 出版社排不出 Knuth 的書 於是有了 TeX

4. BitKeeper 死要錢 &%$#@*! 於是 Linus 寫了 git

5. 還有很多很多類似的例子

6. 結論

7. 有需求(生氣)才有進步

8. 長輩說

9. 幹壞事是進步最大的原動力

10. 例如： 為了抓圖學會了 perl+wget

11. 還好我們有 Open Source/Free Software

12. % ls ~/src/mirror|wc -l 244

13. 有了 Source Code 想做什麼都可以

14. 如果...

15. 做簡報到一半 OpenOffice.org又當啦！ &%$@*!

16. 聊天到一半... 輸入法又掛啦！ &%$#@*!

17. 不會寫程式 找別人救你

18. 想辦法再當一次

19. 有時候很簡單 有時候很難

20. 紀錄流程

21. 回報

22. 會寫程式的人

23. 自己動手，豐衣足食

24. 想辦法再當一次

25. 有時候很簡單 有時候很難

26. 紀錄流程

27. 回報 抓蟲

28. 回報 (不管蟲有沒有抓到)

29. 回報到哪？

30. 溝通管道

31. Bug Tracking System

32. Mailing List

33. 論壇(Forum)

34. IRC

35. 語言隔閡

36. 不用擔心

37. 用點常識 Use your common sense

38. 共通語言

39. 冠C: I speak C language

40. 爬說語(Python)嘶嘶嘶～

41. 投PATCH問路

42. 有時候，Patch不是目的

43. 是溝通的方式

44. 冠C: I speak C language

45. 爬說語(Python)嘶嘶嘶～

46. 只要有進步，就是好Patch!

47. 沒什麼好害羞的！

48. Patch要給誰？

49. $ git log <file>

50. ChangeLog

51. Linux $ scripts/get_maintainer.pl

52. 專案網頁

53. Bug Tracking System

54. Mailing List

55. 論壇(Forum)

56. IRC

57. 要有耐心

58. 三天沒回覆很正常

59. 一個禮拜沒更新提醒一下

60. 一個月沒回音試試其他管道

61. 熟悉 upstream 做事方法

62. 說明來意

63. 送 PATCH 不要送 tarball

64. 注意授權方式

65. 使用相同的風格 HACKING

66. 測試過才送出

67. 範例欣賞 經驗分享

68. Emesene http://kanru.info/blog/archives/330/

69. Forum vs. IRC vs. Email

70. Notmuch & Xapian http://thread.gmane.org/gmane.mail.notmuch.general/887

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. #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. #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. Credits & License Content by Kan-Ru Chen http://kanru.info License: CC BY-NC-SA

75. OpenOffice.org template by Raphaël Hertzog http://raphaelhertzog.com/go/ooo-template License: GPL-2+

76. Background image by Alexis Younes “ayo” http://www.73lab.com License: GPL-2+