Plugins are not well documented, it's counterproductive because some could really help people, but when going either to github or reading the description of the projects, there's nothing explaining what it is about or how to use it.
From my point of view, there are three minimal things we can do to improve that greatly:
add a small (1/2 lines) explanation of the goal of the plugin and what it brings (agent skills ? contextual menu items ? etc.) that would be accessible from the gama plugin installation window (in the "Details" section). To do so, we just need to edit the description into the plugin's feature.xml
so far only the weka plugin has one
For plugins extending the gaml language (skills and operators) at least package one model to demonstrate all the possibilities
most plugins are already doing it, but some still don't (camisole for example)
Add relevant information in the github's readme:
project's purpose
what is added
how to use
It is not that big of a work and at least it'll make those plugins accessible to people that didn't work on them
Plugins are not well documented, it's counterproductive because some could really help people, but when going either to github or reading the description of the projects, there's nothing explaining what it is about or how to use it.
From my point of view, there are three minimal things we can do to improve that greatly:
descriptioninto the plugin'sfeature.xmlIt is not that big of a work and at least it'll make those plugins accessible to people that didn't work on them