[Wine] The pros and cons of a wiki AppDB
jjmckenzie51 at earthlink.net
Sun Mar 8 10:45:26 CDT 2009
>From: David Gerard <dgerard at gmail.com>
>Sent: Mar 8, 2009 6:59 AM
>To: wine-devel at winehq.org
>Cc: Wine <wine-users at winehq.org>
>Subject: Re: [Wine] The pros and cons of a wiki AppDB
>2009/3/7 IneedAname <wineappdb at googlemail.com>:
>> On Sat, 7 Mar 2009 20:10:13 +0000
>> David Gerard <dgerard at gmail.com> wrote:
>>> Yep. That's why a wiki is nice. If you open it up to everyone to
>>> contribute, you'll get bad stuff but you'll get good stuff you just
>>> wouldn't get otherwise. It's a great format to capture that.
>> We would use the same system for edit rights that we use now.
>> Make appDB account then ask to be a maintainer then you can edit the wiki page for that app.
>> The wiki is only for application notes.
>> Anyone can read the wiki history.
>> It would be very hard to set up.
>Con: Becoming a maintainer is a pain in the backside. You won't get
>useful drive-by contributions, and a lot of this stuff is drive-by.
Example? I've been a maintainer for over a year now. I've received two postings for the program. I don't think a lot of Linux and Mac users are using the program, or they are not experiencing problems. I will update the entry, now that you have reminded me to do so.
>> Do not cross post or you may up set people with power.
>So when we're talking about a service to users, you're saying "God
>forbid we ask the users"?
We are discussing what is a development issue. We really don't need to confuse users with this. Besides, I don't think most users really care if we are using a Wiki or a Web Application to record what is hsppening with Applications and their ability to run on Wine.
More information about the wine-users