Scribd Logo
Fazer o upload

Bem-vindo(a) ao Scribd!

  • The Birth of The Industrial Haskell Group: CUFP 2009

    Enviado por

    Don Stewart
    84 visualizações26 páginas
    It has long been thought that commercial users of Haskell could benefit from an organisation to support their needs, and that as a side-effect the wider Haskell community could benefit from the actions of such an organisation. The stronger community would in turn benefit the commercial users, in a positive feedback cycle. At last year’s CUFP, users of several FP languages raised the issue that there was no organisation that they could pay to do the important but boring work of maintaining and improving common infrastructure. Shortly after CUFP, in partnership with major commercial users of Haskell such as Galois and Amgen, we started to set wheels in motion, and in March 2009 we announced the birth of the Industrial Haskell Group (IHG). The IHG is starting off with a limited set of activities, but already it is having an impact on the state of the Haskell development platform. We expect that as it expands, it will become a significant force driving Haskell forwards. In this presentation we will talk about the motivation leading to the formation of the IHG, how it has worked thus far and what lessons we can learn that might benefit other FP communities. We will also look at how we can encourage the positive feedback cycle between commercial users and the wider community. Original post: http://blog.well-typed.com/2009/09/slides-from-the-ihg-talk-at-cufp/

    Título original

    The Birth of the Industrial Haskell Group : CUFP 2009

    Direitos autorais

    © Attribution Non-Commercial (BY-NC)

    Formatos disponíveis

    PDF, TXT ou leia online no Scribd

    Você considera este documento útil?

    Este conteúdo é inapropriado?

    Denunciar este documento
    It has long been thought that commercial users of Haskell could benefit from an organisation to support their needs, and that as a side-effect the wider Haskell community could benefit from the actions of such an organisation. The stronger community would in turn benefit the commercial users, in a positive feedback cycle. At last year’s CUFP, users of several FP languages raised the issue that there was no organisation that they could pay to do the important but boring work of maintaining and improving common infrastructure. Shortly after CUFP, in partnership with major commercial users of Haskell such as Galois and Amgen, we started to set wheels in motion, and in March 2009 we announced the birth of the Industrial Haskell Group (IHG). The IHG is starting off with a limited set of activities, but already it is having an impact on the state of the Haskell development platform. We expect that as it expands, it will become a significant force driving Haskell forwards. In this presentation we will talk about the motivation leading to the formation of the IHG, how it has worked thus far and what lessons we can learn that might benefit other FP communities. We will also look at how we can encourage the positive feedback cycle between commercial users and the wider community. Original post: http://blog.well-typed.com/2009/09/slides-from-the-ihg-talk-at-cufp/

    Direitos autorais:

    Attribution Non-Commercial (BY-NC)
    Baixe no formato PDF, TXT ou leia online no Scribd
    Sinalizar o conteúdo como inadequado
    84 visualizações26 páginas

    The Birth of The Industrial Haskell Group: CUFP 2009

    Enviado por

    Don Stewart
    It has long been thought that commercial users of Haskell could benefit from an organisation to support their needs, and that as a side-effect the wider Haskell community could benefit from the actions of such an organisation. The stronger community would in turn benefit the commercial users, in a positive feedback cycle. At last year’s CUFP, users of several FP languages raised the issue that there was no organisation that they could pay to do the important but boring work of maintaining and improving common infrastructure. Shortly after CUFP, in partnership with major commercial users of Haskell such as Galois and Amgen, we started to set wheels in motion, and in March 2009 we announced the birth of the Industrial Haskell Group (IHG). The IHG is starting off with a limited set of activities, but already it is having an impact on the state of the Haskell development platform. We expect that as it expands, it will become a significant force driving Haskell forwards. In this presentation we will talk about the motivation leading to the formation of the IHG, how it has worked thus far and what lessons we can learn that might benefit other FP communities. We will also look at how we can encourage the positive feedback cycle between commercial users and the wider community. Original post: http://blog.well-typed.com/2009/09/slides-from-the-ihg-talk-at-cufp/

    Direitos autorais:

    Attribution Non-Commercial (BY-NC)
    Baixe no formato PDF, TXT ou leia online no Scribd
    Sinalizar o conteúdo como inadequado
    de 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 An idea for shared development

    Outline

    A shared infrastructure

    Establishing a consortium

    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 An idea for shared development

    Outline

    A shared infrastructure

    Establishing a consortium

    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 IHG announced

    Doom and gloom

    “Great idea! Call us back in a year.”


    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 An idea for shared development

    Outline

    A shared infrastructure

    Establishing a consortium

    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 Establishing a consortium An idea for shared development

    A quick poll...
    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

    Você também pode gostar