1. Jeff Matson

    I personally prefer using WordPress.org for anything public-facing due to the amount of exposure, as well as the simple search from within WordPress to install it. Github is the better option for something that isn’t quite polished though.


  2. Lester Chan (@gamerz)

    Personally, I moved my plugins to GitHub (https://github.com/lesterchan) & using scribu’s bash script (http://scribu.net/blog/deploying-from-git-to-svn.html) to push it to SVN. Works very well for me. Best of both world


  3. Andy Fragen

    Sarah, thanks so much for the shout out to GitHub Updater. I can honestly say that developing on GitHub has made me better and made eat his plugin better. I couldn’t have done it myself and I’ve had lots of help from the ubiquitous Gary Jones and Seth Carstens.

    There are reasons it wasn’t allowed in the WP repo and it mostly has to do with promoting an outside repository. As you pointed out, there is no code review or the ability to pull a plugin/theme out of the repo on GitHub. In the end I believe the WP repo maintainers were just looking for the safest experience for the majority of users.

    Thanks again for the shout out.


  4. Otto

    It’s worth noting this post by Nacin last week: http://make.wordpress.org/core/2014/01/15/git-mirrors-for-wordpress/

    Long term, the choice should not come down to svn vs. git. We hope to support both and let developers use what they’re comfortable with on WordPress.org.


  5. Piet

    Nice article Sarah, thanks. Another advantage of Github is that you can make branches.

    I host my plugins on both WordPress.org and Github and use the latter to develop the next versions on. In the WordPress Repo I also mention explicitly that I only offer support via Github, not on the forums there. Some people don’t like that (the comments I get is “yet another login”), but it just works much better for me.

    Although I am aware of their existence, I haven’t yet used any of the git to svn scripts you mentioned in the article. Must check them out again now.


  6. Khürt Williams

    It depends on the audience for the plugin. From a normal end user perspective WordPress.org is what is needed. Confidence in the code and ease of use of finding and installing etc. are key.

    GitHub is great for geeks designing for other geeks.


  7. Ryan Hellyer

    There are so few collaborative projects, that I don’t see there being much use for Github in hosting WordPress plugins (obviously many people disagree with me on this). The only thing I use GIthub for, is hosting plugins before they’re ready to shunt onto WordPress.org.


  8. Greg Winiarski

    Sensible approach i see some developers are using is to keep beta version on GitHub so any power-user can take advantage of it, and additionally stable version (for anyone) in WordPress repository.


  9. Ajay

    I’m finally starting the process of moving my plugin code to GitHub. But, this is to foster collaboration, if anyone is interested.

    The end plan is to always upload the stable release version to WordPress.org.


  10. Kathy

    I use Patrick Rauland’s version of the deploy script: https://gist.github.com/3767319 otherwise I don’t think I’d have plugins in the repo… or wouldn’t update them. I can’t seem to get my head around SVN, but sort-of understand Git. I’ve been able to easily submit features or bugfixes to other github-hosted plugins and have had a few people do the same with mine; something I haven’t done with SVN. It is just a matter of personal preference.. and probably what you use first.

    If you want lots of people to find and use your plugin, then the repo is the place to be. Of course, that also means a ton more support issues will crop up.


  11. WordPress.org vs. GitHub | ClarkWP WordPress Magazine

    […] Sarah Gooding has written an great article that can help you to decide where to host your open source WordPress plugin or theme . Do you know the pro’s and con’s of each? If you want to then check out her article! […]


  12. Arūnas Liuiza (IdeaG)

    WP.org has some more disadvantages than listed here:
    1. If you are doing any promotion of your plugin, there is NO way of checking if it is working or how well. Number of downloads in the ‘stats’ section is a joke, not a metric.
    2. Doing support on WP.org is inconvenient to put it mildly. I just keep missing support requests because the only way I can be notified is through RSS, which I don’t use for anything else. There is no convenient way of marking progress on issues, etc.


    • Samuel "Otto" Wood

      > the only way I can be notified is through RSS

      Or email. There are email subscriptions available for almost everywhere that there are those RSS feeds. Including the various plugin support forums.


  13. Aubrey Portwood

    Thought you might like to look at https://github.com/aubreypwd/deploy-git-wordpress-org It’s my version of a deploying plugins to WordPress.org script. It accepts the plugin file, username for WordPress.org, and only makes updates to readme.txt if you want it to.


  14. aristath

    Incidentally, this plugin is banned from the WordPress.org repository.

    Why is that?
    Is there anything wrong with its code? ‘Cause I can’t find anything wrong with it…
    Is there a policy for plugins hosted on w.org that forbids what this plugin is doing?


  15. sinanisler

    I hate svn :(

    I’m using only for wordpress.org


Comments are closed.

%d bloggers like this: