Meeting URL: https://meet.jit.si/StableHaskellMeetBiWeekly
Previous meeting notes
-
ghc-pkg, Cabal, stack, and plugins
- Could we separate out the bits of cabal ghc needs to a separate package?
- In theory it could happen
- Need a cabal release.
- Don't know what is involved there.
- Cabal release is "slowly moving forward".
- Conclusion: fix this issue and hope we don't hit it again.
- Idea: Get more cross team involvement: Various parties invited to the Thursday Cabal sync
- Could we separate out the bits of cabal ghc needs to a separate package?
-
Gracefully handling package abandonment
- A member of the community reached out for us to discuss this.
- Botan bindings as an example:
- Community groups with multiple maintainers
- None
-
Extension lifecycle framework proposal #601
- Under renovation to serve as basis for Renovating GHC's extensions mechanism #628 and Articulate stability goals #625
- Pretty short: Experimental, Stable, Discouraged, Deprecated.
- Relates to Adam's classification proposal #635
-
Bulletin discussed previously
- Previously holding the token: Chris
-
GHC warning policy document as discussed previously
- Previously holding the token: Chris