Apply for Outreachy by Feb 22 or sign-up to mentor a project by Mar 3
Hi all, The GNOME Foundation has confirmed funding for three spots in Outreachy for the May 2021 round! Initial Outreachy applications are due by 4pm UTC on February 22, which is tomorrow. If you are interested in participating or know someone who might be, you can learn more at https://www.outreachy.org/docs/applicant/ Initial applications are relatively short, and people whose initial applications are accepted will need to work on required open source contributions with mentors between March 15 and April 16. If you would like to mentor this round, please head to https://www.outreachy.org/communities/cfp/gnome/ and submit your project idea by March 3. All project ideas need to be added in the Outreachy's application system by mentors and approved by the triage committee (Matthias Clasen, Allan Day, and Sriram Ramkrishna) and coordinators (Kristi Progri, Felipe Borges, and me) by 4pm UTC on March 7. Only ideas approved in the system by that date will be available for Outreachy this round. You can offer the same project idea for Outreachy as you are offering for Google Summer of Code (you still need to list it in the Outreachy system as described above). However, please note that the time commitment and payment amount is different for Outreachy and GSoC. For Outreachy, interns are expected to work for 40 hours for 12 of 13 weeks of the internship, or 480 hours total. There is an exception for interns whose availability is affected by anything related to COVID-19 who can choose to only work for 30 hours for 12 of 13 weeks of the internship, or 360 hours total. For GSoC, participants are expected to work 175 hours distributed in any way the participant and mentor decide over 10 weeks. Outreachy has 6,000 USD stipend regardless of where the intern is located. GSoC has 1,500 USD to 3,300 USD stipend depending on the Purchasing Power Parity value of the country where the participant is located. More on GSoC stipend amounts is at https://developers.google.com/open-source/gsoc/help/student-stipends . Because GNOME only usually has a few participants in Outreachy, we are looking to offer projects that are most strategic for GNOME. These include, but are not limited to, projects in the area of privacy, GTK+, core experience, core applications, developer experience, and development infrastructure. More information about GNOME's participation in Outreachy is available at https://wiki.gnome.org/Outreach/Outreachy . Please feel free to e-mail gnome-outreachy-l...@gnome.org , which is a private mailing list with Outreachy coordinators and mentors for GNOME, with any questions. Thanks, Marina ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Can we enforce beta release for the freeze
Hi Georges, I appreciate that, and I'm sorry my email was perhaps abrasive and that it upset you. I'll try to choose my words more carefully in the future. It really wasn't my intention to assign blame. I'm also struggling to keep plates spinning, and sometimes I drop them as well. What I want is a discussion on how we can ensure beta releases happen in the future. For example, can we do more to automate releases? Or (again, for example), could we have an automated script that emails this list with modules missing beta releases? Then even if releases are missed, people like me would at least know what to expect from the beta. On Sun, 2021-02-21 at 20:41 -0300, Georges Basile Stavracas Neto via desktop-devel-list wrote: > Hi Shaun, > > I appreciate how frustrating it is to have someone else negatively > impacting your > day work, and I'm sincerely sorry about that. I'm usually responsible > for doing > the Settings unstable releases, and Robert usually takes care of > stable releases. > I should have asked Robert to do this unstable release this time. > Unfortunately, I > cannot offer you any solid reason for this delay - it just fell > through the cracks. > > I'd like to offer another perspective: as of lately, I'm struggling > to keep all these > plates spinning. This time, one fell. After waking up unusually early > to do a > Sunday morning release, I can't say that reading this email put a > smile on my > face. > > You can try and squeeze maintainers for more, for tight schedules, > for no mistakes, > but I'm afraid this one is already dry. > > With respect, > > Em dom., 21 de fev. de 2021 às 17:18, Shaun McCance > escreveu: > > Hi all, > > > > I just wasted a whole lot of time trying to figure out why I wasn't > > seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to > > discover that gnome-control-center didn't get an upstream 40.beta > > release until a few hours ago today. > > > > This is extremely frustrating. For all practical purposes, that > > means > > the freeze actually started today, not last week, because we can't > > do > > post-freeze work on unreleased software. > > > > The freeze is pointless without beta releases, so what can we do to > > enforce that beta releases happen? > > > > Thanks, > > Shaun > > > > > > ___ > > desktop-devel-list mailing list > > desktop-devel-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Can we enforce beta release for the freeze
On Sun, 2021-02-21 at 15:47 -0500, Matthias Clasen via desktop-devel- list wrote: > > > On Sun, Feb 21, 2021 at 3:18 PM Shaun McCance > wrote: > > The freeze is pointless without beta releases, so what can we do to > > enforce that beta releases happen? > > > > > Help out with the modules that are missing releases. > > It is a small group of people doing a lot of hard work. The control > center maintainer, > Georges, is also one of the main forces behind the gnome-shell > redesign. > > And days only have 24 hours. I am sympathetic to time constraints. I really truly am. And I know I've missed releases too. But the group of people doing documentation is also very very small, and we also only have 24 hours in a day. If I take on more release responsibilities, I will have zero time to do work on documentation, which is my only real motivation to have the beta releases done. Our infrastructure for putting beta releases in front of actual humans is *so* much better than it was 20 years ago. That's in large part because some awesome folks automated a lot of stuff. But there's still a lot of human work in releases. I rolled around 10 releases last weekend, and it took me a couple hours (In part because I have to log out and back in under Xorg to roll Yelp because of old colde I haven't made the time to update.) Can we reduce or eliminate that? -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Can we enforce beta release for the freeze
Hi Shaun, I appreciate how frustrating it is to have someone else negatively impacting your day work, and I'm sincerely sorry about that. I'm usually responsible for doing the Settings unstable releases, and Robert usually takes care of stable releases. I should have asked Robert to do this unstable release this time. Unfortunately, I cannot offer you any solid reason for this delay - it just fell through the cracks. I'd like to offer another perspective: as of lately, I'm struggling to keep all these plates spinning. This time, one fell. After waking up unusually early to do a Sunday morning release, I can't say that reading this email put a smile on my face. You can try and squeeze maintainers for more, for tight schedules, for no mistakes, but I'm afraid this one is already dry. With respect, Em dom., 21 de fev. de 2021 às 17:18, Shaun McCance escreveu: > Hi all, > > I just wasted a whole lot of time trying to figure out why I wasn't > seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to > discover that gnome-control-center didn't get an upstream 40.beta > release until a few hours ago today. > > This is extremely frustrating. For all practical purposes, that means > the freeze actually started today, not last week, because we can't do > post-freeze work on unreleased software. > > The freeze is pointless without beta releases, so what can we do to > enforce that beta releases happen? > > Thanks, > Shaun > > > ___ > desktop-devel-list mailing list > desktop-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/desktop-devel-list > ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Can we enforce beta release for the freeze
On Sun, Feb 21, 2021 at 3:18 PM Shaun McCance wrote: > Hi all, > > I just wasted a whole lot of time trying to figure out why I wasn't > seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to > discover that gnome-control-center didn't get an upstream 40.beta > release until a few hours ago today. > > This is extremely frustrating. For all practical purposes, that means > the freeze actually started today, not last week, because we can't do > post-freeze work on unreleased software. > > The freeze is pointless without beta releases, so what can we do to > enforce that beta releases happen? > Help out with the modules that are missing releases. It is a small group of people doing a lot of hard work. The control center maintainer, Georges, is also one of the main forces behind the gnome-shell redesign. And days only have 24 hours. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
Can we enforce beta release for the freeze
Hi all, I just wasted a whole lot of time trying to figure out why I wasn't seeing GNOME 40 settings in both Rawhide and Tumbleweed, only to discover that gnome-control-center didn't get an upstream 40.beta release until a few hours ago today. This is extremely frustrating. For all practical purposes, that means the freeze actually started today, not last week, because we can't do post-freeze work on unreleased software. The freeze is pointless without beta releases, so what can we do to enforce that beta releases happen? Thanks, Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list
