Hi Paul, > My concern is that publishing (and publicizing) beta docs will lead to > them being widely distributed and many people will use them for > reference instead of for reviewing.
Yes, it could be. To solve it, we can organize it through subscription to some close list, where we will be able to send notifications of updates, and also we'll BIG notice about beta stage in the beginning, suggesting to get new version, with URL where update is located. I can create such list and provide all infrastructure - signup forms, automatic subscriptions and unsubscriptions, etc. > > An alternative might be to invite knowledgeable Firebird users as beta > reviewers and provide them with the material. (We could approach certain > people directly and/or post a message in e.g. fb-general explaining what > is needed and asking people to step forward if they feel they can help > with this.) Yes, this is a good idea. > > That being said, I think this should be Helen's call, because the burden > of weeding through all the feedback will be largely on her. There always will be mistakes and some unclear things. Even Knuth still improves some details. It is easier to find and eliminate them if you know what and where to look, then try to check everything. Regards, Alexey ------------------------------------------------------------------------------ _______________________________________________ Firebird-docs mailing list Firebird-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-docs
