mirror of
https://github.com/typeorm/typeorm.git
synced 2025-12-08 21:26:23 +00:00
chore(docs): add announcement (#11125)
* chore: add announcement file * chore: add link from home page to announcement * fix: link to announcement in readme * chore: remove todo * chore: add Tauri links
This commit is contained in:
parent
e7649d2746
commit
db508424c8
@ -36,6 +36,13 @@ maintainable applications in the most productive way.
|
||||
TypeORM is highly influenced by other ORMs, such as [Hibernate](http://hibernate.org/orm/),
|
||||
[Doctrine](http://www.doctrine-project.org/) and [Entity Framework](https://www.asp.net/entity-framework).
|
||||
|
||||
> **📣 Announcement: The Future of TypeORM**
|
||||
>
|
||||
> We’re excited to share our vision for a revitalized TypeORM—a strategy focused on building a stable, robust, and sustainable foundation for the long term. Learn how we’re structuring maintenance
|
||||
> and bringing together dedicated resources to ensure TypeORM thrives for years to come.
|
||||
>
|
||||
> [Read the full announcement](./docs/future-of-typeorm.md)
|
||||
|
||||
## Features
|
||||
|
||||
- Supports both [DataMapper](./docs/active-record-data-mapper.md#what-is-the-data-mapper-pattern) and [ActiveRecord](./docs/active-record-data-mapper.md#what-is-the-active-record-pattern) (your choice).
|
||||
|
||||
50
docs/future-of-typeorm.md
Normal file
50
docs/future-of-typeorm.md
Normal file
@ -0,0 +1,50 @@
|
||||
# The Future of TypeORM
|
||||
|
||||
> By [David Hoeck (@dlhck)](https://github.com/dlhck) and [Michael Bromley (@michaelbromley)](https://github.com/michaelbromley)
|
||||
|
||||
|
||||
TypeORM is one of the most high-performance, feature-rich, and battle-tested ORMs in the Node.js ecosystem, relied upon by hundreds of thousands of projects and companies worldwide. With nearly 2 million downloads each week, it powers countless applications as a critical dependency. However, over the past few years, maintenance has slowed significantly, leading to growing uncertainty about the project’s future among its dedicated community.
|
||||
|
||||
We’re thrilled to announce that Michael Bromley and David Hoeck, under the umbrella of our parent company [Elevantiq](https://elevantiq.com/), are
|
||||
stepping up to lead TypeORM into its next chapter. At Elevantiq, where we
|
||||
specialize in enterprise digital commerce solutions, TypeORM is a critical dependency—not
|
||||
only for [Vendure](https://vendure.io/), our flagship open-source project, but also for many of our other solutions.
|
||||
With our reliance on TypeORM and the growing needs of its vibrant community, we saw an
|
||||
opportunity to contribute back and ensure the project remains active, maintained, and secure.
|
||||
|
||||
After discussions with TypeORM’s original maintainers, Umed and Dmitry, we’ve reached an agreement to take on the project’s maintenance, inspired by successful, community-centric open-source projects. One standout model is [the Tauri project](https://github.com/tauri-apps/tauri), a self-governing open-source initiative co-founded by [Daniel](https://github.com/denjell-crabnebula), who we already collaborate with through Michael and Vendure. Our discussions with Tauri have set the foundation for the organizational structure we envision.
|
||||
|
||||
## Our Vision for TypeORM’s Future
|
||||
|
||||
To ensure long-term stability and governance, we plan to establish a non-profit
|
||||
foundation for TypeORM, likely under the [Commons Conservancy](https://commonsconservancy.org/) in the Netherlands.
|
||||
This foundation will be led by a board of seven members: Michael and David,
|
||||
along with five additional board members dedicated to the project’s success.
|
||||
The board will work closely with a **Working Group** comprising companies, contributors,
|
||||
and other community members who heavily rely on TypeORM. This collaborative setup will help guide
|
||||
strategic decisions that align with the needs and goals of TypeORM’s ecosystem.
|
||||
|
||||
## Organizational Structure
|
||||
|
||||
To drive TypeORM forward, we’ll introduce three core domains:
|
||||
|
||||
- **Development**: Led by core developers with expertise across various database engines and adapters, this team will focus on TypeORM’s architecture and ongoing technical maintenance and advancements.
|
||||
- **Operations**: Handling day-to-day needs, from documentation to sponsorship accounting, this team will keep the project running smoothly.
|
||||
- **Community**: Dedicated to engaging, moderating, and supporting our growing community, this team will foster collaboration through platforms like Discord.
|
||||
|
||||
## Scaling Sponsorships and Full-Time Development
|
||||
|
||||
A significant part of our strategy is to increase sponsorships, reaching out to
|
||||
companies and collaborating with organizations like [OSS Pledge](https://opensourcepledge.com/). Our goal is to fund and
|
||||
employ two full-time developers who will lead the Development team, ensuring ongoing progress
|
||||
and project maintenance.
|
||||
|
||||
We’re confident that, with this structure, we can build a sustainable future for TypeORM. But the
|
||||
_success of this vision depends on the support of the community_.
|
||||
We’ll also remain in close contact with [Umed](https://github.com/pleerock) to keep his insights and vision connected to the project’s evolution.
|
||||
|
||||
## Join Us in Supporting TypeORM
|
||||
|
||||
If your company is interested in starting or expanding its sponsorship with TypeORM, we encourage you to reach out to us directly [via e-mail](mailto:typeorm@elevantiq.com).
|
||||
|
||||
Thank you for your support, and we’re excited to embark on this journey with the TypeORM community!
|
||||
Loading…
x
Reference in New Issue
Block a user