Sustainable Free and Open Source Communities – About SFOSC

Docs: Code of Conduct

Thu, 06 Dec 2018 12:27:40 -0800

This page details guidelines for interaction and behavior in the SFOSC community.

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

Using welcoming and inclusive language
Being respectful of differing viewpoints and experiences
Gracefully accepting constructive criticism
Focusing on what is best for the community
Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

The use of sexualized language or imagery and unwelcome sexual attention or advances
Trolling, insulting/derogatory comments, and personal or political attacks
Public or private harassment
Publishing others’ private information, such as a physical or electronic address, without explicit permission
Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers 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, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at adam@stalecoffee.org. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq

Docs: Contributing

Thu, 06 Dec 2018 12:27:40 -0800

This page includes information about contributing to SFOSC

Request for Contributions

We would love to have you help us evolve the principles, write new social contracts, and further explore what it means to create sustainable free and open source communities.

In particular, we seek the following types of contributions:

ideas: participate in an issues thread or start your own to voice your idea
copy editing: contribute your expertise by helping us expand, clarify and proofing our content
code: improve the design, usability and functionality of the sfosc page
artwork: contribute graphics or any other artwork improving the presentation of sfosc

Read this guide on how to do that.

How to Contribute Ideas

Prerequisites: familiarity with GitHub Issues.

Our community mainly communicates over github issues threads. Please voice any idea, criticism or feedback in them so we can have an open discussion. Of course you can also feel free to contact any of our members privately if you think this is necessary.

How to Contribute Code

Prerequisites: familiarity with GitHub Pull Requests

If you want to contribute code, fork the repository and make a pull-request with your changes.

If you want to view/test your changes locally before, you can build this static web page with hugo, please check their extensive documentation on how to install and use this site generator.

A sfosc member will review your pull-request. And if the pull request gets a positive review the reviewer will merge it.

However, please bear in mind the following things:

Discuss Large Changes in Advance

If you see a glaring flaw within the SFOSC, resist the urge to jump into the code and make sweeping changes right away. We know it can be tempting, but especially for large, structural changes it’s a wiser choice to first discuss them in the issue list. It may turn out that someone is already working on this or that someone already has tried to solve this and hit a roadblock, maybe there even is a good reason why that flaw exists. If nothing else, a discussion of the change will usually familiarize the reviewer with your proposed changes and streamline the review process when you finally create a pull request.

A good rule of thumb for when you should discuss on the issue list is to estimate how much time would be wasted if the pull request was rejected. If it’s a couple of minutes then you can probably dive head first and eat the loss in the worst case. Otherwise, making a quick check with the other developers could save you lots of time down the line.

Small Commits & Pull Request Scope

A commit should contain a single logical change, the scope should be as small as possible. And a pull request should only consist of the commits that you need for your change. If it’s possible for you to split larger changes into smaller blocks please do so.

Limiting the scope of commits/pull requests makes reviewing much easier. Because it will usually mean each commit can be evaluated independently and a smaller amount of commits per pull request usually also means a smaller amount of code to be reviewed.

Proper Commit Messages

We are keen on proper commit messages because they will help us to maintain this in the future.

The title of your commit should summarizes what has been done
- If the title is to small to explain what you have done then elaborate on it in the body
Explain why you have changed this instead of the how. This is the most important content of the message.
Explain potential side-effects of this change, if there are any

Please also:

Leave a blank line between the commit subject and body

Tools like rebase could not work properly otherwise.

Mention related issues

If this commit fixes an issue you need to mention it like Fixes #1234

Give kudos to Co-authors

If the commit has more than one author tag them with Co-authored-by: name <name@example.com>.

Try that the commit subject is not longer than 50 characters
Try that each line of the commit body is not longer than 72 characters

How to Conduct Yourself

Please make sure that while contributing you follow our Contributor Covenant Code of Conduct!

Happy Hacking! - :heart: Your SFOSC Team

Docs: Membership

Thu, 06 Dec 2018 12:27:40 -0800

This page includes information about membership in SFOSC

Membership in the SFOSC

Welcome! Anyone who is interested in contributing to the SFOSC in any way is welcome to become a member.

Membership is not a requirement for participating in the community. Members may be consulted about governance of the community. For example through votes. The CONTRIBUTING GUIDELINES explain several ways you can contribute regardless of membership.

Membership in the community is broad based, available to anyone who is participating in any fashion. Requirements for membership involve a minimal amount of verification of identity, and proof of engagement with the community. Membership consists solely of individuals - there are no corporate community members.

At the moment, the only privilege membership brings is being able to vote for the project leader. And, of course, the glory of having your name appended to this file.

Applying

