Skip to main content

Home/ QN2019/ Group items tagged soutenabilité

Rss Feed Group items tagged

Aurialie Jublin

Les Communs numériques sont-il condamnés à devenir des « Communs du capital »... - 0 views

  •  
    Faudrait-il que les géants du numérique fassent davantage et qu'ils prennent en charge de manière significative la soutenabilité à long terme du Commun numérique que représente Wikipédia ? Cette question renvoie à celle de la réciprocité pour les Communs, qui est à la fois absolument essentielle et très ambivalente. Si on élargit la perspective aux logiciels libres, force est de constater que ces Communs sont devenus une infrastructure essentielle sans laquelle Internet ne pourrait plus fonctionner aujourd'hui (90% des serveurs dans le monde tournent sous Linux, 25% des sites internet utilisent WordPress, etc.). Mais beaucoup de ces projets souffrent d'un problème de maintenance et de financement, car leur développement repose sur des communautés dont les moyens sont sans rapport avec l'importance des ressources qu'elles mettent à disposition du monde entier. C'est ce que montre très bien l'ouvrage « Sur quoi reposent nos infrastructures numériques ? Le travail invisible des faiseurs du web » signé par Nadia Enghbal
Aurialie Jublin

Open source sustainability | TechCrunch - 0 views

  • Engineers around the world pour their sweat and frankly, their hearts into these passion projects that undergird all software in the modern internet economy. In exchange, they ask for nothing in return except for recognition and help in keeping their projects alive and improving them. It’s an incredible movement of decentralized voluntarism and represents humanity at its best.
  • Two years later, a new crop of entrepreneurs, open source maintainers, and organizations have taken Eghbal up on that challenge, developing solutions that maintain the volunteer spirit at the heart of open source while inventing new economic models to make the work sustainable. All are early, and their long-term effects on the output and quality of open source are unknown. But each solution offers an avenue that could radically change the way we think of a career in open source in the future.
  • Eghbal’s report two years ago summarized the vast issues facing open source maintainers, challenges that have remained essentially unchanged in the interim. It’s a quintessential example of the “tragedy of the commons.” As Eghbal wrote at the time, “Fundamentally, digital infrastructure has a free rider problem. Resources are offered for free, and everybody (whether individual developer or large software company) uses them, so nobody is incentivized to contribute back, figuring that somebody else will step in.” That has led to a brittle ecosystem, just as open source software reached the zenith of its influence.
  • ...22 more annotations...
  • Eghbal pointed to OpenSSL as an example, a library that powers a majority of encrypted communications on the web. Following the release of the Heartbleed security bug, people were surprised to learn that the OpenSSL project was the work of a very small team of individuals, with only one of them working on it full-time (and at a very limited salary compared to industry norms).
  • No one wants open source to disappear, or for maintainers to burnout. Yet, there is a strong cultural force against commercial interests in the community. Money is corrupting, and dampens the voluntary spirit of open source efforts. More pragmatically, there are vast logistical challenges with managing money on globally distributed volunteer teams that can make paying for work logistically challenging.
  • Kyle Mitchell, a lawyer by trade and founder of License Zero, says that there is an assumption that “Open source will continue to fall from the sky like manna from heaven and that the people behind it can be abstracted away.” He concludes: “It is just really wrong.”That view was echoed by Henry Zhu, who is the maintainer of the popular JavaScript compiler Babel. “We trust startups with millions of VC money and encourage a culture of ‘failing fast,’ yet somehow the idea of giving to volunteers who may have showed years of dedication is undesirable?” he said.
  • Mitchell believes that one of the most important challenges is just getting comfortable talking about money. “Money feels dirty until it doesn’t,” he said. “I would like to see more money responsibility in the community.” One challenge he notes is that “learning to be a great maintainer doesn’t teach you how to be a great open source contractor or consultant.” GitHub works great as a code repository service, but ultimately doesn’t teach maintainers the economics of their work.
  • Perhaps the greatest debate in sustaining open source is deciding who or what to target: the individual contributors — who often move between multiple projects — or a particular library itself.
  • Patreon is a crowdsourced subscription platform, perhaps best known for the creatives it hosts. These days though, it is also increasingly being used by notable open source contributors as a way to connect with fans and sustain their work. Aboukhadijeh launched his page after seeing others doing it. “A bunch of people were starting up Patreons, which was kind of a meme in my JavaScript circles,” he said. His Patreon page today has 72 contributors providing him with $2,874 in funding per month ($34,488 annually).
  • That may seem a bit paltry, but he explained to me that he also supplements his Patreon with funding from organizations as diverse as Brave (an adblocking browser with a utility token model) to PopChest (a decentralized video sharing platform). That nets him a couple of more thousands of dollars per month.
  • Aboukhadijeh said that Twitter played an outsized role in building out his revenue stream. “Twitter is the most important on where the developers talk about stuff and where conversations happen…,” he said. “The people who have been successful on Patreon in the same cohort [as me] who tweet a lot did really well.”
  • For those who hit it big, the revenues can be outsized. Evan You, who created the popular JavaScript frontend library Vue.js, has reached $15,206 in monthly earnings ($182,472 a year) from 231 patrons. The number of patrons has grown consistently since starting his Patreon in March 2016 according to Graphtreon, although earnings have gone up and down over time.
  • While Patreon is one direct approach for generating revenues from users, another one is to offer dual licenses, one free and one commercial. That’s the model of License Zero, which Kyle Mitchell propsosed last year. He explained to me that “License Zero is the answer to a really simple question with no simple answers: how do we make open source business models open to individuals?”
  • License Zero is a permissive license based on the two-clause BSD license, but adds terms requiring commercial users to pay for a commercial license after 90 days, allowing companies to try a project before purchasing it. If other licenses aren’t available for purchase (say, because a maintainer is no longer involved), then the language is no longer enforceable and the software is offered as fully open source. The idea is that other open source users can always use the software for free, but for-profit uses would require a payment.
  • Mitchell believes that this is the right approach for individuals looking to sustain their efforts in open source. “The most important thing is the time budget – a lot of open source companies or people who have an open source project get their money from services,” he said. The problem is that services are exclusive to a company, and take time away from making a project as good as it can be. “When moneymaking time is not time spent on open source, then it competes with open source,” he said.
  • Supporting individuals makes a lot of sense, but often companies want to support the specific projects and ecosystems that underpin their software. Doing so can be next to impossible. There are complicated logistics required in order for companies to fund open source, such as actually having an organization to send money to (and for many, to convince the IRS that the organization is actually a non-profit). Tidelift and Open Collective are two different ways to open up those channels.
  • Fischer and his team wanted to create a platform that would allow open source ecosystems to sustain themselves. “We felt frustrated at some level that while open source has taken over a huge portion of software, a lot of the creators of open source have not been able to capture a lot of the value they are creating,” he explained.Tidelift is designed to offer assurances “around areas like security, licensing, and maintenance of software,” Fischer explained. The idea has its genesis in Red Hat, which commercialized Linux. The idea is that companies are willing to pay for open source when they can receive guarantees around issues like critical vulnerabilities and long-term support. In addition, Tidelift handles the mundane tasks of setting up open source for commercialization such as handling licensing issues.
  • Tidelift initially launched in the JavaScript ecosystem around React, Angular, and Vue.js, but will expand to more communities over time. The company has raised $15 million in venture capital from General Catalyst and Foundry Group, plus former Red Hat chairman and CEO Matthew Szulik.
  • Fischer hopes that the company can change the economics for open source contributors. He wants the community to move from a model of “get by and survive” with a “subsistence level of earnings” and instead, help maintainers of great software “win big and be financially rewarded for that in a significant way.”
  • Where Tidelift is focused on commercialization and software guarantees, Open Collective wants to open source the monetization of open source itself.Open Collective is a platform that provides tools to “collectives” to receive money while also offering mechanisms to allow the members of those collectives to spend their money in a democratic and transparent way.
  • Xavier Damman, founder president of Open Collective, believes that this radical transparency could reshape how the economics of open source are considered by its participants. Damman likens Open Collective to the “View Source” feature of a web browser that allows users to read a website’s code. “Our goal as a platform is to be as transparent as possible,” he said.
  • Open Collective was launched in late 2015, and since then has become home to 647 open source projects. So far, Webpack, the popular JavaScript build tool, has generated the most revenue, currently sitting at $317,188 a year. One major objective of the organization is to encourage more for-profit companies to commit dollars to open source. Open Collective places the logos of major donors on each collective page, giving them visible credit for their commitment to open source.
  • Damman’s ultimate dream is to change the notion of ownership itself. We can move from “Competition to collaboration, but also ownership to commons,” he envisioned.
  • It’s unfortunately very early days for open source sustainability. While Patreon, License Zero, Tidelift, and Open Collective are different approaches to providing the infrastructure for sustainability, ultimately someone has to pay to make all that infrastructure useful. There are only a handful of Patreons that could substitute for an engineer’s day job, and only two collectives by my count on Open Collective that could support even a single maintainer full time. License Zero and Tidelift are too new to know how they will perform yet.
  • The change though can happen through all of us who work on code — every software engineer and product manager. If you work at a for-profit company, take the lead in finding a way to support the code that allows you to do your job so efficiently. The decentralization and volunteer spirit of the open source community needs exactly the same kind of decentralized spirit in every financial contributor. Sustainability is each of our jobs, every day. If we all do our part, we can help to sustain one of the great intellectual movements humanity has ever created, and end the oxymoron of open source sustainability forever.
  •  
    "Open source maintainers are exhausted and rarely paid. A new generation wants to change the economics."
Aurialie Jublin

Timeline of progress towards a more sustainable web - Susty WP - 0 views

  •  
    De 2006 (The Green Web Foundation) à nos jours
Aurialie Jublin

Building for sustainability with WordPress - Susty WP - 0 views

  •  
    "This website aims to act as a guide to making WordPress websites more sustainable, and to serve as a practical example of how we can tune our websites and reduce their carbon footprint. The homepage of this website is delivered to your browser with just 7KB of data transfer. This is achieved by its theme, plugins and configuration. As of 2016, the average website data transfer was 2.3MB, making it 333 times bigger than this website!"
1 - 4 of 4
Showing 20 items per page