Published on August 13, 2014
I'm happy to tell you all that as of today I'll be taking over the ongoing development of the Laravel.IO platform. Except for the Laravel.IO's podcast, which will still remain in Shawn McCool's hands, I'll be managing all of the rest of Laravel IO's activities. The reason for the change is that it has been proven difficult for Shawn and the rest of the Laravel.IO core team (which consists of Nick Spelt and Mitchell van Wijngaarden) to continue the development with the limited time they've got on their hands. I'd like to take this opportunity to thank all three of them for all of the work they've done so far for Laravel.IO and the Laravel community at large. The Laravel.IO platform has undergone some big changes in the past year and it's all thanks to their hard working effort.
Now that the transfer is official it's time to take a look at the future for Laravel.IO. The way I see it is that Laravel.IO is currently a place where all of the Laravel community comes together. Whether it is to discuss or ask a question in the forums, listen to the podcast or share their code using the pastebin, Laravel.IO is a place where you can rely on great Laravel content. I feel strongly about continuing down this path and expanding Laravel.IO into a platform where you'd always go if you want to find something Laravel related. I have a vision for Laravel.IO where it's the homepage for Laravel developers, from which they start their search for packages, resources, educational material, help or other great content about Laravel. In the next couple of months I'm going to dedicate all of my work I put in open-source in my free time to making that vision a reality.
Something else people might have been wondering about is what the hell happened to Laravel Weekly. Truth be told, at some point I lost interest in the current format because a lot of work existed in manually putting the newsletter together which is an extremely repetitive process. In the past few months I've been looking at overhauling the newsletter to create a separate platform where the content would be automated and newsletters would be put together by aggregating from different sources. A few weeks ago I started working on the platform but needless to say because of the current events with Laravel.IO I've stopped working on that platform for now. But this isn't the end for Laravel Weekly. I plan on making Laravel Weekly an integral part of the Laravel.IO platform in a later stage. But for now, Laravel Weekly is on hold.
The road ahead and the future for Laravel.IO is bright. I'm planning on getting the development of Laravel.IO started actively again. I want Laravel.IO to be an example of a platform which empowers all of Laravel's best practices ranging from Eloquent to Homestead and Forge. I want Laravel.IO to be an open-source project people can go to, contribute to and learn from. The source code for Laravel.IO is and will always remain open-source under the MIT license. Currently I see the platform being at 2.0. I've pushed a release/3.0 branch to the Laravel.IO Github repository where I'll be working on the next version. Feel free to check it out. I'll try to post a new blog post after Laracon EU is over to provide more details with the new roadmap for Laravel.IO.
Again, thanks to Shawn McCool for believing in me. I know maintaining an open-source project of this scale is time consuming and takes a lot of effort but I promise to the community that I'll put my heart and soul into this. It'll take quite some dedication but I hope to make the vision I have for Laravel.IO a reality soon.
Come talk to me at Laracon EU if you want to know more about the future for Laravel.IO or find me on IRC in #laravel or #laravel-offtopic when I'm around :-)
Thanks for reading and code happy!