Start glossary of aspects around sustainability

_aspects/foundation.md

@@ -0,0 +1,11 @@
+---
+title: "Foundations"
+excerpt: "Non-profit foundations providing services to affiliated projects."
+tags:
+  - Organization
+  - Funder
+---
+
+Non-profit foundations provide services for one or more open source projects.  Many foundations directly host project communities, giving them both a legal, fiscal, organizational, and sometimes structured home separate from the individual developers.  Some foundations provide a more hands-off set of services, often involving fiscal pass-through of fundraising monies.
+
+Foundations are typically distinct from traditional software companies in terms of governance.  Foundations typically have boards and bylaws that focus on the needs of their project communities or the vendors investing in that ecosystem - not shareholders.

_aspects/government.md

@@ -0,0 +1,18 @@
+---
+title: "Governments"
+excerpt: "Governments set legislative policies, provide grants, and are often major software users."
+tags:
+  - Organization
+  - Policy
+  - Funder
+  - Grant
+---
+
+Governments may seem removed from open source communities, but impact sustainability in many ways over the long term.
+
+- **Policy setting** National and some regional governments pass legislation or set policies that affect FOSS in many indirect ways, and some direct ways like the EU's product liability legislation.
+- **Software usage** Governments are often large consumers of software, and procurement policies or actions often have broad effects when businesses in those jurisdiction default to following those procurement policies.
+- **Software contributions** Whether with direct contributions due to use in government agencies, or through consultant or third party contributions focused on providing support to agencies, governments often drive significant contributions.
+- **Grant funding** Many government agencies lead or influence funding grants for a wide variety of purposes.
+
+Governments also introduce complexity when legislation or policy differs by jurisdiction.  While open source software is just "everywhere on the internet", the communities of organizations and individuals that manage that software are constrained by their jurisdiction.

_aspects/maintainer.md

@@ -0,0 +1,21 @@
+---
+title: "Maintainers"
+excerpt: "Maintainers are individuals in charge of a software project."
+tags:
+  - Individual
+refs:
+ - https://en.wikipedia.org/wiki/Software_maintainer
+---
+
+Maintainers are individuals who are in charge of maintaining a software project.  Maintainers may own the core software repository, and have the rights to publish releases, update the website, and manage the project overall.  Projects may have a sole maintainer, or may have a team or community of maintainers.  
+
+A maintainer has a higher level of responsibility and access than other contributors or committers, because maintainers typically can change the list of who has write access to the code repository or website.
+
+The maintainer role has several aspects:
+
+- Technical: they often have responsibility for project direction, when to make official releases, security issues, and the like.
+- Branding: maintainers may be often personally associated with the project in question.  A sole maintainer would typically be seen as a trademark owner, if one exists.
+- Financial: many maintainers manage one or more projects outside of a traditional work environment, either in their spare time, or as just part of a paid position.  Hence many maintainers are not directly paid in a way that's tied directly to the project's work.
+- Social / Emotional: maintainers often identify with their projects, and sometimes write about how overwhelming it is to feel responsible in the face of bugs, complaints, and questions from large numbers of users.
+
+Many projects do not have maintainers, but rather emphasize a Project Management Committee or entire community of people who are responsible.  A key difference is if the project emphasizes the specific people who maintain a project, versus emphasizing the community as a whole (i.e. not focusing on any individuals) is responsible. 

_aspects/ngo.md

@@ -0,0 +1,14 @@
+---
+title: "NGOs"
+excerpt: "Non-governmental organizations provide technical standards and more."
+tags:
+  - Organization
+  - Policy
+  - Grant
+---
+
+A wide variety of NGOs in technical spaces set the de facto (or de jure) standards that affect software in many ways.
+
+- **Policy setting** The IEEE, W3C, ISO and many other NGOs set the policy standards that much of the world relies on for how software is built, is used, and many other aspects.  NGOs often write or influence standards set by government legislation as well.
+- **Software contributions** Many technical NGOs like the W3C directly build or contribute to important software that defines or validates operation to their standards.
+- **Grant funding** Some NGOs host events, papers, or other grant-based work that directly contributes either to their standards or even to software implementations.

_config.yml

@@ -13,4 +13,25 @@ social:
   name: Punderthings℠ LLC
   links:
     - http://punderthings.com/
-    - http://shanecurcuru.org/
+    - http://shanecurcuru.org/
+
+collections:
+  aspects:
+    output: true
+    permalink: /:collection/:path
+
+defaults:
+  - scope:
+      path: ""
+      type: "aspects"
+    values:
+      layout: "aspects"
+  - scope:
+      path: ""
+      type: "posts"
+    values:
+      layout: "post"
+  - scope:
+      path: ""
+    values:
+      layout: "default"

_layouts/aspects.html

@@ -0,0 +1,13 @@
+---
+layout: default
+---
+
+<h1>{{ page.title }}</h1>
+
+<blockquote><p>{{ page.excerpt }}</p></blockquote>
+
+{{content}}
+
+{% if page.tags %}
+  <small>Tags: <em>{{ page.tags | join: "</em> | <em>" }}</em></small>
+{% endif %}

_pages/aspects.md

@@ -0,0 +1,7 @@
+---
+title: "Aspects of Sustainability"
+excerpt: "Various groups, people, policies, tools, etc. that affect sustainability."
+permalink: /aspects/
+tags:
+  - aspects
+---