# TL;DR
- Our license/terms of service approach is “you can do what you want this code, just don’t kill anyone and be responsible.” while allowing for other social justice clauses.
- We’re similar to open source but with additional terms focused on preventing military use and respecting the wishes of anyone who does not want their code to kill. Code Bloom is intended to provide security and ensure compliance with receipts for legal agreements.
- When we cant license contributions under an Ethical Source License we will redistribute FLOSS software in an Ethical vetted manner
- While we are in solidarity with many different causes, we aim to be narrow in scope with regard to our core ethics and to be a higly pluralistic organization; accomidating in many different people of many different perspectives without getting too strongly tied to an overall ideological framework
- We exist to normalize the idea of a life-affirming kill-free world, give exposure to the Consistent Life Ethic, and show solutions in action. We uphold our principles joyfully, and we hope you will give us a chance.
- Putting your code on Code Bloom might be a good idea If your a researcher, an engineer, or your just building a very general product
- AND your work has a potential for misuse (possibly mass-surveillance, a missile, military/killer robots or AI?)
- OR your work will be used when a person is in someone else’s care (health, education, elderly care, search & rescue, etc.)
- OR you just don’t want your code being scraped for AI training (and you might want that AI licensed ethically)
- THEN putting your code on Code Bloom might be a good idea
# How Do You Plan To Achieve All This?
Good question, we plan to do so through a combination of policy & technology. We don’t want to get too specific yet, as we plan to put our specifics into proposals that will be available once our system is up. Roughly, however, based on what we have in mind for now (with no future commitment):
- Our “threat model” will be centered around preventing someone from being able to obtain covered software/source code an official source without legal agreement and producing evidence of legal agreement, this part will be backed by our technology, we will develop our “Ethics Based Access Control” technologies around this
- Some repositories may have more “security” than others depending on the contributor’s wishes, the applications of the work, how developed a work is, or the generality of the work
- Our licenses and terms of service will outline the specific ways in which others are suppose to be good Stewards of the software, their responsibilities and limits, our systems will ensure they are giving their informed consent.
- Different terms will apply to different types of entities, individuals and hobbyists will be bound to a lower standards than large companies or government agencies
- There may be a concept of “targeted traceability” as an enforcement mechanism, where obtaining software is anonymous, tracing is difficult (and therefore only done when necessary) and often privacy & anonymity preserving (sounds like a contradiction? wait for our proposal)
- Our approach is as much about the social structure & community as it is about policy & technology Please keep in mind this is all proposed, its not concrete yet, we have simply put a lot of thought into these things, drafted some things, researched, etc. We plan to build this in ethical-source way.
# Do We Really Need All This?
Unfortunately we do; many engineers, developers, researchers, and scientists do not wish to contribute to war/killing or the development of weapons, but simply feel they have no other choice but to work within such a system that uses their work to kill (even if that just means putting their work out in the open). Alternatively those same developers/scientists/engineers/researchers may not feel they have much opportunity for work within their chosen field other than to directly contribute to military/weapons research/work/development be that directly or indirectly.
In fact during the process of getting code-bloom started, the U.S department of defense/war actively started to contradict what we stand for, the ability of developers to be uninvolved in unethical/lethal use, we did even not know that would happen when we got started!
However it does not need to be this way, if we wish to avoid contributing to killing with our work (and many people do) or build a more life-affirming & ethical world: we need to establish purpose-built alternative institutions and get going! In the case of Code Bloom, this is how we give people the chance to divest (or propose an alternative way of hosting company projects) while also providing the opportunity to work on more life-affirming projects.
Simply do a search for “open source military” or “free software military” and you will see formal evaluations that various agencies have made about the use of FLOSS in the military
We will be posting more information which will make the need for our cause more clear with future blog posts (…perhaps or subscribe to our RSS feed?), but for now you can simply look at the list of Other Organizations below for further information. However in summery, funding for Science Technology Engineering and Mathematics has long been tied and entangled with the military industrial complex.
With our work, we hope to push other organizations and companies that host source code towards similar standards. By investing in Code Bloom your investing in making the peaceful future happen today!
# Are You Going To Track or Surveil People?
No. We have ideas about how to implement anonymity and privacy preserving accountability measures but nothing concrete yet though we have “canidate” ideas on how to implement this:
- Having levels of trust
- Partner with communities and work with their processes for inviting, reccomending or authenticating individuals
- Use of a Cryptographic Web of Trust or reputation system
- Use of Zero Knowledge Poofs
- Require secure multi-party compute to recover information
- Require computationaly expensive operations to recover information
- Require voluntary consent for certain processes, such as disclosing a token proving legal agreement
- The use of smart contracts or the blockchain
None of this is concrete, finalized, or perfect and we likely will implement several mechanisms, we would love to hear your feedback or proposal when our proposals page is ready! In the mean time drop us a line or get involved
# What is “Ethical Source”?
Ethical Source is similar to Open Source or Free/Libre software but with limitations or obligations put on the terms of use or rights granted for ethical reasons or intended to uphold certain values. We like to think of it like pairing each right to a responsibility. This modification could also be made to Open Core, Shared Source/Source Available, or Proprietary software. Here at Code Bloom we focus on the “FLOSS” variant and have an affinity for the ethical thought behind Free/Libre Software: helping one’s neighbor, preventing the exercise of unjust power over a user, etc.
# What is the “Consistent Life Ethic”?
The Consistent Life Ethic (CLE), can be described a life-affirming ethic for the preservation of life, a duty of basic care, and concern for human dignity while being in opposition to killing, aggressive violence (compatible with the Non Aggression Principle), and deprivation of basic needs. It incorporates elements of the Ethic of Non-Killing (ENK), Non-Violence or Pacifism which extended beyond concern about war. While the CLE has its roots in Catholic thought, the CLE is a universally accessible philosophy that does not depend on any particular religious, political, or ideological background about something that is common to all of us: life. Code Bloom aims to be an institution that upholds it and creates the conditions for anyone who upholds any part of it to have a safe place to share their work and collaborate! To learn more please visit:
# Consistent Life Ethic
- Rehumanize International’s website
- Consistent Life Network’s website.
- The Global Center for Non-Killing’s (non-killing, not CLE) website
- Wikiversity ethics/nonkilling
- See Other Organizations
# Do I Have To Agree With The Whole Consistent Life Ethic to use Code Bloom
# Effectively: No
Code Bloom mostly exists to protect against military use of code, We intend to include explicit disclaimers in all our licenses/terms of use that the use of our services, licensing a work under our licenses, or using a work licensed in such a way is an endorsement of the Consistent Life Ethic.
It will also always be possible to distribute your work under a different license through a different channel
# Thinking of Others
You don’t have to agree with all people and parts of the CLE to respect the wishes of others and empathize with their view, especially when they consider it - literally - to be a matter of life or death (via an empirically verifiable phenomena), all are welcome
# Will You Make a License That Makes X Part of the Consistent Life Ethic Optional or Add an Exception?
No, we will not exclude any group of person from being protected intentionally
# Why Not Just Be Pacifist Only?
Its not who we are 🙂
We don’t want our work to be used to kill anyone in any way, nor do we wish to distribute the work of others to do so. Code Bloom is a safe harbor not a long term solution; you could make another “safe-harbor” platform that is “only pacifist” and we would consider that to be a good thing, we only ask you do not engineer in an intentional incompatibility.
# What About Open Source and Free/Libre Software
We love Free/Libre and Open Source Software (FLOSS)! However from the beginning it has always been intended that FLOSS be allowed for military use nor does it allow for discriminating against fields of endeavor (see no. 6) even when those fields of endeavor involve surveying people so they can be tortured, the death penalty, and abortion (you can look at our blog for more). In an ideal society piecemeal solutions like Code Bloom would not exist and we would have laws prohibiting all forms of killing people, In such a world, free software licenses would be unchanged and specific ethical source licenses either would not exist, or would only exist for the purpose of vigilance, we plan to defer to local law when such a law sufficiently covers a certain area of concern.
# With Code Bloom FLOSS Developers Will Have Options:
- If you own the copy-right, they may choose to dual-license or re-license their code to a compatible Ethical Source License
- Code may be re-hosted or forked and hosted on a Code Bloom server and redistributed under the server’s/Code Bloom’s Terms of Service; preventing uses that violate the Consistent Life Ethic.
- Developers can pull from upstream and contribute patches, fix bugs or add features to the Code Bloom version that do not get used in a way that violates the CLE
# What About Existing Ethical Source Licenses
Existing Ethical Source licenses such as the Do No Harm License, the Hippocratic License, or the Licenses offered by The Organization for Ethical Source are great, however, they are a but broad in scope or are somewhat unrealistic given social constraints. We value these licenses, however, we take the approach of being specific, minimal, and “narrow”(-ish) as to what our licenses entail/allow.
# I Also Care About [X] And Want My License To Address It!
Great! We are glad you’re a conscientious person who is passionate about something. We need more people like you! We plan to create modules for additional specific social justice causes that can be added on to our licenses, and the ability to customize our licenses so long as the Consistent Life Ethic is upheld. Some of these additional areas of concern will be Environmentalism, Privacy, anonymity, Civil Rights, AI, Ethical Supply Chains, and ethical Content Moderation & Anti-Censorship. Wealso plan to have a way to submit additional proposals.
# You Can’t Not Use All Technology The Military Has Touched
You’re right! Our objective is to build ethical and life affirming technologies while not contributing to lethal technologies. We consume the system but do not contribute back to the outside system.
# But The Military Does Some Good Things!
The military is often is associated with humanitarian work (though this sometimes comes with a strategic objective), search and rescue efforts, and other “good things”. Many people would also say that proportionate defensive wars as a last resort are justified. While pacifists and consistent-life people may land in different places on this issue we stipulate the following
- It is not necessary for all software to support the military or the development of weapons. Even if you support these efforts in some way, we are allowed to have a safe space to develop it free from these concerns
- The vast majority of cases where weapons are used do not meet the criteria most of pacifists or CLE supporters. Our community will help them insulate their work from unjust use in lethal weapons
- Most militaries have committed some sort of atrocity that any sober, rational person who agrees that ends do not justify means would find abhorrent
- You do not have to be a pacifist to object to certain practices or to use our services, you may simply see a potentially harmful use for your technology and do not want it used in a context where a person could be killed (see the Stop Killer Robot’s website for an example)
- Industry and research are replete and saturated with military use and constantly: asking/pressuring/demanding/requiring people to compromise on, assist with, or ignore dual-use or military use; hardly any spaces exist that are explicitly just for peaceful technologies without fear that they will be used to harm or kill
- Our licenses will make allowances for the military to use technology for some of these “good things” or will allow conditional approval. Additionally you will always have the ability to distribute your own copyrighted works under a different license to whomever you choose.
# Do You Hate Soldiers?
No. We don’t hate anyone. In fact our licenses will not blanket prevent members of the military or military organizations from using licensed works (as stated above). We maintain the virtue of self-sacrifice for others is an undeniable good and act of love. We simply object to the means by which our country is protected or the choices our leaders make. We also think that what our laws, systems, and leaders require of our soldiers is unjust.
# Do You Think There Should Be No Standing Army/Military?
Code Bloom is not an organization that is intended to be a direct outlet for the philosophy of pacifism or the Consistent Life Ethic, nor any particular political cause (perhaps beyond not using our code/work to kill), but we will provide a brief “survey of the field”:
- Generally most academic and religious pacifists as well as many consistent-life pacifists believe in just-war-theory, and would answer “no”.
- The answer may depend on what is meant by “military”
- Some in the “ethic-of-non-killing” community(ies) envision a military that does not kill and possibly does not perpetrate any act of violence (sometimes it acts more like a humanitarian aid organization, peace corps, or government disaster relief agency).
- Yet some others might simply object to the use aggressive violence and or the use of lethal weapons and lethal strategies.
- More still believe there should be no military (at least not one that is violent). Functionally in a military context we are primarily concerned with preventing the use of lethal weapons, the use of lethal strategies, and killing
# Any Other Long-Term Plans?
- We intend to support people seeking to become employed in ethical jobs, as well as scientists, researchers & artists.
- Build a professional association for Consistent Life/Ethical upholding professionals focused on STEM fields
- We plan to extend to hardware
- Establishing similar organizations for research papers, funding other projects, creating standards, etc.
- Creating a special opt-in data set only to be used with ethical AI/archives, possibly allowing those who opt-in their data to be paid some percentage of profits and benefit freely from the technology
- Educating others about socially responsible technology
- Create featured Life Affirming Community Projects, which we will encourage members of our community to assist in developing, such as apps that help people connect with medical care. Depending on legality and availibility, we may have grants for contributors.
- We may consider adding “ethical source available” repositories in the future for software-as-a-product industries, especially ones that involve some risk, such as the game industry, to encourage auditable & modifiable community-shareable code, software longevity, and communal involvement & stewardship. While not completely inline with the FLOSS ethos, we consider this a better alternative to industries primarily dominated by proprietary software and we may be unique position to adapt Ethics Based Access Control technologies for this purpose. Friendly reminder that these are all proposed ideas at this point which will be open to community discussion when the time comes
- We may offer standards or certification of products and services to authenticate their ethical production and use
- We may offer nodes for decentralized and peer to peer services that comply with our ethical standards or interoperate with those with the same/similar standards
# Other Organizations
# Consistent Life Ethic & Non Killing
- Rehumanize International website
- Consistent Life Network website.
- The Global Center for Non-Killing website
# Pacifism & War Resistance
- War Industry Resister’s Network website
- Code Pink website
- Veterans for Peace website
- International Peace Bureau website
- World Beyond War website
- United for Peace website
- War Resistors League website/100 years
# Science, Technology, and Peace
- Union of Concerned Scientists website
- The Bulletin of the Atomic Scientists website/doomsday clock
- Peace in Space website
- Waging Peace & Nuclear Age Peace Foundation website
- Space 4 Peace website
- Stop Killer Robots website
- Future of Life website