Stimulating the Russian Open Source: how to develop open technologies and motivate contributors

Why open source, not proprietary software

According to the results of the first quarter of 2023, according to a study by Scarf, Russia topped the list of countries with the highest growth in open source software downloads - plus 220% compared to the same period in 2022. If in 2022 proprietary software (domestic and foreign solutions) occupied 81% of the Russian market, then as of mid-2024 it already accounts for 62%, and two years later, according to experts, its share will completely decrease to 36%. According to Skolkovo, today more than half of the decisions in the register of domestic software are written using open source, and Open Source products in one form or another are used by more than 85% of IT companies. All this speaks of the increased interest in open source, but why did it suddenly turn out to be so more convenient than proprietary software, or has it always been?

lucabravo на Freepik

Advantages of Open Source over proprietary software:

• Open source allows you to use world-class developments in commercial products. Since different experts work on OS solutions, as a rule, members of IT communities, this collective approach allows you to get the best result.
• Commercial software created on the basis of open source code allows corporate clients to quickly implement it into operation and adapt it to the needs of a specific company. OS tools are used by major market players, for example, X5 Group, VTB, Norilsk Nickel and many others.
• Open software retains independence from software owners. The market especially appreciated this advantage at the moment when large vendors left Russia, and the companies were left without technical support, the possibility of software updates and its further development. Open Source gives greater security and confidence, as different teams of specialists can work with open source. In addition, according to the requirements of FSTEC Russia, Open Source solutions can be used to provide a critical information infrastructure.
• An unconditional advantage is a more profitable price policy of "open" solutions compared to proprietary software.

Both IT market participants and software consumer companies believe that it is not worth counting on the return of departed suppliers of proprietary software in the near future. This means that the Russian IT market is more interested in its own independent solutions than ever.

Open Source Issues

With all the above advantages, Open Source Russia there are a number of restraining factors for wide development and application. These are, for example, the lack of qualified specialists in the Open Source solutions segment, strict state regulation and problems safety with and confidentiality. However, many of the above reasons are far from the "Russian factor," they deter developers around the world from increasing the share of published source code. But many of these risks cease to exist if the Open Source market is formed and there are large players setting the rules - independent communities, development teams, business.

What is needed for the development of Open Source in Russia

According to data, in Rosstat 2023 there were only 857 thousand in Russia. IT professionals.^[1]. Russian professionals are not sufficiently involved in the development of Open Source, while it is obvious that ON it is Linux TensorFlow Greenplum possible to create a competitive similar,, Apache only with a high concentration of IT forces. This means that the Russian IT community will have to purposefully create conditions for the development of the segment and increase the number of contributors. There are several tools that will help in solving this problem:

1. Building Infrastructure for Open Source Projects

Open Source has long ceased to be the business of "IT enthusiasts," today it is an independent niche that requires serious infrastructure throughout the production cycle: from development to documentation.

To develop the industry, there must be OS libraries in which developers can upload their projects and modified third-party solutions. Part of the infrastructure should be storefronts - aggregator platforms, where the Open Source databases of projects from various repositories are presented. The showcase can help a potential customer assess the landscape of available solutions, and direct developers to popular tasks. In addition, it can include tools that allow you to assess the professional contribution of contributors: rating system, gratitude system, social activity.

Now in Russia, git repositories appear "like mushrooms after rain" and the discussion of a centralized national repository does not subside. From our point of view, it is much more important to formulate the principles of forming OS communities and develop application services that will contribute to the development of the open source industry in general and individual projects in particular.

2. Financing of Open Source projects

Open and free software does not mean that it cannot generate income for its authors. Large companies and corporations invest a lot both in the purchase of Open Source solutions and in their own development of open source code and software based on it. Nevertheless, most of the Open Source developers are independent contributors, so additional resources are needed to form the industry - funds from private or public funds, grant programs and other investment mechanisms.

3. Creation of specialized funds for the development of Open Source

The task of such funds is also to provide the material part for the development of projects. Companies (usually small and medium-sized businesses), entering the fund's portfolio, receive funds and resources for development: contacts, a tender consortium, a backofice, complementary digital solutions and much more in exchange for a minority stake in the project.

4. Removal of administrative barriers

