18 Sep 2020

feedPlanet Ubuntu

The Fridge: Call for Ubuntu Community Council nominations

As you may have noticed, the Ubuntu Community Council has been vacant for a while. Happily, a decision has recently been made to repopulate it. Thus, this official announcement for nominations.

We will be filling all seven seats this term, with terms lasting two years. To be eligible, a nominee must be an Ubuntu Member. Ideally, they should have a vast understanding of the Ubuntu community, be well-organized, and be a natural leader.

The work of the Community Council, as it stands, is to uphold the Code of Conduct throughout the community, ensure that all the other leadership boards and council are running smoothly, and to ensure the general health of the community, including not only supporting contributors but also stepping in for dispute resolution, as needed.

Historically, there would be two meetings per month, so the nominee should be willing to commit, at minimum, to that particular time requirement. Additionally, as needs arise, other communication, most often by email, will happen. The input of the entire Council is essential for swift and appropriate actions to get enacted, so participation in these conversations should be expected.

As you might notice from Mark Shuttleworth's post, there is a greater vision for the structure of the Ubuntu community, so this term could be an exciting time with perhaps vast and sweeping changes. That said, it would be wise that nominees have an open mind as to what is to come.

To nominate someone (including yourself), send the name and Launchpad ID of the nominee to community-council [AT] lists.ubuntu.com. Nominations will be accepted for a period of two weeks until 29 September 2020 11:59 UTC.

Once the nominations are collected, Mark Shuttleworth will shortlist them and an actual election will take place, using the Condorcet Internet Voting Service . All Ubuntu Members are eligible to vote in this election.

If you have any other questions, feel free to post something in the Ubuntu Discourse #community-council category so all may benefit from the answer.

Thanks in advance to all that participate and for your desire to make Ubuntu better!

18 Sep 2020 7:32pm GMT

Ubuntu Blog: The Expandables – snapcraft extensions and the secret code

If you're a snap developer, you know that snap development is terribly easy. Or rather complex and difficult. Depending on your application code and requirements, it can take a lot of effort putting together the snapcraft.yaml file from which you will build your snap. One of our goals is to make snap development practically easier and more predictable for everyone. To that end, we created a framework of snap extensions, designed to make the snap journey simpler and more fun.

In a nutshell, extensions abstract away a range of common code declarations you would normally put in your snapcraft.yaml file. They help developers avoid repetitive tasks, reduce the knowledge barrier needed to successfully build snaps, offer a common template for application builds, and most importantly, save time and effort. But what if you want - or need - to know what is behind the abstraction?

Expand your horizons, expand your extensions

Let's examine a real-life example. Just a few weeks ago, Jonathan Riddell and I did a workshop on how to build snaps during KDE Akademy. We demonstrated with KBlocks, and the snapcraft.yaml file references the kde neon extension, which makes the latest Qt5 and KDE Frameworks libraries available to KBlocks at runtime. The necessary code block [sic] is as follows:

adopt-info: kblocks
- kde-neon
common-id: org.kde.kblocks.desktop

But we need to see what happens behind the scenes.

You can expand an extension declaration in any snapcraft.yaml file by running:

snapcraft expand-extensions

This command will look for the snapcraft.yaml file in the current directory or snap subdirectory, and print to the standard output the expanded version of the YAML file. You can redirect the output into a separate file, and then compare the two to understand what gives.

The diff is greener on the other side

The expand-extensions command does quite a bit. First, we can see that the declaration of the extension for the kblocks app in the YAML has been removed. Then, we can also see that the expanded file has several additional plugs declared, namely desktop, desktop-legacy, wayland, and x11. Another important element is the desktop-launch command, which contains a number of common environment configurations to make sure the application runs correctly.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh4.googleusercontent.com/XC7l3swl0B2Rfo4O4MFu0OVobu5oW-CfEcy5S2AhlJWcZclk7hpfM2WvvIVFZp9EEqbhlxHhD0wfrSphLX26RNodrWow5Wf32WbaX5uk8459vAClmcrbFzy59qEZJskGgTNAyaGR" width="720" /> </noscript>

Original YAML on the left, the expanded version without the extension on the right. For brevity, only part of the complete snapcraft.yaml file is shown.

The biggest difference is an entire new block of code at the bottom of the YAML - not visible in the screenshot above, but you can just grab the KBlocks snapcraft.yaml file we used in the workshop, and try for yourself:

- g++
plugin: make
source-subdir: kde-neon
default-provider: gtk-common-themes
interface: content
target: $SNAP/data-dir/icons
content: kde-frameworks-5-core18-all
default-provider: kde-frameworks-5-core18
interface: content
target: $SNAP/kf5
default-provider: gtk-common-themes
interface: content
target: $SNAP/data-dir/sounds

As you can see from the example above, extensions not only save time, they also ensure your snaps use a consistent structure, containing all the required assets to look and run correctly. You also end up with smaller snaps, because the common components and libraries are already included in the content snaps. This can be quite useful, especially if you develop multiple applications that share common code, as is the case with the KDE software.

What's next?

Now, you may actually have a use case that only requires a portion of the code shown above, or you want to understand how extensions work behind the scenes. You can expand existing YAML files, and then use the relevant snippets as you sit. Overall, the use of extensions, in full or in part, should help you make snaps with a more consistent theming, smaller size, and more predictable behavior, as you baseline against a well-tested set of packages used across a large number of applications.


Extensions and the associated expand command allow you to make best use of the snapcraft.yaml files, whether to learn new things, or to adopt existing code for your own needs. You may already have snaps published in the Snap Store, and you would like to improve your code. Indeed, we encourage developers to use the extensions, as they can help avoid various papercut issues in the look & feel of their applications, as well as reduce the development burden, as they need to maintain a smaller, more compact, more precise code base.

If you have any questions or suggestions on this topic, please join our forum for a discussion. In particular, if you can think of practical use cases that would warrant a creation of new extensions, we'd definitely like to hear from you.

