My version of a plugin repository

[NiLSPACE]

Yeah, but we shouldn't filter out plugins with only a little Lua code. For example, @xoft's PluginMemory plugin is mostly JavaScript due to jQuery.

[DrMasik]

If you want to control plugins repository you can look at FreeBSD ports collection and do like that.
It it use port mantainer (plugin creator) and authorize him (allow to update and create new plugins).

[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.

---

Filter out plugins with no Lua code? You would be so heartless as to remove my Cuberite-Autoupdate-Script? :(

[Mathias]

Perhaps we could allow reviews/comments from guests too, if they complete a captcha or something similar? I think it seems quite unlikely that users of a plugin would create a Github account to leave a comment, which means plugin developers won't get much feedback from the user.

[DrMasik]

...
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

[DrMasik]

Perhaps we could allow reviews/comments from guests too, if they complete a captcha or something similar? I think it seems quite unlikely that users of a plugin would create a Github account to leave a comment, which means plugin developers won't get much feedback from the user.

Captcha do not protect from bots and spammers. It's checked by myself.

[sphinxc0re]

@tigerw when your auto-update-script isn't containing any lua code it is by definition not a Cuberite plugin. So bombs away!

[ShadowCone]

May I suggest some kind of CI which loads a cuberite installation In a container and tries to load the plugin? If it succeeds, good, if not, bad. Would probably reduce a lot of spam and that bit whars left can be human moderated.

Of course combined with a capcha

[xoft]

We're actually thinking of implementing a test-bed for plugins, that could be used to verify plugins, too.
https://github.com/cuberite/cuberite/issues/3321

[tigerw]

It must, of course, be written in PHP.