[wp-meta] [Making WordPress.org] #3937: Feature request: Add standardized field for git/svn repo on plugin pages

[Making WordPress.org]

#3937: Feature request: Add standardized field for git/svn repo on plugin pages
------------------------------+--------------------
 Reporter:  thedonquixotic    |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 Lots of wordpress plugins are open source, but I often don't know that
 unless I decide to actually search for "{{plugin-name}} github" on google.
 This is a problem. And it creates a huge disconnect between the discussion
 and maintenance of open source projects.

 It's a far too common site on the wordpress plugin repo. Some dev needs to
 solve a problem, they do a little bit of work, and then upload it, and
 then it goes untouched for half a decade. Does the plugin still work?
 Maybe? Who knows? I can see if a plugin has been updated recently but that
 doesn't mean it doesn't work. And it may have a lot of installs, or maybe
 not! But neither of those is a particularly good indicator whether or not
 a plugin will work or how well it will work.


  Most open sourced projects are hosted on github etc and developers have
 much better and specialized tools to directly addressing technical bug
 reports etc through those tools. The code and the issue report are near
 each other, easily linked etc. And often times with an open source project
 the relationship between the dev and the people using it isn't the same
 "customer/service provider" relationship which the WP plugin support
 forums presuppose. A github issue is someone logging a complaint but it's
 also an invitation for other users to help, or even just the person
 logging the bug being able to document their process, make a fix, and then
 pull request it into the project.

 WordPress forums simply aren’t built with an open source issue tracker in
 mind. WordPress itself doesn’t use the wordpress forums to discuss the
 majority of the issues for projects they’re working on. Instead teams like
 the Gutenburg team etc use github and discuss issues related to technical
 issues primarily through github.

 It should be standard practice that any wordpress theme or plugin that is
 open sourced to have a dedicated field to link to their repo. Yes, they
 can always do that through their project description etc, but it’s about
 positioning and prioritizing open access to code. Too often plugins are
 made by a developer, then abandoned. Some other users might take up the
 torch and continue to develop it, if there was a greater amount of access
 and transparency in the way that the code repo was linked to the plugin
 repo.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/3937>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org