Photo by Charlie Seaman on Unsplash.

18 Sep 2020 11:11am GMT

17 Sep 2020

feedPlanet Ubuntu

Podcast Ubuntu Portugal: Ep 108 – Sim podemos

Em semana se regresso às aulas, mais 1 episódio no melhor podcast sobre Ubuntu, software livres e outras cenas, de Portugal. Raspberry pi, marmitas e pinetabs fazem parte deste fantástico cardápio.

Já sabem: oiçam, subscrevam e partilhem!


Podem apoiar o podcast usando os links de afiliados do Humble Bundle, porque ao usarem esses links para fazer uma compra, uma parte do valor que pagam reverte a favor do Podcast Ubuntu Portugal.
E podem obter tudo isso com 15 dólares ou diferentes partes dependendo de pagarem 1, ou 8.
Achamos que isto vale bem mais do que 15 dólares, pelo que se puderem paguem mais um pouco mais visto que têm a opção de pagar o quanto quiserem.

Se estiverem interessados em outros bundles não listados nas notas usem o link https://www.humblebundle.com/?partner=PUP e vão estar também a apoiar-nos.

Atribuição e licenças

Este episódio foi produzido por Diogo Constantino e Tiago Carrondo e editado por Alexandre Carrapiço, o Senhor Podcast.

A música do genérico é: "Won't see it comin' (Feat Aequality & N'sorte d'autruche)", por Alpha Hydrae e está licenciada nos termos da [CC0 1.0 Universal License](https://creativecommons.org/publicdomain/zero/1.0/).

Este episódio e a imagem utilizada estão licenciados nos termos da licença: Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0), cujo texto integral pode ser lido aqui. Estamos abertos a licenciar para permitir outros tipos de utilização, contactem-nos para validação e autorização.

17 Sep 2020 9:45pm GMT

Ubuntu Podcast from the UK LoCo: S13E26 – The evil eye

This week we've been playing with arcade boards and finishing DIY in the kitchen. We discuss if old technology is more fun than new technology, bring you a command line love and go over all your wonderful feedback.

It's Season 13 Episode 26 of the Ubuntu Podcast! Alan Pope, Mark Johnson and Martin Wimpress are connected and speaking to your brain.

In this week's show:

opusenc in.wav --downmix-mono --bitrate 6 --cvbr --framesize 60 out.opus

That's all for this week! If there's a topic you'd like us to discuss, or you have any feedback on previous shows, please send your comments and suggestions to show@ubuntupodcast.org or Tweet us or Toot us or Comment on our Facebook page or comment on our sub-Reddit.

17 Sep 2020 2:00pm GMT

16 Sep 2020

feedPlanet Ubuntu

Ubuntu Blog: Design and Web team summary – 16th September 2020

The web team here at Canonical run two-week iterations. Here are some of the highlights of our completed work from this iteration.

Web squad

Our Web Squad develops and maintains most of Canonical's promotional sites like ubuntu.com, canonical.com and more.

CloudNative Days Tokyo 2020

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/vnlJn8qtif4HB5kaWzVKRnx8gC-e4yWjgYc5OoWIm-o9YRVHcO3dx6YEocggu3LjyqRLYi5D4QaunJp_lMalRaC92UG2Re8CY3uU-cAxmVrw5EdUyJPd8qmwPp9KgXBAQ4n3zA1n" width="720" /> </noscript>

This year will see a lot of physical events move to a virtual event format. However, most virtual booths bring low engagement with the audience, limit the abilities to do demos and showcase interactive content and have very low conversion rates.

Visit the CloudNative Days Tokyo 2020

New homepage for Ubuntu.com

We released a refreshed homepage for ubuntu.com. Providing a lot more outreach for different audiences.

Visit the new homepage

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/auOOq3g_4VKdp4GVFtgSEPz8IxpvxUZS9NjL-bfghOpqNJFEL5utNU_oevva_I8N5men_--TVPpiCvlzL9yleuPDF7rK2DMs8D4A39RnW6i4qZYTG6Y_joXeYnhdl57mCSmidJUv" width="720" /> </noscript>

EdgeX page on ubuntu.com

A new page with information about the exciting EdgeX ecosystem. Allowing you to sign up for our new EdgeX newsletter.

Visit the EdgeX page

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh5.googleusercontent.com/UtYbWTyUgb1wmUjgSYzRewEuig-t-F3_DrZic_jIzmYw9Lss6KAcNVp7dkRcTfbjaug_zv1d25ckRJt4vAfzIrGgM8RHOlnkmFDAY7gtjyKWW0JPqVVFcLTO0kfDutZfi0JlQUre" width="720" /> </noscript>


The Brand team develop our design strategy and create the look and feel for the company across many touch-points, from web, documents, exhibitions, logos and video.

Brand Hierarchy

We collated all of the work we have done so far, analysed the content and decided on the outcomes and next steps to complete the system and roll it out across all areas of the company.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/w_Un-Dfeow1zPhtul6oPbItmenvRMCcjGNNLa57B035F21xhAmCoVl5vYqLe3aBTmwjQQ9Av7f1pRW-KoaAtjqvMq92s_kPI7i9GXUHCO1RUzkKYBrc6Yo7EQ6mkGOIo3EKDipTk" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/fMebCJ7Q3XvtfbEgGrzmEmDh6XfZLAfIkFbXIY-pjB_g0nMLCJ_JxhbLg7QvV4UN6xDaAEKuCHVF48k7ATKnlz8OpmRSo9cPWOj8zw2_dcbZxpn82qIiDiGT6EF6gYYeca7lDzUe" width="720" /> </noscript>

Charmed Kubeflow

