Why Fedora? The Fedora Message Warren Togami Fedora Founder Associate Software Engineer Red Hat, Inc.

Slides:



Advertisements
Similar presentations
Dell IT Innovation Labs in the Cloud “The power to do more!” Andrew Underwood – Manager, HPC & Research Computing APJ Solutions Engineering Team.
Advertisements

Update on the California Dairy Future Task Force and moving forward December 5, 2012 CONFIDENTIAL AND PROPRIETARY Any use of this material without specific.
Ανοιχτό Λογισμικό & Βέλτιστες Πρακτικές Υλοποίησης Έργων Πληροφορικής σε Επιχειρήσεις Dimitris Andreadis Software Engineering Manager JBoss Application.
By: Chinwoo CHAPTER 25: MARKETING PLANNING. Marketing planning: The process of making appropriate strategies and preparing marketing activities to meet.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Implementing Strategy Chapter 7. Objectives Upon completion of this chapter, you should be able to:  Translate strategic thought to organisational action.
This slide deck is for LPI Academy instructors to use for lectures for LPI Academy courses. ©Copyright Network Development Group Module 01 Introduction.
COMMUNITY TO COMMERCE: The Red Hat/Fedora/FOSS Model Paul W. Frields Fedora Project Leader, Red Hat October 9, 2009.
PARTICIPATING IN THE FEDORA / RED HAT / FOSS MODEL Paul W. Frields Fedora Project Leader, Red Hat June 24, 2010.
All about Eugene Teo Linux Users' Group (Singapore) April 2006 Meeting Core 5.
Building Communities GNOME.Asia Summit 20 th November 2009 Pockey Lam, Beijing Linux User Group
Expanding Involvement of Women in F/OSS Presented by Elizabeth Krumbach Philadelphia area Linux Users Group September 2, 2009.
Fedora Installation Workshop. Introduction to Fedora Project and Fedora.
Introducing Fedora Core 5 Codename: Xxxxxxxx March 18, 2006 Robert 'Bob' Jensen Fedora Ambassador Release Notes Editor-in-Chief.
A Model For Sustainable Open Source Development Jared Smith Paul W. Frields Red Hat, Inc. This presentation is made available under a Creative Commons.
- 12 August 2006.
Why Fedora? Overview and Q&A Warren Togami Associate Software Engineer Red Hat, Inc. Southern California Linux Expo Feb 11-12, 2006.
And how to avoid it Tom “spot” Callaway Presented by Fedora Engineering Manager This presentation is licensed under a Creative Commons Attribution-Share.
Introduction to Fedora David Nalley September 10, 2008 version 0.2.
Open Source Policy Community Call 1:00 PM, Eastern Thursday, March 24, 2016 Seong K. Mun, PhD Don Hewitt Arlington, VA.
340,000 Fedora boxes checked in for updates last week.
What is LINUX??? Linux is an operating system. It was initially created as a hobby by a young student, Linus Torvalds, at the University of Helsinki in.
Red Hat & Fedora: A Strategy for Open Source Success Jared Smith Fedora Project Leader – Red Hat, Inc. This presentation is made available under a Creative.
An Introduction to. Where did Fedora come from? Boxed set every 6 months == Failed business model [
Karsten Wade Sr. Developer Community Mgr, Red Hat.
Fedora Project Your Name Your Title(s) Relevant SIG/Project Affiliation(s) This presentation is licensed under a Creative Commons Attribution-ShareAlike.
Introduction to Fedora and What's new in Fedora 11 and Fedora 12? Rahul Sundaram Fedora 11 Release Party, Pune, India Sat July 4 th 2009.
Fedora Project Paul W. Frields Red Hat, Inc. Fedora Project Leader This presentation is licensed under a Creative Commons Attribution-ShareAlike (BY-SA)
Expanding Involvement in F/OSS Presented by Elizabeth Krumbach Philadelphia area Linux Users Group September 2, 2009.
STRATEGIC pLANNING Lifetime Networks.
2017 Education Series – NCHCA/CEO/City of Ottawa February 24, 2017
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Fedora Project Your Name Your Title(s) Relevant SIG/Project Affiliation(s) This presentation is licensed under a Creative Commons Attribution-ShareAlike.
Improve yourself in real world
Where we are, where we’re goin’
Creating and nurturing communities of contributors
IT Governance at the SCO
Business Model Validation Lab
Introduction to Fedoraproject
Introduction SOFTWARE ENGINEERING.
Elanex presentation to FLA technology symposium, November 14th, 2007
Information Technology Project Management – Fifth Edition
Failures of Fedora What we learned from it Rahul Sundaram
A Career in Open Source Software
Building a career with Ubuntu and FOSS
Building a Career in FOSS
Fedora Project Paul W. Frields Red Hat, Inc. Fedora Project Leader
TSMO Program Plan Development
Jeff Williams OWASP Foundation Chair
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Development of the Team
THE POWER OF BEING CONNECTED
Overcoming questions and objections
IS4550 Security Policies and Implementation
Creating a Business Architecture Practice
Implementing Cooperative Sustainability – The 2012 Plan
Visual Story Network Strategic Planning
4 Ways to PEPP Your Channel Sales
IS3440 Linux Security Unit 8 Software Management
Enterprise Architecture Methods
Automating Profitable Growth™
All staff briefing 13 Dec 2018 TUPE transfer to NHSI.
The Canterbury Clinical Network
Small Organizations are Different?
Delegation Skills.
Automating Profitable Growth™
GA’s SPDG Lessons Learned
Implementation of EuP in Industrial Practice
Regional Operations Forum Setting the Stage
Module 02 Operating Systems
Presentation transcript:

Why Fedora? The Fedora Message Warren Togami Fedora Founder Associate Software Engineer Red Hat, Inc.

Please set Cell Phones to Silent

Agenda ● What is the Fedora Project? ● How does Red Hat benefit from Fedora? ● Past Mistakes ● Community Building Strategies ● Future Direction

Warren's Past Life 2000 Linux Advocate and Hawaii LUG K12LTSP for schools $3,000 for 30 seat school lab. Easy sell? Limited success: Two elementary schools

Warren's Past Life Linux Advocate and Hawaii LUG K12LTSP for schools $3,000 for 30 seat school lab. Easy sell? Limited success: Two elementary schools Software was not good enough... Took too much effort and time Mission: Must make FOSS better

History 2002 school project at University of Hawaii Proposal to Community: Collaborative development of a centralized repository “Extras” add-on software for Red Hat Linux proposal to merge, create bigger project

History 2003 proposal to merge, create bigger project January 2004 hired as Intern Red Hat's Need ● Differentiate community project from ● Enterprise product

Fedora Today Rapidly growing community of volunteers Various sub-projects “Open Development Lab” Fedora Core ● Operating System that was Red Hat Linux ● Only indirect contributions from community ● Bug reports and patches Documentation Project

Fedora Today Volunteer Sysadmins Fedora Ambassadors ● ~100 marketing volunteers globally ● Fedora presence at events worldwide Fedora Legacy ● Red Hat engineering must focus on the Future ● Community security maintenance of older Fedora releases ● Community Project, Community chance to decide fate

Fedora Development Cycle

Fedora Today Fedora Extras ● Fedora grew from the model of Extras ● Collaborative, Central Development ● Package Guidelines, Processes, Policies ● Thorsten Leemhuis, tech journalist Leader ● Over 100 contributors, 90% community ● Almost 2000 source RPM packages

Fedora Today Translators ● accounts!

Fedora: Open Development Lab Research & Development

Fedora: Open Development Lab

Fedora Leading the Way Progress in FOSS Ecosystem

What Fedora has Become 2003 Proposal: Collaborative development of a centralized repository Nothing New... Obvious question... Why didn't Warren work on Debian?

Primary Goal of Fedora Rapid Progress of Free and Open Source Software

Fedora = Progress

How We Achieve Rapid Progress Understand Key Difference ● Community motivation ● Commercial motivation

How We Achieve Rapid Progress Community Motivation ● “fun” short-term benefit ● Attention to detail, Real World ● Volunteers not accountable to Progress or Schedules ● Decisions by Consensus, Tough Decisions are not made ● Too Much Effort

How We Achieve Rapid Progress Commercial Motivation “boring” Long-Term Strategic Benefit i.e. GCC, NPTL, O(1) kernel scheduler, exec-shield, FORTIFY_SOURCE, SELinux, Xen, OSS Java, Directory Server Very Expensive if Done Alone Community and Commercial are better at different aspects of Development

How We Achieve Rapid Progress

Community works on short-term issues Company works on long-term issues Community Motivation: Debian Commercial Motivation: Sun We Do Better because We Have Both Mutual Benefit - Complement Strength and Weaknesses of each other Rapid Progress, cost effective

Fedora is Critical to Red Hat Perception: Fedora will be abandoned Red Hat interested in only Enterprise Corporate Suicide Critical to Red Hat's Business Red Hat invests millions Good for community? Achieve Progress Together

Fedora is Critical to Red Hat Community is Force Multiplier

Past Mistakes

The Dark Age 2003 RHLP and Fedora Launch PAIN, Frustration, Anger, Confusion “Join us to build a community project!” No Leadership No Infrastructure No Tools We expected the community to do it.

Satire: The Dark Age 2003 RHLP and Fedora Launch PAIN, Frustration, Anger, Confusion “Join us to build a community project!” No Leadership No Infrastructure No Tools We expected the community to do it. Google for “EAT YOUR BRANE”

Communities do not “Happen” Opening software alone will not create a community Fedora is not a “magic bullet” to solve problems (Neither was Foundation) Do not expect communities to happen Communities must be Built But how?

Community Building Strategies

Community Building Clear Leadership ● Lead by Example ● Release Early, Release Often ● Show Constant Forward Progress ● Momentum is Key Organization (website, policies, processes) Communication (lists, forums, IRC etc.) Infrastructure (servers, networks, people)

Community Building Learn from RHLP/Fedora Launch Mistakes Fedora Directory Server Launch Careful planning Delayed for weeks and months Prepared website and infrastructure People responsible for communication Anticipate questions, already in FAQ

Attitudes about Fedora “Perpetual Beta of RHEL” Negative Message Better ways of saying it ● Benefit of Being True Scope of Fedora much larger today ● Community wants to do more ● Let them do it (Extras, Games etc.) We cannot productize all this

Micro-Communities For any problem there are usually volunteers interested and willing to work on it Only Need Organization Connect Problems to People interested

(Recap) Community Building Clear Leadership ● Lead by Example ● Release Early, Release Often ● Show Constant Forward Progress ● Momentum is Key Organization (website, policies, processes) Communication (lists, forums, IRC etc.) Infrastructure (servers, networks, people)

Micro-Communities For any problem there are usually volunteers interested and willing to work on it Only Need Organization Connect Problems to People interested Micro-Community Community formed to solve a particular problem e.g. Extras, Perl Team, Ambassadors Fedora Games Fedora Art?

Fedora Summary Points Primary Goal: Rapid Progress of Open Source Software Open Development Lab where R&D happens Community is a Force Multiplier

Future Direction of Fedora Open Core to direct contributions from the Community Safeguards protect integrity Reward for proven contributors Get upstream developers involved Decision of RH package maintainers

Questions and Answers