Hi Stuart,

[...]
> I guess the problem is how to ensure backend plugins are prominently visible

Probably need to mention them on the home page, install page, start of
the user guide, all pointing to where they are at the end of the user
guide.

> and are not seen as second class citizens. As well as raising user awareness
> in the documentation they also have to be painless to install and uninstall
> -- maybe the backend option should accept a URL as well as a file name e.g.
>
>  asciidoc --backend install
> https://github.com/downloads/srackham/asciidoc-fossil-backend/fossil.zip

That would help.

For what its worth my experience from another project that gathered a
number of plugins is that:

1. a few are distributed with the project and automatically installed
with the base package, this got into the major distros

2. eventually a combined plugins project was created with a bunch of
the popular plugins all in the same VCS repository but still with
their individual maintainers and with a shared website and all
installed in one package, this also got into the major distros

3. there are a few plugins that remain defiantly independent but are
pointed to from the plugin project website

The big thing was distro acceptance, base project ok, fine and so
those plugins were always available (though the user has to enable
them) but individual plugins were never accepted by the distros, it
took the combined package to get them accepted.

Packages in the distro repositories provides a better user experience
since they install with their normal installer/uninstaller and have to
install at most two packages.

In this model the main project is responsible for the combined plugins
package and the maintainers of individual plugins send pull requests
from their own github forks.  As the main project has always got the
blame for malcontent plugins it is now starting to be more assertive
regarding plugin quality.

Cheers
Lex

-- 
You received this message because you are subscribed to the Google Groups 
"asciidoc" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/asciidoc?hl=en.

Reply via email to