Illustrations and web design for the updated Kubeflow page.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh4.googleusercontent.com/Jh33wunpzxHijpfJw-yqvSlzEG600gcIr2AMbvOujXyz0uBJZDa6zfIVPTSairyHiGaw6hsLgLqr0YdjYGvUneL-4YIn7nY38OZTAO1EHzQ-msXfL9hM_SJzWKRhNcUGkN0sQDX2" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/i-CEz66-vxLEuK6qwRmxiWDuyO5sBJI65jPGFMDJF6NuZ3RwPwqLNj-L7KEWn1FRguYbdNtwbC1mbBU3txZ8-_JS0LZGPRYhRigNtsjENsZ9X_fWWdEhLSx_pKmMjXIFoeIGPDJ3" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh4.googleusercontent.com/djazh7CkHsEOHYn7zRxb8YrXwJY3ysHOWgJkx2oyMZ9QlflLTvAd3EU79wsHGOMBNtPQIFYhp352fEVWZneDAuaeDSBlIkQRt2fFCBoFWGxA1Wh6eEX222VJ3VLWj7ltfsER-J-r" width="720" /> </noscript>

Document Hierarchy testing

We took the templates developed in the last iteration and inserted real content to make sure that the styles and typography are robust enough to roll out.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/8JzpTzb9Rp0m1zi0XNZq6XhDUTRGgY2yOQmsmo4ZAwaFDKfZ8pXr1NJpjvcw8zh_gGFx3w_BlqAgUmZjiwGVCXd2arYyOQaxBV_dfnZ_hKo5I0bYXSKnQJ3X84oYORf5fGq0-Ztj" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/yf6KjFstWGGBSOva5aPn6VjZLhr3MlFb9eECmBRzUpkEQkb3wR3xoPlDtUuwiOtk17jcgfU4c_KuNtYzYbyMybfDFD3CfSTU6-vqnTPg-Vg85rdkqvaS4K8IUDdLyDlyIVN-F-Cz" width="720" /> </noscript>

Livechat branding

Initial colour and design work to brand the Eye catcher and Livechat instance on Ubuntu.com.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/KdZNf9v08AkF8g2gpt0wMKUpv5npS1JK-lH1UCP95s1lxztEikuCgi2ho5Jw_D6FAC0RA435glyMF6IzJLnxd9_vN-vgak_-9pYH4Vy0RMVvsLb1Yb_SM6syZZtPCnabveB1RIRl" width="720" /> </noscript>


The MAAS squad develops the UI for the MAAS project.

MAAS new CLI iteration 2

Last week, we have been testing out the CLI prototype with 6 MAAS CLI users to collect feedback on what we can do to improve our current CLI experience.

The first thing we tested out was the concept of the initial help or what our testers mostly referred to as "cheat sheet".

When a user types "maas" or "maas -help", you will see a cheat sheet as a guideline to help you do basic operations. In the first prototype, we introduced the concept of a primary object (machine), so by default, MAAS interprets an action against machines as an object when no object is indicated.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/0ZxEv9RCHLyRvBGgQzYFXvmeT9OV19Xu4h3oBubv9pE9OzrgruwsGd46Xfa6WfC4urydunYVzmeXLMFcUa5maxRuGw8808Kx0evh2Z1KzUN7ZvJ9zY_M8nv2TBkSS5ahy08R7E1G" width="720" /> </noscript>

We received a lot of positive feedback for this concept and our testers wanted to see what other objects are available in the CLI. So to provide learnability, we added "Hints" to this page and indicate the current version of MAAS as well as other useful information.

One use case was frequently mentioned during the test regarding how to operate bulk actions for multiple MAASes or data centres.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh5.googleusercontent.com/ms7zsQ8jebMU0BhRwmT4cq4pAEJ5d-Zz3nG1KPKzRsQLIlOtijxfansCvoVIhi79CieqVf5cpR9S8ElkSYaFq00SsoYTpyoHHTEk15uuiBVvN-CrWPH3GyyqDnE9U_qV8GSjjECl" width="720" /> </noscript>

Breaking down MAAS objects. In the current CLI, we have both singular and plural forms of object as a way to indicate collection services VS individual services. In this version, we stripped down all plural objects and broke them down into different categories for readability. We've also added a link to the documentation page for further readings.

Highlight: 5 out of 6 users mentioned that they don't like reading the documentation and would not bother to read them because when they are working with the CLI they feel like they have to start the search over again in the documentation page. It felt like they have to do a double search to get to the point where they get the answer. So to reduce that hassle, we attached the right documentation link to the relevant commands help page.

In this prototype, we also introduced the concept of the primary profile, which is reflected in the current prompt. A user may log in to multiple profiles and set one of the profiles as their primary profile. When a user wants to take actions on multiple profiles such as deploying 10 identical machines 3 MAAS profiles, they just need to apply a profile flag to their deployment action.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/Ek10Al6qUZbQ0qC8q79IXHd9xqKJrrt52Fk2CiwBReXaFvvfWWmHmts11hF1t2Ez4a_6KPp-ror9bUm4-dYAHqz1hCfpaE4PslY69iGdpK4hFGKvxi6gJz3GXVTp5PxeNm67zzg0" width="720" /> </noscript>

The user will always see their current profile when they take action. This is to help prevent our users from making mistakes and that they are aware of their current environment.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh5.googleusercontent.com/X_tsLShqm5kObsDpU6GtF2OQuHAjs5KsRu0xivoyx4JarFSYaqLUCW25nIMkzRB8wNqgqTfdFBLoTGdnNW94EJFTFIfbJ5FybaJbcEKP55ruz7PPcebivsVhiJmFrS85vZRw42A3" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/uorh-w7Vd-1Uhh9gkhmf0nyzb8DkYJasOKEGbFNy2fs-Syd3mz-Hgw2V8Ph6of0UkjA6wvWL4bVxXedIX-om3rnxIapzy-xAVYbC33CkhlQRdtqgC47yClOzVnrWW3nN1Tdp_Ggf" width="720" /> </noscript>

