Thursday 2 May 2024

2024 Open Source Professionals Job Survey Report Available Now

2024 Open Source Professionals Job Survey Report Available Now

Toronto, 04-23-2024 — Linux Professional Institute (LPI), in conjunction with Open Source JobHub, released today the 2024 Open Source Professionals Job Survey Report, which summarizes the results of a job survey among open source professionals. Based on the responses from administrators, developers, and non-technical professionals, the report highlights the concerns of employees in the world of free and open source software (FOSS).

Respondents care most about work-life balance and remote work options when considering a new role. A stated policy for using and contributing to open source software and opportunities for training and certification were also important to respondents.

This report details findings from the survey and provides insight both for job seekers and for hiring managers aiming to attract and retain open source professionals. The full report can be downloaded under https://www.lpi.org/2024-open-source-professionals-job-survey-report/

“Our mission is to promote the use of open source by supporting the people who work with it. This includes helping employers understand what our community members want from their jobs and work environments. Our aim was to collect relevant data that we felt was not sufficiently covered in other reports.”—G. Matthew Rice, Executive Director of LPI

“It is beneficial for both sides, employees and employers, to know each other’s expectations. Employers say in job advertisements what they expect and what they offer. But what do the people who are asked to apply expect? We wanted to show what potential is available in the workforce and what offers and values are relevant to leverage that potential.”—Brian Osborn, Founder of Open Source JobHub, CEO & Publisher at Linux New Media

Linux Professional Institute (LPI) is the global certification standard and career support organization for open source professionals. It’s the world’s first and largest vendor-neutral Linux and open source certification body. LPI has certified professionals in over 180 countries, delivers exams in multiple languages, and has hundreds of training partners. Our mission is to promote the use of open source by supporting the people who work with it.

Open Source JobHub aims to help everyone find a place in the open source ecosystem by connecting job seekers with employers looking for top talent. Let us help you turn down the noise and find the perfect job fit.

Source: lpi.org

Tuesday 30 April 2024

FOSS, Privacy, and Innovation: Meet Tuta Mail

FOSS, Privacy, and Innovation: Meet Tuta Mail

Tuta Mail is one of the privacy-preserving software projects with a big potential impact. In this interview with Tuta, we explore the transformative role of Free and Open Source Software (FOSS) in both the business realm and its broader social and economic impacts. This discussion aims to shed light on how open-source projects like Tuta are pioneering privacy-focused solutions, challenging conventional business models, and contributing to technological innovation and community empowerment.

Hi, Hanna, and thank you for this interview. Would you start with a few words about how and when you started your journey at Tuta?

I started at Tuta – called Tutanota back then – when it first launched in 2014. That’s already ten years ago, and it has been an amazing journey! During that time we’ve grown from 4 to more than 25 people on the Tuta Team and from 0 to more than 10 million users of our secure email service, Tuta Mail.

Can you share the journey and motivation behind Tuta’s commitment to privacy and open-source principles? And what are the benefits for Tuta in using FOSS?

At Tuta we do not simply build a secure email and calendar service; we see ourselves as freedom fighters. We believe that everyone has the right to privacy and we want to defend against growing surveillance tendencies online, by governments but also by big tech services. We achieve our goals through built-in and easy-to-use encryption.

Being open source is an integral part of this: only code that can be reviewed by peers can be considered truly secure. With closed-source code no one would be able to know whether a backdoor was hidden in the code.

We love the open source community. At Tuta we use a lot of other open source projects to build our encrypted service, and we also give back to the community by donating Tuta Mail to open source developers.

What are the biggest challenges in developing your own push notification system to replace Google’s FCM, and how did you overcome them?

Building our own push notification system was a huge challenge – but also one that was very dear to us. We wanted to offer our app via F-Droid (our favorite app store on Android), and this is possible only if you do not use any Google services, which also includes Google Push. Getting rid of Google Push is really difficult because Google doesn’t want you to. For instance, Google’s integrated battery optimization kills other notification services, so people using the Tuta Android app must disable Google battery optimization for our app to receive push notifications instantly and reliably.

