I've run across the following two articles on the wow wiki. The first link is the general page for Linux/Wine. The sound and voice chat is what I'm most interested in about the second link. Can anyone comment on how current and useful these tips are? It's nice to know that Blizzard knows about and actually seems to "care" about Linux users, but I really do NOT want to break anything because of misinformation. http://www.wowwiki.com/Linux/Wine http://www.wowwiki.com/Linux/Wine/Misc Thanks, Jim -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.winehq.org/pipermail/wine-users/attachments/20080320/06be5781/attachment.htm
Jim Hall wrote:> and useful these tips are? It's nice to know that Blizzard knows about and > actually seems to "care" about Linux users, but I really do NOT want toWoWWiki is maintained by volunteers, not by Blizzard. Given Blizzards past history, they definitely don't care about Linux users. They tolerate us but they don't care about us. tom
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 20 March 2008 01:29:15 pm Jim Hall wrote:> I've run across the following two articles on the wow wiki. The first link > is the general page for Linux/Wine. The sound and voice chat is what I'm > most interested in about the second link. Can anyone comment on how current > and useful these tips are? It's nice to know that Blizzard knows about and > actually seems to "care" about Linux users, but I really do NOT want to > break anything because of misinformation. > > http://www.wowwiki.com/Linux/Wine > > http://www.wowwiki.com/Linux/Wine/MiscI would encourage them to link to the appdb and submit their findings there instead of making a seperate resource for it. - -- Paul Johnson baloo at ursine.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH4uzIUCxPKZafKh0RAh3dAKDzPKO0ZqEN0IQZ0bCF5khwQ0V8GACeNKaC VDgLTHB3Ot9wGIV698zxeQM=8AVb -----END PGP SIGNATURE-----
Paul Johnson wrote:> I would encourage them to link to the appdb and submit their findings there > instead of making a seperate resource for it. >That is exactly what did not work because of the horrid AppDB interface. So no, people need to keep information where it's easily maintainable and readable.
Dan Kegel wrote:> > That's too bad. I've asked the WoW appdb maintainer to comment. > > As a maintainer for Photoshop and a few other apps, I do find > that it's easy to not notice test data submissions, so sometimes > I don't approve them as quickly as I should. I always try to > explain why when I reject or remove stuff. > - DanI personally think the HowTo sections and such should be more like a Wiki and be updated by all. These sections often go out of date and become incorrect. They should at least be flagged as outdated if the maintainer hasn't touched it within the last 10 releases--the same way that test data is. They should also be flagged if a linked bug is resolved. Of course if the DB entry for an app gets flagged a message should be sent to all of its maintainers. If none respond within a week or so, the application's entry becomes unmaintained (ie the maintainers are removed for not being maintainers). Additionally there's a lot of test data with the three text fields filled in with "everything", "nothing", and "nothing" (everything works, nothing doesn't work, and everything was tested). It gets a platinum rating despite the fact every post prior to or after rated it much lower and expressed significant problems. These are the worst kinds of posts because they really don't give any useful information and serve to frustrate users who can't get an app working. All they know is that there is some unsubstantiated claims that it can be done. I think that the suggestions expressed in other threads in the list, with respect to improving the rating system, are also very relevant and should be considered as well. If time and resources permit I think it would be great to have these kinks worked out by 1.0 time--at least to what extent they can be.
As a maintainer for several applications myself, I like the current AppDB interface but it does need a wiki section that is update-able by all. I would suggest putting it right below the "howto" section. The wiki would allow the self-policing, history and up-to-date information while still keeping the howto and comments intact. As a further suggestion, I would put javascript validation code into the comment submission form that uses heuristics to detect spam or when a user submits a big error log and warns them to not do that. Maybe restrict comments to 100 lines or so...