Hi all,
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
Thanks, Mitchell Mebane
On Wed, 2005-06-08 at 19:32 -0500, Mitchell Mebane wrote:
Hi all,
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
Thanks, Mitchell Mebane -- The roots of education are bitter, but the fruit is sweet. --Aristotle
For best results, integrate it with Bugzilla. I should be able to go to an application in AppDB, fill out a form that says "bugs affecting this application" and that should then link me to those bugzilla bugs.
Bonus points for doing it in reverse. That way we can sorta prioritize what bugs we hunt after (if we're in a bug-hunting rather than particular app mood - particularly important as we try and stabilize Wine to end regressions for maintained apps). I have a suspicion it'll invite fans of a particular app to participate as well (since they'll have a specific bug to try and tackle).
Thanks, Scott Ritchie
Scott Ritchie wrote:
On Wed, 2005-06-08 at 19:32 -0500, Mitchell Mebane wrote:
Hi all,
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
Thanks, Mitchell Mebane -- The roots of education are bitter, but the fruit is sweet. --Aristotle
For best results, integrate it with Bugzilla. I should be able to go to an application in AppDB, fill out a form that says "bugs affecting this application" and that should then link me to those bugzilla bugs.
Good idea. I think I could handle that.
Bonus points for doing it in reverse. That way we can sorta prioritize what bugs we hunt after (if we're in a bug-hunting rather than particular app mood - particularly important as we try and stabilize Wine to end regressions for maintained apps). I have a suspicion it'll invite fans of a particular app to participate as well (since they'll have a specific bug to try and tackle).
Thanks, Scott Ritchie
.
Now that one is tougher. Mostly because I know absolutely no Perl.
I'm not too terribly familiar with BugZilla, but might it work to add each app as a BugZilla bug, then set the other bugs as blockers? That way I could do it by having the AppDB interface with the BugZilla DB, instead of having to modify BugZilla itself.
--Mitchell Mebane
On 6/8/05, Mitchell Mebane mmebane@ev1.net wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
One thing I'd like to see is a way to send feedback to the maker of the software to tell them their application is being used with Wine. Maybe that's just a link within the AppDB to a page on their website describing how to contact them, or maybe it's a link to a real comment form (on WineHQ or their site). Whatever the case, it should probably be controlled by the app maintainer.
-Brian
On Fri, 2005-06-10 at 09:27 -0600, Brian Vincent wrote:
On 6/8/05, Mitchell Mebane mmebane@ev1.net wrote: I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
One thing I'd like to see is a way to send feedback to the maker of the software to tell them their application is being used with Wine. Maybe that's just a link within the AppDB to a page on their website describing how to contact them, or maybe it's a link to a real comment form (on WineHQ or their site). Whatever the case, it should probably be controlled by the app maintainer.
-Brian
I agree. If Valve software, for instance, knew that nearly 10,000 of their customers were running Half Life with Wine perhaps they'd adopt a better policy than "completely ignore us and avoid having people even talk about Linux on the forums."
-Scott
I've been updating the wiki as I think of new things. I've tried to add the suggestions so far from this thread. Please feel free to add things to the todo list or to improve the formatting of the page. I'll be marking the ones that I'm working on so I don't conflict with anyone else that wants to jump in. I've got no plans to work on the bugzilla integration though.
http://wiki.winehq.org/AppdbInfo
Chris
On 6/10/05, Scott Ritchie scott@open-vote.org wrote:
On Fri, 2005-06-10 at 09:27 -0600, Brian Vincent wrote:
On 6/8/05, Mitchell Mebane mmebane@ev1.net wrote: I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
One thing I'd like to see is a way to send feedback to the maker of the software to tell them their application is being used with Wine. Maybe that's just a link within the AppDB to a page on their website describing how to contact them, or maybe it's a link to a real comment form (on WineHQ or their site). Whatever the case, it should probably be controlled by the app maintainer.
-Brian
I agree. If Valve software, for instance, knew that nearly 10,000 of their customers were running Half Life with Wine perhaps they'd adopt a better policy than "completely ignore us and avoid having people even talk about Linux on the forums."
-Scott
On Wednesday 08 June 2005 08:32 pm, Mitchell Mebane wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
I have some ideas about the AppDB, but I've been working on some of them myself, and others really need the approval of the WinHQ webmaster more than anything. Still, I'd like to hear what other people think of them:
1. The AppDB, Bugzilla and the Wiki ought to send last-modified information for most of their pages. This would speed things up, in some cases, for dialup users, but the real advantage would be as protection against a slashdotting or onslaught of AOL users. Many of the pages also send other headers that prevent caching of positive lookups.
Today I sent a patch to the AppDB maintainer to do this for images, which are probably the biggest performance hit (they cause the AppDB main page to take about 30 seconds to load over a dialup connection). However, almost any page in each of these databases could in theory be cached. Bugzilla bug display pages already display a "Last modified" datum in the text of the page, and so do Wiki pages (bug 2889 mentions this).
Several of the AppDB tables already have TIMESTAMP columns, so I was planning to write some code to just gather them all together and send the latest one as the last-modified date. The only problem is that if a page contains an item which is then deleted, its timestamp will go backwards.
2. The "robots.txt" on bugs.winehq.org is overly restrictive, and the 'robots.txt' on appdb.winehq.org and wiki.winehq.org are HTML pages. (Yes, I know that they have a big red "404" in the middle when viewed by a human, but they come back with "200 OK" responses to a spider). There might be fewer duplicated requests for help in different places if search engines could actually get at the text of bug reports and app comments.
3. It would be nice if the application display page could do a query against the Bugzilla database directly, and diplay it, something like
(no reported bugs) _add one_
or
[12 open bugs, 6 closed]
with the numbers being links to the Bugzilla query page for full details.
It would also be helpful to be able to associate a bug with more than one application.
4. The wiki should recognize the phrases "app <number>" and "bug <number>" and make them links to the corresponding AppDB and Bugzilla entries.
5. Perhaps the information about Linux alternatives for each app could be kept as a separate table, instead of as haphazard notes in app descriptions.
6. There are a couple more flags that would be nice:
license ENUM('OpenSource','Freeware','Commercial'), availability ENUM('Available','Discontinued'), linuxVersionAvailable ENUM('Yes','No')
Feel free to update the wiki page with the appdb ideas here: http://wiki.winehq.org/AppdbInfo
Chris
On Tuesday 14 June 2005 12:48 pm, David Lee Lambert wrote:
On Wednesday 08 June 2005 08:32 pm, Mitchell Mebane wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
I have some ideas about the AppDB, but I've been working on some of them myself, and others really need the approval of the WinHQ webmaster more than anything. Still, I'd like to hear what other people think of them:
- The AppDB, Bugzilla and the Wiki ought to send last-modified
information for most of their pages. This would speed things up, in some cases, for dialup users, but the real advantage would be as protection against a slashdotting or onslaught of AOL users. Many of the pages also send other headers that prevent caching of positive lookups.
Today I sent a patch to the AppDB maintainer to do this for images, which are probably the biggest performance hit (they cause the AppDB main page to take about 30 seconds to load over a dialup connection). However, almost any page in each of these databases could in theory be cached. Bugzilla bug display pages already display a "Last modified" datum in the text of the page, and so do Wiki pages (bug 2889 mentions this).
Several of the AppDB tables already have TIMESTAMP columns, so I was planning to write some code to just gather them all together and send the latest one as the last-modified date. The only problem is that if a page contains an item which is then deleted, its timestamp will go backwards.
- The "robots.txt" on bugs.winehq.org is overly restrictive, and the
'robots.txt' on appdb.winehq.org and wiki.winehq.org are HTML pages. (Yes, I know that they have a big red "404" in the middle when viewed by a human, but they come back with "200 OK" responses to a spider). There might be fewer duplicated requests for help in different places if search engines could actually get at the text of bug reports and app comments.
- It would be nice if the application display page could do a query
against the Bugzilla database directly, and diplay it, something like
(no reported bugs) _add one_
or
[12 open bugs, 6 closed]
with the numbers being links to the Bugzilla query page for full details.
It would also be helpful to be able to associate a bug with more than one application.
- The wiki should recognize the phrases "app <number>" and "bug <number>"
and make them links to the corresponding AppDB and Bugzilla entries.
- Perhaps the information about Linux alternatives for each app could be
kept as a separate table, instead of as haphazard notes in app descriptions.
- There are a couple more flags that would be nice:
license ENUM('OpenSource','Freeware','Commercial'), availability ENUM('Available','Discontinued'), linuxVersionAvailable ENUM('Yes','No')
David Lee Lambert wrote:
On Wednesday 08 June 2005 08:32 pm, Mitchell Mebane wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
I have some ideas about the AppDB, but I've been working on some of them myself, and others really need the approval of the WinHQ webmaster more than anything. Still, I'd like to hear what other people think of them:
- The AppDB, Bugzilla and the Wiki ought to send last-modified information
for most of their pages. This would speed things up, in some cases, for dialup users, but the real advantage would be as protection against a slashdotting or onslaught of AOL users. Many of the pages also send other headers that prevent caching of positive lookups.
Today I sent a patch to the AppDB maintainer to do this for images, which are probably the biggest performance hit (they cause the AppDB main page to take about 30 seconds to load over a dialup connection). However, almost any page in each of these databases could in theory be cached. Bugzilla bug display pages already display a "Last modified" datum in the text of the page, and so do Wiki pages (bug 2889 mentions this).
Several of the AppDB tables already have TIMESTAMP columns, so I was planning to write some code to just gather them all together and send the latest one as the last-modified date. The only problem is that if a page contains an item which is then deleted, its timestamp will go backwards.
David,
I don't see this patch on wine-patches. Did you send this in?
--Mitchell Mebane
The patch needed some minor changes and clarifications. I haven't received a resubmission yet.
Chris
On 6/27/05, Mitchell Mebane mmebane@ev1.net wrote:
David Lee Lambert wrote: On Wednesday 08 June 2005 08:32 pm, Mitchell Mebane wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
I have some ideas about the AppDB, but I've been working on some of them myself, and others really need the approval of the WinHQ webmaster more than anything. Still, I'd like to hear what other people think of them:
- The AppDB, Bugzilla and the Wiki ought to send last-modified information
for most of their pages. This would speed things up, in some cases, for dialup users, but the real advantage would be as protection against a slashdotting or onslaught of AOL users. Many of the pages also send other headers that prevent caching of positive lookups.
Today I sent a patch to the AppDB maintainer to do this for images, which are probably the biggest performance hit (they cause the AppDB main page to take about 30 seconds to load over a dialup connection). However, almost any page in each of these databases could in theory be cached. Bugzilla bug display pages already display a "Last modified" datum in the text of the page, and so do Wiki pages (bug 2889 mentions this).
Several of the AppDB tables already have TIMESTAMP columns, so I was planning to write some code to just gather them all together and send the latest one as the last-modified date. The only problem is that if a page contains an item which is then deleted, its timestamp will go backwards.
David,
I don't see this patch on wine-patches. Did you send this in?
--Mitchell Mebane
-- I find that a great part of the information I have was acquired by looking up something and finding something else on the way. -- Franklin P. Adams
Chris Morgan wrote:
The patch needed some minor changes and clarifications. I haven't received a resubmission yet.
Chris
On 6/27/05, Mitchell Mebane mmebane@ev1.net wrote:
David Lee Lambert wrote: On Wednesday 08 June 2005 08:32 pm, Mitchell Mebane wrote:
I'm putting together a Summer of Code proposal for working on the AppDB. I've been talking with Chris Morgan, and he has a few suggestions, but I was looking for more. Does anybody have any features they'd like added to the AppDB, quirks they'd like worked out, or things of that nature?
I have some ideas about the AppDB, but I've been working on some of them myself, and others really need the approval of the WinHQ webmaster more than anything. Still, I'd like to hear what other people think of them:
- The AppDB, Bugzilla and the Wiki ought to send last-modified information
for most of their pages. This would speed things up, in some cases, for dialup users, but the real advantage would be as protection against a slashdotting or onslaught of AOL users. Many of the pages also send other headers that prevent caching of positive lookups.
Today I sent a patch to the AppDB maintainer to do this for images, which are probably the biggest performance hit (they cause the AppDB main page to take about 30 seconds to load over a dialup connection). However, almost any page in each of these databases could in theory be cached. Bugzilla bug display pages already display a "Last modified" datum in the text of the page, and so do Wiki pages (bug 2889 mentions this).
Several of the AppDB tables already have TIMESTAMP columns, so I was planning to write some code to just gather them all together and send the latest one as the last-modified date. The only problem is that if a page contains an item which is then deleted, its timestamp will go backwards.
David,
I don't see this patch on wine-patches. Did you send this in?
--Mitchell Mebane
-- I find that a great part of the information I have was acquired by looking up something and finding something else on the way. -- Franklin P. Adams
.
If you don't hear from him, please send me his patch and your notes and I'll take a look at it.
--Mitchell
-
Brian Vincent -
Chris Morgan -
Chris Morgan -
David Lee Lambert -
Mitchell Mebane -
Scott Ritchie