#Avocode tutorial full version
#Avocode tutorial update

We set these up via their Community Bridge project (now the LXF Crowdfunding platform), and have had a steady trickle coming in ever since. With our acceptance to the Linux Foundation, we were also finally able to start receiving donations. We were formally accepted as a Linux Foundation project on March 24, 2020! From there, we made some revisions to the original draft charter the LF had provided us, voted to ratify it, and returned it for acceptance to the LF. In February, I asked the members of our legacy community review board to either step back or commit to being members of the Technical Steering Committee under the Linux Foundation we also extended invitations to several new people who had provided help during our migration. There was also one lingering, but important, item left in our migration to complete: ratification of our charter with the Linux Foundation.

#Avocode tutorial full version

You can watch the full version for free, below. I recently recorded a webinar that covered the material in this blog and more.

#Avocode tutorial update

Surprisingly, we've had very little reason to update it since, other than occasional tweaks to message formatting and frequency. I did this work in January 2020, and got the bot launched under our v domain. Geert Eltink, one of our contributors, had done some similar work using Expressive and Swoole, and gave me access to his work so I could write the bot in PHP. One problem: it was written in Node.js, and was fairly difficult to maintain, in large part due to running on outdated dependencies. Since many of our processes had changed, and, more importantly, the repository locations, we needed to update the bot. Under Zend Framework, we'd had a bot that would build documentation for us, create GitHub releases from tags, and perform some Slack integrations. We also had lost some tooling along the way. Users pinned to 2.2.1, on an update, would receive 2.2.1p2, correcting any issues that the original rewrite had missed. As an example, laminas-diactoros 2.2.1 had issues, and we released 2.2.1p1 and 2.2.1p2 to correct them. In each of these, we decided to create 'patch releases' of the historical release that fixed the edge cases, and then marked the package as a replacement for the earlier tag. The first several weeks were spent ironing out issues users had when migrating surprisingly, we had very few of these! The majority were a handful of components where early releases had a largely different source tree than later releases, which in turn led to edge cases that we had not handled. No migration the size of this one will be 100% successful. The Technical Steering Committee and Discussions.In this blog, I look back at some of these milestones, including the ratification of the Linux foundation charter, the formation of the technical steering committee, an important inflection point for the Laminas project, and more. Since then, the project has grown incrementally, achieving some substantial milestones along the way. Last year, on New Years Eve 2019, we successfully migrated the codebase of Zend Framework to the Laminas Project.