Hello everyone!

As described in the latest blog post [1], we are trying to create strike teams for our repos to streamline the work that needs to be done. We will start by creating these for our major repos (dmd, druntime, phobos) and if it works out, we can expand it to other areas (testing infrastructure, documentation, etc.).

The strike team will receive the major tasks from the leadership and will have to implement them. The components of a strike team need to contribute either with expertise or with actual code (ideally, both). To be effective from an organizational stand point, we will keep these teams small (5-10 people).

If you are contributing to any of the repos, but want to do it in a more organized matter, than you should seriously consider joining a strike team.

If you are not contributing, but have expertise on the repos, you should seriously consider joining a strike team.

To join any of the strike teams, please contact me via email (razvan.nitu1305@gmail.com) or on slack (razvan.nitu).

Cheers,
RazvanN

[1] https://dlang.org/blog/2021/05/18/a-pull-request-managers-perspective/

On Thursday, 20 May 2021 at 08:06:18 UTC, RazvanN wrote:

I think every effort to structure the community better in order to pool the available forces in a targeted manner is very good!

(But it should not be forgotten to make the goals for these efforts measurable in order to be able to evaluate the success of the strategy. The old saying applies: no path is the right one without a goal. => D Vision Document 2021?)

On Thursday, 20 May 2021 at 09:33:08 UTC, Martin Tschierschke wrote:

Yes, it is crucial that the leadership assures a constant stream of tasks. This includes: features to be implemented, PRs to be reviewed, issues to be fixed. We are discussing this as we speak.