X.org EVoC Ideas

[Dylan Baker]

Quoting Rob Clark (2017-04-18 11:27:14)
> On Tue, Apr 18, 2017 at 1:32 PM, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> > On 18 April 2017 at 16:48, Rob Clark <robdclark at gmail.com> wrote:
> >> On Fri, Apr 14, 2017 at 1:04 PM, Raghav Jajodia
> >> <jajodia.raghav at gmail.com> wrote:
> >>> Hi there
> >>>
> >>> I am Raghav Jajodia, an Engineering student from India. While going through
> >>> the X.org foundation, I felt that X.org is a great community for new Open
> >>> Source developers. I am deeply interested in being a part of the community.
> >>> Although, while going through the GSoC and EVoC Ideas, I found that all the
> >>> ideas revolve around C, C++, QT or Compilers.
> >>>
> >>> Working extensively on Web, Moile and Desktop applications, I have gained
> >>> good experience with Python, JS, PHP, Ruby etc. But I do not have any
> >>> experience with C/C++.
> >>>
> >>> So, is not possible for a student to participate in EVoC if he doesn't have
> >>> any experience with Open source softwares built on C/C++. Are there any
> >>> project ideas using languages apart from C/C++ that a student can work on
> >>> for EVoC 17/18?
> >>
> >> Hi, the only requirement regarding programming languages is that
> >> "Applicants know their target programming language."..  there isn't
> >> any requirement otherwise, but I think the fast majority are largely
> >> C/C++.  There are bits of python here and there (piglit, for example..
> >> possibly others that I don't know of).
> >>
> >> From a quick look all of the suggested projects involve C and/or C++.
> >> But that doesn't mean a candidate couldn't suggest a different project
> >> that is not on the list.
> >>
> > FWIW the python in piglit is fine, while the one in Mesa is in a dire shape.

I tend to agree, the only thing that might be useful (and I'd want to see a
proposal of what and how because it would need to be really good) is to overhaul
the piglit summary html tool to be not so awful. Someone with a good grasp of
javascript could probably make that webpage not a 25mb monstrosity that actually
loaded in a reasonable amount of time.

> 
> I didn't realize there where TODO's for py involved in mesa build..
> maybe we should add some to the SummerOfCodeIdeas wiki page[1]
> 
> /me would add convert nir_intrinsic.h + multiple #includes to .py
> generating .c and .h if there was such a topic..  maybe not enough for
> a EVoC/GSoC project on it's own but perhaps if combined w/ some other
> work needed on mesa's python..

The only large one I'm aware is to convert the mapi/glapi generators to use the
khronos XML and not the handwritten XML we use currently. It's been on my radar,
but I haven't really gotten started on it. Presumably sub-requirements of that
would be to use mako instead of `print`s and to be at least close to python3
ready (i.e., a complete rewrite). There's also what has been described as a
fairly simple C project to rip out a level of abstraction in that subsystem.

There's also a bunch of smaller projects to convert the other generators to be
python2/3 hybrid ready (since python 2 is *finally* starting to get the boot in
distros), and to use mako (where applicable). Some of these are really awful,
some of them are pretty good.

Dylan

> 
> BR,
> -R
> 
> [1] https://www.x.org/wiki/SummerOfCodeIdeas/
> 
> 
> > That said, I believe Rob summarised it perfectly:
> > Take a look around and feel free to propose something if the ones
> > listed do not interest you.
> >
> > Regards,
> > Emil
> _______________________________________________
> dri-devel mailing list
> dri-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20170419/a7c580be/attachment-0001.sig>