documentation in GSoC

2011-02-03 Thread Matt Dew
I want to add documentation as an Xorg GSoC 2011 project. Should any student choose it, you guys be up for being pestered? Matt On 02/03/2011 03:10 PM, Peter Hutterer wrote: On Wed, Feb 02, 2011 at 06:50:23PM -0800, Alan Coopersmith wrote: Signed-off-by: Alan Coopersmith This should proba

Re: documentation in GSoC

2011-02-03 Thread Alan Coopersmith
Sure, but remember that GSoC projects are supposed to be equivalent to a full-time job for 3 months, so it would have to be a bit more than just fixing the documentation for a single library. Perhaps something on the order of the long dreamed about integration of the protocol specs into the XCB XM

Re: documentation in GSoC

2011-02-03 Thread Matt Dew
I didn't want to be presumptious and volunteer everyone on the list as a mentor for docs updating. Peter's reply was a nice entryway into asking people. There's lots of docs that need some lovin'. Content-wise, style-wise, xml tags update-wise. More than enough work to keep a couple people bu

Re: documentation in GSoC

2011-02-08 Thread Donnie Berkholz
On 15:04 Thu 03 Feb , Alan Coopersmith wrote: > Sure, but remember that GSoC projects are supposed to be equivalent to a > full-time job for 3 months, so it would have to be a bit more than just > fixing the documentation for a single library. Unfortunately, GSoC projects have to be coding, no

Re: documentation in GSoC

2011-02-08 Thread Matt Dew
On 02/08/2011 09:18 AM, Donnie Berkholz wrote: On 15:04 Thu 03 Feb , Alan Coopersmith wrote: Sure, but remember that GSoC projects are supposed to be equivalent to a full-time job for 3 months, so it would have to be a bit more than just fixing the documentation for a single library. Unfor

Re: documentation in GSoC

2011-02-09 Thread Peter Hutterer
On Tue, Feb 08, 2011 at 10:18:47AM -0600, Donnie Berkholz wrote: > On 15:04 Thu 03 Feb , Alan Coopersmith wrote: > > Sure, but remember that GSoC projects are supposed to be equivalent to a > > full-time job for 3 months, so it would have to be a bit more than just > > fixing the documentation