In this post, I’ll discuss the topic which is the focus of my internship project — adding search to the Hubs platform. The previous posts are helpful in understanding the forthcoming material since they describe the way in which the application is modeled.
Note: I’ll use the term Hubs to refer to the Fedora Hubs application and hubs for the hubs that are its constituents.
As we have seen, all data in Hubs comes from different sources and finds its place in widgets across different hubs. It is then cached and updated when obsolete using the CachedFunction mechanism described in…
In this post, I’ll try to briefly describe the widget architecture of the Hubs framework.
To put it simply, Hubs is an application that gathers data about a project in one place to make it easier for contributors to collaborate.
Since a project’s data usually resides on different platforms — e.g. Github for version control, Bugzilla for bug tracking, IRC for communication — the approach that Hubs uses to collect all of it is using special “widgets”.
These widgets hook on to the respective platform’s APIs, cache their response and listen for events that could possibly invalidate the cached data.
I’m Shaily, an Outreachy Round 15 intern at Fedora.
Outreachy is a three month internship program run by Software Freedom Conservancy — a charity that helps promote Free and Open Source Software projects.
The program is aimed at people from groups traditionally underrepresented in tech. Its goal is to “create a positive feedback loop” that supports more people to participate in free and open source software.
programming enthusiast, outreachy intern at fedora