Re: [XBoard-devel] Installer

[h.g. muller]

>  My take would be to create an installer and add whatever we want and add 
> a text on the webpage along the lines: "if you want your engine/code xyz 
> to be included in the next release of winboard, please contact us". It's 
> not as if we are like Microsoft and won't change what software we bundle, 
> we are open to add stuff to it ;)

We should be careful with that. What if we get 150 replies of people that 
think it would be a great idea to include their engine? (The 90% that are 
not excessively weak all being clones, of course.) Even sending people a 
rejection letter could become a full-time job...

Perhap we should better phrase it like:

"
If you have suggestions for inclusion of tools in the installer bundle
that would really enhance the functionality, please contact us.
We do realize that many choices we make here are really arbitrary,
but we do employ a few guide-lines for choosing between alternatives.
We favor components that are
* stable
* Open Source
* Licenced under GPL or freeware
* versatile (e.g. we'd rather provide one engine that plays 6 variants than 
6 that play one each.)
We dislike:
* more of the same (e.g. more WB or UCI engines that only play "variant 
normal")
* software of unclear origin or license
"