Skip to content

Commit

Permalink
Feb 2025 newsletter blog and 2025 Plans blog (#314)
Browse files Browse the repository at this point in the history
  • Loading branch information
rfay authored Feb 8, 2025
1 parent 3d05056 commit 2064571
Show file tree
Hide file tree
Showing 4 changed files with 120 additions and 0 deletions.
Binary file added public/img/blog/2025/02/ddev-2025-plans.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
67 changes: 67 additions & 0 deletions src/content/blog/2025-plans.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,67 @@
---
title: "DDEV 2025 Plans"
pubDate: 2025-02-08
#modifiedDate: 2025-02-06
summary: DDEV 2025 Plans
author: Randy Fay
featureImage:
src: /img/blog/2025/02/ddev-2025-plans.png
alt: Futuristic view of DDEV 2025 plans
credit: "Ideogram.ai: DDEV 2025 Plans: A futuristic cityscape with towering skyscrapers, some of which have unique and innovative designs"
categories:
- Community
---

Every year we try to clarify goals early, and here we go for 2025! We'd love to have your thoughts and opinions! Some of the things we [planned in 2024](2024-plans.md) aren't quite done yet, but we're working and planning and responding to your needs.

At the DDEV Advisory Group's 2-hour [annual review/planning meeting on March 4, 2025](https://www.meetup.com/ddev-events/events/303197425/?eventOrigin=group_events_list), we'll talk about plans and priorities for 2025. You are invited!

We'd love to have your input as daily users as we work through these this month.

(I expect to edit this blog post several times as people express their opinions.)

## Community

- **Continue outstanding user support** even with growth of our user base. This remains a key priority from last year, but we still need to involve the entire community (meaning you!) in all the places.
- **Begin formal governance for the DDEV Foundation**. We've been talking about this in the Advisory Group for years, but this year I'll propose a 3-person board for the DDEV Foundation, where I retain operational control, but we have at least one other board member fully enabled on financial controls and payments. Future years can bring future refinements.

## Sustainability and Finance

- **Improve our Marketing CTA and information**: The [ddev.com "Support DDEV"](https://ddev.com/support-ddev/) page says lots of things, but the financial CTA gets lost there. We need to make it completely clear that for the project to be sustainable, the community will need to support the two developers who are working full-time on it, and make clear the many ways that this can be done.
- **Continue to develop contributors and maintainers**: As the project grows, we need more skilled contributors and maintainers. (The only difference between those is that maintainers typically have a higher level of direct access to project resources, but as a wide-open source project, almost all interested contributors can accomplish almost anything without enhanced privileges.) In the last two years, we've had [quite a lot of contributor trainings](/blog/category/training), and anecdotes indicate that people are using those recordings and blogs for training, but the actual attendance at them was not impressive. I'm thinking that this year these topics should probably be addressed with screenshare recordings and updated blogs instead of calendar-scheduled events. Given the financial struggles in our contributors' world, I doubt that we'll be able to add paid maintainers in 2025, I'm most interested right now in the reasonable goal of retaining and paying the two amazing maintainers we currently have.

## Features and Initiatives

### Funded and Work-In-Progress Initiatives

- The TYPO3 Association has agreed to fund the [integration of XHGui into DDEV](https://typo3.org/article/four-ideas-to-be-funded-in-quarter-1-2025) as part of their Community Budget Ideas. Part of this work has already been done in the [ddev/ddev-xhgui](https://github.com/ddev/ddev-xhgui) project, and it must be completed by March 31, 2025.
- [Top-level Node.js support](https://ddev.readthedocs.io/en/latest/users/extend/customization-extendibility/#using-nodejs-as-ddevs-primary-web-server) as planned in 2024 has been committed to HEAD. There will be a number of follow-up opportunities, including Caddy support, etc.
- [Web-based Add-on Registry](https://github.com/ddev/ddev/issues/6383) is a work-in-progress and is expected to land soon.

<a name="proposed-features"></a>
### Proposed Features and Initiatives

1. [Implement mDNS as an alternate name resolution technique](https://github.com/ddev/ddev/issues/6663) in addition to DNS and hosts file manipulation. Our traditional use of DNS and hosts-file manipulation have been successful, but mDNS might allow avoiding hosts-file manipulation, especially with non-ddev.site URLs and when internet DNS is not available. This has been submitted for funding to the TYPO3 Community [Q2 Community Budget Ideas](https://typo3.org/article/call-for-community-budget-ideas-q2-2025)
2. [Allow Add-ons to include other add-ons](https://github.com/ddev/ddev/issues/6912): Add-ons can already require other add-ons, but they should be able to automatically result in a download.
3. [Go-based Upsun Add-on like ddev-platformsh](https://github.com/ddev/ddev/issues/6533). (This would pioneer golang-based add-ons; Go is probably a much better language for complicated add-ons of this type.)
4. Rewrite ddev-platformsh Add-on in Go: Assuming success of the Upsun add-on, it would be great to backport that work to [ddev-platformsh](https://github.com/ddev/ddev-platformsh). It's even possible that the two add-ons could be combined into one and maintained in one place.
5. Develop a replacement for "Gitpod Classic", which has EOL in April, 2025. This may not need much more than improved GitHub Codespaces support, but we have loved Gitpod and hope to have something to replace it.
6. [Improve self-diagnose capability](https://github.com/ddev/ddev/issues/6461) . We currently have ddev debug test but it would be great to implement something that was readable and actionable for ordinary mortals.
7. [DDEV's Message-of-the-day and ddev.com should show current funding status and need](https://github.com/ddev/ddev/issues/6892). We now have an automatically updated JSON feed that can make this possible.
8. DDEV Windows/WSL2 packaging and installation: The traditional Windows installer needs work, and the WSL2 install scripts are written in hard-to-maintain PowerShell. This work can be consolidated and improved, including [improving the Windows hosts-file escalation technique](https://github.com/ddev/ddev/issues/6440).
9. [Rewrite `ddev launch` in Golang instead of as script](https://github.com/ddev/ddev/issues/6394).
10. [Rework configuration system using Viper](https://github.com/ddev/ddev/issues/5763).

In addition to prioritizing these initiatives, we have applied to the [Google Summer of Code](https://summerofcode.withgoogle.com/), hoping that we can mentor contributors in that program and see work on one or more of these be successful through GSoC. We'll also be looking for community mentors (is that you?), and maybe some of you would like to sign up for being mentees via Google this summer!

Do you see other important things in the [issue queue](https://github.com/ddev/ddev/issues) or elsewhere that are important to you? Are there frictions that impact your work that DDEV could fix? Please let us know.

We would dearly love to have your input on these as the planning process goes forward. You can respond so very many ways in all of the [support venues](https://ddev.readthedocs.io/en/stable/users/support/).

Want to keep up as the month goes along? Follow us on

- [blog](https://ddev.com/blog/)
- [LinkedIn](https://www.linkedin.com/company/ddev-foundation)
- [Mastodon](https://fosstodon.org/@ddev)
- [Bluesky](https://bsky.app/profile/ddev.bsky.social)
- and join our community on [Discord](/s/discord)
53 changes: 53 additions & 0 deletions src/content/blog/ddev-feb-2025-newsletter.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
---
title: "DDEV February 2025 Newsletter"
pubDate: 2025-02-10
#modifiedDate: 2025-02-06
summary: DDEV February 2025 Newsletter
author: Randy Fay
featureImage:
src: /img/blog/2025/02/nancy-lewis-winter-scene.jpg
alt: Nancy Lewis winter scene painting
credit: "Plateau Creek Mile Marker 55, by Nancy Lewis"
categories:
- Community
---

**Happy February!**

**DDEV v1.24.2** was [released](https://github.com/ddev/ddev/releases/tag/v1.24.2) with [MySQL 8.4 support](https://ddev.com/blog/database-improvements) and improved `ddev composer create` making it nearly compatible with `composer create-project`.

**DDEV Notes and News**

- The [DDEV Advisory Group](https://github.com/orgs/ddev/discussions/6853) met January 8. The primary topic of discussion was the [change in DDEV's funding](https://ddev.com/blog/platform-sh-ddev-funding-changes) and budgeting response to it. Our decision was to continue the arrangement with Stas as-is (bill hours at $50/hour, cap $4000/month). Randy will also bill at $50/hour with cap of $4000, but limited by always trying to leave $6000 in the bank.
- **We need your input!** Please take a look at the proposed [2025 Plans for DDEV](2025-plans.md) and let us know your opinion, how these things should be ordered, and what we might have missed!
- macOS users will be interested in the (not-DDEV-focused) [Docker Performance macOS 2025](https://www.paolomainardi.com/posts/docker-performance-macos-2025/).
- [The Open Source Pledge and DDEV: A Path to Sustainability](https://ddev.com/blog/open-source-pledge).
- [MySQL 8.4 is now in DDEV v1.24.2](https://ddev.com/blog/database-improvements/).
- DDEV v1.24.2 has improved argument handling for `ddev composer create`, making it nearly compatible with `composer create-project`. Additionally, the `ddev composer create-project` alias has been added for improved usability.
- The Gitpod that we have known and loved is shutting down. This affects DDEV contributors that have used it and makes [DrupalPod as it stands obsolete](https://www.drupal.org/project/drupalpod/issues/3500792). If you're interested in DrupalPod and will be at DrupalCon Atlanta, there is a Birds-of-a-Feather session scheduled on the path forward, 04:00pm - 04:30pm Tuesday, March 25, 2025.
- The Drop Times did a nice and extensive [interview with Randy](https://www.thedroptimes.com/interview/45389/making-ddev-past-present-and-future-in-focus) and [video interview](https://www.youtube.com/watch?v=EctDtSZcBhU).
- Tag1 Consulting did a performance comparison of the new Drupal CMS vs WordPress, (using DDEV for everything). See [Drupal CMS vs WordPress Performance](https://www.tag1consulting.com/blog/drupal-cms-vs-wordpress-performance-2025).
- The latest DDEV Quickstarts in the docs are for [Drupal CMS](https://ddev.readthedocs.io/en/stable/users/quickstart/#drupal-drupal-cms) and [ProcessWire](https://ddev.readthedocs.io/en/latest/users/quickstart/#processwire)! Congratulations to the Drupal community on Drupal CMS, and welcome ProcessWire folks. Thanks to [Bernhard Baumrock](https://github.com/BernhardBaumrock) for the ProcessWire initiative!
- [DDEV: We use it on all our projects](https://www.youtube.com/watch?v=WkOoPEbtHwI). (Followups in [Reddit r/php](https://www.reddit.com/r/PHP/comments/1ijsev2/ddev_we_use_it_on_all_our_projects/) and [Reddit r/drupal](https://www.reddit.com/r/drupal/comments/1ijsemd/ddev_we_use_it_on_all_our_projects/)).

**Ongoing DDEV Work**

- **Node.js** improved support: People have asked for some time for Node.js to be the primary web server (instead of Nginx+php-fpm, etc), and now it can be done in a number of ways. This is now in [DDEV HEAD](https://ddev.readthedocs.io/en/stable/developers/building-contributing/#testing-latest-commits-on-head) and there are Quickstarts for [Simple Node.js](https://ddev.readthedocs.io/en/latest/users/quickstart/#nodejs-nodejs-web-server) and [SvelteKit](https://ddev.readthedocs.io/en/latest/users/quickstart/#nodejs-sveltekit). Incidentally, this also provides experimental support for [FrankenPHP](https://frankenphp.dev/) and provides a [Quickstart](https://ddev.readthedocs.io/en/latest/users/quickstart/#generic-frankenphp) for it as a demonstration of the "generic" web server type.
- **Web-based Add-on Registry**: As add-ons have become so very popular it's hard to sort them out and understand which ones are meaningful for a particular need. This long-term goal is nearing completion as Stas has a proof of concept and now has to push it through to a maintained production status.
- **Automated Tests for Quickstarts**: You won't see these, but it's a big step for us. Because our [Quickstarts](https://ddev.readthedocs.io/en/stable/users/quickstart/) are so dependent on the behavior of the upstream projects, it's always been hard for us to know when the target project has had a change that invalidates them. Now we have automated tests for the quickstarts of number of project types, and will add others as maintenance is done. Thanks to [Ralf Koller](https://github.com/rpkoller) for extensive work on the Drupal, WordPress, and TYPO3 quickstarts.
- **Funding situation data feed**: Aiming for ever-increasing transparency in the DDEV funding situation, we now have an automatically-updated feed showing our [funding situation from all sources](https://github.com/ddev/sponsorship-data). You can see the [exact situation](https://github.com/ddev/sponsorship-data/blob/main/data/all-sponsorships.json) at any time. We expect to use this feed in the message-of-the-day on DDEV, as well as ddev.com and the DDEV README.
- **New contributors and maintainers**: As DDEV's community grows, we always need new contributors and maintainers. We love to get contributors trained and get privileges to maintainers as needed! We already have lots of [Contributor Training](https://ddev.com/blog/category/training/) material, and [docs on how to contribute](https://ddev.readthedocs.io/en/stable/developers/) but we'll do anything you ask for! Need help with something? Need updates? Join us in [Discord](/s/discord) or [make an appointment with me](https://cal.com/randyfay/30min).

**Funding DDEV and especially to help both maintainers go full-time on DDEV**: _We need your help and your organization's help! Let me know if you need help getting this into your 2025 budget!_ Our key financial goal is to [fully fund @stasadev so he can work exclusively on DDEV](lets-fund-stas-maintainer.md). We've slipped back in recent months. We need about $3700/month in increased pledges from organizations and individuals. See [Full information about supporting DDEV](https://github.com/sponsors/ddev). We’re happy to invoice you, happy to [do a call discussing this](https://cal.com/randyfay/30min), and would love it if you’d include DDEV in your 2025 budgeting process. (Our current status: We receive about $3000/month, have been spending about $3000-$4000/month. Bank balance is about $6,000, down from $8,600 last month.)

**THANKS to all of you who are supporting DDEV’s path to sustainability** and who have gotten your organizations to do so.

Want to keep up as the month goes along? Follow on

- [blog](https://ddev.com/blog/)
- [LinkedIn](https://www.linkedin.com/company/ddev-foundation)
- [Mastodon](https://fosstodon.org/@ddev)
- [Bluesky](https://bsky.app/profile/ddev.bsky.social)
- and join our community on [Discord](/s/discord)

Happy February from Randy Fay, DDEV Project Lead. It's a delight to collaborate with you!

0 comments on commit 2064571

Please sign in to comment.