Fighting Forks

•

2 gostaram•321 visualizações

Gunnar Hellekson

Tecnologia

Licenses keep open software open.
That's all we have.

Our process keeps software closed.
Licenses keep open software open.
That's all we have.
The world conspires against us.

Licenses keep open software open.
Tivo-ization.
Which is a fancy all we have. free-riding.
That's word for

Licenses keep Open software open.
Secret open Source.
If my lawyer finds out That's allGPL code, he's gonna kill me.
I used we have.

Licenses keep open software open.
Tweakers.
That's all we have.
I just added this one teeny-weeny patch...

Licenses keep open software open.
Government is Government.
No code distribution That's all we have. it's all Government.
requirements:

Licenses keep open software open.
Government Forges.
That's all we have.
Roach motels for code.

Licenses keep open software open.
Security.
DSS > GPL. Andall we have.
That's don't forget ITAR.

Licenses What openwe do?
keep can software open.
Hack the process.all we our act together.
That's Get have.

What do we want from the process?
Let's ask an expert.

Design for evolution.
Open a dialogue between inside and outside perspectives.
Invite different levels of participation.
Develop both public and private community spaces.
Focus on value.
Combine familiarity and excitement.
Create a rhythm for the community.

Etienne Wenger, Richard McDermott, and William M. Snyder
Cultivating Communities of Practice, 1st ed. (Harvard Business Press, 2002)

Licenses keep for Evolution open.
Design open software
That's all we have.
Include upstream contributions in contracts.

Invite different levels of participation.
Operationalize Dave Wheeler and Dan Risacher.

Develop public and private spaces.
Forges are for secrets. Unclassified work should be public.

Open a dialogue.
Talk to your PMs, your lawyers, your engineers.

Focus on value.
Less talking. More doing. Perfect is the enemy of the good, etc.

“Democracy is the enemy of useful work.” - Clay Johnson

Combine familiarity with excitement.
Tools are important.

Create a rythym.
Stay vocal and stay visible.

Do these three things.

Understand the contribution process in your patch.
Make sure everyone knows they can come to you with
questions. We have your back.

Shout your success.
We're winning every day, but nobody knows about it.

Find one patch, one script you can free.
These little guys are whithering. Get them out into the
sunlight, where they can grow.

Mais conteúdo relacionado

Semelhante a Fighting Forks

Every company needs to address how they manage open source. Verizon Media is the merger of Yahoo and AOL, and those two companies ran their open source programs quite differently. The result of bringing them together was surprisingly good, but the process to get there offers many insights into how you can structure your open source program office to address the biggest problems you may face. Ashley Wolf and Gil Yehuda explain how Verizon Media now addresses license compliance, community management, the publication process, and how to run a program office at scale. You’ll explore real-world examples of things that worked well and things that needed much repair—as well as details on how it was done—and get advice on how to apply these lessons to your businesses. Neglecting your open source program leads to problems. Ashley and Gil highlight some big ones, like when the wrong people have access to your code, license issues get you in hot water, and employees make well-meaning but incorrect decisions about code publications. Sometimes it takes a revolution to force you to step back and get a better hold on your open source program. But you don’t have to wait for a merger to force the changes. Better to set the processes right starting today; Ashley and Gil show you how. If you don’t have a formal open source program office, or if you have one that needs a boost with some new ideas about how to maximize your value to the company, join this talk.

A tale of two cities: Merging Yahoo and Aol’s open source programs

Ashley Wolf

Introduction To Open Source

Uchechukwu Obimma

Open Source Compliance at Twitter

Chris Aniszczyk

"The reason why open source happened, the reason it started, was because the people who make software are artists and craftsmen. They are not just mindless drones, that show up every day and put in their hours. They spend their evenings, their weekends, unbelievable amounts of time crafting this software. And they wanna see it used by the most people, and they wanna see it used for the best purposes, typically, and they didn’t see that happening in the proprietary software world, not any of the proprietary software companies. And so they decided – because they could – to write their own world!" Danese Cooper

