[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  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by thedonquixotic):

 Fair enough. I just know that as a developer who is also a user, when a
 plugin doesn't work or has a bug, I've gotten much better help (as a user)
 by going to github issue trackers than I have by going to the support
 forum. This could be a purely cultural thing, but I think it's at least
 partially structural.

 In the case of a developer abandoning a project, other users with similar
 problems can band together to figure something out, or you can always
 check the forks and see where newer development is being carried on by
 other people.

 And while I am using this stuff as a user, being a dev, being able to see
 the code in close proximity help gives me valuable information about how
 well developed the plugin is. I can actually see what the last couple of
 commits were and whether the development on the project is active (I have
 a sneaking suspicion that at least a fair number of plugin devs just do a
 rudimentary change every version in order to make the plugin say a recent
 "last updated" while they haven't actually fixed any bugs or addressed
 major issues)

 Also since a git repo has active integration into the devs development
 work pipeline, I think they tend to be more responsive because they're
 actually checking their github/gitlab regularly while they won't
 necessarily be checking their support page.

 Though like I said this stuff could also be ultimately cultural. If
 nothing else, I think I'm pointing to some problems I see in the way that
 plugins are developed and maintained in the WP community. Coming from
 outside the wp community, it is sometime frustrating to separate the wheat
 and the chaff, and I think my thinking was that greater transparency and a
 smaller wall between code and community would help with that. That's also
 a difficulty that perhaps is inherent to a more publically focused CMS
 community versus a more dedicated and focused developer community. But
 that's just my opinion. Take it as you will.

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