This session is intended for developers and developers-in-training who want to begin or continue learning about Git. This session could also be applicable for managers or people in other roles who wish to know more about the vocabulary, concepts, and workflows that their development team is using.
Git is the industry standard for collaborating and tracking changes to code bases of all kinds, including websites.
It is a good general rule of thumb that if you have a project involving any original code, then that code should be tracked with Git. In terms of WordPress sites, this means that if you have a custom child theme or a custom plugin in use on your WordPress site, then Git is most likely going to be a best practice that you want to implement in your website's workflow.
In contrast, if you are using a third-party theme, all third-party plugins, and not adding any custom code to your site, then Git is most likely not applicable to your website's workflow.
In the session, we'll look at basic Git workflow operations like branching, adding, committing, pushing/pulling, and merging. We will also explore GitHub collaboration tools like pull requests, issues, and reviews.
If you want to participate in the collaboration part of the evening, make sure to have a GitHub account setup before the session. This will allow you to contribute to our working repository that we'll set up and work with.
Tell us what topics you are interested in for future meetups - https://forms.gle/GNF4nnXCjuLivEdj8
In the WordPress Plugin Directory, many great plugins exist but are no longer maintained by their original contributors. Developers abandon plugins for a myriad of reasons. They might get too busy with other projects, something better might come along and steal their thunder, or they might not be great marketers and they simply couldn't get the word out leading to a failure of adoption. Whatever the reason, plugins don't have to die a slow death in the graveyard of once-great ideas. If there's a plugin our there that you think you might be able to improve, it might be worth a shot to ask the original contributor to take it over, as I recently did with the Radio Station plugin, which helps radio stations create show pages, show playlists, posts related to shows, a master schedule, and widgets to announce upcoming shows, current show DJ/host, or current song playing. In this talk, I'll walk through how I identified the plugin I wanted to take over and the process for doing so. We'll also cover how we now maintain the plugin on git and what our process is to manage and improve the plugin.