Google is offering students summer stipends to contribute to open source projects! To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
It would be cool if the Wine project put together a list of suggested projects for students to work on. It would be like http://www.winehq.org/site/contributing#devel but perhaps with a bit more guidance, and oriented around things the students can finish (and get past Alexandre!) by September 1st.
I think we should jump on this, folks.
I don't know if Wine has an 'allotment' of $4,500 stipends, but if they are on a first come, first serve basis, we should get as many as we can. And lord knows we can use more Wine hackers...
I can think of a few projects that ought to be fun and not too hard for a bright student.
How should we structure it? My first thought was that we ought to have a set of volunteers (a dreaded committee perhaps), that reviews and agrees on the tasks (so that they can be normalized a bit). I'll even volunteer :-/. Other ideas?
And I think that we indicate to Google that the task is done when: a) We, the committee agree that it accomplishes the goal AND b) Alexandre commits it.
Anyone else up for this? Dan, do you have any guidance for us?
To be candid, I'm tempted to set the bar a bit higher than with some of the other student projects you've been working on (e.g. help Ivan get copy protection working); is that out of line?
Cheers,
Jeremy
Daniel Kegel wrote:
Google is offering students summer stipends to contribute to open source projects! To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
It would be cool if the Wine project put together a list of suggested projects for students to work on. It would be like http://www.winehq.org/site/contributing#devel but perhaps with a bit more guidance, and oriented around things the students can finish (and get past Alexandre!) by September 1st.
On Tue, 2005-05-31 at 20:44 -0500, Jeremy White wrote:
To be candid, I'm tempted to set the bar a bit higher than with some of the other student projects you've been working on (e.g. help Ivan get copy protection working); is that out of line?
That may be a bit much. However, a perfect set of candidates maybe the integration projects: http://wiki.winehq.org/IntegrationProjects
We have a full range from simple to complicated, and it has a good "feel" to them as they pull things together. It's all about cooperation, and it seems to me to fall perfectly well within the spirit of this initiative.
Dimi Paun wrote:
On Tue, 2005-05-31 at 20:44 -0500, Jeremy White wrote:
To be candid, I'm tempted to set the bar a bit higher than with some of the other student projects you've been working on (e.g. help Ivan get copy protection working); is that out of line?
Sure, the bar should be higher than in the UCLA project, where all the kids had to do was contribute one conformance test.
That may be a bit much. However, a perfect set of candidates maybe the integration projects: http://wiki.winehq.org/IntegrationProjects
We have a full range from simple to complicated, and it has a good "feel" to them as they pull things together. It's all about cooperation, and it seems to me to fall perfectly well within the spirit of this initiative.
That's a nice list. Can you link to it from http://winehq.org/site/contributing#devel ?
Wikis are nice and all, but they're kind of like information ghettos unless you link to them from the outside...
After talking in the chatroom setup by Google, here's what I was able to glean:
1) We don't need to form a formal "mentoring organization" as Google calls it right now, since someone from Google (by the name of "Dan") has volunteered to process the Wine applications. That's how we got listed on the projects page. I have no idea if he is an actual Wine developer, was at WineConf, or what, but either way he's our "mentoring organization" for the moment
2) Google loves Wine. As do we all. If we can show real work, likely most of our applications will be accepted. They said they have no set limit for this stuff (IE: if they receive a ton of good apps they might allot more than they initially planned).
3) I'll try and call you at work tomorrow, unless my phone is still broken. I talked with you a bit about a Wine organization before, and I think it may be time to take the steps to create that organization ourselves - even if it's just to take over for Dan for coordinating donated student funds.
Thanks, Scott Ritchie
PS: get on IRC please :)
On Tue, 2005-05-31 at 20:44 -0500, Jeremy White wrote:
I think we should jump on this, folks.
I don't know if Wine has an 'allotment' of $4,500 stipends, but if they are on a first come, first serve basis, we should get as many as we can. And lord knows we can use more Wine hackers...
I can think of a few projects that ought to be fun and not too hard for a bright student.
How should we structure it? My first thought was that we ought to have a set of volunteers (a dreaded committee perhaps), that reviews and agrees on the tasks (so that they can be normalized a bit). I'll even volunteer :-/. Other ideas?
And I think that we indicate to Google that the task is done when: a) We, the committee agree that it accomplishes the goal AND b) Alexandre commits it.
Anyone else up for this? Dan, do you have any guidance for us?
To be candid, I'm tempted to set the bar a bit higher than with some of the other student projects you've been working on (e.g. help Ivan get copy protection working); is that out of line?
Cheers,
Jeremy
Daniel Kegel wrote:
Google is offering students summer stipends to contribute to open source projects! To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
It would be cool if the Wine project put together a list of suggested projects for students to work on. It would be like http://www.winehq.org/site/contributing#devel but perhaps with a bit more guidance, and oriented around things the students can finish (and get past Alexandre!) by September 1st.
Scott Ritchie wrote:
After talking in the chatroom setup by Google, here's what I was able to glean:
- We don't need to form a formal "mentoring organization" as Google
calls it right now, since someone from Google (by the name of "Dan") has volunteered to process the Wine applications. That's how we got listed on the projects page. I have no idea if he is an actual Wine developer, was at WineConf, or what, but either way he's our "mentoring organization" for the moment
Dan has asked us, the Wine Project, to help him come up with a list of good projects. I'm responding to his request for help.
I don't think we need a 501(c) organization to do this; I think Dimi can do it all <grin>. Seriously, I think we have plenty of volunteers to give Dan the idea set he needs, and we have a very nice criteria for completion - a commit by Alexandre.
Dimi, my issue is that I don't think we want to set the bar too low. I don't think an easy integration project is appropriate. Maybe I'm wrong, but I at least think it would be cool if these led to some very meaningful and truly useful improvements to Wine, and perhaps to a new talented student getting hooked on Wine.
Cheers,
Jeremy
On Tue, 2005-05-31 at 22:07 -0500, Jeremy White wrote:
Dimi, my issue is that I don't think we want to set the bar too low. I don't think an easy integration project is appropriate. Maybe I'm wrong, but I at least think it would be cool if these led to some very meaningful and truly useful improvements to Wine, and perhaps to a new talented student getting hooked on Wine.
Well, I'm not opposed to your copy-protection idea, I just think its a very special sort of project to ask of somebody. But this is all irrelevant I think, we should setup a pool of projects so that interested students can pick whatever tickles their fancy.
And yes, I agree the bar shouldn't be too low. But on the integration page we have a number of cool, fun, not-all-that-easy projects that would be very good for wine to have: * http://wiki.winehq.org/KernelHandleSupport * http://wiki.winehq.org/ThemingSupport * http://wiki.winehq.org/MozillaIntegration * http://wiki.winehq.org/DIBEngine * http://wiki.winehq.org/SingleSignOn * http://wiki.winehq.org/SoftWinelib
Also, we can add stuff like: * jscript.dll reimplementation using the Mozilla JScript * A new DLL maybe?
Dimi Paun wrote:
And yes, I agree the bar shouldn't be too low. But on the integration page we have a number of cool, fun, not-all-that-easy projects that would be very good for wine to have:
I doubt that a newbie could do that to anybody's satisfaction.
- http://wiki.winehq.org/ThemingSupport
- http://wiki.winehq.org/MozillaIntegration
- http://wiki.winehq.org/DIBEngine
- http://wiki.winehq.org/SingleSignOn
- http://wiki.winehq.org/SoftWinelib
Also, we can add stuff like:
- jscript.dll reimplementation using the Mozilla JScript
How about implementing hhctrl.ocx and hh.exe? That would give us code that exercises the IE6 embedding features of shdocvw, and the basis of code for a propper browser...
Or else, complete the integration with Gnome, so that we have a Gnome VFS library that can recreate the Windows menu heirachy, without having to resort to the wineshelllink hack.
Mike
On Wed, 2005-06-01 at 13:02 +0900, Mike McCormack wrote:
Or else, complete the integration with Gnome, so that we have a Gnome VFS library that can recreate the Windows menu heirachy, without having to resort to the wineshelllink hack.
Good idea for the integration page, mind creating a page for it?
On Wed, 01 Jun 2005 00:10:11 -0400, Dimi Paun wrote:
On Wed, 2005-06-01 at 13:02 +0900, Mike McCormack wrote:
Or else, complete the integration with Gnome, so that we have a Gnome VFS library that can recreate the Windows menu heirachy, without having to resort to the wineshelllink hack.
Good idea for the integration page, mind creating a page for it?
That won't work, GNOME doesn't use gnome-vfs for menu creation anymore. We have to use wineshelllink and keep them synchronized.
thanks -mike
On 5/31/05, Dimi Paun dimi@lattica.com wrote:
Also, we can add stuff like:
- jscript.dll reimplementation using the Mozilla JScript
- A new DLL maybe?
Along similar lines, Google's Picasa2 works really well with Wine. The main missing feature is MAPI stuff to email pictures. Jon, you worked on that recently, any idea how reasonable it is to tackle that stuff or what the to-do list would look like?
-Brian
Hello.
I was talking with my cousin about Google "Summer of Code" and he is interesting in working on Wine. The problem is what he could do. He'd like to work on a translation tool with UI for rc files (say winetranslator). AFAIK there is no open source project like this and, as the state of translation is not really good , it would be useful for Wine. If we had such tool more people could help us as they wouldn't need to know anything about rc files ( I have no idea if this tool will be able to change things like size of controls, which is useful for translation, but it's not so important). What do you think? Should he look for something else or can he go for it?
Jacek
Maybe he could reuse the code of poedit (http://www.poedit.org/) and just change the parsing/writing part to handle rc files instead of po's ?
This tool is quite good for translating language files (it can make automatic proposal from reading other files in the same or other projects and has spellchecking among other features).
jonathan
Le jeudi 02 juin 2005 à 16:59 +0200, Jacek Caban a écrit :
Hello.
I was talking with my cousin about Google "Summer of Code" and he is interesting in working on Wine. The problem is what he could do. He'd like to work on a translation tool with UI for rc files (say winetranslator). AFAIK there is no open source project like this and, as the state of translation is not really good , it would be useful for Wine. If we had such tool more people could help us as they wouldn't need to know anything about rc files ( I have no idea if this tool will be able to change things like size of controls, which is useful for translation, but it's not so important). What do you think? Should he look for something else or can he go for it?
Jacek
On Thu, 2 Jun 2005, Jonathan Ernst wrote:
Maybe he could reuse the code of poedit (http://www.poedit.org/) and just change the parsing/writing part to handle rc files instead of po's ?
I think a better way would be to extend po4a to handle RC files. This would allow the use of any po tool to perform the translation.
The tricky part (in all of these schemes really) is knowing how to handle the coordinates. They'd have to be put in the msgid together with the actual stuff to translate. But in fact you can't know what to set the coordinates to unless you see a graphical representation of the dialog... This would mean we need a real resource editor :-/
Just a late night random thought.
The tricky part (in all of these schemes really) is knowing how to handle the coordinates. They'd have to be put in the msgid together with the actual stuff to translate. But in fact you can't know what to set the coordinates to unless you see a graphical representation of the dialog... This would mean we need a real resource editor :-/
Having an open source graphical resource editor would be usefull for more than just translating WINE dialogs :)
On Fri, 03 Jun 2005 12:09, Jonathan Wilson wrote:
The tricky part (in all of these schemes really) is knowing how to handle the coordinates. They'd have to be put in the msgid together with the actual stuff to translate. But in fact you can't know what to set the coordinates to unless you see a graphical representation of the dialog... This would mean we need a real resource editor :-/
Having an open source graphical resource editor would be usefull for more than just translating WINE dialogs :)
Has anyone considered approaching the OpenWatcom team to see about getting a fork of the OpenWatcom resource editor released under the LGPL?
Or at the least, studying it to see how a resource editor differs from a bog-standard graphics editor like kpaint.
Just a thought.
Wesley Parish
Francois Gouget wrote:
But in fact you can't know what to set the coordinates to unless you see a graphical representation of the dialog... This would mean we need a real resource editor :-/
I dont have a way of testing it under wine, but a good resource editor (that actually mentions translating stuff quite frequently) is Restorator.. http://www.bome.com
Of course it is shareware, but at least it could be used to edit windows binaries..
Or am I missing the point?
Dustin
Am Dienstag, den 31.05.2005, 23:44 -0400 schrieb Dimi Paun:
would be very good for wine to have:
- http://wiki.winehq.org/KernelHandleSupport
- http://wiki.winehq.org/ThemingSupport
- http://wiki.winehq.org/MozillaIntegration
- http://wiki.winehq.org/DIBEngine
- http://wiki.winehq.org/SingleSignOn
- http://wiki.winehq.org/SoftWinelib
Also, we can add stuff like:
- jscript.dll reimplementation using the Mozilla JScript
- A new DLL maybe?
printui.dll with ghostscript to get Windows Printer-Driver working via wine
msnp32.dll / netali32.dll: Get the "Microsoft Network" - Client working with libsmbclient.so ?
On Tue, 31 May 2005 22:07:44 -0500, Jeremy White wrote:
my issue is that I don't think we want to set the bar too low. I don't think an easy integration project is appropriate. Maybe I'm wrong, but I at least think it would be cool if these led to some very meaningful and truly useful improvements to Wine, and perhaps to a new talented student getting hooked on Wine.
We need more people working on app compatibility! :) Maybe we can choose some apps that are "nearly there" and get people to solve the last few bugs or alternatively make one of the projects "Bring any 3 apps up to Gold status in the appdb".
Really not enough Wine hackers these days (IMHO) bash away and fixing popular apps ... we have a lot of infrastructure and janitorial work going on at times, as well as filling out DLLs - all this is important but being able to run apps doubly so!
thanks -mike
Hello,
We need more people working on app compatibility! :) Maybe we can choose some apps that are "nearly there" and get people to solve the last few bugs or alternatively make one of the projects "Bring any 3 apps up to Gold status in the appdb".
I've a few app suggestions: Half-Life 1 (+Mods like Counter-Strike) Star Wars Jedi Knight Jedi Academy Star Wars Jedi Knight Jedi Outcast Warcraft III Microsoft Visual Basic Microsoft Visual C++ UltraISO Quicktime player Anno 1602
Most Apps need only minor patches, except the 2 Star Wars games and Warcraft III, which need Installshield to work with builtin dlls. Is there any official Documentation what 'Gold status' means? I understand that the app installs and runs on a fresh wine installation without any config file changes and without installing any apps/libs that come with windows(IE, dcom, ...).
Really not enough Wine hackers these days (IMHO) bash away and fixing popular apps ... we have a lot of infrastructure and janitorial work going on at times, as well as filling out DLLs - all this is important but being able to run apps doubly so!
I have the plan to get this apps to Gold status one day, but up to now I only made sure that there were no regressions and that these apps keep running as they did with the past wine versions. Once an app reaches Gold status, the biggest problem is to make sure that there are no regressions.
I'll to check Googles "Summer of Code", it looks interesting to me :-)
Stefan
On Wed, Jun 01, 2005 at 03:11:49PM +0000, Stefan D?singer wrote:
Anno 1602
different sources in the net say, that the game works without problems and the last time i tried it worked. the places telling it works, say so for about 3 years. i guess the game is hardly to buy nowadays and its successor is already in the shelfs for about 2 years or so (or even no longer in the shelfs). not to mention that as any game made in germany there was a big market outside the EU.
Most Apps need only minor patches, except the 2 Star Wars games and Warcraft III, which need Installshield to work with builtin dlls.
games in general are hard to make them work out of the box due to the copy protections; once the vendor decides to remove the copy protection in a patch this is something else - but i doubt, that this three games work without a "no cd crack".
Am Mittwoch, 1. Juni 2005 14:59 schrieb Christoph Frick:
On Wed, Jun 01, 2005 at 03:11:49PM +0000, Stefan D?singer wrote:
Anno 1602
different sources in the net say, that the game works without problems and the last time i tried it worked. the places telling it works, say so for about 3 years. i guess the game is hardly to buy nowadays and its successor is already in the shelfs for about 2 years or so (or even no longer in the shelfs). not to mention that as any game made in germany there was a big market outside the EU.
Installer issues... The builtin installer works for the base version, the extensions installer fails. There's an install shield based installer for win2k, which has the usual install shield problems.
Most Apps need only minor patches, except the 2 Star Wars games and Warcraft III, which need Installshield to work with builtin dlls.
games in general are hard to make them work out of the box due to the copy protections; once the vendor decides to remove the copy protection in a patch this is something else - but i doubt, that this three games work without a "no cd crack".
For Warcraft III a no cd crack is indeed necessary, but the 2 others don't need one. With the base version of Jedi Knight Jedi Academy the single player .exe file complains about an debugger, but that chack is removed in the 1.01 update :-). Multiplayer works out of the box.(except the installer issues).
Half-Life needs a patch which makes it's main window managed, otherwise it's neccessary to activate Desktop mode.
So if one doesn't count the install shield problems, these games are nearly there. It would be nice to have these 'nearly there' apps working out of the box, it simply makes a much better impression to the user. For example Half-Life: Instally nice, runs better than on Windows*. But if a newbe has to create a config file to make the main menu work, than this leaves an unnecessary bad impression.
*For me, because there are incompatiblities between the Windows ATI graphics driver and the Half-Life engine. Anyone here who blames ATI for not being capable of writing good Linux drivers? I also blame them for not being able to write good Windows drivers.
Cheers, Stefan
Hi everybody,
On Mittwoch 01 Juni 2005 03:44, Jeremy White wrote:
I think we should jump on this, folks.
...this is about the perfect moment to hopefully get one of my projects up and running: Wine in Academics[tm]. As some of you might know, we (ITOMIG) have a nice working agreement with professor Spruth at Tübingen university. He's willing to supervise academic projects based on Wine. So far, we have Michael, who's starting his work on the subject of porting Windows-based applications using the Winelib.
I intended give a talk to students about Wine and possible ways of doing e.g. a Master's thesis based on Wine, on june 13. The Google stipends are a very pleasant surprise that might help me in convincing people ;) However, I think as the Summer of Code applications must be made before june 14, I'll try to move that to next monday (june 6). For that purpose, I'd be very happy if you could help us in brainstorming and coming up with some ideas for cool projects. I'd present some of those ideas on monday, too, and I'll advertise all Wine-based candidates for the SOC at my faculty.
I have created a Wiki page at http://wiki.winehq.org/WineInAcademics that describes what kind of work would make good projects here - "Studienarbeit" and "Diplomarbeit" don't seem to have very good equivalents in the US system. However, a Diplomarbeit corresponds approximately to a Master's thesis, and I think almost all projects that fit into the Summer of Code would make at least a nice Studienarbeit, or maybe even serve as a good basis for a Diplomarbeit.
I can think of a few projects that ought to be fun and not too hard for a bright student.
That's great! I've taken myself the liberty of creating a Wiki page for project proposals, in order to make it easier to keep track of them. Volia: http://wiki.winehq.org/SummerOfCode
How should we structure it? My first thought was that we ought to have a set of volunteers (a dreaded committee perhaps), that reviews and agrees on the tasks (so that they can be normalized a bit). I'll even volunteer :-/. Other ideas?
Sounds good to me. Maybe it would be wise to first collect many ideas, and then make a selection for the SOC. Projects that are not selected might make a good base for other academic works or similar things, so I would be sad to see good ideas lost, even if they don't fit perfectly.
Cheers,
David
On 6/1/05, David Gümbel david.guembel@gmx.de wrote:
Sounds good to me. Maybe it would be wise to first collect many ideas, and then make a selection for the SOC. Projects that are not selected might make a good base for other academic works or similar things, so I would be sad to see good ideas lost, even if they don't fit perfectly.
Hello All,
The ToDo list is still up at : http://www.winehq.org/site/status_todo It has some of the same general tasks that have been brought up here and some others that haven't. The list was last updated about four months ago and I believe everything listed is still relevant.
Tom
Cheers,
David
Jeremy White jwhite@codeweavers.com writes:
How should we structure it? My first thought was that we ought to have a set of volunteers (a dreaded committee perhaps), that reviews and agrees on the tasks (so that they can be normalized a bit). I'll even volunteer :-/. Other ideas?
And I think that we indicate to Google that the task is done when: a) We, the committee agree that it accomplishes the goal AND b) Alexandre commits it.
Just to let people know, we have now organized an "official" committee composed of Jeremy, Dimi, Lionel, Dan Kegel and myself. We'll be reviewing the applications that Google forwards to us. So now if your application gets rejected you know who's to blame ;-)
On Tue, 31 May 2005 17:31:00 -0700, Daniel Kegel wrote:
It would be cool if the Wine project put together a list of suggested projects for students to work on.
Johan Dahlin suggested GTK+ theming integration as a project on IRC, and I agree that this would probably be about the right level of difficulty/work. Or rather, supporting theming in our widget toolkit, even if the actual GTK+ bridge wasn't written.
thanks -mike
Johan Dahlin suggested GTK+ theming integration as a project on IRC, and I agree that this would probably be about the right level of difficulty/work. Or rather, supporting theming in our widget toolkit, even if the actual GTK+ bridge wasn't written.
IMO, such "themeing" should be done via a suitable implementation of the UXTHEME dlls (and related functionality) with the GTK+ theming integration being implemented as a "theme" file (AFAIK a theme file is just a windows DLL file with special stiff in it).
Although since doing it The Right Way would probobly require SxS/Activation Context/etc support in WINE, it might be harder :)
On Mittwoch 01 Juni 2005 02:31, Daniel Kegel wrote:
To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
JFTR, is that June 14th or June 24th? Google's webpage says 14th, but maybe I got something wrong.
Cheers,
David
On 6/1/05, David Gümbel david.guembel@gmx.de wrote:
On Mittwoch 01 Juni 2005 02:31, Daniel Kegel wrote:
To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
JFTR, is that June 14th or June 24th? Google's webpage says 14th, but maybe I got something wrong.
Cheers,
David
It's the 14th. Originally the site said the 24th and the PDF said the 14th, it was fixed.
Chris Debona clarified that on Slashdot; there was an error; it's supposed to be the 14th.
David Gümbel wrote:
On Mittwoch 01 Juni 2005 02:31, Daniel Kegel wrote:
To qualify for a stipend, you have to submit a proposal by June 24th, and the proposal has to be approved. See http://code.google.com/summerofcode.html
JFTR, is that June 14th or June 24th? Google's webpage says 14th, but maybe I got something wrong.
Cheers,
David
On 5/31/05, Daniel Kegel dank@kegel.com wrote:
Google is offering students summer stipends to contribute to open source projects!
As part of the Summer of Code, Google will be giving each project $500 for each proposal that gets accepted.
Right now the Wine Party Fund is doing ok. What do you guys think about contributing $250 of the $500 back to the developer as an extra incentive? It might give people extra incentive to work on Wine. Tom Wickline pointed out that might be seen as cheating by the other projects, but I think it's pretty fair.
-Brian
On Wed, 2005-06-01 at 16:55 -0600, Brian Vincent wrote:
As part of the Summer of Code, Google will be giving each project $500 for each proposal that gets accepted.
Right now the Wine Party Fund is doing ok. What do you guys think about contributing $250 of the $500 back to the developer as an extra incentive? It might give people extra incentive to work on Wine. Tom Wickline pointed out that might be seen as cheating by the other projects, but I think it's pretty fair.
I think 4500 is enough -- adding another 250 can't make that much of a difference anyway (~5%). We can use that money for the next WineConf, it's not like we have too much in the Party Fund.
Brian Vincent wrote:
On 5/31/05, *Daniel Kegel* <dank@kegel.com mailto:dank@kegel.com> wrote:
Google is offering students summer stipends to contribute to open source projects!
As part of the Summer of Code, Google will be giving each project $500 for each proposal that gets accepted.
Right now the Wine Party Fund is doing ok. What do you guys think about contributing $250 of the $500 back to the developer as an extra incentive?
I don't think that's allowed. Here's what Chris DiBona replied to a similar question:
--- snip --- No. This is not right. Every student gets 4500$, not 5k. If KDE doesn't want the $500 stipend they can either not take part in the Summer of Code program, not accept the money, or donate it, themselves to another organizations.
If in fact I learn of a sideways payment to a student, KDE and the Student will not be allowed to take part and their students will be reassigned. --- snip ---
The $500 is meant to compensate the mentor for his/her time. It's not always easy shepherding a newbie through the process of getting code developed and submitted. - Dan