Re: [Slashcode-development] [ slashcode-Patches-431439 ] Arepository for plugins

[Brian A. <br...@ta...>]

Alvaro del Castillo wrote:
> and admin plugin rol. We can have an ACL that controls this. It could be
> a good idea to test the ACL system with this simple plugin to learn the
> possibilities of the ACL system ;-) If not, we can use the seclev
> system. To activate a plugin you need to have more that 5000 or 10000.
You know, I can not remember where we ended up with the debate on ACL's.
Pudge, do you remember?

> > 2) With category there needs to be a table listing
> > category (AKA so they actually make sense).
> Yes. We can use the createSelect function in Slash and have this
> categories in a table. Maybe plugins_params ;-) because I think that a
> plugin will change the info related to it in the near version of
> slashcode.
This is why code_params was created :)
Easy enough for plugins to add items for getDescriptions().

> But I am not sure if you refere to this. Maybe you talk about the
> changes in the plugin between different versions and the patch needed to
> upgrade the plugin.
Yep, I was talking about revisions.

> > 5) RSS output so that people can use it in slashboxes.
> Yes, this is wonderfull :-)
Pretty much everything should have the ability to dump data via
RSS by this point. There is a Slash::XML library that was written
for this (its only in Fry right now though, I could add a CVS module
though for people to be able to extract it and install on their
own). About a minute's worht of work.

> - Instalation instructions.
> - The possibility to have comments about the plugins from other users
> maybe using a slash story.
Comments for items like this is a fry feature, you can't really do them
well in Bender.

> - The possibility for the user to give points/stars to the plugins
Overall moderation system tied to anything in the system. 
Cliff, any thoughts on this? I would love to see someone take the
karma system and turn it into a plugin that could be used with
any item. Since moderation is now tied in Fry to discussions you
might be better off doing a seperate moderation system that
worked on entities in the database. AKA tie it to anything
with a primary key.

	-Brian