Last night the nominations and applications phase of the election reached an end. We received six applications and the names of the candidates are:
• Axel Braun
• Gertjan Lettink
• Mark Stopka
• Maurizio Galli
• Nathan Wolf
• Neal Gompa
Note that this election is to fill three vacant seats on the openSUSE Board.
All candidates are encouraged to set up their election platform on the openSUSE wiki. The campaign begins now!
Last night the nominations and applications phase of the election reached an end. We received six applications and the names of the candidates are:
• Axel Braun
• Gertjan Lettink
• Mark Stopka
• Maurizio Galli
• Nathan Wolf
• Neal Gompa
Note that this election is to fill three vacant seats on the openSUSE Board.
All candidates are encouraged to set up their election platform on the openSUSE wiki. The campaign begins now!
It's election time (again)!
Yes, but this time, it is the regular board election that is happening. The previous elections that were conducted during the past year were due to ad-hoc and unforeseen circumstances. However, as per the regular election cycle, we have three seats that are going to be vacant on the openSUSE Board in December. They are the seats of Axel Braun, Marina Latini and Stasiek Michalski. Note that Stasiek was elected this year to replace Christian Boltz whose term ends in 2020. However, Stasiek is opting out from this election due to personal commitments.
My friend from the Election Committee, Ariez Vachha, made the election announcement on the project mailing list yesterday. The election wiki page has been updated accordingly, which includes the usual election schedule poster. That's courtesy of our friends from the openSUSE Indonesia community.
At the time of writing this blog post, that is less than 24 hours since the annoucement of the election, we received emails from three members who wish to stand as candidate in this election. It's a very good start.
The call for nominations and applications will continue until Sunday 29th of November. If you would like to nominate a member from the openSUSE community, please send us an email, [email protected]. We will be glad to inform the member about his/her nomination.
It's election time (again)!
Yes, but this time, it is the regular board election that is happening. The previous elections that were conducted during the past year were due to ad-hoc and unforeseen circumstances. However, as per the regular election cycle, we have three seats that are going to be vacant on the openSUSE Board in December. They are the seats of Axel Braun, Marina Latini and Stasiek Michalski. Note that Stasiek was elected this year to replace Christian Boltz whose term ends in 2020. However, Stasiek is opting out from this election due to personal commitments.
My friend from the Election Committee, Ariez Vachha, made the election announcement on the project mailing list yesterday. The election wiki page has been updated accordingly, which includes the usual election schedule poster. That's courtesy of our friends from the openSUSE Indonesia community.
At the time of writing this blog post, that is less than 24 hours since the announcement of the election was made, we received emails from three members who wish to stand as candidate in this election. It's a very good start.
The call for nominations and applications will continue until Sunday 29th of November. If you would like to nominate a member from the openSUSE community, please send us an email, [email protected]. We will be glad to inform the member about his/her nomination.
Last November, Microsoft announced that its Edge browser is coming to Linux in the near future. That day has arrived.
On 20 October 2020, Microsoft released Edge preview builds for Linux and with that Microsoft Edge is now available for all major desktop and mobile platforms.
DEB and RPM packages are available on the Microsoft Edge Insider website. These packages are updated weekly.
Hence, to install Microsoft Edge on openSUSE, simply download the .rpm file and use zypper for the installation.
sudo zypper in ~/Downloads/microsoft-edge-dev-88.0.680.1-1.x86_64.rpmThat's it! You should now be able to run Edge on openSUSE. In fact, the above screenshots are from the Edge build version 88.0.680.1 running on openSUSE Tumbleweed.
Saamiyah pinged me a few days ago about the Hacktoberfest event that she was organising and asked whether I would be free to present a topic. Sure, why not?
As many tech meetups at the moment, the Hacktoberfest event also was virtual. It was hosted on the Jitsi instance of the Mauritius Software Craftsmanship Community. The event was scheduled to start at 19h30 on Friday, i.e last evening. I was late to join but "luckily" so was everybody.
Local hacktoberfest is live 😊 #mauritius pic.twitter.com/qFoNmFDn78
— Saamiyah 🇲🇺 (@smearthelove) October 23, 2020
As the event started, we had some small-talk before the presentations really kick-off. We talked about flexi-time, work-from-(home|anywhere), and how they compare to being full-time in office.
Saamiyah did the first presentation in which she talked about the concept of Hacktoberfest, a month where open source software is celebrated. Sandeep spoke about local open source projects on GitHub.
I spoke about Flatpak and how to set it up on openSUSE. I concluded my presentation with an observation on the rise of Flatpak fuelled by the idea of having immutable & maintenance-free systems such as Fedora Silverblue and openSUSE MicroOS Desktop.
The presentation slides are available at speakerdeck.com.
The next speaker, Alan, spoke about Docker Swarm, followed by Pritvi who talked about software licenses. It was 22h00 by that time and I could not stay longer. I bid goodnight on the chat room and wished everyone to continue having fun!
oSLO 2020 kicked-off on Thursday 15 October at 10h00 UTC with an opening address by The Document Foundation's Chairman, Lothar Becker.
The conference was due to happen in Nuremberg, Germany, but because of the pandemic the plan was changed and the event went fully online. Three sessions ran simultaneously in virtual rooms. Two rooms hosted the short & long talks while the third room hosted the workshops.
During the opening session, as more people kept joining, the platform started to show signs of high load. People reported issues with the audio quality and some said that the page was not loading at all. Thanks to the Telegram group dedicated to the oSLO Conference communications, issues were being promptly reported and handled. Within a matter of minutes the organizers arranged to move the all sessions to The Document Foundation's Jitsi instance. The latter worked like a charm. The organizers and volunteers who helped in the swift transition did a great job.
The conference room 1 easily held more than 80 participants at one time and there was no degradation in the quality of audio/video.
I had my talk on Podman scheduled at 13h30 UTC on the first day of the conference. It went fine, except my poor timing of not being able to wrap it up as a short talk of 15 mins. I'll improve next time. 😉
Listening to @IshSookun talking at the @openSUSE conference about:
— Peter Czanik (@PCzanik) October 15, 2020
Getting started with #Podman
Learn about #containers & what they are made of...https://t.co/c5hQgeGdO7
I shared my slides on speakerdeck.com right after the talk.
The second day was even more fun. I hopped into the conference chat room from time to time to have a chit-chat with friends. It was not the same as having a geek talk over a beer during the conference after parties, but I was glad to see friends from the other side of the planet. I was happy to see that they are doing well.
At one time during the beer chat, I was talking to two conference participants, one was from Taiwan and the other from Bulgaria. It is always funny to see people's reaction on how small Mauritius is compared to the other countries. Well, I am proud of the tiny dot in the middle of the ocean. 🇲🇺
The last session in the room 1 of the conference, on the second day, was held by the openSUSE Board members.
They provide updates and statistics about the project over the past year and tell us a bit about what the Board is planning for the future.
It is also the time when openSUSE members can ask questions.
The session was scheduled at 21h00 UTC which was 01h00 in the morning (the next day) for me. I was tired but I enjoyed the session. I jumped into the conversation when there was a comment about having a diverse representation on the Board with people from different parts of the world. I commented as an official of the Election Committee, encouraging members from all parts of the world to step up & run as candidate or nominate someone for the next Board election.
Italo Vignoli, founding member of The Document Foundation, during the closing keynote of the openSUSE + LibreOffice Conference (oSLO 2020), asked participants to share comments on how to improve the conference experience. He pointed out that this might not be the last virtual conference, considering the pandemic, although we all would love to have a physical conference soon.
Kudos to the organizers and volunteers for a successful conference. 👏
The openSUSE Ad-hoc Board Election is now concluded.
Stasiek Michalski has been elected to join the openSUSE Board. The complete result is as follows:
234 out of 510 eligible members have cast their vote in this election. We recorded 4 blank votes.
We thank both of them for stepping up and running in this election and we congratulate Stasiek for his win.
Lastly, thanks to Edwin Zakaria and Ariez Vachha for their help in the planning of this election.
Back in February 2020 Christian Boltz resigned from the openSUSE Board explaining the reasons behind his decision on the project mailing list. His resignation came about two weeks after Sarah Julia Kriesch's resignation from the Board.
The openSUSE Board was left with two vacant seats to be filled. Sarah had been a board member for just about a few weeks after the 2019-2020 board elections. After her resignation, the openSUSE Board decided to appoint Vinzenz Vietzke on the board based on the results of the 2019-2020 board elections. Following that, only one seat remained vacant on the board. However, before the Election Committee could start discussions for an election to fill that vacant seat, about two weeks after Vinzenz's appointment, openSUSE member Pierre Böckmann called for a No-Confidence vote against the current board. It was unprecedented in the community and that put things on halt for a while.
The board election rules state that:
If 20 per cent or more of the openSUSE members require a new board, an election will be held for the complete elected Board seats.
The Election Committee was tasked to find out whether 20% of the community is indeed calling for a re-election. At this point I should disclose that I am an election official in the openSUSE Election Committee and the task given to us was not easy. After much consultation, we finally came up with a way to "measure" this 20% requirement of the election rule. We set up an electronic petition using the voting platform that is used for openSUSE Board elections.
A few days ago the petition ended and the result showed that only 11.6% of the community was in favour of a re-election. That does not satisfy the requirement for a forced re-election and thus an ad-hoc election will be carried to fill the one vacant seat only.
Ariez Vachha announced the ad-hoc board election schedule on the project mailing list and details are also available on the openSUSE wiki.
Starting now and until the 2nd of August openSUSE members wishing to run for this election or nominate someone from the community can do so by sending an email to [email protected]. I wish to remind that only openSUSE members can run for board candidacy and vote in this election.
The Election Committee is composed of Ariez Vachha, Edwin Zakaria and myself.
Today, while pulling the latest Nextcloud container image from the docker.io repository I noticed that it is failing. Looking at the read: connection reset by peer error I assume it could be primarily due to network failure; maybe poor quality of the connection.
Note that Mauritius is far from "everywhere" else and connectivity issues are nothing new.
ish@coffee-bar:~> podman pull docker.io/library/nextcloud
Trying to pull docker.io/library/nextcloud...
Getting image source signatures
Copying blob e0276193a084 done
Copying blob eb2d00c10344 done
Copying blob 3a60f364b0c5 done
Copying blob e0d3d1244592 done
Copying blob f54006e0dc29 done
Copying blob 8559a31e96f4 done
Copying blob b22875b95a2a done
Copying blob f65316e96b10 done
Copying blob 3e309988c00b done
Copying blob 0c78caf16ec3 [======================================] 13.1MiB / 13.2MiB
Copying blob 4fc30aae7ee5 done
Copying blob 37b016cacdc6 done
Copying blob fd56bf3cc539 done
Copying blob e3cd35f544b5 done
Copying blob 467fea8f6f80 done
Copying blob 0dc7444f9282 done
Copying blob 547ae6684264 done
Copying blob 3139b6de5be7 done
Copying blob 00e77223b529 done
Copying blob 2b37e3b3a856 done
read tcp 192.168.100.6:33536->104.18.124.25:443: read: connection reset by peer
Error: error pulling image "docker.io/library/nextcloud": unable to pull docker.io/library/nextcloud: unable to pull image: Error writing blob: error storing blob to file "/var/tmp/storage720474498/10": read tcp 192.168.100.6:33536->104.18.124.25:443: read: connection reset by peer
Podman does not retry to copy the image in case of failures.
A few days ago there was a suggestion to implement a similar feature in Podman that is present in Buildah, which provides the image copy retry functionality.
For the curious, the implementation can be seen here.
Container images that are pulled by Buildah are stored in the local repository which can also by accessed by Podman, so that's an advantage. I tried pulling the Nextcloud container image using Buildah and it completed successfully.
ish@coffee-bar:~> buildah pull nextcloud
Getting image source signatures
Copying blob e0d3d1244592 done
Copying blob 8559a31e96f4 done
Copying blob eb2d00c10344 done
Copying blob 3a60f364b0c5 done
Copying blob f54006e0dc29 done
Copying blob e0276193a084 done
Copying blob f65316e96b10 done
Copying blob b22875b95a2a done
Copying blob 3e309988c00b done
Copying blob 0c78caf16ec3 done
Copying blob 4fc30aae7ee5 done
Copying blob 37b016cacdc6 done
Copying blob e3cd35f544b5 done
Copying blob fd56bf3cc539 done
Copying blob 467fea8f6f80 done
Copying blob 0dc7444f9282 done
Copying blob 547ae6684264 done
Copying blob 2b37e3b3a856 done
Copying blob 00e77223b529 done
Copying blob 3139b6de5be7 done
Copying config 327476ebe3 done
Writing manifest to image destination
Storing signatures
327476ebe3280c7b570d8463edd136956eab120959976b643cb7dbfaa73f98c1Now, the downloaded container image is also accessible by Podman.
ish@coffee-bar:~> podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/libreoffice/online latest 0586fecfa3c1 28 hours ago 2.84 GB
docker.io/library/nextcloud latest 327476ebe328 3 days ago 774 MBTo conclude, while we are waiting that a retryCopyImage function is available in Podman, we can use Buildah to pull container images that are troublesome due to network issues.