To enhance the experience for learnability, we also try to break down the help page to be more meaningful. This is an example of the new help page. It will show you a brief description of the action, options, different ways to customise the outputs, examples, and related commands. For instance, maas list will list multiple or individual node description in a compact format as an overview. Whereas a related command is "maas show", where a user can drill down detailed information of a particular machine in an elaborate manner.

After going through this user test, our team has agreed to make the default experience in the CLI compatible with our scripting users because we have a separate MAAS UI that can achieve the same purpose. However, if a user prefers to do things in MAAS using the CLI and expecting a beginner's experience, they can use the" -interactive " flag or " -i" to use the interactive prompt.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh5.googleusercontent.com/Q16H5JAb2m0uvnNjVcrxs9d21iaaazHbWvUZE2WoS6ttymgvUsQIB4ggQbGlAUFZmHbSXqqNOdNtfo_UcKPVxBraS-5pxnT0mjWYLRPSIoYydyO39eC8FvzIOTovcLnMGQ3Nr6jO" width="720" /> </noscript>
<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/ZS1oklyxeT3Z3eqlQAialO9FfwSShE0SkDT7oHw3FO33ReI_Vge00QdB1HSs3Ls8pWV4PTBt73RCDJ7WH1nh_eIRi65drtoKdobWxpzyMKq9pdrfircnNFuTgnPhy7P__ESb6CXN" width="720" /> </noscript>

When a user indicates -i in the CLI, they will be presented with an interactive prompt where, it will ask for required information for the deployment such as OS, release, kernel, setting a machine is a KVM host, and customising cloud-init user-data.

By default, "maas deploy" will throw an error, because a user needs to supply information about the machine or a characteristic of a collection of machines they wish to deploy.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/qjQlXaIojoYS4o05H2qLDGCesJeOLl59aoYpt-ZTzYU6fAepeVpkaGLwczKqrODNoIrznZDdv2spJo9N64_iUgvweC9a9fGZudOXrgol4nmDTTWkiG66u94KLJwASUWgRLUigpWM" width="720" /> </noscript>

However, if an error occurs, the prompt will provide guidelines and suggestions including documentation to help our users perform an action correctly.

Since the default experience is tailored to scripting users, by default a user will get the prompt back when they perform an action. They will also be informed that the machine(s) they deployed are running in the background and they may use any of these suggestions to check up on the status of the deployment.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh5.googleusercontent.com/GCCnRj-vqxo68Ui7qDS9DqwVYELPnj40na1nCpdC86XUhzEpBXQGz0th0pDS2V70Ztx14F07Zmv8ZanQt0C9RzHZu_NF6egmCGXO6SA2ptJVdgNdZ6cLt2vDNcQnjLy1r1i5-7fk" width="720" /> </noscript>

If a user wishes to have their prompt block when performing an action and want to see if it's running, they can use the --wait flag to see the waiting state of the CLI. This will show a broken down version of the running task, a loading indication, and the time elapse. Time is quite important for MAAS users because for many users, if something is processing longer than usual, they would rather have that process aborted and reboot.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/RoBhXczx_fHKaiax1UOaF6bhiWb25p7rR48YebWIVyOL-OJKerUKB_9sX9hGcXFLVVCXXtrQ9koeX9ih5Tq0AKvPipO7WgYS81INDFgeOMeggJZxZmAIf1ZYQTw1eUzljOexsDZq" width="720" /> </noscript>

What's next?

  1. We are still working to define a better way to help our users debug when an error occurs. So the error state is another important piece that we are focusing on. Our current goal is to enhance the learnability aspects of our CLI and help our users recover from their errors or mistakes.
  2. Another interesting feature is partial matching of the machine name. Currently, MAAS operates on machine IDs, which is not easy to fetch. We will allow our users to operate based on the machine names instead and they can either supply the full FQDN or just hostname. The current prototype provides suggestions for misspelt names and our next task is to allow partial string matching for this.

If you are reading about this and would like to add feedback, we are more than happy to find out how we can improve the CLI experience. Your feedback is a gift.


The JAAS squad develops the UI for the JAAS store and Juju GUI projects.

Cross model relations

We posted our UX work about CRM on discourse last iteration, thanks for the positive feedback from the community. The final visuals for the MVP has been completed - the Cross-model relations information is displayed in the Relation view, Application panel and a dedicated Relation details panel.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh4.googleusercontent.com/mHL6Fb1-YpNTArFoHRDe0fhK_jxUkpmFlLnz1TSHxBo_W_KwijTVDCBy7yXlqjEgLIOEmivXPzXwo36gpaIc0kZ5QvrqqX5CnSk1NXFtSS35FUbapsZA2XGMLfkB6RkdjscpCFsK" width="720" /> </noscript>

Relations view

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh3.googleusercontent.com/N_DZ90e01ARXLW0p-RH-aGVKo-czOJEgfP9lELT18RvbVs3QZAIUOEHzaxTik3yhy55JB2-fv7ni4P2JdFw36zcz84rpgVUDjs9jXwCyIJktE4N1O6YJe3ZzX46Y3d6BLgYU-KG1" width="720" /> </noscript>

Apps panel with relation and offer details

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh4.googleusercontent.com/WiBqZO-xKtsEfhsv66wLKEHEiWzc5vBMIDT28YZdBSLJZzQA0NIpuypV_HYXdxQ4WqTFhYk2m4rVbBHUaYyFWP5e8cXAHKOM7T92bOKKPH4d4XW7rAqXpXfm9Tipu1vkirirsAOE" width="720" /> </noscript>

Relation details panel

Charm Actions UX Exploration

The team are exploring ways to provide actions which can be performed on a charm or units, with better visual affordance and representation. We started investigating the existing feature sets from Juju CLI, talking to charm writers and Juju users, organising feedback and comments from Discourse. A workshop with prepared design proposals and ideas will be held next week.


The Vanilla squad designs and maintains the design system and Vanilla framework library. They ensure a consistent style throughout web assets.


