On Thu, Apr 20, 2017 at 10:58 PM, Emil Velikov <emil.l.velikov@xxxxxxxxx> wrote:
Codebase has 700+ TODO snippets, although most of the TODO files areOn 18 April 2017 at 20:38, Daniel Vetter <daniel@xxxxxxxx> wrote:
> On Tue, Apr 18, 2017 at 02:27:14PM -0400, Rob Clark wrote:
>> On Tue, Apr 18, 2017 at 1:32 PM, Emil Velikov <emil.l.velikov@xxxxxxxxx> wrote:
>> > On 18 April 2017 at 16:48, Rob Clark <robdclark@xxxxxxxxx> wrote:
>> >> On Fri, Apr 14, 2017 at 1:04 PM, Raghav Jajodia
>> >> <jajodia.raghav@xxxxxxxxx> 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 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..
>>
>> BR,
>> -R
>>
>> [1] https://www.x.org/wiki/SummerOfCodeIdeas/
>
> Or just add a link to the TODO in the codebase here? That's essentially
> what we're doing for the kernel, at least for the cleanup/refactor tasks.
unmaintained.
The freedreno and nouveau Trello boards are in good shape, but those
are C/C++ only.
Some python ideas:
mapi/glapi:
- consolidate where applicable (there's 25 scripts) and use the
Khronos XML files.
anv/radv:
- the entrypoint generators share ~90% (before the former was
rewritten) that can be factored and reused
glsl/glcpp:
- rewrite completely - currently a python generator creates a shell
scripts which executes another python script
generic:
- use mako
- make the scripts compatible with python 2 and 3
- add generic function/class to manage input and output files in
consistent manner
- move and reuse src/mapi/glapi/gen/license.py to generate the license blorb
Sadly my python skills are quite limited so I won't be a good mentor
for either of these :-\
Hi Emil,
I am following this mailing list from months, but this thread looks could suit me :)
I am interested in pythonic tasks.
May be if you can elaborate them or can link me to some document i could start working on them one by one :)
-Emil
[1] https://cgit.freedesktop.org/mesa/tasks/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
Thanks,
Rahul jain
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
