On Tue, Apr 15, 2014 at 10:13:15AM +0300, Pekka Paalanen wrote: > On Mon, 14 Apr 2014 12:11:11 +0530 > Srivardhan M S <[email protected]> wrote: > > > Hi, > > > > I am new to Wayland, and I would like to contribute to it. I have already, > > downloaded the source code and have built it. Now reading the documentation > > for understanding. Can you pls tell me how I can start involving and > > contributing to wayland? > > Hi, > > if you have no idea where to start or any features you would like to > add, here are some suggestions specific to Weston. If you want to work > on a different compositor, or maybe toolkits, or maybe things like > SDL's Wayland support, those would be welcome, too.
Maybe adding more tests? Any particular features recently added that could benefit from tests added? Bryce > I suppose the similar principles apply. Once you pick a topic, the > people involved can better explain what's involved. > > Weston is always short of patch reviewers. You could take patches from > the mailing list, and test them. Check if they do what it says in the > description, or if you can find something that breaks. Then post your > findings as reply to the patch on the mailing list. For more > information, see: > http://wayland.freedesktop.org/reviewing.html > > You could go through the bugzilla reports and try to fix something. > > Especially if you have a non-Intel GPU, you could test various > compositors on DRM (not on top of an X server), and file bugs on any > issues you find. For example, there is already: > https://bugs.freedesktop.org/show_bug.cgi?id=75761 > > > Thanks, > pq > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