The free software history and communities’ journey ahead

Ricardo Amaro

Stefan Marsiske - What would hackers use? part2

ecommerce poland expo

Succeeding with FOSS!

M A Hossain Tonu

Economics of Open Source Software

Ray Toal

Collaboration for Good Futures

Mike Linksvayer

Industry Moves to Fill Gap for Building Trusted Supply Chain Technology Accre...

Dana Gardner

How Data Loss Prevention End-Point Agents Use HPE IDOL’s Comprehensive Data C...

Dana Gardner

Open Source Solutions Swansea April 2009

Mark Hughes

How to sharpen the demand for public code across Europe and monitor progress with TEDective For six years, the Free Software Foundation Europe has been calling with a broad alliance for publicly funded software to be published as Free Software. This initiative has become a great success: Our demand "Public Money? Public Code!" has found its way into government strategy papers, party programs, as well as coalition treaties, and is being discussed in public administrations across Europe. At the same time, we see less progress than expected and vendor lock ins remain a crucial issue. Digital sovereignty is redefined bypassing Free Software. There is openwashing in publicly funded companies, and government projects in favour of Free Software remain empty words. Public statistics on the procurement of Free Software are largely unavailable. It is therefore no longer enough to promote the idea of "Public Money? Public Code!". We as the Free Software community should be even more vigilant than before – continuing to praise small steps in the right direction, but pointing out and criticising omissions and lack of implementation. We should become more like watchdogs. In the talk we will look at some examples of lack of implementation of Free Software policies. We will discuss how we, as civil society, can identify such shortcomings and how to deal with them. We will present our initiative TEDective – a free-software solution that makes European public procurement data explorable for non-experts, aiming to provide you with a powerful tool to keep an eye on real progress towards "Public Money? Public Code!" across Europe.

SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...

South Tyrol Free Software Conference

Open Source & Free Software

Freddy Rolland

Ken has over 20 years experience in the global library software business. He set up his consulting business in 2007 and has worked on projects for the UK's JISC (Joint Information Systems Committee), SCONUL (Society of College, National and University Libraries) and the UK’s Research Information Network (RIN). He is currently working on a HEFCE funded project that include both shared services and Open Source in its remit. He works on technology issues and strategy development with major libraries. He has published articles and presented widely on the strategic impact of technology driven change’

Session 2 - Libraries and Open Source

Jonathan Field

Gup2011| open source

Outserve

Ethical Consideration of Open Source Software

Larry Jennings

The Role of IT for Social Change

Netcetera

Why software freedom matters

Ruwan Ranganath

Free software basics

Vitor Pamplona

Open Source & Open Development

Sander van der Waal

Semelhante a Fighting Forks (20)

A tale of two cities: Merging Yahoo and Aol’s open source programs

Introduction To Open Source

Open Source Compliance at Twitter

The free software history and communities’ journey ahead

Stefan Marsiske - What would hackers use? part2

Succeeding with FOSS!

Economics of Open Source Software

Collaboration for Good Futures

Industry Moves to Fill Gap for Building Trusted Supply Chain Technology Accre...

How Data Loss Prevention End-Point Agents Use HPE IDOL’s Comprehensive Data C...

Open Source Solutions Swansea April 2009

SFSCON23 - Johannes Näder Linus Sehn - Let’s monitor implementation of Free S...

Open Source & Free Software

Session 2 - Libraries and Open Source

Gup2011| open source

Ethical Consideration of Open Source Software

The Role of IT for Social Change

Why software freedom matters

Free software basics

Open Source & Open Development

Último