We had to get rid of Google Push in Tuta because Google and Apple monitor all push notifications – and we achieved this in 2020. This was an incredible success and our developers are proud of this achievement to this day, as not many services – not even secure ones – take this extra step to protect the privacy of their users.

How does Tuta manage to balance user convenience with strict privacy standards in app development and service provision? Can you tell us more about what seems a win-win situation?

It is a clear win-win: user convenience and strict privacy standards in all our apps are closely interlinked. We are developing an end-to-end encrypted service that lets you send encrypted email messages easily, store and share your encrypted calendars, and secure all your contacts in our app, which can be synced to your phone with a few taps. We must make sure that our encrypted service is as easy to use as a not-encrypted service. Our service comes with the same features – and still protects the user’s privacy to the maximum. While this is often a challenge in development, it pays off in quality. We cannot take any short-cuts when developing because we need to make sure that everything works smoothly without leaking any data to third parties.

Because of this we have achieved a very high standard within our apps, and people honor our effort and commitment to privacy when rating our apps: all of them have a 4+ rating. This makes us a bit proud and motivates our team to continuously strive for the best!

How does Tuta’s approach to minimal data retention and user privacy compare with the broader industry trends? What is Tuta’s “recipe” to achieve that?

We do see the trend to collect more and more data by big tech companies as an immense threat to people’s privacy and an intrusion into their personal lives. Why should a huge corporation that offers email or file storage services have full access to users’ content and use the data for personalized ads or to train their AI systems? Instead, we call on a ban for targeted ads. At Tuta, we do not want to collect personal data on our users. To the contrary, we encrypt everything by default so that only the user can access their data.

We hope that more and more people understand the value of their data and switch to services like Tuta that respect their right to privacy and keep the data ownership fully with the user – not with the service.

In addition to our own stance on privacy rights, we are in the fortunate position that Germany has some of the best privacy laws in the world. Thus it is easy for us to keep as little data as possible from our users – and be as transparent about it as possible; because transparency plays a huge part when offering a private and secure service like Tuta Mail. There is no data retention for email in Germany, which is not the case in Switzerland – a country that is often perceived as having good privacy laws while the Swiss themselves tend to disagree.

Thinking ahead, #1: With the increasing threat of quantum computing to encryption, what steps is Tuta taking to ensure future-proof security for its users?

As quantum computers are rising on the horizon, we need to upgrade to post-quantum cryptography now! That’s why we have started a research project – PQMail – years ago, and we now have a working prototype that is capable of sending and receiving messages encrypted with a hybrid protocol: standard, proven algorithms (AES & RSA) in combination with quantum-resistant algorithms. This is a huge success, and we are eager to publish this major security upgrade to our millions of users. Stay tuned, as we are working hard to make this a reality!

Thinking ahead, #2: What are Tuta’s future plans for enhancing secure communication in the face of evolving digital threats?

In addition to future-proofing our encryption protocol, we also plan to add more services to Tuta. Right now we are optimizing our email and calendar apps in terms of usability and features. Next up, we also want to build an encrypted cloud storage and file sharing solution so that people can also store and share large files with post-quantum secure encryption.

How does Tuta navigate the challenges of maintaining user privacy while ensuring compliance with global data protection regulations?

Being compliant with data protection regulation is pretty easy for us: Because we focus on protecting our users’ privacy, we are usually one step ahead of legal requirements. We protect our users’ data much better than most services—even better than required by the EU GDPR—because privacy is in our DNA!

FOSS wouldn’t exist without its communities.Can you discuss the role of community feedback in Tuta’s development process and how it shapes your privacy tools?

Our community is very special to us. From the start our users’ feedback has influenced our development decisions – and do so to this day. We love to interact with our users on GitHub, through social media, or via email when they write to our support team. It’s important to get first-hand feedback in order not to be limited to your techy-FOSS bubble. While we are open source and privacy advocates, we also must comply with people’s feature requests, like getting notifications on Android even when they do not use Google Push. When we implemented our Google Push alternative, in part it sprang from our own commitment to free people from using any Google services with Tuta, but in part it was also the FOSS community demanding this change.

