WordPress.org

Making WordPress.org

Opened 3 years ago

Closed 3 years ago

#2132 closed enhancement (wontfix)

Change “Browse in Trac” link to something more meaningful

Reported by: geekysoft Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

Please split the “Browse in Track” link on individual plugin pages into two links to facilitate better use of the Track system and encourage more contributions.

<a href="https://plugins.trac.wordpress.org/query?status=!closed&component=PLUGIN-SLUG">List all known issues</a>

<a href="https://plugins.trac.wordpress.org/newticket?component=PLUGIN-SLUG">Report a new issue or submit patches</a>

I strongly believe that having these two links instead of the rather cryptic “Browse in Trac” link will increase engagement. The suggested links don’t require prior knowledge of what Trac is and makes Trac easier to use for new users by bypassing the complications of locating the correct component (and knowing what component to choose from a list of thousands of plugins). Automatically assigning/notifying the plugin author is of course required for this to work properly.

Only 1906 out of the 47 161 total plugins (4,04 %) have components in Trac. Why? Either get rid of Trac entirely to not confuse people, or fix it so it works for all plugins.

Change History (1)

#1 @Otto42
3 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

Currently, the plugins trac ticketing system is not actually used for plugin bug-reports and patch submissions. It's there, but really, nobody ever really used it and I'd guess that it's likely that we'll simply wipe it and delete all those tickets.

We really only use the plugins.trac as a convienent way to look at the SVN for diffs and the like. There's no point in adding a "new ticket" link when we don't really want people adding new tickets there where plugin authors will never actually see them.

By and large, the plugin SVN is not meant for development and collaboration. It's a release repository. Yes, you can do development on it, but most people prefer to collaborate on systems like github, and then push only the final release versions to the SVN for deployment to the directory.

Note: See TracTickets for help on using tickets.