To apply for membership, send a pull request to this file, adding your name and GitHub username.

Please mention why you became interested in SFOSC and share some related work. This is optional though, please share only as much as you would like to.

Existing members will review your application. The aspects we look for currently are: - Full name and GitHub username, to serve as minimal verification of identity. - You have either engaged with SFOSC directly, or have related experience we can verify. If this experience is not easily found from your GitHub profile, please mention it as part of the pull request.

Interested, but not sure if you meet the requirements? Go ahead and submit your pull request! We’re glad you’re interested and there to help.

Members

Adam Jacob (adamhjk)
Karl Amrhein (karlamrhein)
Elias Secchi (eliassecchi)
Camille Moulin (camillem)
Daniel Thompson-Yvetot (nothingismagick)
Vanessa Sochat (vsoch)
Chris Alfano (themightychris)
Nick Kellett (nickkellett)
Marc Laporte (marclaporte)
Robin van Boven (beanow)

Docs: Social Contract

Thu, 06 Dec 2018 12:27:40 -0800

This page includes information about SFOSC social contracts.

Introduction

This document describe the social contract for the community around a piece of open source software (“the software”). It lays out the moral and ethical rules the community agrees to in order to ensure a long, healthy, sustainable life for the software.

It is not a legal agreement, although sections of it reference legal agreements. It is a moral and ethical one - it is the foundation upon which the community is built.

By joining the community, you agree to the rules and beliefs outlined in this social contract.

Principles

We follow the principles of sustainable free and open source communities.

We are a unified body of individuals, scattered throughout the larger society, who work in support of the creation, evolution, use, and extension of the software; while ensuring its longevity through meeting the needs of the present without compromising the ability of the community of the future to meet its own needs.

We want the software to exist, to solve our problems, to continue to improve, and to be available for our use. Therefore, we commit that we will uphold these four freedoms for all, under all circumstances:

The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1).
The freedom to redistribute copies so you can help others (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3).

We do this because:

We believe that software is better when it is produced in the commons.
We believe that sustainable communities are based on just and fair institutions.
We value the ability of every person to use the software to better their own lives.

Governance

Code of Conduct

To ensure that all people are welcome, treated fairly and safely, this community has a code of conduct, published at CODE OF CONDUCT. It applies equally to all members of the community, both on-line and in person. Membership and participation in the community requires following the Code of Conduct.

Membership

Guidelines for membership can be found at MEMBERSHIP GUIDELINES.

Voting

Periodically, the membership may be requested to vote in elections, or on a referendum on an important issue. Each member is entitled to a single vote, and all votes count equally.

Guidelines for voting can be found in VOTING GUIDELINES.

Leadership

Leadership in the community is based on a strong executive model. The Project Leader will be elected by a simple majority vote according to the voting guidelines. The Project Leader will serve for 1 year, at the end of which a new election for Project Leader will be held.

The Project Leader has broad authority to manage the project as they see fit, to delegate positions of authority, and to enact new governance rules. The exception is amending this social contract. This can only be done with a ³⁄₄ vote of the membership.

A new election can be held for the Project Leader at any time, regardless of term, based on a simple majority vote of the membership.

The full set of guidelines for the Project can be found at PROJECT RULES.

Licensing, Copyrights, Patents, and Trademarks

Software License

All software produced by the community will be published under the SOFTWARE LICENSE. All contributors to the software agree to publish their work under this license, and to have it included in any distributions or derivatives allowed under the same terms.

Copyrights

All copyrights remain the property of the original copyright holder, under the terms of the SOFTWARE LICENSE.

Patents

Any patents included in the software must be made available under the same terms as the SOFTWARE LICENSE.

Trademarks

Any trademarks that may exist, relating to the software directly, are the ethical property of the community itself. Their use in the software is made available under the same terms as the SOFTWARE LICENSE.

Further details can be found in the TRADEMARK POLICY.

Economic Sustainability

Community Intent

Any commercial activity around the software should, in part, further the sustainability of the community. The potential for economic benefit is available to all members of the community equally.

Donations

This project will be sustained through a donation model. Currently the project has no expenses, so no system of donations is yet available.

Docs: Trademark

Thu, 06 Dec 2018 12:27:40 -0800

This page includes information about SFOSC trademarks.

Trademark Policy

The Sustainable Free and Open Source Community, and the SFOSC, are not currently trademarked. We do ask that, if you want to republish this content, you do so in line with the terms of our license.

Docs: Voting

Thu, 06 Dec 2018 12:27:40 -0800

This page details guidelines for voting in SFOSC.

Voting Guidelines

Every member in the MEMBERSHIP file is allowed one vote. We will use Helios to organize the actual vote, and certify the results.