Re: Porting applications to meson
On 22.05.2017 21:39, Daniel García Moreno wrote: > > I've been today reading the meson documentation to try to port > libgepub[1], but I can't find any example of a lib with gir and all > this stuff, so I decided to wait until other libs are ported. > How about https://git.gnome.org/browse/nautilus/tree/libnautilus-extension/meson.build ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GSoC student introduction
On 27.03.2017 20:20, Owen Taylor wrote: > Hi Armin - > Hello, > Thanks for being interested in Mutter and putting forward this proposal! > > One thing you need to realize is that this is a really hard development task. > Without really working through the details, my guess is that getting GNOME to > the point where it can start without an Xwayland server running is 3-6 months > of full time work for an experienced GNOME Shell developer - someone who has > been working on this code for years. > There are several major challenges: > > 1. The GTK+ backend challenge. Mutter and GNOME Shell use various GTK+ APIs. > They use the X11 backend of GTK+ - which requires an X connection. Using the > Wayland backend to GTK+ would make no sense. So you'd either have to remove > all usage of GTK+ or add some sort of custom GNOME-private backend to GTK+. > 2. The code reorganization challenge. You'll simply need to move a lot of > stuff around. > 3. Lots of different types of residual X usage within Mutter, GNOME Shell > and GNOME more broadly that need to be addressed one by one > I was already told that. Original goals included far more than it could possibly be done by me in the GSoC period. It was trimmed down to just one goal and that is to make libmutter and an example compositor not require XWayland, ie move a lot of code around so it runs only when XWayland is available. > I think that a successful SOC project could be done around this subject, but > you need to be pretty realistic about what you can accomplish - you should > think of the outputs being: > > A) Documentation of the challenges > B) Documentation of possible approaches to each challenge, what works and > what doesn't work > C) A successful prototype that shows Mutter starting up. > Yes, this is the idea. I have updated my proposal to reflect this. Blog updates will come weekly, with information about past week challenges and accomplishments. > I would consider having a branch of Mutter code that is ready to be merged > very much a stretch goal. > > I like that you are focusing initially on just Mutter - while there are > additional challenges within GNOME Shell and the GNOME Desktop environment > that will affect how work on Mutter is done starting with just Mutter > definitely keeps things more doable. > > You'll also need to line up a possible mentor - probably one of Florian, > Jonas, Rui, or Carlos Garnacho (or Jasper, but he doesn't have much time for > Mutter work these days.) > As outlined in my proposal, Jonas and Carlos Garnacho have volounteered to be my mentors before I wrote the proposal. > - Owen > Thank you for taking your time to reply. signature.asc Description: OpenPGP digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: GSoC student introduction
On 25.03.2017 11:54, Carlos Soriano wrote: > Hello Armin, > Hi, > I'm Carlos Soriano, one of the mentors in GNOME. > This project idea looks like a key project for GNOME and I'm sure all of us > are looking forward to see it happen! > > I read your proposal and the points outlined and goals looks good. I > understand the complexity of Mutter + Wayland prevents you to have a clear > idea and timeline of it, but I think it will be better if you dig a little > more in the code and have a clearer idea of it, so a rough timeline can be > done. I think it's important to know how much time every goal will take and > what do you think you are capable of, and it's also important for us. But > again, I completely understand this is going to be difficult for this project. >> Also put a link to your previous GSoC and a link to your contributions in >> other FOSS projects so it's easier to evaluate your proposal (this is part >> of the GNOME template, would be nice to have it already since it's an >> important point for the evaluation and it can help the GNOME community to >> get excited about the you and the project :) ) I have updated my proposal to include your suggestions. Additional feedback is appreciated. Big thanks goes to Jonas, who helped me to properly word it. > > In any case, your potential mentors will help you more on the details. Feel > free to share with us the final proposal again when it's done. > > Looking forward to see your contributions! > Carlos Soriano > Thank you for taking your time to look at the proposal. > Original Message > Subject: GSoC student introduction > Local Time: March 24, 2017 9:22 PM > UTC Time: March 24, 2017 8:22 PM > From: krezovic.ar...@gmail.com > proposal which can be found at [2]. > [2] > https://docs.google.com/document/d/1C7iCqTdCZR4aLSHfACfleRFqfKRzojBHKI8C30XHs9k/edit?usp=sharing signature.asc Description: OpenPGP digital signature ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
GSoC student introduction
Hello everyone, I am Armin Krezović, and I've decided to apply to Google Summer of Code to work on Mutter. I have completed all the necessary steps outlined in [1], and also written a proposal (can be still considered as a draft), which can be found at [2]. The proposal was written trying to answer as many questions outlined in [1], but not all of them could be answered (at this point, or at all). I'd like to know if that would pose a problem, and if it could be improved somehow. I would be thankful to anyone who could take the time to quickly review the proposal. Looking forward to working with you. TIA, Armin. [1] https://wiki.gnome.org/Outreach/SummerOfCode/Students [2] https://docs.google.com/document/d/1C7iCqTdCZR4aLSHfACfleRFqfKRzojBHKI8C30XHs9k/edit?usp=sharing ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
