Open Source Software inan Academic Environment - Developing, Supporting and Integrating Presented at the Future Networks 6th FP7 Concertation Plenary Meeting

1. Brussels, 2010 Open Source Software inan Academic Environment Developing, Supporting and Integrating Diogo Gomes <dgomes@ av.it.pt>

4. Peer-Review

5. Open Access

6. It is therefore natural that important Open Source projects started in Academic Environments, e.g.

7. Stallman started GNU while at MIT

8. Linus started Linux while at HUT

10. It gives researchers open access to important technologies, e.g.

11. Network Simulators (NS, OMNET++)

12. Database Systems (MySQL, PostgreSQ, CouchDB)

13. Mobile Platforms (Android, MeeGo)

14. And they give it back to the Open Source Community, e.g.

15. Developing (Diameter, Linux IPv6 stack)

16. Supporting (hosting, patching, enhancing)

18. By interacting with an existing OSS project

19. Through collaboration with an established OSS project

20. Forking a project

21. Mostly out of need…

22. In order to achieve a given research goal, the need usually arises to develop a given technology

23. Due to lack of an affordable alternative

25. Msc and Phd thesis

26. Research Projects

27. Timeframes

28. Short to Medium

29. 1 Developer (Msc/Phd student)

30. Medium to Long

31. >2 Developers

32. Community formed around the project

34. The vitality of the project (#commits, #bug fixes)

35. The level of documentation

36. The size of its community (not just #devs)

37. The amount of visibility given to (articles, website references)

38. Supported given by Univ. Aveiro to OSS projects:

39. GLUA (Univ. Aveiro Linux User Group)

40. Seeding a community of OSS enthusiasts

41. CodeUA

42. A platform for project hosting (similar to SF.net, Google Code)

43. Fostering young students to join research projects as OSS developers

45. Many of the partnerships established by the Academia with Industry partners in which there is a transfer of knowledge involve OSS projects previously developed by the Academia.

46. Integrating OSS into existing products

47. Rapid Prototype creation through the use of OSS

48. OSS is mostly used as a common ground in consortiums with legal issues regarding software licenses

50. COPSpp – IETF COPS protocol implementation

51. MRD6 – Multicast Routing Daemon for IPv6

52. Odtone – IEEE 802.21 protocol implementation

53. PMIPv6 – IETF Proxy Mobile IP Protocol Implementation (ongoing)

54. Licenses

55. We have used GNU Lesser General Public License in all projects

56. Feedback from the community

57. MRD6 has evolved into part of the Debian distribution.

58. Odtone is widely accepted by the IEEE802.21 community as a reference implementation OSS @ University of Aveiro

60. Integration

61. Linux, MIPL, Gstreamer, OpenIMS, Sailfin, Android

62. Development

63. MRD6 – IST-Daidalos

64. Odtone – ICT-C-CAST

65. Some projects required that we explained to partners the rules of OSS

66. Release of code developed in the project as OSS, enabled a better dissemination of the project results, leading to several internal follow-up projects.

68. Developing, Supporting and Integration OSS is a challenging task but also a very fruitful one

69. Students are early engaged with real life software development problems and challenges

70. Many resources are spent supporting the projects

71. OSS projects usually lead to a better dissemination of ideas and accomplishments then just academic publications

72. Research Projects take advantage of the existence of OSS to quickly bootstrap

73. Many OSS Projects lead to new companies and businesses.

74. The University of Aveiro has already fostered several OSS projects and continues to support students and researchers that wish to develop and release OSS.