-
Notifications
You must be signed in to change notification settings - Fork 87
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #320 from grails/grails-future
grails future
- Loading branch information
Showing
1 changed file
with
57 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
--- | ||
title: Grails Future Planning | ||
date: June 7, 2024 | ||
description: Grails Community Steering Committee is working on plans for the future of Grails. | ||
author: Jeff Brown | ||
image: grails-blog-index-5.png | ||
--- | ||
|
||
# [%title] | ||
|
||
[%author] | ||
|
||
[%date] | ||
|
||
**[%description]** | ||
|
||
The Grails Foundation would like to follow up on the | ||
[Open Letter To Our | ||
Community](https://objectcomputing.com/resources/news/2024/05/10/open-letter-our-open-source-communities) that was recently published by Object Computing, Inc. (OCI). | ||
We have assembled a Grails Community Steering Committee with the goal of | ||
helping define the path forward for the Grails framework. One of the first | ||
priorities of the group is to define the scope for a meaningful and valuable | ||
Grails 7, which can be created and supported responsibly. Achieving that will | ||
require contributions from a combination of passionate community members and | ||
organizations who care about being involved in the future of the technology. | ||
|
||
Our experience has shown that increased transparency regarding challenges and | ||
opportunities is crucial for the Framework's continued development. We're | ||
committed to improving communication in this area. | ||
|
||
The Grails Steering Committee’s current focus is on three key goals: | ||
|
||
1. Defining an MVP (Minimum Viable Product) for Grails 7. | ||
2. Outlining Community Contribution Opportunities: We'll clearly define how individuals and organizations can contribute to the MVP's development. | ||
3. Highlighting Contribution Methods: We recognize that contributions come in various forms. Some organizations may prefer dedicating engineering resources, while others might choose to provide financial support for a core development team. | ||
|
||
Previously, these contribution avenues have existed but lacked clear | ||
communication. We're committed to making them more visible and accessible. | ||
|
||
The work we are doing right now will enable our community to have a greater | ||
impact on the future of the Grails framework. The feedback we get in the coming | ||
weeks will be enlightening. We must understand what is important from the | ||
community’s perspective, and for us to envision the possible paths to accomplish | ||
desired outcomes. OCI is committed to stewarding the framework forward including | ||
helping the technology and the community find a public place for the community to | ||
rally around the technology. | ||
|
||
Creating and maintaining these free and open solutions is a significant commitment | ||
and it will take a positively energized community to help us carry things forward. | ||
Every single message we have received and every single conversation we have been | ||
involved in in recent weeks has been helpful, appreciated, and respectful. This | ||
community is remarkable and your input is sincerely appreciated. | ||
|
||
We will continue to communicate more information here in the coming weeks. Always | ||
feel welcome to reach out to us at [info@grails.org](mailto:info@grails.org) if you have any questions, | ||
concerns, or would like to engage in ways that you are currently not. Together | ||
we are all defining the way forward and your help is appreciated. |