In what ways does Tuta envision contributing to the broader FOSS ecosystem in the coming years?

We contribute to the FOSS ecosystem indirectly – by offering Tuta Mail for free to open source projects – and directly by building a communication app with quantum-resistant cryptography that is fully published as open source under the GPLv3. Everyone will be able to view and inspect the code, but also use the code for their own open source projects. We love how the community works together, helps each other, and builds upon each other’s ideas to make the web as whole a better place!

Source: lpi.org

Saturday 27 April 2024

Open Source Licenses: Source Code and the Legal Code

Open Source Licenses: Source Code and the Legal Code

Among the objectives for the new Linux Professional Institute (LPI) Open Source Essentials certificate, the candidate has to deal with legal aspects of developing and using open source software in a professional environment. These aspects include license compliance, legal compliance, asset protection, privacy law, and more. In this article, Andrea Palumbo, lawyer, helps us understand more about those topics.

The emerging prominence of open source software development in the 1990s heralded a paradigm shift across the computing spectrum, profoundly affecting coders, vendors, and legal regulators alike. This revolution extended beyond mere coding practices to challenge and redefine the traditional commercial and legal frameworks of software distribution. Open source licenses, as legal instruments, emerged as pivotal in governing the use, modification, and sharing of software. Such licenses underlie the infrastructure of today’s digital services, from cloud computing solutions to essential daily applications. This evolution signifies the crucial role of open-source software in laying the foundational elements of our modern digital ecosystem, making it a subject of both technological and legal significance.

Until the late 1980s, the market was dominated by a proprietary approach, with the application of so-called closed source licenses to most software, and where free software licenses represented more of a beautiful dream than a real alternative (with a few but significant exceptions). The advent of open source software changed the rules of the game.

The new legal approach that emerged in the software development scene, which by the dawn of the new millennium had established itself as a concrete reality, was primarily the assertion of a principle: that the writing, dissemination, modification, and reuse of code should be subject to rules that are not exclusively protective. Instead, these rules should allow access and utilization by others, ensuring that the benefit derived by the public (and the author themselves) from the sharing of creative works not be hindered. This concept challenges traditional views on intellectual property rights.

The era of Free Culture, as defined by Lawrence Lessig, begins here – at least regarding software. This concept promotes a “free culture” that:
“…supports and protects creators and innovators. It does this directly by granting intellectual property rights. But it does so indirectly by limiting the reach of those rights, to guarantee that follow-on creators and innovators remain as free as possible from the control of the past. A free culture is not a culture without property, just as a free market is not a market in which everything is free.” [Lawrence Lessig, Free Culture, Penguin Press, New York, 2004, p. 5.]

Free and open source licenses serve as the legal framework enabling the adaptation of law to meet the evolving demands of technology and culture. These licenses facilitate the sharing, modification, and distribution of software code, aligning with the shifting paradigms in technology use and development. Understanding the intricacies of these licenses is crucial, as they dictate how software can be used, shared, and built upon, ensuring that the legal code supports the dynamic nature of software creation and innovation.

The Significance of Open Source Licenses for Software Developers and Their Managers


While the genesis of the open source movement and the consequent development of its licenses are well documented, it’s more complex to elucidate how the rules governing the use, distribution, and modification of software are linked to software development. Open source licensing rules should be well-understood and should inform the decisions of creators throughout all stages of coding and designing software services.

Some might suggest that licenses are merely legal formalities to be addressed by legal experts after the main development process. Yet this perspective overlooks the profound impact of legal frameworks on technological development and innovation. Open source licenses exemplify the fusion of legal and technical domains, making decisions about code accessibility and collaborative conditions integral to the development cycle. These licenses highlight the essential role of legal considerations in technological advancements, refuting the notion of a divide between legal obligations and technical endeavors. Open source licensing demands that developers consider legal implications from the outset, ensuring that their decisions on sharing and improving code align with broader legal and ethical standards. The impact of the licenses underscores the intertwined nature of law and technology in fostering innovation.

