15 February 2022

[patrick91]

Strawberry meeting

Date: February 15th, 2021, at 16:30 UTC+1 (your timezone)

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
Ester	@estyxx	@Etty
Bryce	@BryceBeagle	@ignormies
Mike Ossareh	@ossareh	@ossareh
James Chua	@thejaminator	@jamesc

Agenda Items

1. Discord roles
2. Monorepo
3. Maintainers
4. Documentation revamp
5. Deprecation policy
   A. Custom dataclass init PR -> We should finally merge this

Discord roles

We were planning of having custom roles for notifications (so we don't spam @everyone all the time), and for users that have been contributing a lot on discord.

Roles for notifications could be:

1. @meeting-watchers: this would be used to notify people when the meeting is about to happen
2. @releases: this would be used to notify people about new releases (message will be in a dedicated announcement channel)
3. @breaking-changes: this would be used to notify people about releases with breaking changes
4. More?

Roles for users would be:

1. @community-expert: this would be for people that answer a lot of questions on discord ^^

we can have public or private nomination.

^ All these roles can only be pinged by admin, in order to prevent spamming :)

Monorepo

Let's chat about whether having a monorepo or multiple repos makes sense for us.

To fill during the call:

Pros

• ...
• It's easier have everything in one repo when we updates the stuff and mantain consistency between integrations

Cons

• harder to merge the PR, takes more time to review

@patrickpy to add more notes
@patrickpy to publish the notes about the refactoring

#849

Pending Decision: we keep the monorepo for now @patrickpy to add reasons

Deprecation policy

It is time to declare a formal deprecation policy for Strawberry. We should make it easier to upgrade to latest releases and bring the number of breaking changes to a minimum.

Here's an example of a PR that includes breaking changes: Custom dataclass init PR.

We've postponed the merge of this PR for quite a while now due to not having a proper deprecation policy.

Some ideas:

1. Don't change behaviours without deprecating previous behaviour first
   A. The PR above doesn't do that unfortunately, but maybe we shouldn't hold it off (this would be an exception)
2. Give users enough time to fix deprecation
   A. How much time is enough?

Related: https://github.com/strawberry-graphql/strawberry/pull/1587/files

Decision: Let's go with 3 months for now, maybe after we release v1 we can discuss this again.
TODO: we need some reminders for this (using the current discord bot). @patrickpy
we could also create the PR for removing the warning and merge it later.

Maintainers

Patrick was chatting with Lauri about the django package and he said that he's quite busy in order to maintain it.
Patrick would love to take over but not sure how much bandwidth he'll have in the next few weeks.

Is anyone interested in helping out? We should definitely work on moving the package to core (pending the discussion above)

Also we have a few people like James and Matt that have been contributing a lot to Pydantic and other things, shall we recognise them as maintainers?

Decision: New maintainer role that can merge PRs for Pydantic
Codeowners (to check if it is paid).

Decision: talk with Thiago for the django integration and do a open maintainers call for django

Documentation revamp

Patrick: I was thinking of creating a new issue with a new structure for the documentation on GitHub, following the Diátaxis Framework. I think having a list of tutorials/guides to write would be nice so we can get contributors to write them too.

Shoutouts

Strawberry Playground now supports multiple versions of Strawberry. We'll be migrating this to play.strawberry.rocks soon

@Etty as the newest core dev