---
# System prepended metadata

title: 'Developer call June 11, 2020'

---

# Developer call June 11, 2020

These are collaborative notes. Please feel free to add points to the agenda that you wish to discuss. If the notes are missing things that you consider important, please add your thoughts. Thank you!

What's here will be transferred to the Fairlearn repo.

Attendees:
- [Roman Lutz](https://github.com/romanlutz)
- [Miro Dudik](https://github.com/MiroDudik)
- [Hilde Weerts](https://github.com/hildeweerts)
- [Hanna Wallach](https://github.com/hannawallach)
- [Parul Gupta](https://github.com/parul100495)
- [Adrin Jalali](https://github.com/adrinjalali)

Agenda:
- new website at https://fairlearn.github.io/
    - please provide feedback and feel free to submit PRs to update/edit/add content or styling
    - content in the process of getting created, please help if you're interested! This includes
        - user guides
        - roadmap, vision/mission, FAQ
        - contributor guide
            - acceptance criteria
- Governance
    - copyright updated to "Copyright Microsoft Corporation and contributors"
    - short-term:
        - define how to become core dev
        - define requirements for contributions to be accepted
    - long-term:
        - would it help for Fairlearn to become a foundation / charity? at which point?
            - NumFocus?
            - def. need to transition if there are outside institutional contributors; possibly earlier? if we reach a larger scale

- Kevin in Gitter:
  > fwiw i'd be excited to hear if people on the team have thoughts on:
    - > who are the current users of fairlearn, what do they love about it?
        - how do we find out?
    - > what's the roadmap for the project in the next 3-6mos?
        - TODO: start a PR around a short-term roadmap
    - > from i'd also be excited to discover if there are any co-conspirators interested in working towards addressing practioner needs (eg, holstein et al. 2019) or supporting practioners facing the wider scope of sociotechnical fairness work (eg, madaio et al. 2020; selbst et al. 2020).
        - TODO: meet and discuss (already planned!)

- Metrics: Simplicity/usability and more complex metrics group objects with
  richer functionality don't need to be mutually exclusive. We will iterate on
  the current state.

- Notebooks
    - development process needs to be established
    - porting notebooks from `notebooks` over to `examples` as a good first issue
    - To work out proper examples with a focus on sociotechnical framing we'll
      set up a weekly hour where everyone who wants to discuss and contribute
      can do so. It'll be at the same time as the developer call
      (Thursday 8am)

- UX
    - There's already a separate call scheduled (originally meant to be on
      6/12, but had to be rescheduled to next week) to discuss various kinds
      of potential UX research directions.
    - Beyond that there's an immediate need to remove obstacles to contribute
      to the UX. Clarifying the roadmap as mentioned above is one step in this
      journey. Currently the contributor guide is focused entirely on Python
      code, with basically no explanation on how to work with the typescript
      based dashboard. 
