3. If players are testing a mod it is usually advantageous if they actually know about it and are ready to give feedback at the appropriate place (i.e. where the modder can see it). I had no problem to find players who are ready to test my mods. All the other players have to wait until that is done before they get the new version as an official download. But then, what use does it make to rush the release if the mod is not fully tested?
We already have a lot of rumors going around - there being modders [plural] not wanting their mods being fixed or included into mega mod installs is one of them. I would like to spare more of these kind.
The way jastey does it for her own mods is probably the best example of how the author should decide on when and if they want their mods included in BWS.
- she puts links with a stable beta version up and invites testers, but without submitting the mod to BWS. This way people using the beta version know exactly what they have to expect.
- when the mod is thoroughly tested this way, she declares it official and to be added to BWS.
Another example is modder Raduziel who wants his mods to be exposed by BWS to a larger audience to be tested and improved. The mods are marked as beta versions and continuously updated per github. This is an alternative approach and also supported by BWS.
In both examples, the decision is fully in the hands of the mod author.
Things have been handled different in the past and the aftertaste of this is still found in some discussions.
Fact is that no mod has been added to BWS and no patch has been introduced into BWFixpack within the last 12 month WITHOUT having the author involved. (This does not include editorial updates of download links or versions, if those have been notified in which ever way).