Work continues on a unified notifications pattern for use across our websites and web apps. Our UX team has been working on defining problems, auditing our use of notifications and benchmarking against the best-in-class notification experiences.

We're hoping to deliver a notification experience that's useful, lightweight and doesn't interrupt user flow as they accomplish their important tasks in our software.

Accessibility audit and fixes

We've completed a component-wide accessibility audit, and we've started applying enhancements to many components and example pages, including navigation, breadcrumbs, the switch component, buttons and others.

Modular table React component

We've been continuing the work on creating a new modular table React component. After initial proof of concept, we created a basic component in our React components library and will continue to extend it with features used by the tables in our products.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/IFE3h1Fbyxcne7X15fb3MplUIg5ByuMjZTkYe3DSfAqyOwe2IZyU1L_27aaL2ffUEStJ7k4U2er6ka0E0L-IWwvm-kUAXxjWFmhIMJcPOQhO70ELENkkNTSrvOiOMWSDJa67A2Pj" width="720" /> </noscript>

Snapcraft and Charm Hub

The Snapcraft team works closely with the Store team to develop and maintain the Snap Store site and the upcoming Charm Hub site.



The snap team have published a forum category. You can come and join us by giving feedback or engaging in design conversations with us directly there.

Weekly active device by architecture

Snapcraft publishers page can now get the weekly active device by architecture. A publisher can go to the snap metrics page and filter by architecture. Please, provide us feedback in the forum.

<noscript> <img alt="" src="https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,w_720/https://lh6.googleusercontent.com/_GHcGdYSQdSfV9k-uEMzV4uzZeA61zu1NPJvt0KoEZu3AT1etvip6pPbXPM4p8lzQpD8n5zLvOWq-sL3KF5dOPz7VFLuSwujtD2j_LQTniRpu1YAiqYNeh5jsxOB4z00KkcZy2Q6" width="720" /> </noscript>

Your month in snaps email

The system that was providing the "Your month in snaps" emails has now been updated to run as a cron job in the Webteam's Kubernetes. The repository for this cronjob can be found on GitHub.

Brand store admin

The brand store admin pages are in the process of being re-designed to become more useful, provide deeper insight into how the snaps published in them are used, and to become more easily manageable. With the redesign they will also be moved into snapcraft.io, from dashboard.snapcraft.io.

Charm Hub

Charm Hub Developer Experience

We have been iterating on the charm detail pages to be able to accommodate for content that helps charmers build their own new charms by reusing Python libraries from other charms, as well as help consumers, make integrations between charms in a more intuitive way. Along with the improvements of the developer experience, we have done visual improvements on the rest of the detail pages.

Store page

Responsive filters and sorting have been added to the store page for a better experience when browsing charms and bundles.

With ♥ from Canonical web team.

16 Sep 2020 8:58pm GMT

Full Circle Magazine: Full Circle Weekly News #182

Groovy Gorilla Is In Feature Freeze
Ubuntu Beginning the Switch to NFTables in Groovy Gorilla
IP Fire 2.25 Core Update 148 Released with Location-based Firewall
Lenovo to Ship Fedora on its Thinkpads
Raspberry Pi OS 2020-08-20 Out

Q4OS 3.12, Centaurus Out

Linux from Scratch and Beyond LFS 10 Out

Linux Mint's Warpinator via Flatpak Out

SuperTuxKart 1.2 Out

Htop 3.0 Out

Ubuntu "Complete" sound: Canonical

Theme Music: From The Dust - Stardust

16 Sep 2020 5:47pm GMT

15 Sep 2020

feedPlanet Ubuntu

Raphaël Hertzog: Freexian’s report about Debian Long Term Support, August 2020

A Debian LTS logo Like each month, here comes a report about the work of paid contributors to Debian LTS.

Individual reports

In August, 237.25 work hours have been dispatched among 14 paid contributors. Their reports are available:

Evolution of the situation

August was a regular LTS month once again, even though it was only our 2nd month with Stretch LTS.
At the end of August some of us participated in DebConf 20 online where we held our monthly team meeting. A video is available.
As of now this video is also the only public resource about the LTS survey we held in July, though a written summary is expected to be released soon.

The security tracker currently lists 56 packages with a known CVE and the dla-needed.txt file has 55 packages needing an update.

Thanks to our sponsors

Sponsors that recently joined are in bold.

No comment | Liked this article? Click here. | My blog is Flattr-enabled.

15 Sep 2020 10:01am GMT

Stephen Michael Kellat: Middle of September 2020 Notes

"A person is praised for his insight, but a warped mind leads to contempt." - Proverbs 12:8 (Common English Bible)

It has been a while since I have written anything that might appear on Planet Ubuntu. Specifically the last time was June 26th. That's not necessarily a good thing.

I have been busy writing. What have I been writing? I knocked out a new novelette in Visual Studio Code. The print version was typeset using the novel class using LuaLaTeX. It is a bit of a sci-fi police procedural. It is up on Amazon for people to acquire though I do note that Amazon's print-on-demand costs have gone up a wee bit since the start of the planet-wide coronavirus crisis.

I also have taken time to test the Groovy Gorilla ISOs for Xubuntu. I encourage everybody out there to visit the testing tracker to test disc images for Xubuntu and other flavours as we head towards the release of 20.10 next month. Every release needs as much testing as possible.

Based upon an article from The Register it appears that the Community Council is being brought back to life. Nominations are being sought per a post on the main Discourse instance but readers of this are reminded that you need to be a current member either directly or indirectly of the 609 Ubuntu Members shown on Launchpad. Those 609 persons are the electors for the Community Council and the Community Council is drawn from that group. The size and composition of the Ubuntu Members group on Launchpad can change based upon published procedures and the initiative of individual to be part of such changes.

