[Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread Denis Steckelmacher
Hello, I'm a Belgian young student and I follow the Mesa's development for nearly two years now. I'm just 18 yars old and it's the first year I'm elligible to the Google Summer of Code. I originally planned to work on KDE, but I find Mesa more interesting. The project on which I would work is

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread Alex Deucher
On Mon, Mar 14, 2011 at 2:18 PM, José Fonseca wrote: > On Mon, 2011-03-14 at 10:06 -0700, Matt Turner wrote: >> On Mon, Mar 14, 2011 at 4:52 PM, José Fonseca wrote: >> > If we want a cleaner / more agile code base, then we could fork off the >> > old mesa drivers which aren't being actively maint

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread José Fonseca
On Mon, 2011-03-14 at 10:06 -0700, Matt Turner wrote: > On Mon, Mar 14, 2011 at 4:52 PM, José Fonseca wrote: > > If we want a cleaner / more agile code base, then we could fork off the > > old mesa drivers which aren't being actively maintained/tested into a > > separate branch, put them in just-b

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread Matt Turner
On Mon, Mar 14, 2011 at 4:52 PM, José Fonseca wrote: > If we want a cleaner / more agile code base, then we could fork off the > old mesa drivers which aren't being actively maintained/tested into a > separate branch, put them in just-bugfixes/no-new-features life support > mode; therefore allowin

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread José Fonseca
I also agree with Marek FWIW. If we want a cleaner / more agile code base, then we could fork off the old mesa drivers which aren't being actively maintained/tested into a separate branch, put them in just-bugfixes/no-new-features life support mode; therefore allowing greater freedom to refactor s

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread Denis Steckelmacher
Hello, Thank you for your mail, it's exactly what I need to be able to find the right GSoC project. I agree with you for most of the points, but I have some small comments. > I don't think forking the current Mesa codebase and making a > Core-profile-only state tracker is a good idea. The Open

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-14 Thread Brian Paul
Denis, I completely agree with Marek. It always sounds exciting to start with a clean slate and disregard the "old" code but I don't think it's the right move here. A very large portion of the 4.1 core profile overlaps with the code we have now and the code we need to write to support OpenGL 3.x

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-13 Thread Marek Olšák
Hi Denis, I don't think forking the current Mesa codebase and making a Core-profile-only state tracker is a good idea. The OpenGL 4.1 Core and Compatibility specifications have 518 and 678 pages, respectively, which means more than 70% of the codebase would be the same. The Core profile is not so

Re: [Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-13 Thread Corbin Simpson
Sounds quite cool. This would definitely be a worthwhile project. My only concern is that this would be too much work for a single summer. Projects should err on the side of being too small rather than too big. I'd definitely recommend applying when applications are open. On Sun, Mar 13, 2011 at

[Mesa-dev] GSoC : Thoughts about an OpenGL 4.1 state tracker

2011-03-13 Thread Denis Steckelmacher
Hello, I'm a Belgian young student and I follow the Mesa's development for nearly two years now. I'm just 18 yars old and it's the first year I'm elligible to the Google Summer of Code. I originally planned to work on KDE, but I find Mesa more interesting. The project on which I would work is