Software developers must also know whether the code they modify or reuse, or the libraries they integrate into their services, can be freely used. Restrictions in the license could impose limitations on their software. These limitations can range from a simple obligation to credit the original author to more stringent restrictions on redistribution, such as those imposed by GPL licenses. Developers must also consider if the license they want to apply to their software is compatible with the original software’s license and if they wish to release their software under a dual licensing model.

Hence, this decision is not merely a legal one, but also involves business model choices, technical decisions, and ethical considerations.

What Aspects Commonly Govern Open Source Licenses, and Why You Should Study Them


The landscape of Open Source licenses is diverse and extensive, ranging from “strong copyleft” licenses like GPL to “weak copyleft” ones such as LGPL and MPL, and even “permissive” licenses like BSD or Apache 2.0. Each of these licenses governs differently and to varying degrees the rights of the public to:

  • View the software’s source code
  • Use the software’s source code
  • Modify and create derivative works from the software’s source code
  • Distribute and share of the software’s source code, both in its original version and in derived works

These rights are complex for both the original author and those of derivative works to manage. However, this cannot be an excuse for failing to understand them.

In the constantly evolving digital realm, the decision-making process on software licensing must include the programmers themselves, as legal considerations increasingly influence software development. This mutual impact underscores the necessity of understanding and integrating legal frameworks from the inception of coding to avoid market disadvantages.


Source: lpi.org

Thursday 25 April 2024

Roles in Open Source: Bringing Order to the Chaos

Roles in Open Source: Bringing Order to the Chaos

By nature, software developers – and especially open source software developers – tend to value their independence. And like all of us, they each have opinions about how things should be done. So dealing with disagreements can be all part of the fun when it comes to managing community projects.

Carefully designing a healthy and intelligent organizational structure can sometimes keep a lid on the bubbling chaos. Clear rules and policies help to establish unambiguous expectations for how the project operates and how contributions are managed. Intelligent rules can help to define the project’s governance structure, including how decisions are made, who has decision-making authority, and how conflicts are resolved.

Wherever possible, open source project managers should seek to create a friendly and accommodating environment for their volunteers. One unfortunate example that illustrates this point involves a recent decision made by a major player in the open source world. The organization changed the open source license governing code contributions to an important project, and also introduced a new Contributor License Agreement (CLA). Some of the most important contributors were deeply upset by the move and cut ties with the parent organization, causing some harm to the overall project. I don’t have an opinion over who was right here and whether the dispute could have been prevented, but I do use that particular software nearly every day, so I care deeply about the project.

A large open source project is a community effort. This won’t be the product of just a single individual and, in most cases, there won’t be a company with all its resources to fill any holes. Instead, the responsibility for making sure things get done will be distributed across the entire group. But that’ll require some serious collaboration. The first thing is to be aware of the various roles you’ll need to fill:

Project leads are typically appointed or elected by the community to lead a particular project or set of projects. They’re responsible for guiding the project’s direction and ensuring that it stays on track. They work closely with contributors to ensure that the project meets its goals and objectives. The project lead is the one who is ultimately responsible for just about everything, including tasks like planning and roadmapping, community building, coding, but tracking, and code review.

Benevolent dictators are typically the founders or original creators of an open source project. They’re responsible for making the final decisions about the project’s direction and ensuring that it stays true to its original vision.

Developers are responsible for writing, testing, and maintaining the code. They may work on specific features or modules, fix bugs, and provide code reviews.

Release managers are responsible for coordinating the release of a software product or service. They manage the release process, communicate with stakeholders, manage risks and issues, and ensure that the product meets the required quality standards.

Designers are responsible for creating the user interface and user experience of the project. They may work on the project’s branding, design assets, and visual design elements.

Testers…well, testers test the code to ensure that it is free of bugs and works as intended. They may write test cases, perform manual or automated testing, and report any issues to the development team.

