My version of a plugin repository

[xoft]

Can't PHP execute OS scripts?

[PureTryOut]

Yes it can

[tigerw]

...
It seems like the plugin repository is based on the same design as Ports, just with different names for things and different content. We have plugin owners who can modify plugins they submitted, and can also make new ones.
...

I think you are not right. Anybody who have githum login can post plugin in plugin repository. FreeBSD port collaction can update only port mantainer. You mut first allow post plugins in old style (some as I'm) and after some success plugins - allow access to the official Cuberite plugin repository. It's li Linux pkg system too

So would you suggest a system whereby plugins are posted in the forum first, and if, and only if, they get enough votes, they can then be added? If so, how do you think about GitHub stars as a way of voting?

[tigerw]

Can't PHP execute OS scripts?

Well, I was making a joke.

[PureTryOut]

So would you suggest a system whereby plugins are posted in the forum first, and if, and only if, they get enough votes, they can then be added? If so, how do you think about GitHub stars as a way of voting?

All way too... complicated... Seriously, just add the ability to the existing plugin repository to upload plugins manually (without needing a Github account), like how Bukkit does it. Maybe add the option to view plugins by author/uploader.

[xoft]

Nah, GitHub is fine and it's not like you couldn't put your plugin there, even if you use a different provider for the development.

What we need more is proper UX. The plugin list is a joke, seriously. Adding a plugin is slow and buggy. There's nothing in the plugins' descriptions. There's no documentation about what info the repository extracts and uses.

[tigerw]

Adding a plugin is slow

True, but making multiple network requests to GitHub on a free web instance is inherently slow

There's nothing in the plugins' descriptions.

What do you mean? It shows whatever the plugin author provided in their README file and the Info.lua Description field.

There's no documentation about what info the repository extracts and uses.

I suppose that the message above the 'Add entry' button in the add plugin page isn't visible enough. Where would you suggest I place this?

[tigerw]

Also, I've added a releases tracking/download system using GitHub releases. Also added a downloads counter.

[xoft]

1. Why make the network request at the server, when they can be done client-side, and the server can just receive and verify the final repo choice?
2. Icon? Screenshots? Commands and ConsoleCommands? Permissions? Short description vs the long description?
3. There's nothing above the "Add entry" button. There's a bit of info above the "Submit" button on the AddEntry page, but that's really really hidden. There should be a dedicated page for it, especially once you start extracting more.

How about sorting? Searching? List per author?

[tigerw]

1. Why make the network request at the server, when they can be done client-side, and the server can just receive and verify the final repo choice?
2. Icon? Screenshots? Commands and ConsoleCommands? Permissions? Short description vs the long description?
3. There's nothing above the "Add entry" button. There's a bit of info above the "Submit" button on the AddEntry page, but that's really really hidden. There should be a dedicated page for it, especially once you start extracting more.

How about sorting? Searching? List per author?

1. I am hesitant to add JS (see issue on GitHub), not least because that's one more thing to have to maintain
   
2. Icons are implemented, screenshots not. I was under the impression that commands and permissions went in README, like what WorldEdit does. I'm showing all the descriptions I can find. Which are you referring to?
   
3. OK.
   
   Alright, alright, I'm doing this when I'm free :P