Internet Collaboration with A SIGOSSEE Seminar in Stockholm 15ht of Sept 2005 project manager Knut Yrvin Sept 13 th 2005. Foils only for free distribution.

Slides:



Advertisements
Similar presentations
Computer Software 3 Section A Software Basics CHAPTER PARSONS/OJA
Advertisements

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Building free software with For students at UiO Nov 15'th project manager Knut Yrvin Nov Foils are GPL'ed Based on Debian GNU/Linux.
Alternate Software Development Methodologies
CS 3500 SE - 1 Software Engineering: It’s Much More Than Programming! Sources: “Software Engineering: A Practitioner’s Approach - Fourth Edition” Pressman,
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
1 IS371 WEEK 8 Last and Final Assignment Application Development Alternatives to Application Development Instructor Online Evaluations.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Health Informatics Series
CRM SOFTWARE What is CRM, Evolution of CRM software and SaaS, SugarCRM in depth, CRM SW Market.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Lecture 1.
Creation & Development of Teaching Materials in Nynorsk 6. november 2008 Hjalmar Eiksund, Nynorsksenteret
Introduction to AS Computing
Geographic Information Business and Interoperability: The Future of GIS Andrew U. Frank Geoinfo TU Vienna overheads available.
INTRODUCTION TO CLOUD COMPUTING Cs 595 Lecture 5 2/11/2015.
Quality of Information systems. Quality Quality is the degree on which a product satifies the requirements Quality management requires that : that requirements.
Software Development Concepts ITEC Software Development Software Development refers to all that is involved between the conception of the desired.
Designing Interactive, Community-based Websites Michael MacIsaac.
Dr. Tom WayCSC What is Software Engineering? CSC 4700 Software Engineering Lecture 1.
1 Agile Methodology & Programming Ric Holt July 2009.
Agile Programming Principles.
1 CS 456 Software Engineering. 2 Contents 3 Chapter 1: Introduction.
1 SYS366 Lecture 1: Introduction to Systems. 2 What is Software Development? Software Development implies developing some software – but it does not involve.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Marketing Sakai – Partie Deux Developing and Sharing Case Studies Mike Zackrison – rSmart Lois Brooks – Stanford University July 3, 2008.
InWEnt | Qualified to shape the future1 Internet based Human Resource Development Management Platform Human Resource Development Programme in Natural Disaster.
Software Engineering EKT 420 MOHAMED ELSHAIKH KKF 8A – room 4.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
The Systems Development Life Cycle
Accounting Information System By Rizwan Waheed M.Com 710.
Software Engineering 1 Some Definitions Lesson 2.
EPortfolio Technology: Options and Futures Darren Cambridge.
SOFTWARE ENGINEERING1 Introduction. SOFTWARE ENGINEERING2 Software Q : If you have to write a 10,000 line program in C to solve a problem, how long will.
CSE 102 Introduction to Computer Engineering What is Computer Engineering?
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Software Life-Cycle and Models
D R A T D R A T ABSTRACT Every semester each department at Iowa State University has to assign its faculty members and teaching assistants (TAs) to the.
Why? Software Engineers don’t communicate very well…
CS223: Software Engineering Lecture 2: Introduction to Software Engineering.
Chapter 5 How are software packages developed?. What are the main steps in software project development? Writing Specifications - Analysis Phase Developing.
Chapter 10 Information Systems Development. Learning Objectives Upon successful completion of this chapter, you will be able to: Explain the overall process.
Requirements Analysis
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
ANALISA & PERANCANGAN SISTEM Disusun Oleh : Dr. Lily Wulandari Program Pasca Sarjana Magister Sistem Informasi Universitas Gunadarma.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
"proper words in proper places“ translating for the localisation industry LRC Summer School Limerick 16 June 2005.
RANDY MODOWSKI COSC Cloud Computing. Road Map What is Cloud Computing? History of “The Cloud” Cloud Milestones How Cloud Computing is being used.
“Business first, technology's the tool.”. The Application Hosting business model is based on a very simple idea:  Install application software on powerful.
Poka-yoke in software A software products company sells application software to an international market. The pull-down menus and associated mnemonics provided.
We want you! for Presentation at the debian miniconf at LCA 2007 in Sydney Holger Levsen Jan 15 th 2007 aka Debian-Edu.
Lightweight Hardware < 128 MB Software Libre By Knut Yrvin 27 th September 2006 Foils to free use and publication with crediting the author Half thick.
Enabeling aid and business in practice FOSTRADA at HiA August 21 th 2006 by Knut Yrvin For free use. Credit the author.
An Introduction to. Where did Fedora come from? Boxed set every 6 months == Failed business model [
Convergence with Qt The cross platform future by Knut Yrvin Qt by Nokia.
Free Software: Driving Innovation
We want you! for aka Debian-Edu
Intro to SaaS Software as a service (SaaS) is a model of software delivery where the software company provides maintenance, daily technical operation,
Lecture 1 What is Software Engineering? CSC 4700 Software Engineering
Internet Collaboration with
Information Technology (IT) Department
Building free software with
Why Nokia aquired Qt by Knut Yrvin at Community One, Apr 15 - Oslo
Norwegian experiences making
Importance of developer gatherings
About SLX Debian Labs From presentation at SIGOSSEE Seminar Stockholm 15ht of Sept 2005 project manager Knut Yrvin Sept 13th Foils only for free.
An Introduction to Software Engineering
Rapid software development
Presentation transcript:

Internet Collaboration with A SIGOSSEE Seminar in Stockholm 15ht of Sept 2005 project manager Knut Yrvin Sept 13 th Foils only for free distribution SLX Debian Labs

● A complete ICT-solution for the schools – network architecture out of the box – operational concept – digital user profile – OpenOffice and 75 user programs ● Made on our mother tongue with the schools curriculum in mind ● Made for the school budget Skolelinux-project as an example 2

> 200 Skolelinux-schools Hardware vendors: its many more 3

The basic idea ● Pupils interested in technical, under-the-hood things – could learn by example – from source code written by expert programmers ● Using our own mother thong when travelling on the information highway ● Get more ICT-equipment and programs, and less time with maintenance. More for less 4

Start ● 25 people said they would participate, 13 meet on the first meeting ● After a couple of moths we grew to 40 ● s is efficient, but could turn into flame- wars when people don't know each other ● Precise goals

Collaboration ● Had to apply for founding to make developer gatherings – The ings got to hot – Euro for HW and the first 8 gatherings ● Had to make an infrastructure for developers and manuals for contributors ● Had to do a lot of motivating effort

Have to obey ● All code, translations and documentation has to be committed to the Concurrent Versions System on Internet ● Bugs has to be committed to the bug-tracking system ● Commit everything upstream. That means release often running code ● Follow the licence-terms ● Help people to help them selves ● The person who does something decides Do-ocracy 7

Some characteristics ● Started as an voluntary effort 2. July 2001 ● Contribution is over man-hours from ~ 200 developers, translators, and testers ● More than 22 developer gatherings with 20 until 190 participants – 16 in Norway with local Skolelinux-development – 6 Internationally in Norway, Germany and Brazil ● The version system “is our project” 8

Who is Skolelinux today (aka Debian-edu) SLX Debian Labs (a foundation) ● A part of the Debian project ● 3-4 man years A member organisation ● It's own border ● 130 active developers ● 30 over active developers ● > 20 translators 9 Developers and users

Some successes ● We are a Debian project – Debian edu, Custom Debian Distribution for schools – turn key solution – New Debian installer, half thick clients ● A lot of attention and installations – Use in many countries – Awards (e.g. New Media Award 2004) ● Have kick-started others – etch w/security, Edubuntu many languages

Challenges ● Paying people doing software development ● Maintenance when some people get interested doing other things ● Founding the gatherings ● Making a sustainable commercial entity selling maintenance services and up-keep – To founding development etc. ● Lack of open standards even if the policies are right (things takes time)

Q & A 12

Real F/OSS effort is about ● Using the F/OSS development methods and tools – It costed us dearly when the County Councils did not release the OpenOffice-translations ● Using Purchasing Requirements that don't discriminate: Universal Design Requirements – You can't just say: We want open source, and then buy it as you did from your proprietary vendor ● Using Reference Implementations with running and maintained code (FEIDE is on sourceforge) – Please don't reinvent Open Source development methods. You are not that good... 13

What's wrong with just using shrink wrap products methods? excluding the true power of F/OSS development Jonathan Grudin: The development of interactive systems Users identified Developers identified Users identified Developers identified COMPETITIVELY BID CONTRACT DEVELOPMENT PRODUCT DEVELOPMENT IN-HOUSE AND CUSTOM DEVELOPMENT Time Project Start System Delivered

Service financing ● Further development ● Translation ● Architecture ● Teaching aids ● Handbooks ● Sharing of best practices ● introduction ● courses ● maintaining ● day-to-day operation ● updates ● expert help Our contribution > h Common- expenses with the software 15

Faster, Better, and Cheaper Free/Open Source Software Development (F/OSSD) often entails shorter development times that can produce higher quality systems, and incur lower costs than may be realized through developing systems according Software Engineering (SE) techniques. [...] Internet time and F/OSSD projects also tend to produce incremental software releases at a much faster rate, even to the point of releasing unstable but operational daily system builds. This denotes not only a reduction in product release cycle times compared to SE practice, but also a significantly restructured life cycle process and process cycle time reduction. Walt Scacchi from Institute for Software Research University of California, Irvine 16

ICT at school is really about: ● Using the system to send drawings to school classes in other countries. Learning to express, sharing and learn. ● The system is used to make music, to read, gather information or decode words (in lower grades). ● It's not about office-administration with 3- 4 office-products! 17