changeset 286:a5375989d0bc

Merge GitHub work.
author Kai T. Ohlhus <>
date Sat, 28 May 2022 15:49:55 +0900
parents d0b1f463f80d (current diff) fbe0260e079a (diff)
children 7b528322279e
diffstat 2 files changed, 207 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/	Sat May 28 15:49:55 2022 +0900
@@ -0,0 +1,122 @@
+# Contributor Covenant Code of Conduct
+## Our Pledge
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+## Our Standards
+Examples of behavior that contributes to a positive environment for our
+community include:
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+Examples of unacceptable behavior include:
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+## Enforcement Responsibilities
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+## Scope
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+## Enforcement
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+All complaints will be reviewed and investigated promptly and fairly.
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+## Enforcement Guidelines
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+### 1. Correction
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+### 2. Warning
+**Community Impact**: A violation through a single incident or series
+of actions.
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+### 3. Temporary Ban
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+### 4. Permanent Ban
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+## Attribution
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/pages/	Sat May 28 15:49:55 2022 +0900
@@ -0,0 +1,85 @@
+# Octave Governance
+This page should clarify about the various entities and actors around the GNU Octave programming language.
+## GNU Octave
+The GNU Octave project was initialized 1992 by **John W. Eaton** <>.
+It consists of [some code](
+and a community of people who work on that code.
+The most clear cut line that can be drawn is that there is a
+[set of people](
+who have commit access to the GNU Octave Savannah project:
+there are currently 24 committers (10 active and 14 dormant).
+This set of people doesn’t really define the project, however,
+since there are many people who are prolific contributors to the GNU Octave
+ecosystem but who do not have
+“[commit bit](”
+The communal nature of open-source makes it difficult to precisely define
+where the GNU Octave project ends and the greater community begins,
+which is exactly how we like it.
+Until the present day,
+most final development decisions are made or agreed with by John W. Eaton.
+## Free Software Foundation (FSF)
+The FSF <> is a US 501(c)(3) nonprofit organization
+promoting computer user freedom.
+With the help of the FSF, both indivials and corporations have the opportunity to
+[donate to the GNU Octave project](
+Despite the free usage of the FSF infrastructure for distributing
+the GNU Octave source code.
+The GNU Octave project does not receive any direct or indirect
+monetary fundings by the FSF.
+## Related Organizations With No Governance Role
+There are organizations that people sometimes mistakenly believe
+have some kind of official control over the GNU Octave project.
+This section details three of them,
+but please note that neither has any official relationship
+to the GNU Octave project,
+nor any governance capacity with respect to the project.
+Individuals who have some control over the project
+and happen to belong to these organizations,
+have that control as individuals and not as members of those organizations
+and takes the separation of those roles quite seriously.
+### Octave Forge and Octave Packages
+**Octave Forge** <> is the former collection
+of software packages, that can be easily installed and used in GNU Octave.
+The Octave Sourceforge project was initiated in 2000
+and active development stopped in 2018.
+New packages are not accepted, but existing packages are still maintained.
+The project lists [56 members](
+(10 active and 46 dormant) maintaining existing Octave packages,
+but not the source code of GNU Octave itself.
+**Octave Packages** <> is another
+collection of Octave packages and intended as the successor of **Octave Forge**.
+New packages are accepted here and the development is independent of GNU Octave itself.
+Until today full support by Octave's package manager is not given, however,
+it is a fully functional index for Octave packages.
+### GitHub Organization
+The GitHub Organization <>
+was established around 2020.
+It is a loose connection of currently
+[27 members](
+(10 active and 14 dormant)
+developing software intended to be used with GNU Octave,
+but not the source code of GNU Octave itself.
+## Questions
+If you have questions about GNU Octave's governance structure,
+please reach out via email to <>.
+This page is inspired by the [JuliaLang project](