www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - DLF Weekly Planning Session Update (May 19, 2023)

reply Mike Parker <aldacron gmail.com> writes:
The primary goal for this planning session was to establish 
priority high-level goals for the D project. It lasted a little 
under an hour. The following people attended:

* Walter Bright
* Ali Çehreli
* Dennis Korpel
* Átila Neves
* Razvan Nitu
* Mike Parker
* Robert Schadek



We discussed [the feedback from the gripes and wishes 
campaign](https://forum.dlang.org/post/tcdhptxnqvutveyrgmtc forum.dlang.org).
Walter said he really likes it and thinks it's going to be very helpful for us.
He plans to look for any low-hanging fruit in there that he can deal with
immediately.

In the interest of not overextending ourselves, we decided to 
limit ourselves to three active goals. These are:

* stabilize the language/compiler/standard library
* enhance the ecosystem (improving tools, support for third-party 
libraries, etc.)
* strengthen the community (removing cruft from the website, 
updating outdated docs and tutorials, website redesign, etc.)

We agreed that we should have one or two people in charge of each 
goal. Their responsibilities will be to:

* have the final say on which projects and tasks should be added 
to the goal's task list now
* prioritize the task list
* assign projects and tasks

We also decided that we'll revisit our three goals in six months 
to determine if we should shift focus from one or more of them, 
or if we can handle any additional goals.

Our homework for the next week is for each of us to put together 
a list of projects and tasks that align with our current goals. 
At our next meeting, we'll establish who's in charge of each goal 
and start building out the lists.


The gripes and wishes feedback is our primary source of project 
and task ideas, so those of you who participated have already 
contributed. We're going to set up projects on [our GitHub 
Projects page](https://github.com/orgs/dlang/projects) for each 
of the goals so that you can see our current focus.

Until then, I invite everyone who has an interest to peruse [the 
gripes and wishes 
feedback](https://github.com/dlang/vision-document/blob/main/gripes
wishes-feedback.md) and come up with your own lists of priority projects and
tasks. Email them to me (social dlang.org), post about them in the forums, or
DM them to me on Discord. We can use this additional feedback to help us
establish the initial task lists.


[The vision document](https://github.com/dlang/vision-document) 
was our well-intentioned but ultimately futile effort at a step 
toward project management. We got it written and published, but 
had no follow-through. Razvan and Dennis did employ it to help to 
some degree in their work, but ultimately our vision lacked 
vision.

Consider our current effort a reboot with an eye toward more 
focus and organization. The existing vision document is obsolete. 
I'm going to replace it with something inline with our what we're 
doing now. We can count that as a task under "strengthen the 
community".
May 19 2023
next sibling parent reply Ikey Doherty <ikey serpentos.com> writes:
On Saturday, 20 May 2023 at 06:39:53 UTC, Mike Parker wrote:
 In the interest of not overextending ourselves, we decided to 
 limit ourselves to three active goals. These are:

 * stabilize the language/compiler/standard library
 * enhance the ecosystem (improving tools, support for 
 third-party libraries, etc.)
 * strengthen the community (removing cruft from the website, 
 updating outdated docs and tutorials, website redesign, etc.)
This is fantastic news, thanks for the update! I wonder if in the redesign we could have these immediate goals front and center, visible to newcomers? Confident direction leads to confidence in the project.
May 20 2023
parent Mike Parker <aldacron gmail.com> writes:
On Saturday, 20 May 2023 at 08:00:44 UTC, Ikey Doherty wrote:

 This is fantastic news, thanks for the update! I wonder if in 
 the redesign we could have these immediate goals front and 
 center, visible to newcomers? Confident direction leads to 
 confidence in the project.
I don't expect that would be a problem.
May 20 2023
prev sibling parent reply matheus <matheus gmail.com> writes:
On Saturday, 20 May 2023 at 06:39:53 UTC, Mike Parker wrote:
 ...
Thanks for the feedback, but I'd like to know why some of these meetings couldn't be recorded and shared with community? I mean it's an open source project, you want to spread the usage for newcomers, you (I mean the organization) needs support, we are living in 21th century, It's pretty much free to share this as streaming and I think some of these meetings should be recorded and shared with the community. By the way I was taking a look over Dlang channel at yewtu.be (https://yewtu.be/channel/UC5DNdmeE-_lS6VhCVydkVvQ), and the latest video was from 2 weeks ago, and before that it was 2 months ago, so sharing this may engage more people to watch the channel too. Matheus.
May 20 2023
parent Mike Parker <aldacron gmail.com> writes:
On Saturday, 20 May 2023 at 13:44:35 UTC, matheus wrote:
 On Saturday, 20 May 2023 at 06:39:53 UTC, Mike Parker wrote:
 ...
Thanks for the feedback, but I'd like to know why some of these meetings couldn't be recorded and shared with community?
Sorry, but we aren't going to be sharing any recordings of these meetings. Not everyone is comfortable participating when they know everything will be public. And anyway, the value in these planning sessions is what they produce, not how we get there.
 By the way I was taking a look over Dlang channel at yewtu.be 
 (https://yewtu.be/channel/UC5DNdmeE-_lS6VhCVydkVvQ), and the 
 latest video was from 2 weeks ago, and before that it was 2 
 months ago, so sharing this may engage more people to watch the 
 channel too.
I fully intend to get to a place where I can regularly post new content. In fact, I'd be very happy if I could spend the majority of my D time creating content for our YouTube channel. It's useful and I enjoy doing it. I've got a lot of other stuff to chip away at first. My next immediate task is the Bugzilla to GitHub migration.
May 20 2023