Google Git
Sign in
apache / cloudstack-www / 7105246919edf89bdfe90a5863c8ddf3e5fe32c0 / . / bylaws / index.html
blob: 89466a17a1c2410dca12cff40c810ba4cf8a4c96 [file] [log] [blame]
<!doctype html>
<html lang="en" dir="ltr" class="mdx-wrapper mdx-page plugin-pages plugin-id-default" data-has-hydrated="false">
<head>
<meta charset="UTF-8">
<meta name="generator" content="Docusaurus v2.4.3">
<title data-rh="true">Apache CloudStack Project Bylaws | Apache CloudStack</title><meta data-rh="true" name="viewport" content="width=device-width,initial-scale=1"><meta data-rh="true" name="twitter:card" content="summary_large_image"><meta data-rh="true" property="og:url" content="https://cloudstack.apache.org/bylaws"><meta data-rh="true" name="docusaurus_locale" content="en"><meta data-rh="true" name="docusaurus_tag" content="default"><meta data-rh="true" name="docsearch:language" content="en"><meta data-rh="true" name="docsearch:docusaurus_tag" content="default"><meta data-rh="true" property="og:title" content="Apache CloudStack Project Bylaws | Apache CloudStack"><meta data-rh="true" name="description" content="1. Introduction"><meta data-rh="true" property="og:description" content="1. Introduction"><link data-rh="true" rel="icon" href="/img/favicon.ico"><link data-rh="true" rel="canonical" href="https://cloudstack.apache.org/bylaws"><link data-rh="true" rel="alternate" href="https://cloudstack.apache.org/bylaws" hreflang="en"><link data-rh="true" rel="alternate" href="https://cloudstack.apache.org/bylaws" hreflang="x-default"><link rel="alternate" type="application/rss+xml" href="/blog/rss.xml" title="Apache CloudStack RSS Feed">
<link rel="alternate" type="application/atom+xml" href="/blog/atom.xml" title="Apache CloudStack Atom Feed">
<script src="scripts/bootstrap.bundle.min.js" async></script><link rel="stylesheet" href="/assets/css/styles.e12efb83.css">
<link rel="preload" href="/assets/js/runtime~main.60ecdf28.js" as="script">
<link rel="preload" href="/assets/js/main.2d60fa8d.js" as="script">
</head>
<body class="navigation-with-keyboard">
<script>!function(){function t(t){document.documentElement.setAttribute("data-theme",t)}var e=function(){var t=null;try{t=new URLSearchParams(window.location.search).get("docusaurus-theme")}catch(t){}return t}()||function(){var t=null;try{t=localStorage.getItem("theme")}catch(t){}return t}();t(null!==e?e:"light")}()</script><div id="__docusaurus">
<div role="region" aria-label="Skip to main content"><a class="skipToContent_fXgn" href="#__docusaurus_skipToContent_fallback">Skip to main content</a></div><nav aria-label="Main" class="navbar navbar--fixed-top"><div class="navbar__inner"><div class="navbar__items"><button aria-label="Toggle navigation bar" aria-expanded="false" class="navbar__toggle clean-btn" type="button"><svg width="30" height="30" viewBox="0 0 30 30" aria-hidden="true"><path stroke="currentColor" stroke-linecap="round" stroke-miterlimit="10" stroke-width="2" d="M4 7h22M4 15h22M4 23h22"></path></svg></button><a class="navbar__brand" href="/"><div class="navbar__logo"><img src="/img/navlogo.png" alt="apache-cloudstack" class="themedImage_ToTc themedImage--light_HNdA"><img src="/img/navlogo.png" alt="apache-cloudstack" class="themedImage_ToTc themedImage--dark_i4oU"></div><b class="navbar__title text--truncate"></b></a></div><div class="navbar__items navbar__items--right"><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">About</a><ul class="dropdown__menu"><li><a class="dropdown__link" href="/about">About</a></li><li><a class="dropdown__link" href="/history">History</a></li><li><a class="dropdown__link" href="/features">Features</a></li><li><a class="dropdown__link" href="/who">Who We Are</a></li><li><a class="dropdown__link" href="/bylaws">Community Bylaws</a></li><li><a class="dropdown__link" href="/trademark-guidelines">Trademark Guidelines</a></li><li><a class="dropdown__link" href="/security">Security</a></li></ul></div><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">Community</a><ul class="dropdown__menu"><li><a class="dropdown__link" href="/contribute">Get Involved</a></li><li><a class="dropdown__link" href="/developers">Developer Resources</a></li><li><a class="dropdown__link" href="/mailing-lists">Join Mailing Lists</a></li><li><a href="https://github.com/apache/cloudstack/issues" target="_blank" rel="noopener noreferrer" class="dropdown__link">Issues Tracker<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li><li><a href="https://join.slack.com/t/apachecloudstack/shared_invite/zt-1u8qwbivp-u16HRI~LWioLmF1G2D3Iyg" target="_blank" rel="noopener noreferrer" class="dropdown__link">Community Slack<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li><li><a class="dropdown__link" href="/events">Events and Meetups</a></li><li><a href="https://www.cloudstackcollab.org/" target="_blank" rel="noopener noreferrer" class="dropdown__link">Collab Conference<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li></ul></div><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">Use Cases</a><ul class="dropdown__menu"><li><a class="dropdown__link" href="/cloud-builders">Cloud Builders</a></li><li><a class="dropdown__link" href="/kubernetes">Kubernetes</a></li><li><a class="dropdown__link" href="/integrations">Integrations</a></li></ul></div><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">Users</a><ul class="dropdown__menu"><li><a class="dropdown__link" href="/users">Known Users</a></li><li><a class="dropdown__link" href="/blog/tags/case-studies">Case Studies</a></li><li><a href="https://docs.google.com/forms/d/e/1FAIpQLScPHIRetdt-pxPT62IesXMoQUmhQ8ATGKcYZa507mB9uwzn-Q/viewform" target="_blank" rel="noopener noreferrer" class="dropdown__link">Take Survey<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li></ul></div><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">Documentation</a><ul class="dropdown__menu"><li><a href="https://docs.cloudstack.apache.org" target="_blank" rel="noopener noreferrer" class="dropdown__link">CloudStack Documentation<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li><li><a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/Home" target="_blank" rel="noopener noreferrer" class="dropdown__link">Project Wiki<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li><li><a href="https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Books" target="_blank" rel="noopener noreferrer" class="dropdown__link">CloudStack Books<svg width="12" height="12" aria-hidden="true" viewBox="0 0 24 24" class="iconExternalLink_nPIU"><path fill="currentColor" d="M21 13v10h-21v-19h12v2h-10v15h17v-8h2zm3-12h-10.988l4.035 4-6.977 7.07 2.828 2.828 6.977-7.07 4.125 4.172v-11z"></path></svg></a></li><li><a class="dropdown__link" href="/api/">API Documentation</a></li></ul></div><a class="navbar__item navbar__link" href="/downloads">Download</a><a class="navbar__item navbar__link" href="/blog">Blog</a><a href="https://github.com/apache/cloudstack" target="_blank" rel="noopener noreferrer" class="navbar__item navbar__link header-github-link" aria-label="GitHub repository"></a><div class="searchBox_ZlJk"><div class="navbar__search searchBarContainer_NW3z"><input placeholder="Search" aria-label="Search" class="navbar__search-input"><div class="loadingRing_RJI3 searchBarLoadingRing_YnHq"><div></div><div></div><div></div><div></div></div><div class="searchHintContainer_Pkmr"><kbd class="searchHint_iIMx">ctrl</kbd><kbd class="searchHint_iIMx">K</kbd></div></div></div><div class="navbar__item dropdown dropdown--hoverable dropdown--right"><a href="#" aria-haspopup="true" aria-expanded="false" role="button" class="navbar__link">ASF</a><ul class="dropdown__menu"><li><a href="https://www.apache.org/" target="_blank" rel="noopener noreferrer" class="dropdown__link">Foundation</a></li><li><a href="https://www.apache.org/licenses/" target="_blank" rel="noopener noreferrer" class="dropdown__link">License</a></li><li><a href="https://www.apache.org/events/current-event" target="_blank" rel="noopener noreferrer" class="dropdown__link">Events</a></li><li><a href="https://www.apache.org/security/" target="_blank" rel="noopener noreferrer" class="dropdown__link">Security</a></li><li><a href="https://www.apache.org/foundation/sponsorship.html" target="_blank" rel="noopener noreferrer" class="dropdown__link">Sponsorship</a></li><li><a href="https://www.apache.org/foundation/policies/privacy.html" target="_blank" rel="noopener noreferrer" class="dropdown__link">Privacy</a></li><li><a href="https://www.apache.org/foundation/thanks.html" target="_blank" rel="noopener noreferrer" class="dropdown__link">Thanks</a></li></ul></div></div></div><div role="presentation" class="navbar-sidebar__backdrop"></div></nav><div id="__docusaurus_skipToContent_fallback" class="main-wrapper mainWrapper_z2l0"><main class="container container--fluid margin-vert--lg"><div class="row mdxPageWrapper_j9I6"><div class="col col--8"><article><h1>Apache CloudStack Project Bylaws</h1><h2>1. Introduction</h2><ul><li><p>1.1
This document defines the bylaws under which the Apache CloudStack project
operates. It defines the roles and responsibilities of the project, who may
vote, how voting works, how conflicts are resolved and specifies the rules for
specific project actions.</p></li><li><p>1.2. CloudStack is a project of the Apache Software Foundation. The foundation
holds the trademark on the name &quot;CloudStack&quot; and copyright on Apache code
including the code in the CloudStack codebase. The foundation FAQ explains the
operation and background of the foundation.</p></li><li><p>1.3. CloudStack operates under a set of principles known collectively as the
&quot;Apache Way&quot;. Those principles are: Transparency, consensus, non-affiliation,
respect for fellow developers, and meritocracy, in no specific order.</p></li></ul><h2>2. Roles and Responsibilities</h2><p> Apache projects define a set of roles with
associated rights and
responsibilities. These roles govern what tasks an individual may perform
within the project. The roles are defined in the following sections:</p><ul><li><p>2.1. Users.
The most important participants in the project are people who use our software.
Users can contribute to the Apache projects by providing feedback to developers
in the form of bug reports and feature suggestions. As well, users can
participate in the Apache community by helping other users on mailing lists and
user support forums. Users who participate in the project through any mechanism
are considered to be Contributors.</p></li><li><p>2.2. Contributors
Contributors are all of the volunteers who are contributing time, code,
documentation, or resources to the CloudStack Project. Contributions are not
just code, but can be any combination of documentation, testing, user support,
code, code reviews, bug reporting, community organizing, project marketing, or
numerous other activities that help promote and improve the Apache CloudStack
project and community.</p><p> A Contributor that makes sustained, welcome contributions to the project may be
invited to become a Committer by the PMC. The invitation will be at the
discretion of a supporting PMC member.</p></li><li><p>2.3. Committers
The project&#x27;s Committers are responsible for the project&#x27;s technical
management. Committers have access to all project source control repositories.
Committers may cast binding votes on any technical discussion regarding the
project (or any sub-project).</p><ul><li><p>2.3.1. Committer access is by invitation only and must be approved by a lazy
consensus of the active PMC members.</p></li><li><p>2.3.2. All Apache Committers are required to have a signed Individual
Contributor License Agreement (ICLA) on file with the Apache Software
Foundation. There is a Committer FAQ which provides more details on the
requirements for Committers at Apache.</p></li><li><p>2.3.3. A Committer who makes a sustained contribution to the project may be
invited by the PMC to become a member of the PMC, after approval of the PMC.</p></li></ul></li><li><p>2.4. Project Management Committee</p><p> The Project Management Committee (PMC) for Apache CloudStack is responsible to
the board and the ASF for the management and oversight of the Apache CloudStack
codebase.</p><ul><li><p>2.4.1. The responsibilities of the PMC include:</p><ul><li><p>2.4.1.1. Fostering, supporting and growing the project&#x27;s community.</p></li><li><p>2.4.1.2. Deciding what is distributed as products of the Apache CloudStack project. In particular all releases must be approved by the PMC.</p></li><li><p>2.4.1.3. Maintaining the project&#x27;s shared resources, including the codebase repository, mailing lists, websites.</p></li><li><p>2.4.1.4. Speaking on behalf of the project.</p></li><li><p>2.4.1.5. Resolving license disputes regarding products of the project.</p></li><li><p>2.4.1.6. Nominating new PMC members and committers.</p></li><li><p>2.4.1.7. Maintaining these bylaws and other guidelines of the project.</p></li><li><p>2.4.1.8. Managing and protecting the project&#x27;s trademarks and brand.</p></li></ul></li><li><p>2.4.2. Membership of the PMC is by invitation only and must be approved by a
lazy consensus of active PMC members.</p></li><li><p>2.4.3. A PMC member is considered &quot;emeritus&quot; by their own declaration. An
emeritus member may request reinstatement to the PMC. Such reinstatement is
subject to lazy consensus of the active PMC members.</p></li><li><p>2.4.4. &quot;Active PMC members&quot; are all non-emeritus PMC members.</p></li><li><p>2.4.4. The chair of the PMC is appointed by the ASF board. The chair is an
office holder of the Apache Software Foundation (Vice President, Apache
CloudStack) and has primary responsibility to the board for the management of
the projects within the scope of the CloudStack PMC. The chair reports to the
board quarterly on developments within the CloudStack project. The chair must
be an active PMC member.</p></li><li><p>2.4.5. If the current chair of the PMC resigns, or the term of the current
chair expires, the PMC will attempt to reach consensus on a new chair through
discussion, confirming that consensus via a vote to recommend a new chair using
a lazy 2/3 majority voting method. In the case that consensus is not achieved,
the PMC will vote for a chair using Single Transferable Vote (STV) voting. Due
to the fact that the discussions are about specific individuals, this vote
would be held on the cloudstack-private mailing list. The decision must be
ratified by the Apache board.</p></li><li><p>2.4.6. The role of PMC chair will have a one year term. The intention of this
term is to allow for a rotation of the role amongst the PMC members. This
intention does not prohibit the PMC from selecting the same chair to serve
consecutive terms.</p></li></ul></li></ul><h2>3. Decision Making</h2><p>This section defines how voting is performed, the types of approvals, and which
types of decision require which type of approval.</p><ul><li><p>3.1. Voting</p><ul><li><p>3.1.1. Decisions regarding the project are made by votes on the primary project
development mailing list (<a href="mailto:dev@cloudstack.apache.org" target="_blank" rel="noopener noreferrer">dev@cloudstack.apache.org</a>). Where necessary, PMC
voting may take place on the private CloudStack PMC mailing list. Votes are
clearly indicated by subject line starting with <!-- -->[<!-- -->VOTE<!-- -->]<!-- -->. Votes may contain
multiple items for approval and these should be clearly separated. Voting is
carried out by replying to the vote mail.</p></li><li><p>3.1.2. Voting may take four flavors:</p><ul><li><p>3.1.2.1. <!-- -->+<!-- -->1 &quot;Yes,&quot; &quot;Agree,&quot; or &quot;the action should be performed.&quot; In general, this vote also indicates a willingness on the behalf of the voter in &quot;making it happen&quot;</p></li><li><p>3.1.2.2. <!-- -->+<!-- -->0 This vote indicates a willingness for the action under consideration to go ahead. The voter, however will not be able to help.</p></li><li><p>3.1.2.3. <!-- -->-<!-- -->0 This vote indicates that the voter does not, in general, agree with the proposed action but is not concerned enough to prevent the action going ahead.</p></li><li><p>3.1.2.4. <!-- -->-<!-- -->1 This is a negative vote. On issues where consensus is required, this vote counts as a veto if binding. All vetoes must contain an explanation of why the veto is appropriate. Vetoes with no explanation are void. It may also be appropriate for a <!-- -->-<!-- -->1 vote to include an alternative course of action.</p></li></ul></li><li><p>3.1.3. All participants in the CloudStack project are encouraged to show their
agreement with or against a particular action by voting. For technical
decisions, only the votes of active committers are binding. Non-binding votes
are still useful for those with binding votes to understand the perception of
an action in the wider CloudStack community. For PMC decisions, only the votes
of PMC members are binding.</p></li><li><p>3.1.4. Voting can also be applied to changes made to the CloudStack codebase.
These typically take the form of a veto (-1) in reply to the commit message
sent when the commit is made.</p></li><li><p>3.1.5. Non-binding <!-- -->-<!-- -->1 votes are not considered to be vetos for any decision.</p></li></ul></li><li><p>3.2. Approvals</p><p> There are three types of approvals that can be sought. Section 3.4 describes
actions and types of approvals needed for each action.</p><ul><li><p>3.2.1. Lazy Consensus - Lazy consensus requires 3 binding <!-- -->+<!-- -->1 votes and no
binding <!-- -->-<!-- -->1 votes.</p></li><li><p>3.2.2. Lazy Majority - A lazy majority vote requires 3 binding <!-- -->+<!-- -->1 votes and
more binding <!-- -->+<!-- -->1 votes than binding <!-- -->-<!-- -->1 votes.</p></li><li><p>3.2.3. Lazy 2/3 Majority - Lazy 2/3 majority votes requires at least 3 binding
votes and twice as many binding <!-- -->+<!-- -->1 votes as binding <!-- -->-<!-- -->1 votes.</p></li></ul></li><li><p>3.3. Vetoes</p><ul><li><p>3.3.1. Vetoes are only possible in a lazy consensus vote.</p></li><li><p>3.3.2. A valid, binding veto cannot be overruled. If a veto is cast, it must be
accompanied by a valid reason explaining the reasons for the veto. The validity
of a veto, if challenged, can be confirmed by anyone who has a binding vote.
This does not necessarily signify agreement with the veto - merely that the
veto is valid.</p></li><li><p>3.3.3. If you disagree with a valid veto, you must lobby the person casting the
veto to withdraw their veto. If a veto is not withdrawn, any action that has
been vetoed must be reversed in a timely manner.</p></li></ul></li><li><p>3.4. Actions</p><p> This section describes the various actions which are undertaken within the
project, the roles that have the right to start a vote on the action, the
corresponding approval required for that action and those who have binding
votes over the action.</p><ul><li><p>3.4.1. Technical Decisions</p><ul><li><p>A technical decision is any decision that involves changes to the source code that we distribute in our official releases.</p></li><li><p>Technical decisions should normally be made by the entire community using discussion-lead consensus gathering, and not through formal voting.</p></li><li><p>Technical decisions must be made on the project development mailing list.</p></li><li><p>During the consensus gathering process, technical decisions may be vetoed by any Committer with a valid reason.</p></li><li><p>If a formal vote is started for a technical decision, the vote will be held as a lazy consensus of active committers.</p></li><li><p>Any user, contributor, committer, or PMC member can initiate a technical decision making process.</p></li></ul></li><li><p>3.4.2. Non-Technical Decisions</p><ul><li><p>A non-technical decisions is any decision that does not involve changes to the source code that we distribute in our official releases (excluding questions of trademark usage).</p></li><li><p>Non-technical decisions should normally be made by the entire community using discussion-lead consensus-building, and not through formal voting.</p></li><li><p>Non-technical decisions can be made on whichever project mailing list is most appropriate.</p></li><li><p>Non-technical decisions cannot be vetoed, but if there is strong opposition a formal vote can be used to resolve the dispute.</p></li><li><p>If a formal vote is started for a non-technical decision, the vote will be held as a lazy 2/3 majority of active committers.</p></li><li><p>Any user, contributor, committer, or PMC member can initiate a non-technical decision making process.</p></li></ul></li><li><p>3.4.3. Release Plan</p><ul><li><p>Defines the timetable and work items for a release. The plan also nominates a Release Manager.</p></li><li><p>A lazy majority of active committers is required for approval.</p></li><li><p>Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.</p></li></ul></li><li><p>3.4.4. Product Release</p><ul><li><p>When a release of one of the project&#x27;s products is ready, a vote is required to accept the release as an official release of the project.</p></li><li><p>Lazy Majority of active PMC members is required for approval.</p></li><li><p>Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.</p></li></ul></li><li><p>3.4.5. Adoption of New Codebase</p><ul><li><p>When the codebase for an existing, released product is to be replaced with an alternative codebase. If such a vote fails to gain approval, the existing code base will continue.</p></li><li><p>This also covers the creation of new sub-projects within the project.</p></li><li><p>Lazy 2/3 majority of active PMC members.</p></li><li><p>Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.</p></li></ul></li><li><p>3.4.6. New Committer</p><ul><li><p>When a new committer is proposed for the project.</p></li><li><p>Lazy consensus of active PMC members.</p></li><li><p>Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.</p></li></ul></li><li><p>3.4.7. New PMC Member</p><ul><li><p>When a committer is proposed for the PMC.</p></li><li><p>Lazy consensus of active PMC members.</p></li><li><p>Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.</p></li></ul></li><li><p>3.4.8. Committer Removal</p><ul><li><p>When removal of commit privileges is sought. Note: Such actions will also be referred to the ASF board by the PMC chair</p></li><li><p>Lazy 2/3 majority of active PMC members (excluding the committer in question if a member of the PMC).</p></li><li><p>Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.</p></li></ul></li><li><p>3.4.9. PMC Member Removal</p><ul><li><p>When removal of a PMC member is sought. Note: Such actions will also be referred to the ASF board by the PMC chair.</p></li><li><p>Lazy 2/3 majority of active PMC members (excluding the member in question)</p></li><li><p>Any active PMC member may call a vote. The vote must occur on the PMC private mailing list.</p></li></ul></li><li><p>3.4.10. Modifying Bylaws</p><ul><li><p>Modifying this document.</p></li><li><p>Lazy majority of active PMC members</p></li><li><p>Any active committer or PMC member may call a vote. The vote must occur on the project development mailing list.</p></li></ul></li><li><p>3.4.11. Trademark Usage Approvals</p><p>Our project maintains a formal Trademark Usage Guidelines document, which
serves as a additive reference to the Apache Software Foundation&#x27;s trademark
policies. The Apache CloudStack PMC has had approval authority delegated to it
for requests from third parties to use our trademarks. It is the PMC&#x27;s
responsibility to provide these approvals, and to ensure that any requests
are in compliance with both the project and the foundation&#x27;s trademark
usage policies.</p><p>The CloudStack Trademark Guidelines specify how a requester is expected to
request permission for usage of the trademarks.</p><p>The process of approval will typically be as follows:</p><ul><li><p>A request is made that includes the required information for the PMC to make a decision.</p></li><li><p>A PMC member reviews the request and provides an initial acknowledgement response to the requester.</p></li><li><p>If no PMC member raises a concern after 72 hours, the requester can assume approval.</p></li></ul></li><li><p>In situations where a concern is raised, the PMC member is expected inform the
requster that there is some discussion that needs to be had prior to approval
from the PMC. This notice serves to end the assumed approval after 72 hours.</p><div class="codeBlockContainer_Ckt0 theme-code-block" style="--prism-color:#393A34;--prism-background-color:#f6f8fa"><div class="codeBlockContent_biex"><pre tabindex="0" class="prism-code language-text codeBlock_bY9V thin-scrollbar"><code class="codeBlockLines_e6Vv"><span class="token-line" style="color:#393A34"><span class="token plain"> After raising a concern, the PMC member in question is required to forward the</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> concern to private@cloudstack.apache.org, explaining the issue that they have</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> with the request. The use of private@cloudstack.apache.org for discussing the</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> request is to allow the PMC to deliberate without confusing the requester, and</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> to ensure that a formal approval or denial is clear at the end of the</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> discussion.</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> The PMC will then attempt to achieve consensus on how the request for approval</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> will be answered. The requester may be asked for more information to help the</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> PMC make a decision, may be asked to make a change to the proposal in order to</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> gain approval, or may have their request be denied.</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> If consensus is not achieved within the PMC by discussion, then a formal VOTE</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> can be called as a Lazy 2/3 majority of voting PMC members.</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> Votes related to trademark usage approvals may be performed on the</span><br></span><span class="token-line" style="color:#393A34"><span class="token plain"> private@cloudstack.apache.org mailing list.</span><br></span></code></pre><div class="buttonGroup__atx"><button type="button" aria-label="Copy code to clipboard" title="Copy" class="clean-btn"><span class="copyButtonIcons_eSgA" aria-hidden="true"><svg viewBox="0 0 24 24" class="copyButtonIcon_y97N"><path fill="currentColor" d="M19,21H8V7H19M19,5H8A2,2 0 0,0 6,7V21A2,2 0 0,0 8,23H19A2,2 0 0,0 21,21V7A2,2 0 0,0 19,5M16,1H4A2,2 0 0,0 2,3V17H4V3H16V1Z"></path></svg><svg viewBox="0 0 24 24" class="copyButtonSuccessIcon_LjdS"><path fill="currentColor" d="M21,7L9,19L3.5,13.5L4.91,12.09L9,16.17L19.59,5.59L21,7Z"></path></svg></span></button></div></div></div></li></ul></li><li><p>3.5. Voting Timeframes</p><p> Formal votes are open for a period of at least 72 hours to allow all active
voters time to consider the vote.</p></li></ul></article></div></div></main></div><footer class="footer footer--dark"><div class="container container-fluid"><div class="footer__bottom text--center"><div class="margin-bottom--sm"><a href="https://cloudstack.apache.org/" rel="noopener noreferrer" class="footerLogoLink_BH7S"><img src="/img/ACS_logo_slogan.svg" alt="Apache CloudStack logo" class="themedImage_ToTc themedImage--light_HNdA footer__logo"><img src="/img/ACS_logo_slogan.svg" alt="Apache CloudStack logo" class="themedImage_ToTc themedImage--dark_i4oU footer__logo"></a></div><div class="footer__copyright">
<div class="social">
<a href="mailto:dev-subscribe@cloudstack.apache.org">
<img src="/img/mail_mini_icon.svg" alt="">
</a>
<a href="https://join.slack.com/t/apachecloudstack/shared_invite/zt-2aegc22z7-tPCxpptfcebTBtd59qcZSQ">
<img src="/img/slack_mini_icon.svg" alt="">
</a>
<a href="https://github.com/apache/cloudstack">
<img src="/img/git_mini_icon.svg" alt="">
</a>
<a href="https://twitter.com/CloudStack">
<img src="/img/twitter_X_mini_icon.svg" alt="">
</a>
<a href="https://www.youtube.com/@ApacheCloudStack">
<img src="/img/youtube_mini_icon.svg" alt="">
</a>
<a href="https://www.linkedin.com/company/apachecloudstack/posts/">
<img src="/img/linkedin_icon.svg" alt="">
</a>
</div>
<div class="footer-bottom">Copyright © 2023 The Apache
Software Foundation, Licensed under the Apache License, Version 2.0.
“Apache”, “CloudStack”, “Apache CloudStack”, the Apache CloudStack logo,
the Apache CloudStack Cloud Monkey logo and the Apache feather logos
are registered trademarks or trademarks of The Apache Software
Foundation.
<p class="footer-blue"><a href="/trademark-guidelines">Apache CloudStack Trademark Usage</a> - <a href="/bylaws">Apache CloudStack Community ByLaws</a> - <a href="https://github.com/apache/cloudstack-www">Website Source Code</a></p></div>
</div>
<br>
</div></div></footer></div>
<script src="/assets/js/runtime~main.60ecdf28.js"></script>
<script src="/assets/js/main.2d60fa8d.js"></script>
</body>
</html>