Technical writers create and maintain documentation for the project. This can include user guides, developer documentation, and other resources that help users and contributors understand how to use the project.

Community managers build and manage the community around the project. This can include responding to questions and feedback from users, organizing events and meetups, and facilitating communication between contributors.

Translators are responsible for translating the project resources into different languages. This can include the user interface and documentation, which in technical projects normally start out in English.

Finally, your users – and particularly those who engage with your product with particular enthusiasm – will also play important roles. Besides potentially contributing useful ideas for new features, they’re the ones who encounter bugs in your release, and you’ll want to make it as easy as possible for them to report them.

In addition, some users may decide to fork (or copy) your project and use the code to build something new and different. You might (or might not) appreciate the competition, but that’s how open source works.

Like any large and complex endeavor, open source projects require serious planning, good communication, and a cooperative spirit. One excellent place to begin your planning is with the LPI Open Source Essentials certificate curriculum. Having created a book and course covering the cert, I can tell you that the content you’ll need to pass the exam is nicely aligned with exactly the skills you’ll need to succeed with your open source project.

Source: lpi.org

Tuesday 23 April 2024

The Big Open Source Vision at Schleswig-Holstein

The Big Open Source Vision at Schleswig-Holstein

A German state made big news recently by announcing that it was shifting to an open source strategy. Press releases focused on the decision of Schleswig-Holstein’s management to replace Microsoft Office with LibreOffice, the most popular open source office suite. But the strategy is much broader than that, and governments everywhere should take note of Schleswig-Holstein’s reasoning.

Schleswig-Holstein is a modest-sized state with about three million residents. Its best-known city is Lübeck, famous among literary circles as the locale of Thomas Mann’s novel Buddenbrooks.

The switch in office suites, first of all, reflects a desire to save money as well as to avoid vendor lock-in. These are common reasons for adopting free and open source software, but any organization taking such steps must learn to think in an open source manner. That’s what “digitization minister” Dirk Schrödter articulates in the press release (in German) posted on April 3.

Schrödter recognizes the importance of open standards to facilitate communication among different groups. The money that Schleswig-Holstein hopes to save from switching to LibreOffice will go toward a strategy of digital collaboration. Further open source moves and training for staff will follow.

Schrödter’s view of open source as a transformation in how people work with technology is similar to LPI’s approach to open source as enabling and empowering the people who learn and run it.

The use of third-party online services (popularly known as “cloud” services or Software as a Service) is another worldwide trend Schrödter recognizes, and he is very alert to the privacy and data risks that the cloud involves. He plans to adopt cloud services run on open source software, intending to make sure that data privacy is protected.

Following the move to LibreOffice, Schrödter intends a much bigger transition away from Microsoft Windows to GNU/Linux. The city of Munich initiated such a move two decades ago, and they ran into enormous opposition. Even though the rationale for the move was carefully researched and documented, resistance from both internal and external actors held up the move for years.

A switch to free and open source software is more than an installation and training task. Thinking collaboratively and in an open source manner behooves anyone who wants to benefit from open source. Schrödter and Schleswig-Holstein seem to have understood this, and the federal state appears to be on a path that is both innovative and sustainable.

Source: lpi.org

Thursday 18 April 2024

Community Survey – Let Us Know What Matters to You

Community Survey – Let Us Know What Matters to You

A new community survey from the Linux Professional Institute (LPI) is now live. We offer these surveys every 5 years, so please visit the link and help us better understand your needs and priorities.

Our goal is to continue to ensure the role of the individual in the development, adoption and professional use of open source software. To achieve this goal, LPI needs to be more driven and led by open source professionals—by the people whose skills we have certified. Results from this survey will influence the programs, benefits, and resources we offer our community members.

The survey is anonymous, responses are optional, and all data collected is subject to LPI’s Privacy Policy.

Questions cover a range of issues, including what services and training you value from LPI, what kinds of discounts and incentives we should offer, and how we can further help free and open source communities. There are also open-ended questions where you can list your concerns.


Source: lpi.org