Builder started out as a prototype for a new IDE. It is under development an IDE solely targeting GNOME applications. This talk will discuss some ideas and plans for the project and fundamental design features such as a multi-process application, simulators, GNOME SDK’s, auto-completion, code-highlighting, and more.
Christian is a database engineer at MongoDB living in San Francisco, California. He can often be found prototyping developer tools, building cars, and driving the California coast.
Input methods are an important part of a desktop because writing text is one of the most important daily activities of any user.
The talk will focus on evolution/history of input frameworks and the future towards Wayland integration with GNOME.
Firstly, we will introduce a new library which provides a minimal core functions of input method frameworks. In general, input method frameworks with long history have many portability hacks to provide consistent user experience under different environments (X11, GTK+, Qt, etc.). The minial core library could make it easier to port input methods to new platform, like Wayland.
Secondly, we will talk about integration of text prediction features into input methods and desktop as a whole. Most of the input methods provides API’s for text prediction and spell checking, so this talk would explain how we can improve text prediction and spell checking so that users will get native text prediction experience.
Caribou, Gettext, IBus, libkkc, Debian maintainer
GNOME Foundation member
IBus, ibus-typing booster maintainer
Fedora packager, GNOME Foundation member
Flow based programming is a programming paradigm that defines
applications as networks of “black box” processes, which exchange data
across predefined connections by message passing.
based programming (FBP) that provides both libraries to implements the
“black box” responsible for the computation part and a UI to describe
the connections between them.
This talk will focus on the integration between Gnome and NoFlo (https://github.com/noflo/noflo-gnome) to show new ways of creating applications for Gnome in a flow based way.
Lionel Landwerlin is a software engineer and has been involved with a number of projects using software components from the Gnome project.
Cheese has seen many upheavals over the years, such as being split into a library and UI, and the UI being ported to Vala. The library part was always problematic, especially once it started to be used by other applications. Now is a good time to simplify the API and remove it from Cheese once and for all.
This talk will cover the history of an unloved API, the shiny service which will replace it, and finally a future of portals.
David has been involved in GNOME for several years, and maintains EasyTAG, Cheese and Logs. He is an honorary member of the documentation team, and enjoys build systems and static analysis.
GNOME has always been a controversial project due to the decisions they make, the positions they hold, and thus our relationship with FOSS community at times in conflict.
Outreach both internal and external is about defending our story and not allowing others to write it for us. Let’s talk about how we can better present ourselves to the public in the age of social media and reduce the conflict that we have while continuing to pursue our goal of being a competitive desktop based on Free Software and our mission to spread Free Software.
Sri Ramkrishna joined the GNOME project in 1997, and has held various positions from irc water cooler guy, GNOME Journal, and other things. From 2011, Sri has been primarily been interested in engagement with the FOSS community and also runs the GNOME QA team. He’s currently a GNOME Foundation Board member.
We seldom know exactly why one release of GNOME is faster or slower than the last. We have various tests we can run to measure performance, but comparing results for one release with results from a previous release provides less clarity than one might hope. Even if hardware is exactly the same, there are many elements in the software stack – from the kernel, to the graphics drivers, to the toolkits, to the application itself, that can produce performance changes. From one release of GNOME to the next, each of these layers sees hundreds or thousands of changes.
It is much more useful if we can get performance numbers continuously as changes go into the codebase. We will then have a better chance of identifying a change that slows down GNOME or verifying whether if a change that was supposed to improve performance actually did. We already have a system that does continuous builds of GNOME and runs basic tests on them: GNOME Continuous. The tests that GNOME Continuous runs are, however, run on virtual machines, which poses multiple challenges for performance testing – in particular, lack of accelerated graphics, and interference from other use of the same system.
This talk will describe the new GNOME Hardware Testing initiative, which has a goal to take the builds of GNOME and base system software that GNOME Continuous creates, measure the performance on a range of performance tests, record the results, and make charts and graphs of that data available to developers. The talk will discuss technology used: how ostree is used to distribute software to the testing systems, and how upgrading, rebooting, and testing is automated to eliminate any need for manual intervention, while still allowing stock commodity hardware to be tested. It will also cover the selection of appropriate tests to reflect the performance of GNOME in a comprehensible way.
Owen Taylor has been active in the development of GNOME technologies since before GNOME existed. He maintained GTK+ and related libraries, created Pango, which enables GNOME to handle the languages of virtually all of the world’s users, and more recently led the development of GNOME Shell prior to the release of GNOME 3. His current interests relate to display technologies and the full-stack performance of GNOME. Owen is Architect for the Emerging Platform team at Red Hat, which includes the desktop and other related areas.
When we think about the user experience that GNOME provides, we usually focus on implementation and design. It is these factors that are thought to affect the quality of the experience that we provide. However, social factors also play a major role in determining the quality of our software: modules need a sufficient number of contributors, and they need to be organised so that modules can move forward and keep on top of bugs.
In this talk, I’m going to discuss how the social dimension of the GNOME project affects the quality of our software. I will outline some issues with the current situation, and will propose some ideas and initiatives that can help us address them. In doing so, I hope to demonstrate that we need to work on the social as well as the technical aspect of GNOME if we want to improve the quality of our user experience.
I have been contributing to GNOME for 4 or 5 years. I spend most of my time on design, and am a member of the design team, but I also contribute to the Engagement Team. I’ve been working as a part of the Red Hat Desktop Team for almost 3 years.
This presentation will look at how hardware is integrated in GNOME in general, and in Linux in particular, with an eye on the infrastructure changes that occurred to implement the level of integration expected in a modern desktop environment.
Bastien chooses his hardware like a kid writing his Christmas letter to Santa. But he also likes that hardware to work to its full potential. Thankfully, Red Hat, his employer, supports that goal, even providing hardware when necessary.
Fleet Commander is a new project lead by Matthew Barnes and co-developed by Alberto Ruiz that attempts to turn GNOME 3 in the best desktop for sysadmins and large deployments.
It’s core functionality provides the tools neccessary to create configuration profiles through a web interface and deploy those profiles upon users, groups or hosts. Moving forward it intends to provide extended funcionality such as lockdown settings to prevent users from accessing certain apps, adding bookmarks to the web browser or deploy online accounts automagically.
We will present Fleet Commander’s design and roadmap.
Alberto Ruiz works at Red Hat as the engineering manager of the Evolution, LibreOffice, Firefox and now Fleet Commander teams.
Previous to Red Hat he worked at several GNOME related companies as an engineer such as Canonical, Codehtink and Sun Microsystems.
He was born and raised in Gran Canaria, Spain.
In the new GNOME 3.x series we have been working on a new set of core applications for finding and selecting the user’s content. Each application is generically named, tailored to the kind of content that it is meant to handle, and integrates tightly with the cloud and network services. This talk will be about Documents and Photos. We will present the current status of these applications, the high-level design and thoughts behind having them, and shiny plans for the future.
I got my GNOME git account roughly 4 years ago. Currently I maintain the online accounts integration in GNOME, and a couple of new core applications (ie. gnome-documents and gnome-photos). I have been working as a part of the Red Hat Desktop Team since March 2012.