Q: The annual global contribution event is coming up again Saturday, January 25th. If there is still no response, wait a few more weeks then you can contact a admin and they can add you as a maintainer. These can be found on user profile pages. After a week or so, if you don’t get a response, try contacting the current maintainer(s) through their contact forms. Once the issue is created, the current maintainer(s) will view and reply to the issue.ĭepending on the availability of the current maintainer(s), they may not have seen or replied to your issue. Include why you are interested in contributing and what makes you qualified to be a maintainer. When creating the issue, indicate that you are interested in becoming a maintainer. When you’re ready, you can apply to be a maintainer by creating an issue on. Q: What do you want to tell people interested in becoming a maintainer?Ī: I highly recommend that you are active in the issue queues before considering applying to become a maintainer, as experience is key. If I contribute while on work time, I am also issued ‘credits’ that work towards Echidna's ranking within the Drupal services listing on. By contributing these maintained modules, the return for me is that I am building my credibility within the Drupal global community. I also do some stuff on my own personal time, when and if I feel like it. Basically, I contribute time at work through dedicated hours that Digital Echidna knows about, and credit these as such in our time tracking system. Q: How do you split your time between client and volunteer contributed Drupal work?Ī: As you can see, it is with a bit of self-interest that I volunteered maintaining these modules helps me complete my paid client work, even if I spend time at work (or personal time) to maintain them. Since these modules were being used consistently on my projects, I offered to become a maintainer of them to ensure they were up-to-date with Drupal standards, security updates, bug fixes and feature requests. These contributed modules hadn’t received a stable release in a few years but some had received updates to the development version of the module. All current and new projects using the module can use the latest version after downloading it or updating their project with Composer - including all the patches since the previous version was released.Ī: Throughout my work projects, I noticed that I was always using a few contributed modules that had a handful of patches that came along with them.
DRUPAL HOSTING JORDAN FULL
Eventually, the module has gone through so many changes that it needs a full reboot to put all those pieces together - we call this rebooted version a “stable release”.Ī stable release is the latest version of a module it has undergone enough updates / fixes, that have been tested and committed by a maintainer to become the new official version of the module.
DRUPAL HOSTING JORDAN PATCH
Each patch should be applied as it’s released. Throughout its lifespan, a module requires patches for various reasons (functionality alterations, security updates, bug fixes, etc.). It helps if you understand a bit about modules. It can be anywhere from an hour a month to three hours a week.
DRUPAL HOSTING JORDAN CODE
I recently asked him a few questions about his experience.Ī: The time you spend on caring for a module depends on its popularity and if its base functionality is affected by other Drupal code releases. My colleague, Digital Echidna developer Jordan Thompson, is a volunteer module maintainer for the following Drupal modules: This is a volunteer that keeps a module updated and working as it was intended to work. While the most popular modules are consistently updated, less frequently used modules often fall through the cracks or are abandoned by their creators. If you are a developer and ever used a contributed module, for example, you’ve probably had to hunt through the issue queues to find and apply patches to get all of the functionality you need from it.Įnter the role of the module maintainer. Think of it like the cellphone you had 10 years ago - it’s gotten glitchy and outdated.Īs Drupal core evolves, so must its modules. Over time, if the module isn’t maintained it starts to show its age and loses its usefulness. When a module is first released to the Drupal community, it’s akin to a child getting a new toy - everyone’s excited and can’t wait to play with it. In the open-source community, we would be nowhere without the dedication of the numerous volunteers that maintain contributed modules and themes.
0 kommentar(er)
