“Adopt-Me” Plugin Tag Is Now in Use in the WordPress Plugin Directory

adopt-me-yellow

Recently we explored the question of whether or not a clear path for WordPress.org plugin adoption could help to lower the rate of abandonment. Some have suggested that having a standard (unofficial) adoption tag might help to bring more exposure to plugins that need a new owner.

“Adopt-Me” was suggested as one possible tag for developers to use to identify plugins that they would prefer to adopt out rather than abandon. WordPress developer Christian Foellmann is the first to make use of the tag. If you visit the “adopt-me” plugin tag page, you’ll find his Google Analytics MU plugin available for adoption.

Foellmann put his plugin up for adoption because he was no longer able to provide adequate support for it. “I really believe that you have to ‘choose your battles’ when it comes to open source contribution,” he said. “You need to make sure that you do not stretch yourself too thin. So I finally realized that I can only support a plugin (project) properly if I deploy it myself.”

“Free to a Good Home”

Foellmann has a rather unique reason for wanting to find the plugin a new home. “I run all my sites in multisite installations so the tracking of a complete network is something really appealing at first,” he said. “Until you realize the implications of EU and especially German privacy law. When it comes to user tracking the functionality of the plugin can get you into hot water – fast.” It’s for this reason that he’s decided to remove the plugin from his toolbox.

Already on the lookout for a best practice for plugin adoption, Foellmann saw our recent article and decided to be the first to use the “adopt-me” tag in hopes of keeping his plugin alive. He said that the ideal new owner would be a current user who is wiling to keep development open on Github. Foellmann will happily transfer over the Github repo.

Will the “Adopt-Me” tag take off?

The “adopt-me” tag will never catch on if nobody knows about it. Though the tag is technically unofficial, it will require developers to use it and recommend it, if there’s any possibility of it becoming a useful designation on WordPress.org.

When I discussed the matter of an unofficial tag with Samuel “Otto” Wood in a previous conversation, he had little hope of it gaining any traction. His thoughts:

I don’t think it will take off because it’s edge-casey and relies on authors giving away their plugins intentionally instead of simply letting them die from neglect.

His assessment would indicate that most developers who abandon their plugins are likely not motivated enough to put their extensions on the path to adoption, even if there is a known tag.

Foellmann has more hope for his Google Analytics MU plugin, which is actually a fork of a plugin that he originally tried to adopt. Since there was no process at the time and the plugin’s author was unreachable, he was forced to fork the original plugin.

This type of situation may be a contributing factor to the repository having so many plugins which seem to perform the same function. No path for adoption makes it easier to fork an existing work to make small changes or updates.

When I asked Foellmann if he thinks the “adopt-me” tag will take off, he said, “I really hope so. It might reduce the number of corpses rotting away in the repo.”

Is anyone else planning on making use of the tag?

17 Comments


  1. I think that if you’re going to use the tag, then the recommended way of doing it should be the way Christian Foellmann did it: by also adding the tag to the short description as well as to the first paragraph of the long description.

    By just adding the tag like Pippin has done, it will only show for people explicitly looking for the tag.

    Correct me if I’m wrong, but adding the tag basically means that the developer will no longer update the plugin, right? So, if a plugin author does not add any other information, users unaware of the tags will still install the plugin, with all risks involved.

    I would therefore suggest tag, short description, long description; that is if you really want someone to take over development…

    Report


    1. I fully agree with Piet on this, that would be better practice and would help developers really adopting those plugins. Give some description, maybe a contact link, even a GitHub repo could help making the fork/ adopt process more easy for all sides involved.

      Report


      1. Looking at the way Christian Foellmann added the adopt me tag and how Pippin did it, I can see how Christian would have a much better chance at getting a developer to adopt the plugin. By just adding the tag, it’s tiny and easy to miss if you don’t know where to look. Christian’s method places the adopt me text in the three areas where it would be the most noticeable.

        Report


  2. That tag (to me) means I’d like to transfer the plugin, not necessarily that I won’t be updating it anymore. If a user reports a bug, I will still fix it.

    Report


  3. I do not think it is so important that the tag takes off(at least initially). It does at least give other developers the opportunity for find plugins for adoption, whereas before it was more difficult. At least it is a first step in what I would consider the right direction.

    The tag does probably need to be well publicised however.

    Report


  4. Uh oh, I’m afraid I might turn into a crazy cat person and start taking in stray plugins…

    Report


  5. Maybe instead of just adding a readme.txt tag, we should also encourage putting the up-for-adoption Plugin on GitHub (if it’s not already there), so that anyone wanting to adopt the Plugin can make pull requests?

    That’s basically what George Stephanis did with Update Control, which I now maintain. The Plugin was already on GitHub, and I started making pull requests. He then added me as a GitHub committer, and then as an SVN committer.

    The problem with *just* going with the “adopt-me” tag is that the only way to implement an adoption is to skip straight to the SVN-committer step, which requires a great deal of trust. But with GitHub, there’s a built-in trust-building mechanism:

    1) Pull Requests (merges must be accepted by the repo owner)
    2) Add as GitHub committer (can commit directly to GitHub repo)
    3) Add as SVN committer (can commit directly to Plugins SVN)

    Note also: this mechanism doesn’t even require an “adopt-me” tag; anyone who finds a Plugin that could use some love (a bugfix, major updates, whatever) can make pull requests if the Plugin has a GitHub repo.

    Side thought: how could would it be to have git.wordpress.org/chipbennett/plugin-slug – basically, a WordPress-centric GitHub?

    Report


    1. I like the idea of a WordPress centric Github, Chip!

      Report


    2. In my opinion, the adopt-me tag has no future as it is only addressing the case of plugin authors willing to transfer a plugin.

      I am a great believer of the GitHub concept to save the contributors from demotivation.

      I also think that WordPress (core) should allow notifications of plugin updates from other sources (not only WordPress repository)

      Report

Comments are closed.