Webinar Recording: https://www.panagenda.com/webinars/easier-faster-and-more-powerful-notes-document-properties-reimagined/ Have you ever felt frustrated by the small properties dialog in Notes? Had to create an agent or button to quickly change a field? Searched endlessly for the field you wanted to compare each time you selected a new document? Wished you could just make the damned thing bigger? Luckily, there is a solution – and you probably already have it installed! With the free panagenda Document Properties (Pro) you get the properties dialog you always needed. Big, resizable, full-text searchable. View multiple documents at once or compare them with a diff viewer. Modify any field, and finally have an easy way to handle profile documents for all users. Join HCL Lifetime Ambassador Julian Robichaux to discover how Document Properties can simplify your work and assist you daily when using Domino applications – in the client or the designer. You will never look back! Key takeaways from this session - What Document Properties is, which editions there are, and how you can find it in Notes and Domino Designer - How you can search for and edit any field, compare documents, or CSV export all data - How to find, edit, and even delete profile documents - Which configuration settings are available to customize feature

Easier, Faster, and More Powerful – Notes Document Properties Reimagined

panagenda

Extensible Python: Robustness through Addition - PyCon 2024

Patrick Viafore

Designing inclusive products is not only a social responsibility but also a business imperative. This talk delves into the journey of creating accessible hardware products that cater to diverse user needs. Key Topics Covered: 1. Introduction to Inclusive Design - Importance of accessibility in product design - Overview of Comcast's commitment to making products accessible to a wide audience 2. Case Study: Xfinity Large Button Voice Remote - Initial challenges and the evolution of the product - User research and feedback that shaped the design - Key features of the final product and their benefits 3. Designing for Diverse Needs - Understanding human-centered design and its historical context - The impact of designing for people with disabilities on overall product quality - Examples from other industries, such as architecture and industrial design 4. Integrating Accessibility from the Beginning - The cost and efficiency benefits of designing for accessibility from the start - The process of embedding accessibility as a core trait rather than an optional feature 5. Real-World Impact and Continuous Improvement - Insights from in-home studies with users having assistive needs - How continuous feedback and iterative design lead to better products - The role of inclusive research and development practices

Designing for Hardware Accessibility at Comcast

UXDXConf

WebAssembly is Key to Better LLM Performance

Samy Fodil

Webinar Recording: https://www.panagenda.com/webinars/alles-neu-macht-der-mai-wir-durchleuchten-den-verbesserten-notes-eigenschaftendialog/ Haben Sie sich schon einmal über den zu kleinen Eigenschaftendialog in Notes geärgert? Mussten Sie einen Agenten oder eine Aktion erstellen, um schnell mal ein Feld zu ändern? Haben Sie jedes mal endlos nach dem zu vergleichenden Feld gesucht, nachdem Sie ein neues Dokument ausgewählt haben? Wollten Sie das verdammte Ding einfach nur größer machen? Zum Glück gibt es dafür eine Lösung – und sie ist wahrscheinlich bereits installiert! Mit dem kostenlosen panagenda Document Properties (Pro) erhalten Sie den Eigenschaftendialog, den Sie schon immer haben wollten. Größer, anpassbar, und im Volltext durchsuchbar. Sehen Sie mehrere Dokumente gleichzeitig oder vergleichen Sie mit einem Diff-Viewer. Ändern Sie beliebige Felder und haben Sie endlich eine einfache Möglichkeit, Profildokumente für alle Benutzer zu verwalten. Entdecken Sie mit HCL Ambassador Marc Thomas, wie Document Properties Ihre Arbeit vereinfachen und Sie bei der täglichen Verwendung von Domino-Anwendungen unterstützen kann – im Client oder im Designer. Sie werden es nicht bereuen! Für Sie in diesem Webinar - Was Document Properties ist, welche Editionen es gibt und wo es in Notes und Domino Designer zu finden ist - Wie Sie nach einem beliebigen Feld suchen und es bearbeiten, Dokumente vergleichen oder alle Daten per CSV exportieren können - Suchen, Bearbeiten und auch Löschen von Profildokumenten - Welche Konfigurationseinstellungen verfügbar sind, um Funktionen anzupassen - Wie Ihre Endbenutzer davon profitieren - Sehen Sie alles in einer Live-Demo

Easier, Faster, and More Powerful – Alles Neu macht der Mai -Wir durchleuchte...

panagenda

Intro in Product Management - Коротко про професію продакт менеджера

Mark Opanasiuk

This talk offers actionable insights at an executive level for enhancing productivity and refining your portfolio management approach to propel your organization to greater heights. Key Points Covered: 1. Experience Transformation: - The core challenge remains consistent across organizations: converting budget into user-centric designs. - Strategies for deploying design resources effectively in both startups and large enterprises. 2. Strategic Frameworks: - Introduction to the "Ziggurat of Impact" model, detailing layers from basic system interactions to comprehensive customer experiences. - Practical insights on creating frameworks that scale with organizational complexity. 3. Organizational Impact: - Real-world examples of navigating design in large settings, focusing on the synthesis of consumer products and customer experiences. - Emphasis on the importance of designing systems that directly influence customer interactions. 4. Design Execution: - Detailed walkthrough of organizational layers affecting design execution, from touchpoints and customer activities to shared capabilities. - How to ensure design influences both the micro and macro aspects of customer interactions. 5. Measurement and Adaptation: - Techniques for measuring the impact of design decisions and adapting strategies based on data-driven insights. - The critical role of continuous improvement and feedback in refining customer experiences.

Structuring Teams and Portfolios for Success

UXDXConf

Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf

FIDO Alliance

FDO for Camera, Sensor and Networking Device – Commercial Solutions from VinC...

FIDO Alliance

Overview of Hyperledger Foundation

Hyperleger Tokyo Meetup

Are you wondering why everyone is talking about the Flutterwave scandal? You’re not alone! It’s been in the news a lot. We’re going to tell you all about the Flutterwave Scandal in a way that’s easy to get. Keep reading, because we’re going to share the whole story with you. The company Flutterwave is headquartered in San Francisco, California, United States. In 2016, Iyinoluwa Aboyeji, Olugbenga Agboola, and Adeleke Adekoya established Flutterwave. It offers a payment infrastructure to international merchants and payment service providers throughout Africa. The company operates in various African countries including Nigeria, Kenya, Uganda, Ghana, South Africa, and others. They focus on digital payments, helping businesses accept and process payments on various channels like the web, mobile, ATM, and POS. Recently, they’ve been in the news due to allegations of misconduct within the company, which has affected their reputation and value. Flutterwave is an essential player in the African fintech landscape, aiming to drive growth for banks and businesses through digital payment solutions. The Flutterwave scandal involves allegations of misconduct and inappropriate behaviour towards female employees by the company’s co-founder and CEO, Olugbenga Agboola. Reports have surfaced from both current and former employees about bullying, intimidation, and sexual harassment at work. The allegations of inappropriate behaviour towards female employees at Flutterwave, specifically involving the CEO Olugbenga Agboola, were brought to public attention in April 2022.This was when Clara Wanjiku Odero, an ex-employee and current CEO of Credrails, published a Medium post and a series of tweets on April 4, 2022, accusing Flutterwave and Agboola of bullying. These allegations were part of a broader range of misconduct claims that surfaced around the same time The reasons behind the scandal are rooted in accusations of unethical behavior within the company. The allegations suggest a workplace culture that allowed for misconduct and failed to protect employees from harassment and intimidation. Specifically, the Flutterwave scandal refers to the series of events where the CEO was accused of engaging in improper conduct with female colleagues. This led to a broader investigation into the company’s practices and raised serious concerns about the fintech’s corporate governance. The scandal had significant repercussions, including a drop in the company’s stock price and a loss of trust among customers and partners. The trust that customers and investors had in Flutterwave was greatly damaged. People started to doubt the company’s integrity and whether their money and personal information were safe. Market Impact The scandal shook the entire fintech market. Flutterwave’s competitors saw this as an opportunity and started to attract customers who were leaving Flutterwave.

