22 June 2023

[patrick91]

---

tags: strawberry community call

Strawberry meeting

Date: 22 June 2023

Discord: https://strawberry.rocks/discord

Please note:

• Everyone present is held to the Strawberry Code of Conduct

Welcome!

If you are joining the Strawberry Community Call, (optionally) sign in below so we know who was here.

Name	GitHub Handle	Discord Handle
Patrick Arminio	@patrick91	@patrick91
Jeremy Berman	@jerber	@jerber_

Agenda Items

Old PRs

I've started working on closing old PRs, once I'm done with that I'll also
start working on issues, also making sure they have enough context for people
to contribute (either with PRs or comments).

New site

I worked on the new site, it's here: https://beta.strawberry.rocks/

The plan is to release it with version 1.0 (or just before it), so if you
find any issues on it just let me know 😊

We'll also update the playground to reflect the new design.

Version 1

It's time to release V1! We've been holding of it for quite a while now,
but there's no reason to hold it any more. Having v1.0 will help with
adoption since people will know the library is stable.

We've been doing great work to make sure updating the library isn't painful,
v1.0 should help with that, as we have more version numbers to make the releases
more semantic.

We should still keep making releases with deprecations when possible though 😊

Issues that should be solved before merging:

1. refactor: Permissions using Field Extensions #2570
2. Implement unions as annotated types #2840

And ideally implement codemods for 2. (in future we can also add them as a pre-commit hook)

Governance

It's probably time to think about a governance model. At the moment I'm the main
person that merges PR, I'm ok with that, but also I want to make sure every core
dev is empowered to do so when necessary 😊

I'd propose we start culling core devs, removing people that are not active anymore,
but also people that are not interested in being core devs. We'll keep a list of
former core devs on the site, so their work will still be recognised 😊

We can also make the core dev role an annual thing, every year core devs will be asked if
they want to keep being a core dev. Reducing the number of core devs to just the active
ones helps with security and it also fairer to people I think 😊

We also need to work on a governance model to make sure we have a good process for
handling decisions. Here's a resource, but we'll need to discuss this more:
https://github.com/github/MVG

Strawberry Django

Thiago has been doing a lot of awesome work with Strawberry Django and Strawberry Django plus,
he's currently working on refactoring Strawberry Django and merging Strawberry Django plus in
it, so people don't need to install multiple libraries.

We should also make sure docs are visible on the main website

Misc

We found Polars today, it might be useful for getting some funding for
specific issues -> https://polar.sh/dashboard/strawberry-graphql

It also has a nice dashboard we can use to prioritize work 😊