You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to be transparent on how we do things. We lack a lot on this. We should be posting blog posts that range from planned releases, release schedule updates, new release migration guides and other things. This is one way we can communicate with the broader community, help onboard new maintainers and just being transparent on what we have been up to. We have started to cleaning that backlog of PRs but we have a long way to go. Cause as a contributor if no one gets to my PR for weeks or even months that is very discouraging. We do discuss some PRs in WG calls on why we are holding on but it takes a while we respond (and in some cases we just forget to respond) so I suggest we add publish blog monthly that we can draft in WG call and publish it the same week in which we will just outline our goals until next meeting.
The text was updated successfully, but these errors were encountered:
We need to be transparent on how we do things. We lack a lot on this. We should be posting blog posts that range from planned releases, release schedule updates, new release migration guides and other things. This is one way we can communicate with the broader community, help onboard new maintainers and just being transparent on what we have been up to. We have started to cleaning that backlog of PRs but we have a long way to go. Cause as a contributor if no one gets to my PR for weeks or even months that is very discouraging. We do discuss some PRs in WG calls on why we are holding on but it takes a while we respond (and in some cases we just forget to respond) so I suggest we add publish blog monthly that we can draft in WG call and publish it the same week in which we will just outline our goals until next meeting.
The text was updated successfully, but these errors were encountered: