budget template

_journals/2024-06-14_1200.md

@@ -0,0 +1,7 @@
+---
+title: June 14th, 2024
+date: 2024-06-14, 12:00:53 -07:00
+section: journal
+link: https://bmannconsulting.com/notes/tech-event-budget-template/
+---
+I've published my [[Tech Event Budget Template]]. This is a very basic starting point for scoping the costs and ticket + sponsor revenue of an event that is mainly talks and networking.

_notes/Big Time License.md

@@ -0,0 +1,112 @@
+---
+link: https://bigtimelicense.com/
+aliases:
+  - Big Time Public License
+tags:
+  - licensing
+  - noncommercial
+github: https://github.com/berneout/big-time-license
+---
+A public license that makes software free for noncommercial and small-business use, with a guarantee that fair, reasonable, and nondiscriminatory paid-license terms will be available for everyone else.
+
+Created by [[Kyle Mitchell]]
+
+---
+
+Version 2.0.2
+
+<https://bigtimelicense.com/versions/2.0.2>
+
+## Purpose
+
+These terms let you use and share this software for noncommercial purposes and in small business for free, while also guaranteeing that paid licenses for big businesses will be available on fair, reasonable, and nondiscriminatory terms.
+
+## Acceptance
+
+In order to get any license under these terms, you must agree to them as both strict obligations and conditions to all your licenses.
+
+## Noncommercial Purposes
+
+You may use the software for any noncommercial purpose.
+
+## Personal Uses
+
+Personal use for research, experiment, and testing for the benefit of public knowledge, personal study, private entertainment, hobby projects, amateur pursuits, or religious observance, without any anticipated commercial application, count as use for noncommercial purposes.
+
+## Noncommercial Organizations
+
+Use by any charitable organization, educational institution, public research organization, public safety or health organization, environmental protection organization, or government institution counts as use for noncommercial purposes, regardless of the source of funding or obligations resulting from the funding.
+
+## Small Business
+
+You may use the software for the benefit of your company if it meets all these criteria:
+
+1.  had fewer than 20 total individuals working as employees and independent contractors at all times during the last tax year
+
+2.  earned less than $1,000,000 total revenue in the last tax year
+
+3.  received less than $1,000,000 total debt, equity, and other investment in the last five tax years, counting investment in predecessor companies that reorganized into, merged with, or spun out your company
+
+All dollar figures are United States dollars as of 2019.  Adjust for them inflation according to the United States Bureau of Labor Statistics' consumer price index for all urban consumers, United States city average, for all items, not seasonally adjusted, with 1982–1984=100 reference base.
+
+## Big Business
+
+You may use the software for the benefit of your company:
+
+1.  for 128 days after your company stops qualifying under [Small Business](#small-business)
+
+2.  indefinitely, if the licensor or their legal successor does not offer fair, reasonable, and nondiscriminatory terms for a commercial license for the software within 32 days of [written request](#how-to-request) and negotiate in good faith to conclude a deal
+
+## How to Request
+
+If this software includes an address for the licensor or an agent of the licensor in a standard place, such as in documentation, software package metadata, or an "about" page or screen, try to request a fair commercial license at that address.  If this package includes both online and offline addresses, try online before offline.  If you can't deliver a request that way, or this software doesn't include any addressees, spend one hour online researching an address, recording all your searches and inquiries as you go, and try any addresses that you find.  If you can't find any addresses, or if those addresses also fail, that counts as failure to offer a fair commercial license by the licensor under [Big Business](#big-business).
+
+## Fair, Reasonable, and Nondiscriminatory Terms
+
+Fair, reasonable, and nondiscriminatory terms may license the software perpetually or for a term, and may or may not cover new versions of the software.  If the licensor advertises license terms and a pricing structure for generally available commercial licenses, the licensor proposes license terms and a price as advertised, and a customer not affiliated with the licensor has bought a commercial license for the software on substantially equivalent terms in the past year, the proposal is fair, reasonable, and nondiscriminatory.
+
+## Copyright License
+
+The licensor grants you a copyright license to do everything with the software that would otherwise infringe the licensor's copyright in it for any purpose allowed by these terms.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms or the URL for them above, as well as copies of any plain-text lines beginning with `Required Notice:` that the licensor provided with the software.  For example:
+
+> Required Notice: Copyright Yoyodyne, Inc. (http://example.com)
+
+## Patent License
+
+The licensor grants you a patent license for the software that covers patent claims the licensor can license, or becomes able to license, that you would infringe by using the software.
+
+## Fair Use
+
+You may have "fair use" rights for the software under the law. These terms do not limit them.
+
+## No Other Rights
+
+These terms do not allow you to sublicense or transfer any of your licenses to anyone else, or prevent the licensor from granting licenses to anyone else.  These terms do not imply any other licenses.
+
+## Patent Defense
+
+If you make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+## Violations
+
+The first time you are notified in writing that you have violated any of these terms, or done anything with the software not covered by your licenses, your licenses can nonetheless continue if you come into full compliance with these terms, and take practical steps to correct past violations, within 32 days of receiving notice.  Otherwise, all your licenses end immediately.
+
+## No Liability
+
+***As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.***
+
+## Definitions
+
+The **licensor** is the individual or entity offering these terms, and the **software** is the software the licensor makes available under these terms.
+
+**You** refers to the individual or entity agreeing to these terms.
+
+**Your company** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization.  **Control** means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise.  Control can be direct or indirect.
+
+**Your licenses** are all the licenses granted to you for the software under these terms.
+
+**Use** means anything you do with the software requiring one of your licenses.

_notes/Blue Oak Council.md

@@ -0,0 +1,55 @@
+---
+link: https://blueoakcouncil.org/
+tags:
+  - licensing
+---
+Blue Oak Council opens the software commons up to those who can’t find or afford specialized legal help by bringing experienced lawyer-technologists together to publish free, practical materials about software licenses.
+
+## Permissive License List
+
+Blue Oak maintains a [rated list of permissive software licenses](https://blueoakcouncil.org/list)
+
+> Permissive licenses are the bread and butter of software development: simple, effective, and on just about everyone’s “go” list. But most information about free and open source software focuses on other, more complex licenses. The Council publishes this list to identify permissive licenses, so that everyone can recognize, rely on, and use them without expensive legal help.
+
+I've copied the Gold and Silver sections below.
+
+### Gold
+
+These licenses address patents explicitly, use robust language, and require only simple notice of license terms and copyright notices.
+
+- [BSD-2-Clause Plus Patent License](https://spdx.org/licenses/BSD-2-Clause-Patent.html) (`BSD-2-Clause-Patent`)
+
+### Silver
+
+These licenses use robust language but either fail to address patents explicitly or require more than simple notice of license terms and copyright notices.
+
+- [Amazon Digital Services License](https://spdx.org/licenses/ADSL.html) (`ADSL`)
+- [Apache License 2.0](https://spdx.org/licenses/Apache-2.0.html) (`Apache-2.0`)
+- [Adobe Postscript AFM License](https://spdx.org/licenses/APAFML.html) (`APAFML`)
+- [BSD 1-Clause License](https://spdx.org/licenses/BSD-1-Clause.html) (`BSD-1-Clause`)
+- [BSD 2-Clause "Simplified" License](https://spdx.org/licenses/BSD-2-Clause.html) (`BSD-2-Clause`)
+- [BSD 2-Clause FreeBSD License](https://spdx.org/licenses/BSD-2-Clause-FreeBSD.html) (`BSD-2-Clause-FreeBSD`)
+- [BSD 2-Clause NetBSD License](https://spdx.org/licenses/BSD-2-Clause-NetBSD.html) (`BSD-2-Clause-NetBSD`)
+- [BSD 2-Clause with Views Sentence](https://spdx.org/licenses/BSD-2-Clause-Views.html) (`BSD-2-Clause-Views`)
+- [Boost Software License 1.0](https://spdx.org/licenses/BSL-1.0.html) (`BSL-1.0`)
+- [DSDP License](https://spdx.org/licenses/DSDP.html) (`DSDP`)
+- [Educational Community License v1.0](https://spdx.org/licenses/ECL-1.0.html) (`ECL-1.0`)
+- [Educational Community License v2.0](https://spdx.org/licenses/ECL-2.0.html) (`ECL-2.0`)
+- [hdparm License](https://spdx.org/licenses/hdparm) (`hdparm`)
+- [ImageMagick License](https://spdx.org/licenses/ImageMagick.html) (`ImageMagick`)
+- [Intel ACPI Software License Agreement](https://spdx.org/licenses/Intel-ACPI) (`Intel-ACPI`)
+- [ISC License](https://spdx.org/licenses/ISC.html) (`ISC`)
+- [Linux Kernel Variant of OpenIB.org license](https://spdx.org/licenses/Linux-OpenIB.html) (`Linux-OpenIB`)
+- [MIT License](https://spdx.org/licenses/MIT.html) (`MIT`)
+- [MIT License Modern Variant](https://spdx.org/licenses/MIT-Modern-Variant.html) (`MIT-Modern-Variant`)
+- [MIT testregex Variant](https://spdx.org/licenses/MIT-testregex) (`MIT-testregex`)
+- [MIT Tom Wu Variant](https://spdx.org/licenses/MIT-Wu) (`MIT-Wu`)
+- [Microsoft Public License](https://spdx.org/licenses/MS-PL.html) (`MS-PL`)
+- [Mulan Permissive Software License, Version 1](https://spdx.org/licenses/MulanPSL-1.0.html) (`MulanPSL-1.0`)
+- [Mup License](https://spdx.org/licenses/Mup.html) (`Mup`)
+- [PostgreSQL License](https://spdx.org/licenses/PostgreSQL.html) (`PostgreSQL`)
+- [Solderpad Hardware License v0.5](https://spdx.org/licenses/SHL-0.5) (`SHL-0.5`)
+- [Spencer License 99](https://spdx.org/licenses/Spencer-99.html) (`Spencer-99`)
+- [Universal Permissive License v1.0](https://spdx.org/licenses/UPL-1.0.html) (`UPL-1.0`)
+- [Xerox License](https://spdx.org/licenses/Xerox.html) (`Xerox`)
+- [Xfig License](https://spdx.org/licenses/Xfig) (`Xfig`)

_notes/Kyle Mitchell.md

@@ -0,0 +1,15 @@
+---
+github: https://github.com/kemitchell
+link: https://kemitchell.com/
+tags:
+  - person
+  - lawyer
+  - licensing
+  - california
+  - Oakland
+---
+Kyle Mitchell is a prolific writer and creator of software licenses.
+
+Read [his blog](https://writing.kemitchell.com/)
+
+Member of [[Blue Oak Council]]

_notes/Open Source Beyond Licensing - The Evolution Ahead.md

@@ -0,0 +1,6 @@
+---
+tags:
+  - presentation
+  - opensource
+---
+Open source is no longer a radical act. From legal innovation to ways of working remotely and collaboratively, the past 20 years have integrated it as a common baseline. Can we get maintainers paid, make open source a job, and work alongside new tools like AI? What new licenses, ways of working, and principles power the next 20 years?

_notes/Open Source Licensing.md

@@ -36,9 +36,9 @@ Open, share-alike (or rather, "parity") license aka copyleft, where software may
 
 Non-commercial license, where the software may be used for any purpose except for-profit. For profit companies need to buy a license.
 
-### Big Time License
+### [[Big Time License]]
 
-<https://bigtimelicense.com> [[Big Time]]
+<https://bigtimelicense.com> 
 
 > A public license that makes software free for noncommercial and small-business use, with a guarantee that fair, reasonable, and nondiscriminatory paid-license terms will be available for everyone else
 
@@ -93,22 +93,16 @@ There is also an [XLC introduction with some illustrations](https://xlcollaborat
 
 What is not specified in this license is quite how to recognize new contributors, how to share value. aka all the hard stuff. But I _love_ this conceptually. It's "co-op like" without the overhead of creating a formal co-op organization rooted in some particular jurisdiction. "An open source peer co-op" might be a good short form, where "collaborative" is probably the right word so it doesn't trick people into thinking it is a co-op.
 
-## Permissive License, Fenced Community
+## Conclusions
 
-What if you permissively license software, but restrict access to scarce community resources around an open source project?
-
-**Public Goods** are those that can't be depleted. The lines of code and even the compiled binary that make up open source software can be infinitely copied at zero marginal cost. No one loses anything if one more or 1,000 more people download the bits representing code.
-
-**Common Goods** are those that can be depleted, that are finite. For open source software, this is people time. Time spent reading and responding to an issue, whether it's a bug report, a feature request, or even a contribution of new code. Updating dependencies and making a new release. Writing documentation. Chatting in a community chat space. All of this takes people time, and there are only so many maintainers on a project spending time doing these talks.
-
-What if it was required to contribute: either by helping with these tasks -- from code maintenance to community tasks, or by paying to support the project, so contributors could have their hours compensated. And more paid contributors could be brought on, with more external contributions.
-
-Especially with modern open source software and the open nature of Github's public social spaces, we've completely normalized using up the scarce resource of maintainer time.
+Ideologically, I prefer permissive licenses. But, seemingly, we need to go to non-commercial licenses like [[Big Time License]] in order to preserve the ability to charge licenses to large corporations.
 
+I have some other thoughts about [[Permissive Licenses and Fenced Community]].
 ## Blog Posts & Presentations
 
 A variety of blog posts & presentations on the concepts around open source and evolving licenses:
 
+* June 2024, Presentation: [[Open Source Beyond Licensing - The Evolution Ahead]]
 * August 2020, Blog [Public vs Common Goods in Open Source](https://blog.bmannconsulting.com/2020/08/11/public-vs-common.html)
 * July 2020, Presentation: [Open Source: Licensing, Business Models, Community](https://talk.fission.codes/t/open-source-licensing-community-and-business-models-outlier-ventures-basecamp/786)
 * October 2019, Presentation: [Open Source Licensing Evolution](https://noti.st/bmann/aOkl8w/open-source-licensing-evolution)

_notes/Permissive Licenses and Fenced Community.md

@@ -0,0 +1,13 @@
+---
+tags:
+  - licensing
+---
+What if you permissively license software, but restrict access to scarce community resources around an open source project?
+
+**Public Goods** are those that can't be depleted. The lines of code and even the compiled binary that make up open source software can be infinitely copied at zero marginal cost. No one loses anything if one more or 1,000 more people download the bits representing code.
+
+**Common Goods** are those that can be depleted, that are finite. For open source software, this is people time. Time spent reading and responding to an issue, whether it's a bug report, a feature request, or even a contribution of new code. Updating dependencies and making a new release. Writing documentation. Chatting in a community chat space. All of this takes people time, and there are only so many maintainers on a project spending time doing these talks.
+
+What if it was required to contribute: either by helping with these tasks -- from code maintenance to community tasks, or by paying to support the project, so contributors could have their hours compensated. And more paid contributors could be brought on, with more external contributions.
+
+Especially with modern open source software and the open nature of Github's public social spaces, we've completely normalized using up the scarce resource of maintainer time.

_notes/Presentations.md

@@ -0,0 +1,6 @@
+A list of presentations.
+
+## 2024
+
+[[Open Source Beyond Licensing - The Evolution Ahead]]
+

_notes/Tech Event Budget Template.md

@@ -14,7 +14,7 @@ This is a base model for a 100 person conference that assumes:
 There are many other items that are necessary for running larger events. It should also be easily editable for smaller and simpler meetups.
 
 I've plugged in a line item for A/V that is relatively high. Getting high quality recordings of talks are a great resource, something that sponsors can sponsor / have their logos and materials embedded in, and is valuable for speakers and future versions of the event.
-## GSheet Template
+## Google Sheet
 
 Here is the [Google Sheet](https://docs.google.com/spreadsheets/d/1nJAKidA_L7-55BELdEFktoKjpUNu8j3wMCeGCHg-rgo/edit) version. Use the _File » Make a copy_ command to make your own version to work with.