DDEV
2026 Planning Brainstorming meeting 2025-12-04 #7923
Replies: 5 comments 3 replies
-
@ultimike @jenlampton @bmack @deviantintegral @rfay Randy and I use https://clockify.me/ for time tracking. I use the following categories:
But I didn't know if it was possible to see the actual percentage - I found it here: Clockify > Reports > Summary > Group by "Project, Group, Task" > Export as PDF Spoiler, where I have these categories:
My 2025:
My 2024:
My 2023:
|
Beta Was this translation helpful? Give feedback.
-
|
@stasadev This is great stuff! @rfay Do you use the same categories? -mike |
Beta Was this translation helpful? Give feedback.
-
|
Wow, Stas is doing way better than I am. I don't use categories at all, but try to give decent descriptions. But I don't start new sessions for context switches. |
Beta Was this translation helpful? Give feedback.
-
|
Regardless, I think there's some value in Stas' numbers. How best to use this data, is the question... |
Beta Was this translation helpful? Give feedback.
-
|
@stasadev Here's a set of "projects" I'm proposing for myself:
|
Beta Was this translation helpful? Give feedback.
-
|
Sounds good to me. Which category is responsible for weekly dev meetings, advisory group, and contributor trainings? |
Beta Was this translation helpful? Give feedback.
-
Maybe we need a "meetings" category. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We had a brainstorming meeting prior to creating 2026 plans (and 2025 review) in early January, 2026. Present were board members Mike Anello, Benni Mack, Andrew Berry, and Randy Fay, along with DDEV maintainer Stas Zhuk and community member Ralf Koller.
Recording: https://youtu.be/i-XuWnwQARg
Resources:
AI-generated Meeting Notes
Quick recap
The team discussed recent power outages and reviewed two blog posts ready for publication, including one about board updates and another about changes in support. They planned their January blog content, including an annual review post with analytics trends, and explored strategic initiatives for 2026 such as moving testing environments and addressing command issues. The conversation ended with discussions about time tracking methods, potential new markets for DDEV adoption, and plans for drafting objectives for the upcoming year including fundraising efforts.
TODOs
Summary
Board Meeting and Blog Updates
Randy, Michael, Andrew, and Benni joined the call, and Randy introduced the purpose of the meeting as a brainstorming and board meeting to discuss plans and thoughts. They briefly touched on two blog posts that have been reviewed and are ready to be published, discussing the order in which they should be released. The posts are about the board and Articles of Incorporation update, and the change in support from Upsun.
January Blog Post Planning Discussion
The team discussed blog post planning for January, with Randy confirming their annual end-of-year review post tradition and Michael suggesting an additional December review post, though Randy noted December is typically a slow month for projects. Andrew suggested including a graph showing Amplitude analytics trends in the January post, which Randy agreed was a good idea but needed to locate the graph data. They decided to publish the board post first, followed by the review post, and Randy added "Blog post idea: Surprising things learned through DDEV analytics" to their to-do list.
Strategic Initiatives for 2026
Randy presented several strategic initiatives for 2026, including moving testing out of his home environment and addressing issues with concurrent DDEV commands in multiple terminal windows. The team discussed the need to move WSL2 testing to GitHub Actions and the importance of supporting their JetBrains plugin maintainer. Randy also mentioned considering a freemium model for new features, similar to other open source projects, though this was marked as a future consideration rather than an immediate action item.
Strategic Planning and Task Prioritization
The team discussed their approach to strategic planning, with Randy explaining that the current list of items was derived from their 2025 blog and had become a mix of desired tasks for the year. They agreed that some items, like the config rework, were unlikely to be completed due to the high effort required compared to the perceived value. Michael raised questions about the level of effort for different tasks and the percentage of time spent on reactive versus proactive issues, to which Randy responded that DDEV spends a significant amount of time being reactive and addressing community friction.
Task Categorization for Time Tracking
The team discussed tracking time spent on different types of work, with Randy confirming they log hours but don't currently categorize them by task type. Michael suggested implementing a simple taxonomy for categorizing tasks in time sheets, with Andrew proposing a trial period to evaluate the effectiveness before committing to long-term tracking. They agreed to consider this carefully, acknowledging the importance of maintaining DDEV's strong support reputation while gathering data for planning purposes. Andrew also raised the idea of creating a structured process for promoting premium features, potentially including a sponsorship model for organizations contributing to DDEV's development.
DDEV Adoption Strategy Discussion
The team discussed strategies for expanding DDEV's adoption and influence in the development community. They explored the possibility of targeting new CMS or frameworks, with Andrew suggesting a goal of having DDEV adopted as the primary local development platform by one more framework. Randy mentioned DDEV's current adoption by Craft CMS and Type 3, while noting that Laravel might be a better target than WordPress due to its more cohesive community. The group also considered the potential of integrating AI tools securely within DDEV containers, though they acknowledged the challenges of implementing such features. Michael emphasized the importance of reaching out to language communities rather than project communities to find new markets for DDEV. The conversation ended with Randy announcing plans to draft a list of objectives for the upcoming year, including fundraising efforts, and to share this with the board for review before their next meeting in January.
Beta Was this translation helpful? Give feedback.
All reactions