[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):

 Replying to [comment:3 Ipstenu]:
 > All plugins hosted on WordPress.org are open source and all have the
 same SVN URL format: http://plugins.svn.wordpress.org/akismet/
 >
 > But I think you meant that not all plugins have public development
 repositories that everyone can find.
 >
 > The reason we don't allow that is people abused 'hidden' links like the
 donation link. They'd put in URL shorteners and send people to spam pages
 :(
 >
 > The only way it'd work is if we added in code to whitelist what URLs
 showed up.

 Ah that makes sense. Well, considering overwhelming popularity of github,
 bitbucket, and gitlab, it seems to me that there's basically 3 urls to
 whitelist yeah? According to this link Github alone makes up about 50% of
 the publicly hosted repos out there. https://www.datanyze.com/market-share
 /source-code-management/github-market-share   (that's a pretty rough
 estimate but still, Github is the single largest repository for code on
 Earth.)

 I mean, the wordpress org can do whatever they want, I'm just sharing
 feedback, but I think there's a pretty strong argument for better linking
 the development/maintenance of code and the public face of that code.

 I'm also curious how Microsoft manages that issue with their vscode
 extension marketplace. They have a dedicated repo link, and as far as I
 can tell it's not filtered. That might just be a difference in the dev
 community. WP has had problems with spammers etc as I understand it.



 Replying to [comment:4 joyously]:
 > > WordPress forums simply aren’t built with an open source issue tracker
 in mind.
 >
 > Nope. It's a release repository, not development. The forums are about
 community help, not testing and fixing plugin code.

 Right, that's kind of my point though....


 > > any wordpress theme or plugin that is open sourced to have a dedicated
 field to link to their repo.
 >
 > They are ALL open source. It is a minority of users that would have a
 public repo, and a minority of WordPress users that would want to see
 another repo of the code that is already in this repo.

 All the wordpress themes/plugins in the wordpress.org repo are, yes. I was
 not sure that was true, but since I knew of closed source themes/plugins
 out there I was hedging my language.

 Also not sure you can prove that it's a minority of users who would want
 access to a public repo and issue tracker. Considering there is 1,368
 issues open on the Gutenberg github issue tracker, I think there's a
 healthy appetite for that engagement.

 > The WP repo is not there for authors to be seen. It's a place to store
 some code so other users can use it.

 Not really sure what this means, as I don't think I've said anything about
 authors being seen?

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