Breaking Down the Flutterwave Scandal What You Need to Know.pdf

UK Journal

Continuing Bonds Through AI: A Hermeneutic Reflection on Thanabots

Leah Henrickson

Microsoft CSP Briefing Pre-Engagement - Questionnaire

Exakis Nelite

Using IESVE for Room Loads Analysis - UK & Ireland

IES VE

Portal Kombat : extension du réseau de propagande russe

中央社

Choosing the Right FDO Deployment Model for Your Application _ Geoffrey at In...

FIDO Alliance

New customer? New industry? New cloud? New team? A lot to handle! How to ensure the success of the project? Start it well! I've created the 3 areas of focus at the beginning of the project that helped me in multiple roles (BA, PO, and Consultant). Learn from real-world experiences and discover how these insights can empower you to deliver unparalleled value to your customers right from the project's start.

Powerful Start- the Key to Project Success, Barbara Laskowska

CzechDreamin

AI presentation and introduction - Retrieval Augmented Generation RAG 101

vincent683379

Secure Zero Touch enabled Edge compute with Dell NativeEdge via FDO _ Brad at...

FIDO Alliance

Oauth 2.0 Introduction and Flows with MuleSoft

shyamraj55

Fighting Forks

1. Fighting Forks When Open Source Disappears into the Pentagon and What We Can Do About It Gunnar Hellekson Chief Technology Strategist, Red Hat US Public Sector gunnar.hellekson@redhat.com · 202 507 9027 · @ghelleks 3 August 2010

2. Licenses keep open software open. That's all we have.

3. Our process keeps software closed. Licenses keep open software open. That's all we have. The world conspires against us.

4. Licenses keep open software open. Tivo-ization. Which is a fancy all we have. free-riding. That's word for

5. Licenses keep Open software open. Secret open Source. If my lawyer finds out That's allGPL code, he's gonna kill me. I used we have.

6. Licenses keep open software open. Tweakers. That's all we have. I just added this one teeny-weeny patch...

7. Licenses keep open software open. Government is Government. No code distribution That's all we have. it's all Government. requirements:

8. Licenses keep open software open. Government Forges. That's all we have. Roach motels for code.

9. Licenses keep open software open. Security. DSS > GPL. Andall we have. That's don't forget ITAR.

10. Licenses What openwe do? keep can software open. Hack the process.all we our act together. That's Get have.

11. What do we want from the process? Let's ask an expert. Design for evolution. Open a dialogue between inside and outside perspectives. Invite different levels of participation. Develop both public and private community spaces. Focus on value. Combine familiarity and excitement. Create a rhythm for the community. Etienne Wenger, Richard McDermott, and William M. Snyder Cultivating Communities of Practice, 1st ed. (Harvard Business Press, 2002)

12. Licenses keep for Evolution open. Design open software That's all we have. Include upstream contributions in contracts.

13. Invite different levels of participation. Operationalize Dave Wheeler and Dan Risacher.

14. Develop public and private spaces. Forges are for secrets. Unclassified work should be public.

15. Open a dialogue. Talk to your PMs, your lawyers, your engineers.

16. Focus on value. Less talking. More doing. Perfect is the enemy of the good, etc. “Democracy is the enemy of useful work.” - Clay Johnson

17. Combine familiarity with excitement. Tools are important.

18. Create a rythym. Stay vocal and stay visible.

19. Do these three things. Understand the contribution process in your patch. Make sure everyone knows they can come to you with questions. We have your back. Shout your success. We're winning every day, but nobody knows about it. Find one patch, one script you can free. These little guys are whithering. Get them out into the sunlight, where they can grow.

20. 20

Fighting Forks

Recomendados

Recomendados

Mais conteúdo relacionado

Semelhante a Fighting Forks

Semelhante a Fighting Forks (20)

Último

Último (20)

Fighting Forks