Here's my wineconf summary. It's not much of a summary, since it's so damn long. I wanted to record as much as possible for the developers that weren't there because I think a lot of ideas and direction was generated and should be shared among the community.
I put in <> brackets in areas where I need correction, and I am going to correct some of those myself.
Andi, I'd like to put this on winehq somewhere with the presentation files hyperlinked from the same page. Once I get all the presentations, I'll provide you with them. Once it's ready, maybe we can submit it to slashdot for everybody who couldn't be there.
I really want to thank all of you for your participation. I not only learned a lot, I also had a really great time meeting and getting to know all of you. And I think that next time, Andi should buy the beer.
On March 18, 2002 01:03 am, you wrote:
Here's my wineconf summary. It's not much of a summary, since it's so damn long. I wanted to record as much as possible for the developers that weren't there because I think a lot of ideas and direction was generated and should be shared among the community.
Very cool idea, indeed. Thanks for taking the time to do this.
I put in <> brackets in areas where I need correction, and I am going to correct some of those myself.
I have one problem. You refer to me as Dimitry (with one exception). That is not correct, Dimitry is a guy from Russia, and he did not attend the conference. :) My name is Dimitrie, or Dimi for short.
I really want to thank all of you for your participation. I not only learned a lot, I also had a really great time meeting and getting to know all of you. And I think that next time, Andi should buy the beer.
That's a good idea. I vote for it too! :))))
Also, we need to: 1) post the pics 2) pick the best group picture, and annotate it I'll bet you the annotated picture will be the most popular thing.
When all is done, we need to make an announcement on Slashdot.
why does the site lpbn.org does not show the summary of the conference when we use netscape or mozilla ?
it's showed with Internet Explorer !!
think not everyone that uses Linux has an IE compatible web browser !
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
On Tue, 19 Mar 2002, [iso-8859-1] Sylvain Petreolle wrote:
why does the site lpbn.org does not show the summary of the conference when we use netscape or mozilla ?
Works with Konqueror...
LLaP bero
I know, but it's not a normal situation ... everyone should be able to see the entire data, particularily those that don't have Internet Explorer ... Think you don't have kde ? (like pure RedHat users)
why does the site lpbn.org does not show the
summary
of the conference when we use netscape or mozilla
?
Works with Konqueror...
LLaP bero
___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
But due to chicken-and-egg problems, running Windows apps is probably nonnegotiable for most people, so WINE is going to have to get a lot better before Linux is a threat to the desktop. I sort of expected with all the effort Corel put into it, it should be there by now, but they seem to be as far as ever from seamlessly running Win apps. (By the way, a lot of people think that the Windows API is too much of a moving target for WINE to catch up. As a Windows developer, let me say, this is rubbish. Almost every Windows app out there is tested on Win 95 to make sure it runs decently on the entire 32 bit Windows product line. If WINE could ever catch up to Win 95, they would be almost completely done. The target hasn't moved anywhere since August, 1995.)
found it here: http://www.softwaremarketsolution.com/
Igor
I'm glad for you guys you had great time there! :-)
I wanted to raise the Bugzilla topic, but waited for the license discussions to finish.
--- michael cardenas michael.cardenas@lindows.com
Dimitry brought up the issue that it is important to have small enough bugs that developers can work on them.
In this regard there should be 2 categories of bugs: a) metabugs b) tasklets
The metabugs are big and pretty much general. Good metabugs are: "Wine 0.9", "dll separation". Then we make a lot of small bugs - "tasklets" and make the metabugs depend on them.
dimitry suggested posting the top 10 or 20 bugs to wine-devel every other week, and I suggested putting the in WWN.
I'm not sure about usefullness of this one. What we need are people, responsible for Wine subsystems. Whe a bug is confirmed than it is assigned to developer (bug administrator ?), responsible for the subsystem.
A new mailing list will be created, called wine-bugs so that people can be notified of new bugs and hopefully respond to users in a timely manner.
We already have such list. It is called "wine-user" :-) Really, one of the goals of the wine-user list is to discuss issues with wine and the wine users are already signed to it! I don't want to have too many mailing lists to subscribe to.
Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/
On March 19, 2002 08:49 am, Andriy Palamarchuk wrote:
Dimitry brought up the issue that it is important to have small enough bugs that developers can work on them.
In this regard there should be 2 categories of bugs: a) metabugs b) tasklets
The metabugs are big and pretty much general. Good metabugs are: "Wine 0.9", "dll separation". Then we make a lot of small bugs - "tasklets" and make the metabugs depend on them.
Yes, that was the idea. People suggested that we create one level of metabugs, I suggested that we create as many levels as needed to get to the fine granularity of small tasklets. For example:
Wine 0.9 dll separation user func1 func2
so now, func1 becomes a tasklet bug. When a func1 is removed, we close the bug. When all functions for user are closed, user is separated, so we close that metabug. And so on, up the tree.
dimitry suggested posting the top 10 or 20 bugs to wine-devel every other week, and I suggested putting the in WWN.
I'm not sure about usefullness of this one. What we need are people, responsible for Wine subsystems.
No, this is from another perspective. And that is, getting more people into Wine devel, like the Abiword folks do. Problem is that right now the barrier to entry is enormous: the project is huge, and there is no clear list of _small_ tasks (which require little knowledge of the project). Going through Bugzilla is not an option -- few people do that. If we extract a list of 10-20 bugs, and post them on WWN, a _lot_ more people will see them, click on it, etc. It's just a way of getting people into the game, that's all.
A new mailing list will be created, called wine-bugs so that people can be notified of new bugs and hopefully respond to users in a timely manner.
We already have such list. It is called "wine-user"
I'm not sold on the benefit of a bugs list either. We aren't that many people, there's no point into slicing the traffic too much at this point.
--- "Dimitrie O. Paun" dpaun@rogers.com wrote:
On March 19, 2002 08:49 am, Andriy Palamarchuk wrote:
dimitry suggested posting the top 10 or 20 bugs to wine-devel every other week, and I suggested putting the in WWN.
I'm not sure about usefullness of this one. What
we
need are people, responsible for Wine subsystems.
No, this is from another perspective. And that is, getting more people into Wine devel, like the Abiword folks do. Problem is that right now the barrier to entry is enormous: the project is huge, and there is no clear list of _small_ tasks (which require little knowledge of the project). Going through Bugzilla is not an option -- few people do that. If we extract a list of 10-20 bugs, and post them on WWN, a _lot_ more people will see them, click on it, etc. It's just a way of getting people into the game, that's all.
Now I see. This, probably, will be more general "Call for volunteers" where will be published references to the documentation, list of the easiest bugs, references to bugzilla.
Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Yahoo! Sports - live college hoops coverage http://sports.yahoo.com/