490 likes | 503 Views
NTNU activities in Open Source Software (OSS): ideas for cooperation? Reidar Conradi, Daniela S. Cruzes et al. Institutt for datateknikk og informasjonsvitenskap (IDI) / Department of Computer and Information Science, NTNU, NO-7491 Trondheim
E N D
NTNU activities in Open Source Software (OSS): ideas for cooperation? Reidar Conradi, Daniela S. Cruzes et al. Institutt for datateknikk og informasjonsvitenskap (IDI) / Department of Computer and Information Science, NTNU, NO-7491 Trondheim Simula-NTNU Contact Meeting, 7 Dec 2009 (w/ rev. slides) Simula Research Labs, Fornebu near Oslo Attn/ Leon Moonen, Aiko Fallas Yamashita et al., http://www.idi.ntnu.no/grupper/su/oss/simula-oss-7dec09-v2.ppt conradi@idi.ntnu.no, dcruzes@idi.ntnu.no Telenor-NTNU OSS contact meeting, 18 Dec 2008
Table of contents • IDI and NTNU: who, what, … • Software reuse and CBSE • The Open Source Software (OSS) phenomenon • OSS activites at NTNU • Ideas for activities in company YYY on OSS • YYY + NTNU = true? Telenor-NTNU OSS contact meeting, 18 Dec 2008
1. IDI Department at NTNU • IDI (2009): 140 employees, NTNU’s largest – 31 nationalities! • 45+ teachers (faculty w/ six women), 22 tech./adm., 52 PhD fellows, 20 temporary researchers/postdocs/teachers incl. 8 adjunct teachers (II”ere). • 6000 individual exams per year, 800 full-time students, participating in 7 study programs. • 150 master candidates and 10 PhD candidates per year. • Important value chain: teachers – postdocs – PhD students – master students – bachelor students – IT industry. • 11 research groups, incl. SE group below. • Counting ”Frida” publications: 196 in 2007, 184 in 2008, 223 in 2009 • Budgets 2008: 74.8 MNOK from NTNU + 23.3 MNOK in external projects. • Budgets 2009: 80.1 MNOK from NTNU + 26.0 MNOK in external projects. • Software engineering (SE) group in 2009: • 5,2 teachers, 2 researchers, 17 PhD fellows – 13 nationalities!! • Papers: 44/61 of 196/274 (2007), 40/47 of 184/255 (2008), 45/56 of 223/241 (2009); i.e. 25 % of IDI total, ca. 20 each year w/ foreign colleagues; 500 papers in last 10 years. • Ca. 25 master candidates/year; 3 PhDs in 2009, 4? In 2010. • 7 MNOK in external projects (40% of IDI total.) Telenor-NTNU OSS contact meeting, 18 Dec 2008
CBSE: COTS/OSS, Evolution, SCM Software reuse and architecture Software quality Reliability, safety, maintainability SPI, learning organisations, SE education Distributed Software Engin. Software and Art; Computer games Mobile Tech. for Learning Co-operative work Research fields of the SU group (1) Telenor-NTNU OSS contact meeting, 18 Dec 2008
Research profile of SE group (2) • Empirical research methods (all members) • Quality, QA, SPI, knowledge management (Conradi, Stålhane) • Reliability and safety, testing (Stålhane) • Software reuse, component-based development, open source / digital content (Conradi, Jaccheri) • Cooperation technologies, learning. awareness, virtual 3D (Divitini, Prasolova-Førland) • Mobile and ambient technology (Divitini, Wang) • Computer games for higher learning (Wang) • Software and art (Jaccheri) Telenor-NTNU OSS contact meeting, 18 Dec 2008
Research profile of SE group (3) • Reidar Conradi (NTH, IDB since 1975): Empirical research, CBSE, OSS, SPI/KM – COSI, EVISOFT. • Tor Stålhane (NTH-statistics/SINTEF, 2000): QA/SPI, safety, reliability, testing – EU:CAESAR, EVISOFT. • Letizia Jaccheri (Pisa/Torino,1997): OSS, sw and art, EU:ArTe. • Monica Divitini (Milano, 1999): CSCW, ambience, awareness – EU:ASTRA, FABULA, NTNU:-LIKT:MOTUS. • Alf Inge Wang (NTNU, 2003): mobility, computer games – GameNet,Telenor:MOSS. • Ekaterina Prasolova-Førland (NTNU, 2003, 20%): mobile 3D-enabled learning – EU:TARGET, NTNU-LIKT Telenor-NTNU OSS contact meeting, 18 Dec 2008
Research projects in SE group (4) 25++ NFR and EU projects in last 20 years, most with industry: • INCO, MOWAHS, BUCS, SEVO, WebSys: basic SE (NFR IKT2010) • NorskCOSI: inner and open source (ITEA2) • SPIQ, SPIKE, PROFIT, INTER-PROFIT, EVISOFT: empirical SPI in Norwegian software-intensive industry (NFR BiA) • MOSS: Computer games (Telenor, NTNU) • MOTUS-1, MOTUS-2: ICT & learning (NTNU, Telenor) • FABULA: mobile technology and learning (NFR VERDIKT) • ArTe: Computer art: dissemination to youth (NFR regional, 2009) • ASTRA: awareness (EU FET) • TARGET: virtual 3D in learning (EU IP) • Travel in Europe (EU, subcontractor) • CESAR: safety in transport sector (EU IP, ”Airbus” w/ 53 partners) • ++ 5-6 under evaluation by NFR and EU Telenor-NTNU OSS contact meeting, 18 Dec 2008
2. Software reuse and CBSE (1) • Systematic software reuse (from 1970): making shared code for internal (re)use across projects and departments in an organization. • CBSE – Component Based Software Engineering, like hw plugins? • Independent of programming language and OO paradigm. • Cost of reuse: +30-200% to generalize, break-even after 1-2 reuses. • Assumes stable domain and architectural knowledge – reusable software is ”discovered”, not ”pre-designed”! • Huge potential benefits: cost, time, quality, predictability, standardization of architecture and processes/tools (XML, UML, Java, Eclipse) – a gradual modernization of products with ”best practise” processes. • But not widely adopted: assumes adjusted company processes and culture; new roles/responsibilities, need cost/benefit analyses with uniform investment rate, ROI? with upfront investments and unclear later advantages, too small internal component market, implies new dependencies, must handle risks with ad-hoc tradeoffs, Need incremental approach – c.f. OSS later!! Telenor-NTNU OSS contact meeting, 18 Dec 2008
2. Software reuse of components, OTS = Off-The-Shelf (COTS or OSS) (2) • Software reuse: assets often asclass libraries in repositories (as Hibernate) • Develop “for” reuse: make generalized assets / components • Develop “with” reuse: CBSE, using these assets • Advantagesof CBSE, either with internal or external OTS components: • Cheaper, earlier, better, … software • Spread novel work practices & software architectures, leading to standardization • Re-user communities for experience mgmt/support • I.e. software development gets ”modernized” • Mainly non-technical obstacles: price/licensing, ROI, (re)negotiate requirements, less “control”, too “radical” Telenor-NTNU OSS contact meeting, 18 Dec 2008
2. Industrial examples of internal software reuse (3) IBM Federal Systems: empty, low quality garbage, too general. HP: two systems, 1.5 times later reuse (2nd to 3rd system) to break even (see Wayne Lim 1994) Ericsson in Grimstad: 60% reuse between GPRS and UMTS Statoil IT: JEF framework Need … … Telenor-NTNU OSS contact meeting, 18 Dec 2008
3. The OSS phenomenon (1) Since 1995: OSS as a benign tsunami; enabled by Internet and web. Part of “social computing”, cf. Facebook. Generalized into Creative Commons for global development and sharing of “free” digital artefacts in any domain. Over 500 000 OSS components, as in http://SourceForge.net: Infrastructure (ex. Linux, Apache, MySQL, PhP – the LAMP platform) libraries (Hibernate) shelfware (Acrobat, OpenOffice, SVN versioning tool) Based on launched (“gone open”) OSS projects, each with a community of developers, co-developers and integrators/users. Many licensing models: GPL: “contagious” openness by using OSS – so-called “copyleft”. BSD: any use is OK, as long as name of originator follows the OSS copy. eCos v1.1: all local changes to a down-loaded OSS must be reported back to originator, but impractical even via SVN. Telenor-NTNU OSS contact meeting, 18 Dec 2008
3. The OSS phenomenon (2) OSS: attracted much attention from industrial and public policy makers: e.g., IBM and Sun Microsystems; Skattedirektoratet, Kommunenes Sentralforbund, Bærum kommune. St.meld. 17 (2006/2007) by Norwegian Government recommends promoting OSS and open standards, new www.FriProg.no competence center. Also www.FriNett.no (NFR). OSS phenomena is changing the whole paradigm of software development and associated economic patterns and interactions – by cooperative, distributed innovation. To stay competitive and innovative, Norwegian software-intensive companies and public institutions must undergo this economic and cultural revolution: novel Business Models novel Innovation Models ¨ Ex. Often shared/free code w/ surrounding paid service providers – as for Apache, but who is “responsible owner” setting the course and revising requirements? Solution by a social innovation: professional partnership communities to establish and evolve their needed software, itself being OSS. I.e. move away from “unpredictable” volonteers working for free. Telenor-NTNU OSS contact meeting, 18 Dec 2008
Open Source Software: origin and now (3) 1650?: free flow of ideas begins in emerging scientific community. 1967-1977: DoD/DARPA’s development of Arpanet/InternetTCP/IP protocols -- open and distributed development, anti-authoritarian “counter culture”. 1978-85: Openness spreads via Univ.Berkeley’s adaptationof Unix, with built-in Internet protocols and generous BSD licenses with all source provided. 1985: Free Software Foundation: by Richard Stallman from MIT AI Lab; ideological ”CopyLeft”-inspired licenses. 1998: Open Software Initiative: by Eric Raymond from IT industry in US, pragmatic BSD-inspired licenses. ”The Cathedral and the Bazaar”: 2000: FLOSS = FSF +OSI; IFIP WG2.13 uses OSS as common denominator. 2005: Social computing and creative commons for knowledge work – standardized formats for “zero-cost” digital information, the world is ”flat”. 2008: 1,5 billion Internet users, 3 billion w/ mobile phones. 2009: Ex. Wikipedia: 55 mill. “gratis” personhours. Telenor-NTNU OSS contact meeting, 18 Dec 2008
OSS issues (4) • 500.000++ OSS “projects”, each w/ net community lead by original provider, co-developers, code integrators, users, ... Ex. eZ has had 2.3 mill. downloads, over 100 plugins made by community. Ex. Adobe Acrobat similarly over 500 mill. downloads. • COTS and OSS: many similarities, mostly used as black box. • Over 30 portals with domain-specific COTS/OSS software. • New way of making open ICT standards: rough consensus and (two implementations of) running code. • Over 50 licensing schemes. • Ex. Business models: • Apache: open and shared source supported by a cooperative foundation (“IBM”); separate payable services. • eZ: dual model with free previous version, payable current version plus services and support. • Success criteria??: for provider in “going open”, for future co-developers, for code integrators, … Telenor-NTNU OSS contact meeting, 18 Dec 2008
OSS roles (5) OSS (component) provider: Leads a “gone-open” software project, ex. Linus Thorvald w/ Linux OSS co-developer or participant: assists the provider in more technical work – the OSS “idea” of joint, altruistic work OSS integrator: makes new software system by re-using OSS software/components OSS pre-co-developer: reports bugs and wishes for new features, sometimes changing the code. OSS user: may download “free” (not open) binary software on a private computer, e.g. Acrobat OSS customer: specifies and finances new software, later published as OSS? OSS skills: technical, commercial, organizational, creative, … Telenor-NTNU OSS contact meeting, 18 Dec 2008
OSS Business Models (6) In general, to enter in the OSS field, companies have to manage Intellectual Property (IP) differently and to innovate more: Sale/ divestiture Revenues New revenues Spin-off License Own market revenue Own market revenue 0 Internal and external development costs Internal development costs Cost and time savings from leveraging external development Costs [Chesbrough2006] Telenor-NTNU OSS contact meeting, 18 Dec 2008
OSS Business Models (7) From COSI ITEA2-project: Telenor-NTNU OSS contact meeting, 18 Dec 2008
Novel Innovation Models (8) Traditional innovation models are based on the “egoistic” protection of Intellectual Property, i.e. cannot capture value from OSS for companies. So your cards lie with “face down” and contents hidden, as a private and short-term sub-optimalization. Novel innovation models leave your cards “face open” and contents acessible for everyone. This paradoxical altruism promotes maximum combinatorics and future innovation, by a public and long-term exchange for societies and companies to reap the full benefits of OSS: The guidelines for revised development processes from “private investment” to “collectively action” hardly exist. Telenor-NTNU OSS contact meeting, 18 Dec 2008
Novel Innovation Models (9) Several issues need to be addressed: How to succeed in attracting co-developers when “going open”? How can traditional (i.e. paid software development by software companies), coexist and even amplify the benefits for both the “old” and “new” work mode? So rely less on classic OSS idealism, rather refine and commercialize more cooperative work modes. Friprog’s learning ecosystemto systematize the (meta-) services that might be needed (next slide): How to establish such an ecosystem? Roles? How to build competence? How to offer legal or economic advise? How to make decisions about changes in old vs. new systems? How to build and maintain expert communities? How to manage experience bases (avoid the “white elephants”)? Practically: if (most of) the code is shared and “free”, where is the profit coming from? [Chesbrough2006] Henry Chesbrough: “OPEN Business Models”, Harvard Business School Press, 2006. [Browning2008] L. D. Browning, A. S. Sætre, K. Stephens and J.-O. Sørnes: ”Information and Communication Technologies in Action: Linking Theory and Narratives of Practice”. New York: Routledge. Telenor-NTNU OSS contact meeting, 18 Dec 2008
4. OSS research at NTNU (1) Why is this interesting for you? • Experience from industry-related research • What should we focus on in future research? • Experience from theory-driven research • How to validate in practise? • Experience from education • What should students know about OSS? 21 Telenor-NTNU OSS contact meeting, 18 Dec 2008
4. Multi-faceted OSS research (2) … juridical & economical (not yet) psychology political … learning … software engineering social sciences 22 Telenor-NTNU OSS contact meeting, 18 Dec 2008
4. research activities (3) OTS surveys ITEA COSI project Focus on company based software engineering, reuse, and OTS Open source survey Open source and Art Case Open standards (ARM) Education Case Gentoo 23 Telenor-NTNU OSS contact meeting, 18 Dec 2008
4. NTNU: CBSE and OTS studies (4) 1990-98: EU projects (e.g. REBOOT) on internal software reuse; hard! 1995-: New global “bazaar” of COTS/OSS, through web 2003-08: Industrial surveys on OTS reuse Norway, Germany, Italia, China Developer panels and follow-up interviews with qualitative data to give insight Research instruments and raw data: “gone open” – please repeat our studies!! Telenor-NTNU OSS contact meeting, 18 Dec 2008
NTNU: Roles in OTS-based reuse From forthcoming paper by Jingyue Li et al., IEEE Software 2008 Telenor-NTNU OSS contact meeting, 18 Dec 2008
NTNU: gained insights on OTS reuse • 1a. Ask colleagues to find “right” component, e.g. Hibernate, Spring, … (there are 10-20 very common ones). 1b. Otherwise search the net, download 3-6 candidates for further evaluation and possible selection, record the outcome for later use. 1c: If no close match is found, either: – 1c.1 Issue a “bookmark” for the future in an OSS portal. – 1c.2 Consider renegotiate requirements: iterate 1b-1c.2. – 1c.3: Develop new, own software (with OSS parts), post it as OSS and try create project/community. • Summary: no formal selection method, selection can be hosted by most lifecycle processes, need component “uncle” for maintenance, “quality“ not a problem • Problems: effort estimation, integration, debugging, customer non-participation, licensing, company policies, what classification framework (ontologies) for what properties and how to reliably classify components? Telenor-NTNU OSS contact meeting, 18 Dec 2008
Industrial examples of OSS reuse: • Bouvet: measure power consumption in trains (GoOpen’08). • Norwegian Air: travel booking system summer 2002 (GoOpen’08), • Acando: reimbursements for travel for medical treatment (GoOpen’09) • Telenor IS: mapping attitudes to OSS in coop. with NTNU (GoOpen’09). • YYY • YYY Telenor-NTNU OSS contact meeting, 18 Dec 2008
Action Research on Gentoo OSS PhD by Thomas Østerlie Gentoo: OSS release management tool, scripts, 300 co-developers in 40 countries Worked as co-developer for two years; distributed, participative, “in-process” field study Remote debugging: mutual guesswork, as “sense-making”, informal processes Data: diaries, emails, IRC/version logs Telenor-NTNU OSS contact meeting, 18 Dec 2008
research activities OTS surveys ITEA COSI project Focus on company based software engineering, reuse, and OTS Open source survey Open source and Art Case Open standards (ARM) Education Case Gentoo 29 Telenor-NTNU OSS contact meeting, 18 Dec 2008
ITEA COSI project (2006-2008) • Industry and academia • Finland, Netherlands (coord.), Norway, Spain, Sweden • Understand and benefit from Open source software and development practices • Shared internal development • Norwegian COSI • IKT Norway • eZ Systems, Keymind, Linpro, e??farm, Oslo Børs, Friprog, NTNU • Budget about 18 MNOK • Sponsored by NFR: 8.5 MNOK totally Telenor-NTNU OSS contact meeting, 18 Dec 2008
Adoption of OSS in the Software Industry • About 70% (50%) are reusing and integrating OTS (OSS) components • Into all kinds of products • To all kinds of customers • Large companies more often than small • Consultancy companies more often than software houses • 15-20% participate in OSS co-development • Means huge, global and dedicated cooperation communities • About 5% provide their own OSS products (”going open”) • Of these ?? % are attracting other co-developers Telenor-NTNU OSS contact meeting, 18 Dec 2008
Motivations for adoption of OSS • Simplify developer’s job • High availability of information, components and their source code • Simple procurement • Membership of community for support and future influence • Reusable software assets • Increase productivity • Increase quality (reliability, ..) • Increased focus on architecture and even product line • Increase compliance with standards • Reduced costs • Reduced development effort • No license fees Telenor-NTNU OSS contact meeting, 18 Dec 2008
Selection: Identification, Evaluation and choosing of wanted OSS-component(s) • Evaluation until something ”good enough” is found • Tested further through test integration and prototyping • Informal knowledge driven process based on: • Previous experience • Recommendations • Informal searches • “Surveillance” of the OSS community Telenor-NTNU OSS contact meeting, 18 Dec 2008
research activities OTS surveys ITEA COSI project Focus on company based software engineering, reuse, and OTS Open source survey Open source and Art Case Open standards (ARM) Education Case Gentoo 34 Telenor-NTNU OSS contact meeting, 18 Dec 2008
Open standards and • Cooperation between ARM Norway (ex-Falanx with Reodor Felgen innovation award in 2006) and NTNU (with half a dozen master’s theses since 2002) • Describing a master’s project 2007-2008 (single person one year): • development of a multi-platform graphics application. • Used ARM’s platform for embedded graphics. Telenor-NTNU OSS contact meeting, 18 Dec 2008
Open standards and ARM • Open Vector Graphics (OpenVG) • OpenVG is a standard for embedded systems • Targets: Map applications, scalable user interfaces, e-book readers, games and SVG viewers • Scalable Vector Graphics (SVG) • Open format for describing vector graphics in XML which provides uniform representation of 2D graphics. • SVG Tiny – A mobile profile targeting light weight mobile devices Telenor-NTNU OSS contact meeting, 18 Dec 2008
Open standards and the application PC platform SVG Tiny applicationApplication size ~20.000 LOC Open Standards SMIL XML11 DOM3 XLINK Other W3C standards... PNG JPEG ARM platform Telenor-NTNU OSS contact meeting, 18 Dec 2008
Results from application development and porting • Ease of adoption • OpenVG is an open standard, thus royalty-free. • Specification and reference implementation publicly available. No project expenses. • Performance • OpenVG allows for efficient and creative implementations. • Efficient SVG Tiny viewer achievable on a regular PC and ARM platform. • Conformance • OpenVG conformance tests assure correct implementations. • Consistent and correct behaviour of application on PC and ARM platform. • Portability • OpenVG API abstracts and de-couples application from hardware . • High degree of application portability. Less effort Telenor-NTNU OSS contact meeting, 18 Dec 2008
Research activities OTS surveys ITEA COSI project Focus on company based software engineering, reuse, and OTS Open source survey Open source and Art Case Open standards (ARM) Education Case Gentoo 39 Telenor-NTNU OSS contact meeting, 18 Dec 2008
Cases: Art and open source software = SArt • Main objective of SArt • to propose, and assess, and improve methods, models, and tools for software development in art context • Cases (in sourceforge portal) • The Open Digital Canvas Project • Sonic Onyx Project (mobile phones) • The Flyndre Project 40 Telenor-NTNU OSS contact meeting, 18 Dec 2008
SArt: art and open source software 41 Telenor-NTNU OSS contact meeting, 18 Dec 2008
Premiered art competition The Open Wall Open Contest http://mediawiki.idi.ntnu.no/wiki/sart/ Deadline 15th September 2009 The prize award will take place at this year’s festival for art and technology in Trondheim, Trondheim Matchmaking, the 16th – 18th of October. 1st prize 2000 €, 2nd prize 1500 €, 3rd prize 1000 € Telenor-NTNU OSS contact meeting, 18 Dec 2008
5. OSS ideas for Telenor etc. (1) Map existing use of and interest in OSS? – done spring 2009 by two master students.0 Establish teams/fora/communities for OSS at Telenor? Success criteria and ROI models for GoOpen? Alliances with other business units/companies? How to control or influence (OSS) software, that we have come to depend on – like for most purchased products? New business/innovation models? Cooperate with FriProg and NTNU on OSS ecosystem? Telenor-NTNU OSS contact meeting, 18 Dec 2008
5. OSS ideas for software development at Telenor/XX (2) • When new software is built: • Make “modular” structure to enable reuse of “middle layers” from elsewhere. • Try reuse OSS, COTS, or existing internal components. • (Re)negotiate requirements vs. functionality from available components. • Make incentives to promote “lean code”? A any new code line will later consume 2X of initial cost, so aim for “negative” productivity! • Use incremental or agile lifecycle models, e.g. with 4-week increments. • Apply aSVN-like versioning tool for distributed software development. • But inevitably “software rot” of legacy code creeps in, as implicit assumptions made at start will increasingly hinder further changes. Telenor-NTNU OSS contact meeting, 18 Dec 2008
5. OSS ideas for software maintenance at Company XX (3) Maintenance: Any change after first release, 2/3 of costs. To extend, perfect, correct – and restructure the given software. Need tools to analyze such legacy code. Time pressure to prefer ”simple” changes, e.g. to copy and paste from existing code, just ameliorating the chaos. Rather generalize existing code into product lines, and/or try to contribute to OSS, for both code and communities. Possible link to Telenor’s EVISOFT activity with UiO on software maintenance, using e.g. complexity/cost analysis (borger.warloi@telenor.com). More?? – all this depends on you at Telenor Telenor-NTNU OSS contact meeting, 18 Dec 2008
6. Further cooperation berween XX and NTNU: some ideas? (1) • Possible cooperation activities • Subset of previous slide for Telenor activities • Possible work modes • Just NTNU internal • Informal by master and PhD students from NTNU: collect and analyze emirical data from case studies and field work • XX only, or XX + NTNU • Norwegian Research Council • Verdikt, BiA (three possible project types: FP, BP, and CP) • Postdocs, industri-stipendiater (50% coverage), other possibilities • EU’s FP7, ITEA2, Nordisk Råd, …. Telenor-NTNU OSS contact meeting, 18 Dec 2008
6. NTNU Resources (2) • Software engineering group (SU in Norwegian) • publications, student reports, and courses • www.idi.ntnu.no/grupper/su/ (SU group homepage) • www.idi.ntnu.no/grupper/su/publ/INT-PUBL.php3 (publ. list) • www.idi.ntnu.no/grupper/su/oss/ (SU on OSS) • Wiki on open source research at NTNU • http://research.idi.ntnu.no/oss • The ITEA2 COSI Project (2006-2008) • Norwegian partner IKT-Norge w/ subcontrcator NTNU • http://www.itea-cosi.org/ • The Nordic OSS Network, Nordisk råd (2009-2012) • Seven partners incl. NTNU, coord. by Bjørn Lundell at U. Skøvde • http://www.??.his.se Telenor-NTNU OSS contact meeting, 18 Dec 2008
6. Possible NTNU Resources (3) • NFR-VERDIKT proposal by R. Conradi and Alf Steinar Sætre (IØK): “Open Source Software & Industrial innovation Success factors (OSSIS), 15 Oct. 2008. • NFR-VERDIKT proposal by R. Conradi, Daniela S. Cruzes (both NTNU), and Tonje Osmundsen (NTNU Samfunns-forskning (Eds.): “Maintaining Software Systems with an evolving network of open source providers (MAIN-SOFT), 25. Nov. 2009. • Revised education plans • National research school • International master in OSS Telenor-NTNU OSS contact meeting, 18 Dec 2008
6. NTNU resources: master students spring 2010 (4) • Proposed list of topics: • …?? • …?? Telenor-NTNU OSS contact meeting, 18 Dec 2008