#1584 closed task (blessed) (fixed)
Plugin Directory v3 MVP
Reported by: | dd32 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Plugin Directory | Keywords: | |
Cc: |
Description
Some of the Meta team are currently working on a new enhanced version of the Plugins Directory.
This serves as a ticket for the initial MVP import of
- Basic WordPress theme modeled off the existing bbPress theme
- Basic plugin with bare-bones functionality.
A number of things will change as the functionality is fleshed out, a number of items will still be filled with test data as the feature isn't yet implemented.
Change History (70)
This ticket was mentioned in Slack in #meta by obenland. View the logs.
9 years ago
#11
follow-up:
↓ 15
@
9 years ago
@dd32 Re [2555]: What was your idea behind WPorg_Plugin_Directory::get_or_create_plugin_post()
? Shouldn't uploading a zip be the only way to create a plugin in the repo?
Also: Given the premise that plugin posts don't get deleted when the plugin gets rejected, uploading a plugin zip "secures" a specific slug. What would keep us then from adding it to SVN on upload vs. after approval?
/cc @otto42, @coffee2code
#12
follow-up:
↓ 14
@
9 years ago
Plugin post slugs should be renamed or otherwise invalidated after rejection, much the same as the existing system does now. Rejected slugs cannot be reserved forever, and we should not upload anything into the SVN until after the plugin is approved.
If the system is designed such that anybody can reserve a slug by merely requesting it, then the system needs redesigning to avoid that problem.
The current directory renames rejected plugin topics to "rejected-abc-rejected" without creating SVN directories for them.
#14
in reply to:
↑ 12
;
follow-up:
↓ 28
@
9 years ago
Replying to Otto42:
If the system is designed such that anybody can reserve a slug by merely requesting it, then the system needs redesigning to avoid that problem.
I think themes currently work that way. Should that be changed?
#15
in reply to:
↑ 11
;
follow-up:
↓ 16
@
9 years ago
Replying to obenland:
@dd32 Re [2555]: What was your idea behind
WPorg_Plugin_Directory::get_or_create_plugin_post()
? Shouldn't uploading a zip be the only way to create a plugin in the repo?
That will be the main way in the end, however I needed something to create them on-demand for the CLI import script. I expect we'll split the method in half in the end. None of the post handling should be done within the uploader script.
#16
in reply to:
↑ 15
@
9 years ago
Replying to dd32:
None of the post handling should be done within the uploader script.
Where should it be done? Besides the import, which is not ongoing, when else would we create a post?
This ticket was mentioned in Slack in #meta by obenland. View the logs.
9 years ago
#28
in reply to:
↑ 14
@
9 years ago
Replying to obenland:
Replying to Otto42:
If the system is designed such that anybody can reserve a slug by merely requesting it, then the system needs redesigning to avoid that problem.
I think themes currently work that way. Should that be changed?
Themes currently do work that way, however the theme process is different than the plugin process. There's a lot more plugins and therefore slugs, and reserving them for merely requesting is going to create a lot of problems and a lot of extra work.
If the choice is between changing the themes system to match or allowing plugin slugs to become polluted, then yes, themes needs to change. Plugin slugs can not become polluted this way. The workload will significantly increase because of it.
The ideal choice is to leave themes as is (for now) and make plugins behave differently.
In 2499: