The Birth Of The Industrial Haskell Group : Cufp 2009
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View The Birth Of The Industrial Haskell Group : Cufp 2009 as PDF for free.
More details
- Words: 995
- Pages: 26
A shared infrastructure
Establishing a consortium
An idea for shared development
Birth of the Industrial Haskell Group Duncan Coutts
CUFP 2009
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Economics of programming languages The economics drives us to shared languages and implementations. • Private languages are a private cost • Shared languages: • more public resources • more skilled people available
• Shared implementations: • share past development costs • opportunity to share future development costs
A shared infrastructure
Establishing a consortium
An idea for shared development
The more we do share, the more we can share
The more we share already, the greater the opportunity to share costs of new development • Compilers • Standard libraries • Tools (profiling, testing, etc)
A shared infrastructure
Establishing a consortium
An idea for shared development
Models of programming language development • Proprietary product • F# • Open, central commercial vendor • Erlang • Open, no central vendor • Haskell • ML • Lisp
A shared infrastructure
Establishing a consortium
An idea for shared development
Funding programming language development
Who do you pay? • do it in-house • central vendor • consultants • grad students... How do we share costs?
A shared infrastructure
Establishing a consortium
An idea for shared development
Open community languages Open community languages have particular advantages and disadvantages • Loads of stuff for free • Choice of consultants • Academics and open source hackers can have
different priorities and timescales • Harder to share future development costs We think a consortium model is a good match for the open languages.
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Why start a consortium now?
Indicators of commercial use pointing upwards: • Job postings • Informal discussions • CUFP attendance • Mailing list traffic, downloads, feature request tickets
A shared infrastructure
Establishing a consortium
An idea for shared development
Planning discussions
Discussed it with Galois after CUFP last year • Who does the organisation? • Issue of cost and expected number of members
A shared infrastructure
Establishing a consortium
An idea for shared development
The Caml Consortium • Aimed for around 20 members • Cost: e3k– e10k for 12 months ($4k–$14k) • Provides OCaml & libs under 4-clause BSD license • Started with 4 members in 2002, 7 members by 2008 • Initially unable to fund full-time development • Now has 10 members
Our analysis: not charging enough, aiming for too many members
A shared infrastructure
Establishing a consortium
An idea for shared development
The Industrial Haskell Group
• Aim initially for 5 members • Cost £6k for 6 months ($10k) • No special license
A shared infrastructure
Establishing a consortium
An idea for shared development
Starting a venture in a recession...
CUFP 2008
Talking to potential members
Doom and gloom
“Great idea! Call us back in a year.”
IHG announced
A shared infrastructure
Establishing a consortium
An idea for shared development
Birth of the IHG
• Started in March 2009 with 3 members • Including Galois and Amgen • Funded 2 man-months of development work
A shared infrastructure
Establishing a consortium
An idea for shared development
How we decide what to do
• Internal mailing list • Collect wish lists • Look for overlaps and high priority tasks • Collectively agree on the tasks
A shared infrastructure
Establishing a consortium
An idea for shared development
What IHG members asked for
• Short & medium term projects • Feature additions • System integration • Development tools • Not bug fixes • Not releases • Not language or core compiler issues
A shared infrastructure
Establishing a consortium
An idea for shared development
What the IHG has funded so far
• Dynamic libraries on Linux • Ongoing work for dynamic libraries on Windows • Allow building GHC without GMP lib • Cabal improvement to reduce build times by
increased sharing
A shared infrastructure
Establishing a consortium
An idea for shared development
Reflections on the process
• “Individual pots” have not been used much • We would add our own suggestions for projects
A shared infrastructure
Establishing a consortium
An idea for shared development
Future aims
• Expand membership • Add price-point for small companies • Consider “sponsorship” level membership
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
What should consortia fund?
• Whatever the members want! • Short and medium term projects of direct benefit:
adding features • Fixing bugs, testing, performance, making releases • Development infrastructure
A shared infrastructure
Establishing a consortium
An idea for shared development
Investing in infrastructure
A modest investment in development infrastructure... Potentially large benefit • more open reusable code • higher quality (code, tests, docs) Mechanism: help the open community to do more
A shared infrastructure
A quick poll...
Establishing a consortium
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Benefits of a community language Hackage — Haskell’s package archive • 1,500+ packages • 400+ developers • Growing steadily • Mostly uniform packaging Hackage contains • Robust reusable libraries and tools • Latest academic research • Plenty of chaff
A shared infrastructure
Establishing a consortium
An idea for shared development
The Hackage example For example, extend Hackage by publishing • Build results • Test results • Test coverage • Quality metrics Benefits • Distinguish the good packages • Encourage quality Virtuous cycle between commercial and other users
A shared infrastructure
Establishing a consortium
An idea for shared development
Summary
• Opportunities to share development costs • Consortium model for open languages • Invest in development infrastructure
Establishing a consortium
An idea for shared development
Birth of the Industrial Haskell Group Duncan Coutts
CUFP 2009
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Economics of programming languages The economics drives us to shared languages and implementations. • Private languages are a private cost • Shared languages: • more public resources • more skilled people available
• Shared implementations: • share past development costs • opportunity to share future development costs
A shared infrastructure
Establishing a consortium
An idea for shared development
The more we do share, the more we can share
The more we share already, the greater the opportunity to share costs of new development • Compilers • Standard libraries • Tools (profiling, testing, etc)
A shared infrastructure
Establishing a consortium
An idea for shared development
Models of programming language development • Proprietary product • F# • Open, central commercial vendor • Erlang • Open, no central vendor • Haskell • ML • Lisp
A shared infrastructure
Establishing a consortium
An idea for shared development
Funding programming language development
Who do you pay? • do it in-house • central vendor • consultants • grad students... How do we share costs?
A shared infrastructure
Establishing a consortium
An idea for shared development
Open community languages Open community languages have particular advantages and disadvantages • Loads of stuff for free • Choice of consultants • Academics and open source hackers can have
different priorities and timescales • Harder to share future development costs We think a consortium model is a good match for the open languages.
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Why start a consortium now?
Indicators of commercial use pointing upwards: • Job postings • Informal discussions • CUFP attendance • Mailing list traffic, downloads, feature request tickets
A shared infrastructure
Establishing a consortium
An idea for shared development
Planning discussions
Discussed it with Galois after CUFP last year • Who does the organisation? • Issue of cost and expected number of members
A shared infrastructure
Establishing a consortium
An idea for shared development
The Caml Consortium • Aimed for around 20 members • Cost: e3k– e10k for 12 months ($4k–$14k) • Provides OCaml & libs under 4-clause BSD license • Started with 4 members in 2002, 7 members by 2008 • Initially unable to fund full-time development • Now has 10 members
Our analysis: not charging enough, aiming for too many members
A shared infrastructure
Establishing a consortium
An idea for shared development
The Industrial Haskell Group
• Aim initially for 5 members • Cost £6k for 6 months ($10k) • No special license
A shared infrastructure
Establishing a consortium
An idea for shared development
Starting a venture in a recession...
CUFP 2008
Talking to potential members
Doom and gloom
“Great idea! Call us back in a year.”
IHG announced
A shared infrastructure
Establishing a consortium
An idea for shared development
Birth of the IHG
• Started in March 2009 with 3 members • Including Galois and Amgen • Funded 2 man-months of development work
A shared infrastructure
Establishing a consortium
An idea for shared development
How we decide what to do
• Internal mailing list • Collect wish lists • Look for overlaps and high priority tasks • Collectively agree on the tasks
A shared infrastructure
Establishing a consortium
An idea for shared development
What IHG members asked for
• Short & medium term projects • Feature additions • System integration • Development tools • Not bug fixes • Not releases • Not language or core compiler issues
A shared infrastructure
Establishing a consortium
An idea for shared development
What the IHG has funded so far
• Dynamic libraries on Linux • Ongoing work for dynamic libraries on Windows • Allow building GHC without GMP lib • Cabal improvement to reduce build times by
increased sharing
A shared infrastructure
Establishing a consortium
An idea for shared development
Reflections on the process
• “Individual pots” have not been used much • We would add our own suggestions for projects
A shared infrastructure
Establishing a consortium
An idea for shared development
Future aims
• Expand membership • Add price-point for small companies • Consider “sponsorship” level membership
A shared infrastructure
Establishing a consortium
Outline
A shared infrastructure
Establishing a consortium
An idea for shared development
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
What should consortia fund?
• Whatever the members want! • Short and medium term projects of direct benefit:
adding features • Fixing bugs, testing, performance, making releases • Development infrastructure
A shared infrastructure
Establishing a consortium
An idea for shared development
Investing in infrastructure
A modest investment in development infrastructure... Potentially large benefit • more open reusable code • higher quality (code, tests, docs) Mechanism: help the open community to do more
A shared infrastructure
A quick poll...
Establishing a consortium
An idea for shared development
A shared infrastructure
Establishing a consortium
An idea for shared development
Benefits of a community language Hackage — Haskell’s package archive • 1,500+ packages • 400+ developers • Growing steadily • Mostly uniform packaging Hackage contains • Robust reusable libraries and tools • Latest academic research • Plenty of chaff
A shared infrastructure
Establishing a consortium
An idea for shared development
The Hackage example For example, extend Hackage by publishing • Build results • Test results • Test coverage • Quality metrics Benefits • Distinguish the good packages • Encourage quality Virtuous cycle between commercial and other users
A shared infrastructure
Establishing a consortium
An idea for shared development
Summary
• Opportunities to share development costs • Consortium model for open languages • Invest in development infrastructure
Related Documents
The Birth Of The Sun
June 2020 12
The Birth Of Jesus
July 2020 18
The Birth Of Rsi
October 2019 35
The Birth
June 2020 8
The Gospel Of The Birth Of Mary
December 2019 56More Documents from "Saundra"
A Wander Through Ghc's New Io Library
May 2020 12
Multicore Programming In Haskell Now!
May 2020 15
Haskell: Batteries Included
June 2020 6
Haskell Arrays Accelerated With Gpus
June 2020 5