Repository going to be moved to go-goyave organization #129
Replies: 3 comments
-
The framework's website has moved to https://goyave.dev. The website's sources are now located here. The previous location (https://system-glitch.github.io/goyave/) will be removed when v3.7.0 releases. I added a notice there to inform all visitors. |
Beta Was this translation helpful? Give feedback.
-
I am currently working on the migration. I took down https://system-glitch.github.io/goyave/, please use https://goyave.dev from now on. |
Beta Was this translation helpful? Give feedback.
-
Migration done! 🎉 |
Beta Was this translation helpful? Give feedback.
-
Goyave has been updated regularly for over a year, and it slowly getting more attention. My efforts to promote the framework have been rather low because I didn't want the project to attract too many people so early in the life of the framework, letting me flesh it out using the few time I could allocate to it. I'm a ready to announce that it's time to take Goyave to the next step.
Starting soon, I will be able to allocate more time and resources to the development of the framework, its ecosystem and workflow, and towards its adoption. To reach these goals, the first step would be to create a new organization called "go-goyave", which will concentrate all first-party libraries and tools for the framework. All past and future contributors will be invited to join this organization. Migrating to an organization is a step towards a more open and community-centric development, as the framework will no longer be branded under my sole name.
However, this migration comes with a few caveats that I would like to address:
go get -u
will not upgrade the framework to the latest version. As said above, a manual step will be required.I apologize for the inconvenience, but I think this decision is important for a sane growth of the community and the framework. I will keep communicating on this matter as I go, so stay tuned if you are affected. You can join the framework's Discord server to get notified of future announcements, and/or click on "Watch" in the top right corner of the screen.
I also plan on working on more articles and examples to help newcomers getting started. For example, I am planning to write a guide on how to implement the repository pattern with Goyave.
Before I go, I am happy to announce that @ulphidius is going to join us as a contributor, working on a project that I wanted to start long ago: the
gyv
CLI utility.Beta Was this translation helpful? Give feedback.
All reactions