When at the state level there is talk of creating a national repository or discussing the register of domestic software, the first thing that all participants in the discussions agree on is the bureaucracy of the processes. This is a serious barrier for small businesses and independent developers, access to state support or the ability to be included in the repository should be available not only to large corporations, but also to all representatives of the IT sector.

Therefore, to develop open source and free software, it is necessary to simplify certification procedures and, in general, the process of IT interaction with the state, adapt legislation and expand the use of foreign Open Source licenses.

5. Developer motivation

Open Source is formed by market players, their motivation is the main driver of its growth. For each independent programmer, teams and even companies, there are reasons for developing open source solutions: professional growth, community and networking, portfolio expansion, additional income, etc. We will talk more about the reasons and ways to motivate contributors in the next paragraph.

Ways to motivate contributors

1. Community building

This is not just an "interest club," but infrastructure and new opportunities for participants who do not have single players. Communities allow you to create your own projects and participate in third-party modifications. For novice IT specialists, this is an opportunity to collaborate and receive feedback from experienced developers, Open Source projects with the help of the community can develop their own strategy for developing a code base or creating an ecosystem.

2. Public recognition

For developers, it is important to understand their professional contribution to an important and useful project. At the corporate level, there are many recognition and gratitude tools, from mentioning authors in a release or readme projects to "digital thank you." Similarly, they can be applied at the Open Source level of communities and project storefronts.

3. Open Source Project Support and Development Programs

The motive that drives many open source developers is solving extraordinary problems and professional development. A project that defies these ambitions will definitely not go unnoticed by the developers.

4. Learning and Growth Opportunities

The desire of specialists to develop makes it valuable for them to access training in different formats, mentoring authorities in their niche.

5. Reward

It is believed that financial motivation is not the main driver for open source creators, but the lack of material benefit raises at least a number of questions: who will identify vulnerabilities, fix errors, and monitor the security of solutions. Of course, the monetization mechanisms built and working contribute to the development of the market.

6. Loyalty programs, collaborations and projects for the development of Open Source in Russia

These can be internships, hackathons, contests. This is important not only for the formation of a community, but also for the exchange of experience, for working on joint projects in order to strengthen each other.

Prospects for Open Source in Russia

Worldwide, open source drives innovation, unique and powerful solutions. The progress of the Russian IT industry is associated with properly built processes for development, including Open Source, as well as the ability not to be disconnected from the international context. Not the creation of a national open source license in Russia will popularize Russian software, and the Russian open source products needed by the world will be able to popularize the Russian open source license.

For the success of Russia in the field of open source and free software, investments, long-term state support programs and methodical work to create its pool of key Open Source projects are also important.

Guidelines for Working with Open Source Components

1. Regulation of the operating procedure.

Companies working with open source software should develop local regulations and job descriptions that regulate the procedure for working with such components. In these documents, you must specify allowed and prohibited Open Source modules.

2. Obtain consent to use third-party products.

Developers should provide for the obligation to obtain the consent of the manager to use third-party Open Source products in their projects. This will help prevent possible problems related to copyright infringement and the use of unlicensed components.

3. Representations and requirements to contractors.

Contracts with contractors should provide for assurances of the absence of copyright infringement when using third-party Open Source components in the software being developed. This will avoid possible lawsuits and claims from copyright holders.

4. Employee training.

It is important to train employees, especially new ones, about the principles of open source software and the existing risks associated with its use. This will help raise awareness and reduce the likelihood of problems.

5. Use of verification systems.

Using automated systems to find and analyze Open Source code can help minimize the risk of code violations.

6. Analysis of the conditions of use and emergence of new models of technology distribution.

Exploring Open Source development strategies. Understanding the problems associated with licenses and the reasons why developers change them. This will help you focus on your own capabilities and resources of the company, and better understand the initiatives of regulators, Open Source communities.

7. Clear language.

When formulating a proposal for audiences and contributors, it is necessary to be accurate and avoid multiple interpretations, clearly determine what exactly is proposed for distribution: public code, open license or anything else.

8. Attracting professionals to prepare licenses.

The team needs people who have had experience in licensing source code and software products in order to protect their intellectual property and the company's developments.

Notes