Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tell our sustainability story #231

Closed
4 tasks done
Tracked by #237 ...
chadwhitacre opened this issue Jan 30, 2024 · 4 comments
Closed
4 tasks done
Tracked by #237 ...

Tell our sustainability story #231

chadwhitacre opened this issue Jan 30, 2024 · 4 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Jan 30, 2024

@chadwhitacre chadwhitacre mentioned this issue Jan 30, 2024
18 tasks
@chadwhitacre chadwhitacre changed the title Tell our sustainability story. Tell our sustainability story Jan 30, 2024
@chadwhitacre chadwhitacre mentioned this issue Feb 2, 2024
3 tasks
@chadwhitacre
Copy link
Member Author

chadwhitacre commented Apr 9, 2024

Phew! This has gone around the block like 210 times. I thiiiiiiiiinnnnk we're dialing it in?

  1. Sustainability - we value user freedom and developer sustainability
    1. Licensing
      1. Fair Source - general movement
      2. FSL - specific license
    2. Funding
      1. FOSS Funders - low barrier to entry - anyone who gives anything and blogs about it
      2. OSS Pledge - higher barrier to entry - recurring program with an amount tied to some objective measure (e.g., revenue, profit, headcount)
      3. Software Commons - potential future entity with a more active role

@chadwhitacre
Copy link
Member Author

chadwhitacre commented Apr 9, 2024

I guess I'm still chewing on whether we handle licensing and funding under one brand or two. I thought to go with one brand under Software Commons and that didn't work (commons is too loaded a term). Would we want to try this under "Fair"? 🤔

Test:

Fair Source is an evolution of Open Source that elevates developer sustainability to a value on par with user freedom, via two mechanisms: Fair Source licenses, and the Fair Source Pledge.

@chadwhitacre
Copy link
Member Author

The reason to try to do them both under one brand is that they both derive from one set of values. The risk is that we confuse people who are generally either thinking of one or the other as relevant to them.

@chadwhitacre
Copy link
Member Author

Guidance from internal convo:

For me: outcome is pledge gets adoption, not that it validates FSL. If there's not a reason to connect the narratives we shouldnt be forcing it. The pledge getting adoption gives us weight, weight gives us power, power lets us do more things. So don't sacrifice the adoption of the pledge by making it confusing naming just to force couple it to the other efforts. There are ways to benefit the other agendas without naming it something confusing, fwiw, like in the PR/etc. we can always talk about both efforts, or why this is important, and connect it back, etc. But we have to be given a voice to talk about it, so voice is most important.

And:

FWIW I think they need to be separate ideas that support each other:

Fair Source: For companies who want to be open but defend against free-riders. Safe haven for OSS companies, or open-curious cos that never opened up because of the free rider threat (and hopefully if we build enough of a brand around it, companies who never even considered the idea of opening up but now have FOMO). Small tent we want to grow into a medium-and-growing tent

Pledge: Every single tech company that leverages OSS in a meaningful way (every tech co) should take the Pledge, and be seen as a pariah if they don't. Biggest tent imaginable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant