|     IEEE Xplore Digital Library     |     IEEE Standards     |     IEEE Spectrum     |     More Sites

Commit 90f98893 authored by Joshua Gay's avatar Joshua Gay 🙀
Browse files


parent c651e350
## Thanks go to:
##### EMACS, VIM, editors
# -*- mode: gitignore; -*-
##### Linux and MacOS (general)
##### Git GUIs
##### jekyl, and site generators
## Policy, Ethics, and Code of Conduct
IEEE supports open source as one method for consensus development
within its portfolio of collaborative activities. Your participation
as a Leader, Maintainer, or Contributor of any IEEE Open Source
Project and/or your use of the IEEE Open Source Platform is contingent
upon, although not limited to, your agreement to comply with this
manual, the IEEE SA OPen Source Committee Operations Manual, and the
<summary>All applicable IEEE policies and procedures, including but not limited to:</summary>
* [IEEE Code of Conduct](
* [IEEE Code of Ethics](
* [IEEE Terms and Conditions](
* [IEEE Nondiscrimination Policy](](
* [IEEE Principles of Business Conduct and Conflict of Interest](
* [Compliance Related IEEE Policies](, including:
* Anti-Boycott Policy (§12.12)
* Anti-Bribery and Corruption Policy (§12.13)
* Antitrust and Fair Competition Policy (§12.10)
* Civility Policy (§9.25)
* Computer Policy (§9.28)
* Economic Sanctions and Embargoes Policy (§12.11)
* IEEE Records Management Policy Statement (§12.8)
* IEEE Social Media Policy (§9.27)
* Whistleblower and Non-Retaliation Policy (§9.9)
* Remain consistent with definitions of Bullying, Discrimination, Harassment, Retaliation (unumbered front matter text)
<summary>CLAs and Preserve Appropriate Legal Notices </summary>
* Submit any applicable
[IEEE Contributor License Agreement](]( (CLA) where required by specific IEEE Open Source Projects.
* Post and preserve any and all appropriate legal notices (e.g.,
copyright and license file headers) where the license or relevant
IEEE policy requires.
<summary>CLAs and Preserve Appropriate Legal Notices </summary>
* Submit any applicable
[IEEE Contributor License Agreement](]( (CLA) where required by specific IEEE Open Source Projects.
* Post and preserve any and all appropriate legal notices (e.g.,
copyright and license file headers) where the license or relevant
IEEE policy requires.
<summary>In addition we recommend that you adhere to the following terms: </summary>
We recommend that all individuals involved in the design and
development of autonomous and intelligent systems as part of their
participation in an IEEE Open Source Project to strive to be educated,
trained, and empowered to prioritize ethical considerations in the
design and development of autonomous and intelligent systems. The
[IEEE Global Initiative for Ethical Considerations in Artificial
Intelligence and Autonomous
supports those seeking ot satisfy this recommendation; the
Initiative's mission statement is as follows:
> To ensure every stakeholder involved in the design and development of
> autonomous and intelligent systems is educated, trained, and empowered
> to prioritize ethical considerations so that these technologies are
> advanced for the benefit of humanity.
<summary>Ethics and Compliance Helpline</summary>
Reports of violations, or concerns regarding potential violations, of
IEEE Policies or the IEEE Code of Conduct can be filed anonymously
through EthicsPoint:
* :telephone_receiver: Call the 24-hour phone number: +1(888)359-6323
* :computer: [Submit an online report](
\ No newline at end of file
## Quick Start
### Who is needs to read the Maintainers Manual?
:pushpin: Maintainers and Leads of an IEEE Open Source Projects shall (**must**) follow all requirements contained in this manual.
All other users of the IEEE Open Source Platform should follow recommendations and the recommended templates and may benefit from the examples and suggestions throughout.
### What are the requirements?
:bulb: Click on the "▸" and expand the section. Click again to collapse. :bulb:
<summary>Click to expand!</summary>
## Heading
1. A numbered
2. list
* With some
* Sub bullets
### About IEEE
* IEEE is the world’s largest technical professional organization dedicated to advancing technology for the benefit of humanity.
* Mission: IEEE's core purpose is to foster technological innovation and excellence for the benefit of humanity.
* Vision: IEEE will be essential to the global technical community and to technical professionals everywhere, and be universally recognized for the contributions of technology and of technical professionals in improving global conditions.
* This Maintainers Manual is approved by the Open Source Committee of the IEEE SA Board of Governors.
as well as recommendations, and guides fo
* The *Maintainers Manual* contains requirements ("shalls"/"musts"), recommendations ("shoulds"), and , and suggestionsguidelines and advice for someone who is the maintainer This is the the *Maintainers Manual* for IEEE Standards Association Open Source
* policy requirements for leads and maintainers
## Introduction
Whether you are a person downloading a socail app to your phone, a
developer building on top of the next great aschynchronous runtime
library, or a maker bringing a design document to fabrication of your
new IoT gizmo, in each situation, you will almost always be able to
determine quickly and unambiguously whether or not a self-contained
(single-sourced) app, library, or design document you have downloaded
is an open source work. In practice, you can tell if something is an
open source work by simply checking to see if the source code and/or
design documents are made available to you under the terms of an open
source license.
However, the matter can quickly get complex
However, when you are helping to create open source software and
hardware, or you are seeking ot provide support and guidance for the
growth of many new open source communities, a more general definition
to go alongside the licensing terms is essential. The IEEE Standards
Association Open Source Committee Operations Manual provides the
following definition of open source for use by our communities:
> **Open Source** is a digital work for which the human-readable
> source code is available—in the preferred form for making
> modifications—for use, study, re-use, modification, enhancement, and
> re-distribution by the users. Open Source applies to software and
> hardware, which may include computer code, hardware designs, data,
> documentation, documents, and other digital objects.
However, when it comes to nurturing, growing, and sustaining open
source projects, communities, and ecosystems, then open source
software & hardware is more than just licensed source code files, it
is also: open source is also project planning and management; is also
project management, and governance; it is massively distributed,
collaborative development; it is shipping a product to users or
adopters of your work and developing a trusted relationship with them.
The IEEE SA provides a platform of
As a user of, we have granted to you the ability to be If you are a Lead or Maintainer of a project hosted on [](,
Similarly, the IEEE SA offers a platform for users, contributors, support for communities to come and collaborate open source, and so we too are seeking to
As a Lead or Maintainer of a project hosted on the <>, it is essential that you follow
For Leads and Maintainers of open source projects, eaders and maintainers of open source projects, it is often about
fostering a community of users and contributors.
The purpose of this manual is to:
If you are (or are thinking of becoming) a Lead or a Maintainer of an
open source project hosted on <>, then this
manual is required reading. Wherever possible we will do our best to
indicate clearly any requirements we ask you to follow (we will use
terms such as "shall" and "must").
### Contents
This is copy of our internal open source documentation, with a few
exceptions. For a number of reasons, we can't share everything, so you
might find places where a link is missing or some content had to be
Aside from those few cases, this is the same documentation seen by
Google employees. As a result, there is some Google lingo throughout,
as well as references to internal tools and systems. See the glossary
for definitions of some of the most common ones.
There are three primary sections of the docs:
Creating covers how Googlers release code that they've written, either
in the form of a new standalone project or as a patch to an external
project. The same process is used for small 20% projects and full
blown Google projects.
Using explains how we bring open source code into the company and use
it to help build great products. We carefully catalog thousands of
packages to help us maintain license compliance.
Growing describes some of the programs we run inside and outside the
company to support open source communities.
Who this is for
### About IEEE SA Open Source
## Contributors (“engineers”)
IEEE Public (e.g. companies wanting to know how the platform is governed and works …)
### Front Matter and intro
### Scope and Purpose of the Manual
Executive summary .5 page.
* The role and responsibility of the maintainer in the IEEE Open Source environment
* Who needs this (maintainers of group and individual projects)
* Scope & Purpose statement - to document roles and responsibilities and applicable policies.
### Scope and Purpose of the Platform
* Positioning: IEEE Open as a philosophy [Link to Marketing Materials when available, not a blocker] [
* Types of IEEE Open Source Projects [Include and explain]
* Supporting the wider open source community [ included in marketing, not a blocker]
* Access to technical expertise
* Open Source planning, dev, testing, communication tools
* Supporting open consensus standards that incorporate open source [Merge with descriptions of types of projects above]
* Software
* Hardware
* Entire standard as open source
Resources for Maintainers
* Community / IP manager
* Platform resources
* Issue reporting
* (Continuous integration)
* (Peer Review mention)
#### IEEE Open Source Governance
[Roles and responsibilities are in previous section]
[Details are in following sections]
[Governance documents have already been agreed]
Summary of how IEEE governs Open Source
Creating a governance document (see Ops Man 5.1.2 for what needs to be covered)
Samples / Templates… TBD (Group / Official / Standards)
### Account and Group Management
(May separate out things only applicable to group namespaces)
Cross-reference table (individual / group / official / standards)
* Adding users to a project
* Assigning project roles to users
* Granting access
* Creating a project- approvals (if needed)
* Name, description, README file
* LICENSE (choose Apache 2.0 or BSD 3-clause)
* Collaboration responsibilities
* Have fun! glhf
* Responsibilities when you fork a project
* Mattermost / Slack
* List of governance documents
Publicizing your project [ Not clear where this goes but we want to tell maintainers how to access resources for publicizing projects]
### Running a project
* What Leaders and Committers do [links to appropriate policy documents]
* Responsibilities of Maintainers
* Following policies and procedures
* Following additional IEEE agreements (standards, fiscal sponsorship, etc)
* Representing your project and the IEEE outside of the Platform
* Delegating responsibility and access control
* Communicating with OSCM, OSCom, IPR Manager
* Community governance
* Leadership changes
* Configuration Management
* Version control, version (semantic) numbering *within your own project* [once forked, new maintainer - could by you], submodules
* Validation, scanning, and enforcement of CLAs (e.g. responding to alerts) [understanding what they must do to maintain legal notices etc.]
* (later) Peer review and testing -- notice that it is planned, link to OSCom OpsMan
* Aim of peer review
* under development (SIG needed)
[Maybe under release management]
* Release Management
* Mandatory coordination with OSCM
* Official vs unofficial releases [official projects shall designate which releases are official] [blocking issue]
* Signed releases (PGP signing) [should not block MVM]
* Backport (and security) patching [should not block MVM]
* Mirroring and archiving releases [should not block MVM]
* Documentation requirements for open source that is incorporated into standards (including short description of what the software does, how to install it, plus stuff Josh said.)
* Issue problem management
* Creating, assigning, tagging, and managing issues [IT IS REQUIRED THAT MAINTAINERS RESPOND TO SOME TYPES OF ISSUES]
* Email/helpdesk use of issues [should not block MVM]
* Standards considerations
* Roles and responsibility of Standards Committee and WG with OS project - [covered in SASB Ops Man so summarize and link]
* Balloting (see process points document) [covered in SASB Ops Man so summarize and link, need to explain the workflow and how it works]
* Comment resolution group
* Comments made as issues versus ballot comments
* Ballot comments that address open source artifacts (e.g. code) - c.f. The need for a CLA
* Notices [Required notice that it is not an approved standard in the file]
* Interactions with WG (copy/paste other WG guidance?)
### Retiring a group or project [put in, but not a blocker]
* Archive project (or request that OSCM archives project)
* Retiring a group requires agreement among all leadership and approval by IEEE Staff
* Email OSCM
* Special considerations for standards projects
### Licensing policies [blocker]
* CLAs and choice of license
* Use of third-party material and dependency management
* Naming, Branding, Trademark, and Tradename
### Security policies [next]
* Minimum requirements:
* Official IEEE Open Source Projects (including standards that incorporate Official IEEE Open Source Projects) _may_ be required to follow our Security policy?
* IEEE Open Source Projects are able to opt-in
* Responsibilities under policies
* Release and CVE
* Notice that the IEEE may scan all repositories on the IEEE Open Source Platform?
Shall have SVE process for official releases of official / standards projects
Should have SVE process for group projects
May have for individual
\ No newline at end of file
This open source repository contains material that may be included-in
or referenced by an unapproved draft of a proposed IEEE Standard. All
material in this repository is subject to change. The material in this
repository is presented "as is" and with all faults. Use of the
material is at the sole risk of the user. IEEE specifically disclaims
all warranties and representations with respect to all material
contained in this repository and shall not be liable, under any
theory, for any use of the material. Unapproved drafts of proposed
IEEE standards must not be utilized for any conformance/compliance
Place this file in the top level of your project's git repo and rename it ""
# Project Title
One paragraph short description
The following repo contains open source materials intended for
reference by the IEEE 1076 standard when approved and published.
## License
All source code files in this repository are subject to the
following copyright and licensing terms.
Copyright 2020 NAME or GROUP-NAME
See the LICENSE file distributed with this work for copyright and
licensing information, the AUTHORS file for a list of copyright
holders, and the CONTRIBUTORS file for the list of contributors.
## Getting Started
These instructions will get you a copy of the project up and running
on your local machine for development and testing purposes. See
deployment for notes on how to deploy the project on a live system.
* git clone
> *Alternatively, if your repository uses submodule then provide*
> *instructions along these lines*
> For a repo with submodules, we can pull all submodules using
> git submodule update --init --recursive
> for the first time. All submodules will be pulled down locally.
> To update submodules, we can use
> git submodule update --recursive --remote
> or simply
> git pull --recurse-submodules
### Prerequisites
What things you need to install the software and how to install them
Give examples
### Installing
A step by step series of examples that tell you how to get a
development env running
Step through
1. Step one
2. Step two
3. Step three, etc
until finished
## Built With
* [Dropwizard]( - The web framework used
* [Maven]( - Dependency Management
* [ROME]( - Used to generate RSS Feeds
## Contributing
Please read []( for details on our code of conduct, and the process for submitting pull requests to us.
## Versioning
We use [SemVer]( for versioning. For the versions available, see the [tags on this repository](
## Requesting an Official IEEE Open Source Project
An IEEE Open Source Project seeks authorization to become an Official
IEEE Open Source Project by posting a request on the IEEE Open Source
Platform. The request shall include:
* A title and description of the Project;
* The name and contact information of the IEEE Open Source Project Lead;
* Selection of a single Open Source license and associated CLAs;
* An indication of how the Project will be governed
* A description of the relationship of the Project to known Open Source;
* Agreement to adhere to the Terms of Use for the IEEE Open Source Platform
* An indicator of whether the IEEE Open Source Project is intended to
be incorporated into an IEEE standard associated with an IEEE SA
Project Authorization Request (PAR) submitted to the New Standards
Committee of the IEEE SASB (NesCom) or an existing IEEE standards
Project previously approved for Open Source development.
* IEEE Open Source Projects incorporated into IEEE standards shall
agree to an applicable set of Terms and Conditions (T&Cs).
* Authorization of an IEEE Open Source Project incorporated into
IEEE standards shall require that any associated PARs have been
assigned a standards designation
\ No newline at end of file
[NOTE: Users of the platform must first have an IEEE Account to sign in, so the Privacy Policy should be checked at login and redirected if not accepted.]
Welcome to the IEEE Open Source Platform.
Final link: [](
Current link: [](
PDF of current version: <PDF file>
**The following IEEE Abbreviated Individual Contributor License Agreement (ACLA) applies to any Contributions by You for which an IEEE CLA is not required.**
This Abbreviated Individual Contributor License Agreement may only be used in instances where
a) You (the copyright owner of the material being submitted) are submitting an original work of authorship to IEEE Open Source software or documentation, including any modifications or additions to an existing work (“Contribution”);
b) You are making this Agreement with IEEE as an individual, and no other entity has any rights to the material you submit to the development of work on an IEEE Open Source repository;
c) You are not a government/federal/crown employee where your work is not subject to copyright;
d) The work is not being developed in conjunction with an IEEE standards development activity as a normative or informative reference within an IEEE standard.
If Your Contribution does not meet the above requirements for a specific IEEE Open Source Project, You are required to submit the appropriate IEEE CLA(s).
**IEEE Abbreviated Individual Contributor License Agreement**
**1. Grant of Copyright and Patent License.** You hereby grant to IEEE and to recipients of software and documentation distributed by IEEE a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright and patent license (for patent claims licensable by You that are necessarily infringed by the work at the time of Your Contributions) to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works. Except for the license granted in this Agreement, You reserve all right, title, and interest in and to Your Contributions, including the right to terminate this license to a third party in the event of patent litigation by that third party against You alleging
that Your Contributions constitute patent infringement.
**2. Representation.** You are legally entitled to grant the above license and that the Contributions are Your original creations. You also represent that You are not aware of any third-party license or other restrictions associated with any part of Your Contributions.
**3. Application of Grant.** You accept and agree to these terms and conditions for all Your Contributions to any IEEE Open Source Projects in which You participate.
By agreeing to the Terms of Use, users also agree to obey applicable laws. IEEE reserves the right to remove content or take any action it deems appropriate if it determines that a user has not complied with the Terms of Use.
<Accept and Submit>
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment