# Fairlearn community calls notes

This document contains the notes from the fairlearn biweekly commmunity calls. If you would like to enter some notes before the meeting, add a new dated section.

## 15.01.2025
- We are very happy to welcome our new maintainer, Tahar!
- Fairlearn will be in a sprint in Berlin, February 19. February 12 at 7pm CET there will be a pre-sprint online. We have some good first issues, but we might need more (e.g. testing). Docs for setting up your environment is not inclusive enough for beginners.
- There was an issue with the Python version during the Pyladies spring too which Tamara will look into. Our CI was not testing properly for all versions. Tamara will work on more robust config in the coming weeks.
- Several stages where PRs can fall through (1) sociotechnical framing (i.e. can we come up with at least one real world example in which the method would make sense to use), (2) Does the code do what the paper does? (3) Engineering. Also difficult to pick up later with a long comments trail. What type of testing we can require from people that submit new methods to deal with (2) i.e. does the method do what the paper does? Miro will ask some folks who previously organized reproducibility summer school for suggestions.
- Michael will process comments on the survey (def ready before February 19).

## 18.12.2024

- The project still needs short API examples (in contrast to the "example notebooks"). A start would be to create a list of examples. #TODO create an issue.
- Miro will create an issue about some additional work that can be added from another paper and potentially a paper in progress.
- During the next meeting we will brainstorm some new "good first issues", as many were claimed by the last sprint by new contributors.
- Additional work to break down the big "learning objectives" is necessary to make them easier for contributors.
- Upcoming sprint in Berlin on the 18th of February.