Fix a WP.org url going to the wrong tab

[jrfnl]

No description provided.

[franz-josef-kaiser]

The link would be better pointing directly to the readable source on GitHub, which is what we encourage:

Contributors
Please refrain from submitting any commercial products or themes. Links must allow for code browsing (github/bitbucket/svn..etc).

Thanks!

[jrfnl]

@franz-josef-kaiser (nearly) All plugins which are in the wp repo currently point to their wp repo url. A lot of them also have GH repos, some are even up to date ;-)

The wp repos all have browsable source (svn) available via the developers tab/trac.

I would like to suggest for plugins which are in the repo to have both URLs in WP Gear. I actually have a branch locally where I started setting this up.

Reasoning behind this:
If you want to use the plugin - which is for most people who visit WP Gear their initial goal -, the wp plugin repo is normally where you'd want to go, especially as it also contains the screenshots giving an impression of what you'll be getting, while the GH repo often doesn't contain those.
Once you use the plugin, if you want to change/fix/contribute to the plugin, the GH repo is what you'd want.

Making it easy to find both would make sense to me.

The 'line template' which I'm currently using for the local branch is like this:

[Plugin name](WP repo url) [GH](GH url) - Description.

[franz-josef-kaiser]

Changes: I have to admit, that the current state of WPGear is not the best and there's some room for improvement. After a talk with @wycks he agreed to move this repo over to the wecodemore GH account and @Giuseppe-Mazzapica and me already talked about improving the experience for WPGear in 2016.

About the wp.org plugin repo vs. GH repos: First off, the initial idea was to link to source code that is easily readable (read @wycks intro on the gear site for confirmation), which the wp.org repo is not. Lots of people develop mainly using Git as VCS, then just convert things and move the code to the wp.org SVN repo. (ProTip: Look at what Stephen did to simplify that). To us GitHub still is the first route to go (and wp.org just a, for some business concepts necessary, evil). Still, nothing against linking to the wp.org repos as secondary place to go in case someone still uses SFTP or the WP GUI to manage plugins – instead of using a package manager like Composer. In an ideal world there would be a WPackagist link as well for every single (code) repo.

Sidenote: If you just want to see what you get visually from installing a plugin, I suggest using Addendio, which launches ephemeral boxes to try WordPress without the hazzle configuring it locally.