I will highlight an article at Yahoo Finance concerning financial distress among the fifty states. Here in Ohio we are seemingly in the middle of the pack. In Ashtabula County we have plenty of good opportunities in the age of coronavirus especially with our low transmission rates and very good access to medical facilities. With some investment in broadband backhaul an encampment for coders could be built who did not want to stick with city living. There is enough empty commercial real estate available to provide opportunities for film and television production if the wildfires and coronavirus issues out in California are not brought under control any time soon.

As a closing note, a federal trial judge ruled that the current coronavirus response actions in Pennsylvania happen to be unconstitutional. A similar lawsuit is pending before a trial judge here in Ohio about coronavirus response actions in this particular state. This year has been abnormal in so many ways and this legal news is just another facet of the abnormality.

15 Sep 2020 1:49am GMT

Santiago Zarate: Ext4 filesystem has no space left on device? You liar!

Disk usage

So, you wake up one day, and find that one of your programs, starts to complainig about "No space left on device":

Next thing (Obviously, duh?) is to see what happened, so you fire up du -h /tmp right?:

$ du -h /tmp
Filesystem              Size  Used Avail Use% Mounted on
/dev/mapper/zkvm1-root  6.2G  4.6G  1.3G  79% /

Well, yes, but no, ok? ok, ok!

Wait, what? there's space there! How can it be? In all my years of experience (+15!), I've never seen such thing!

Gods must be crazy!? or is it a 2020 thing?

I disagree with you

$ touch /tmp
touch: cannot touch '/tmp/test': No space left on device

Wait, what? not even a small empty file? Ok...

After shamelessly googling/duckducking/searching, I ended up at https://blog.merovius.de/2013/10/20/ext4-mysterious-no-space-left-on.html but alas, that was not my problem, although… perhaps too many files?, let's check with du -i this time:

$ du -i /tmp
`Filesystem             Inodes  IUsed IFree IUse% Mounted on
/dev/mapper/zkvm1-root 417792 417792     0  100% /

Of course!

Because I'm super smart I'm not, I now know where my problem is, too many files!, time to start fixing this…

After few minutes of deleting files, moving things around, bind mounting things, I landed with the actual root cause:

Tons of messages waiting in /var/spool/clientmqueue to be processed, I decided to delete some, after all, I don't care about this system's mails… so find /var/spool/clientmqueue -type f -delete does the job, and allows me to have tab completion again! YAY!.

However, because deleting files blindly is never a good solution, I ended up in the link from above, the solution was quite simple:

$ systemctl enable --now sendmail

Smart idea!

After a while, root user started to receive system mail, and I could delete them afterwards :)

In the end, very simple solution (In my case!) rather than formatting or transfering all the data to a second drive, formatting & playing with inode size and stuff…

Filesystem             Inodes IUsed  IFree IUse% Mounted on
/dev/mapper/zkvm1-root 417792 92955 324837   23% /

Et voilà, ma chérie! It's alive!

This is a very long post, just to say:

ext4 no space left on device can mean: You have no space left, or you don't have more room to store your files.

15 Sep 2020 12:00am GMT

14 Sep 2020

feedPlanet Ubuntu

The Fridge: Ubuntu Weekly Newsletter Issue 648

Welcome to the Ubuntu Weekly Newsletter, Issue 648 for the week of September 6 - 12, 2020. The full version of this issue is available here.

In this issue we cover:

The Ubuntu Weekly Newsletter is brought to you by:

If you have a story idea for the Weekly Newsletter, join the Ubuntu News Team mailing list and submit it. Ideas can also be added to the wiki!

Except where otherwise noted, this issue of the Ubuntu Weekly Newsletter is licensed under a Creative Commons Attribution ShareAlike 3.0 License

14 Sep 2020 10:57pm GMT

13 Sep 2020

feedPlanet Ubuntu

Jonathan Carter: Wootbook / Tongfang laptop

Old laptop

I've been meaning to get a new laptop for a while now. My ThinkPad X250 is now 5 years old and even though it's still adequate in many ways, I tend to run out of memory especially when running a few virtual machines. It only has one memory slot, which I maxed out at 16GB shortly after I got it. Memory has been a problem in considering a new machine. Most new laptops have soldered RAM and local configurations tend to ship with 8GB RAM. Getting a new machine with only a slightly better CPU and even just the same amount of RAM as what I have in the X250 seems a bit wasteful. I was eyeing the Lenovo X13 because it's a super portable that can take up to 32GB of RAM, and it ships with an AMD Ryzen 4000 series chip which has great performance. With Lenovo's discount for Debian Developers it became even more attractive. Unfortunately that's in North America only (at least for now) so that didn't work out this time.

Enter Tongfang

I've been reading a bunch of positive reviews about the Tuxedo Pulse 14 and KDE Slimbook 14. Both look like great AMD laptops, supports up to 64GB of RAM and clearly runs Linux well. I also noticed that they look quite similar, and after some quick searches it turns out that these are made by Tongfang and that its model number is PF4NU1F.

I also learned that a local retailer (Wootware) sells them as the Wootbook. I've seen one of these before although it was an Intel-based one, but it looked like a nice machine and I was already curious about it back then. After struggling for a while to find a local laptop with a Ryzen CPU and that's nice and compact and that breaks the 16GB memory barrier, finding this one that jumped all the way to 64GB sealed the deal for me.

This is the specs for the configuration I got:

This configuration cost R18 796 (€947 / $1122). That's significantly cheaper than anything else I can get that even starts to approach these specs. So this is a cheap laptop, but you wouldn't think so by using it.

I used the Debian netinstall image to install, and installation was just another uneventful and boring Debian installation (yay!). Unfortunately it needs the firmware-iwlwifi and firmare-amd-graphics packages for the binary blobs that drives the wifi card and GPU. At least it works flawlessly and you don't need an additional non-free display driver (as is the case with NVidia GPUs). I haven't tested the graphics extensively yet, but desktop graphics performance is very snappy. This GPU also does fancy stuff like VP8/VP9 encoding/decoding, so I'm curious to see how well it does next time I have to encode some videos. The wifi upgrade was nice for copying files over. My old laptop maxed out at 300Mbps, this one connects to my home network between 800-1000Mbps. At this speed I don't bother connecting via cable at home.

I read on Twitter that Tuxedo Computers thinks that it's possible to bring Coreboot to this device. That would be yet another plus for this machine.

I'll try to answer some of my own questions about this device that I had before, that other people in the Debian community might also have if they're interested in this device. Since many of us are familiar with the ThinkPad X200 series of laptops, I'll compare it a bit to my X250, and also a little to the X13 that I was considering before. Initially, I was a bit hesitant about the 14″ form factor, since I really like the portability of the 12.5″ ThinkPad. But because the screen bezel is a lot smaller, the Wootbook (that just rolls off the tongue a lot better than "the PF4NU1F") is just slightly wider than the X250. It weighs in at 1.1KG instead of the 1.38KG of the X250. It's also thinner, so even though it has a larger display, it actually feels a lot more portable. Here's a picture of my X250 on top of the Wootbook, you can see a few mm of Wootbook sticking out to the right.

Card Reader

One thing that I overlooked when ordering this laptop was that it doesn't have an SD card reader. I see that some variations have them, like on this Slimbook review. It's not a deal-breaker for me, I have a USB card reader that's very light and that I'll just keep in my backpack. But if you're ordering one of these machines and have some choice, it might be something to look out for if it's something you care about.


On to the keyboard. This keyboard isn't quite as nice to type on as on the ThinkPad, but, it's not bad at all. I type on many different laptop keyboards and I would rank this keyboard very comfortably in the above average range. I've been typing on it a lot over the last 3 days (including this blog post) and it started feeling natural very quickly and I'm not distracted by it as much as I thought I would be transitioning from the ThinkPad or my mechanical desktop keyboard. In terms of layout, it's nice having an actual "Insert" button again. This is things normal users don't care about, but since I use mc (where insert selects files) this is a welcome return :). I also like that it doesn't have a Print Screen button at the bottom of my keyboard between alt and ctrl like the ThinkPad has. Unfortunately, it doesn't have dedicated pgup/pgdn buttons. I use those a lot in apps to switch between tabs. At leas the Fn button and the ctrl buttons are next to each other, so pressing those together with up and down to switch tabs isn't that horrible, but if I don't get used to it in another day or two I might do some remapping. The touchpad has en extra sensor-button on the top left corner that's used on Windows to temporarily disable the touchpad. I captured it's keyscan codes and it presses left control + keyscan code 93. The airplane mode, volume and brightness buttons work fine.

I do miss the ThinkPad trackpoint. It's great especially in confined spaces, your hands don't have to move far from the keyboard for quick pointer operations and it's nice for doing something quick and accurate. I painted a bit in Krita last night, and agree with other reviewers that the touchpad could do with just a bit more resolution. I was initially disturbed when I noticed that my physical touchpad buttons were gone, but you get right-click by tapping with two fingers, and middle click with tapping 3 fingers. Not quite as efficient as having the real buttons, but it actually works ok. For the most part, this keyboard and touchpad is completely adequate. Only time will tell whether the keyboard still works fine in a few years from now, but I really have no serious complaints about it.


The X250 had a brightness of 172 nits. That's not very bright, I think the X250 has about the dimmest display in the ThinkPad X200 range. This hasn't been a problem for me until recently, my eyes are very photo-sensitive so most of the time I use it at reduced brightness anyway, but since I've been working from home a lot recently, it's nice to sometimes sit outside and work, especially now that it's spring time and we have some nice days. At full brightness, I can't see much on my X250 outside. The Wootbook is significantly brighter even (even at less than 50% brightness), although I couldn't find the exact specification for its brightness online.


The Wootbook has 3x USB type A ports and 1x USB type C port. That's already quite luxurious for a compact laptop. As I mentioned in the specs above, it also has a full-sized ethernet socket. On the new X13 (the new ThinkPad machine I was considering), you only get 2x USB type A ports and if you want ethernet, you have to buy an additional adapter that's quite expensive especially considering that it's just a cable adapter (I don't think it contains any electronics).

It has one hdmi port. Initially I was a bit concerned at lack of displayport (which my X250 has), but with an adapter it's possible to convert the USB-C port to displayport and it seems like it's possible to connect up to 3 external displays without using something weird like display over usual USB3.

Overall remarks

When maxing out the CPU, the fan is louder than on a ThinkPad, I definitely noticed it while compiling the zfs-dkms module. On the plus side, that happened incredibly fast. Comparing the Wootbook to my X250, the biggest downfall it has is really it's pointing device. It doesn't have a trackpad and the touchpad is ok and completely usable, but not great. I use my laptop on a desk most of the time so using an external mouse will mostly solve that.

If money were no object, I would definitely choose a maxed out ThinkPad for its superior keyboard/mouse, but the X13 configured with 32GB of RAM and 128GB of SSD retails for just about double of what I paid for this machine. It doesn't seem like you can really buy the perfect laptop no matter how much money you want to spend, there's some compromise no matter what you end up choosing, but this machine packs quite a punch, especially for its price, and so far I'm very happy with my purchase and the incredible performance it provides.

I'm also very glad that Wootware went with the gray/black colours, I prefer that by far to the white and silver variants. It's also the first laptop I've had since 2006 that didn't come with Windows on it.

The Wootbook is also comfortable/sturdy enough to carry with one hand while open. The ThinkPads are great like this and with many other brands this just feels unsafe. I don't feel as confident carrying it by it's display because it's very thin (I know, I shouldn't be doing that with the ThinkPads either, but I've been doing that for years without a problem :) ).

There's also a post on Reddit that tracks where you can buy these machines from various vendors all over the world.

13 Sep 2020 8:44pm GMT

10 Sep 2020

feedPlanet Ubuntu

Podcast Ubuntu Portugal: Ep 107 – Viagem no tempo

Demos folga Tiago Carrondo, mas para compensar os ouvintes o David Negreira veio fazer uma perninha. Falámos de redes caseiras, escritórios, do Interrruptor da Rute Correira, do KDE Plasma e workflows, dos novos HP certificados com Ubuntu e das novidades muitas e fixes do
do Groovy Gorila.

Já sabem: oiçam, subscrevam e partilhem!


Podem apoiar o podcast usando os links de afiliados do Humble Bundle, porque ao usarem esses links para fazer uma compra, uma parte do valor que pagam reverte a favor do Podcast Ubuntu Portugal.
E podem obter tudo isso com 15 dólares ou diferentes partes dependendo de pagarem 1, ou 8.
Achamos que isto vale bem mais do que 15 dólares, pelo que se puderem paguem mais um pouco mais visto que têm a opção de pagar o quanto quiserem.

Se estiverem interessados em outros bundles não listados nas notas usem o link https://www.humblebundle.com/?partner=PUP e vão estar também a apoiar-nos.

Atribuição e licenças

Este episódio foi produzido por Diogo Constantino e Tiago Carrondo e editado por Alexandre Carrapiço, o Senhor Podcast.

A música do genérico é: "Won't see it comin' (Feat Aequality & N'sorte d'autruche)", por Alpha Hydrae e está licenciada nos termos da [CC0 1.0 Universal License](https://creativecommons.org/publicdomain/zero/1.0/).

Este episódio e a imagem utilizada estão licenciados nos termos da licença: Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0), cujo texto integral pode ser lido aqui. Estamos abertos a licenciar para permitir outros tipos de utilização, contactem-nos para validação e autorização.

10 Sep 2020 9:55pm GMT

Costales: Unav 3 is here!

The new uNav 3 is here! A simple, easy & beautiful GPS Navigator for Ubuntu Touch! 100% Libre. Doesn't track you, it respects you. Powered by Openstreemap. Online & offline (powered by OSM Scout Server) GPS Navigation. Enjoy it in your UBPorts device!

10 Sep 2020 9:10pm GMT

Ubuntu Podcast from the UK LoCo: S13E25 – 666

This week we have been watching The Mandalorian. We discuss a new look for UKUI, HP Z series computers with Ubuntu pre-installed, elementary OS on Pinebook, Active Directory integration in Ubuntu Desktop, and making apps for GNOME. We also round up some picks from the tech news.

It's Season 13 Episode 25 of the Ubuntu Podcast! Alan Pope, Mark Johnson and Martin Wimpress are connected and speaking to your brain.

In this week's show:

That's all for this week! If there's a topic you'd like us to discuss, or you have any feedback on previous shows, please send your comments and suggestions to show@ubuntupodcast.org or Tweet us or Toot us or Comment on our Facebook page or comment on our sub-Reddit.

10 Sep 2020 2:00pm GMT

07 Sep 2020

feedPlanet Ubuntu

Serge Hallyn: sxmo on pinephone

If you are looking for a new phone that either respects your privacy, leaves you in control, or just has a different form factor from the now ubiquitous 6″ slab, there are quite a few projects in various states of readiness


Different form factors:

Earlier this year I bought a pinephone, braveheart edition. I've tried several OSes on it. Just yesterday, I tried:

So I'm back to running what I've had on it for a month or two - sxmo, the suckless mobile operating system. It's an interesting, different take on> interacting with the phone, and I quite like it. More importantly, for now it's the most reliable as a communication devvice. With it, I can

The most limiting thing about this phone is the battery. It drains very quickly, charges slowly, and if I leave the battery in while turned off, it continues to discharge until, after a day, it doesn't want to turn back on. An external battery charger helps enormously with this. There is also an apparent hardware misfeature which will prevent the modem from waking the cpu during deep sleep - this will presumably be fixed in later hardware versions, remember mine is the braveheart .

07 Sep 2020 3:01pm GMT

06 Sep 2020

feedPlanet Ubuntu

Jonathan Carter: DebConf 20 Online

This week, last week, Last month, I attended DebConf 20 Online. It was the first DebConf to be held entirely online, but it's the 7th DebConf I've attended from home.

My first one was DebConf7. Initially I mostly started watching the videos because I wanted to learn more about packaging. I had just figured out how to create binary packages by hand, and have read through the new maintainers guide, but a lot of it was still a mystery. By the end of DebConf7 my grasp of source packages was still a bit thin, but other than that, I ended up learning a lot more about Debian during DebConf7 than I had hoped for, and over the years, the quality of online participation for each DebConf has varied a lot.

I think having a completely online DebConf, where everyone was remote, helped raise awareness about how important it is to make the remote experience work well, and I hope that it will make people who run sessions at physical events in the future consider those who are following remotely a bit more.

During some BoF sessions, it was clear that some teams haven't talked to each other face to face in a while, and I heard at least 3 teams who said "This was nice, we should do more regular video calls!". Our usual communication methods of e-mail lists and IRC serve us quite well, for the most part, but sometimes having an actual conversation with the whole team present at the same time can do wonders for dealing with many kind of issues that is just always hard to deal with in text based mediums.

There were three main languages used in this DebConf. We've had more than one language at a DebConf before, but as far as I know it's the first time that we had multiple talks over 3 languages (English, Malayalam and Spanish).

It was also impressive how the DebConf team managed to send out DebConf t-shirts all around the world and in time before the conference! To my knowledge only 2 people didn't get theirs in time due to customs.

I already posted about the new loop that we worked on for this DebConf. It was an unintended effect that we ended up having lots of shout-outs which ended up giving this online DebConf a much more warmer, personal feel to it than if we didn't have it. I'm definitely planning to keep on improving on that for the future, for online and in-person events. There were also some other new stuff from the video team during this DebConf, we'll try to co-ordinate a blog post about that once the dust settled.

Thanks to everyone for making this DebConf special, even though it was virtual!

06 Sep 2020 7:50pm GMT