Permalink
Browse files

Initial Commit

Signed-off-by: Mattt Thompson <m@mattt.me>
  • Loading branch information...
0 parents commit a65d01ef7a54e3694d3036f358eb84aa5339e48e @mattt mattt committed May 1, 2015
Showing with 397 additions and 0 deletions.
  1. +43 −0 CONDUCT.md
  2. +91 −0 CONTRIBUTING.md
  3. +149 −0 GOVERNANCE.md
  4. +19 −0 LICENSE.md
  5. +95 −0 README.md
@@ -0,0 +1,43 @@
+# Code of Conduct
+
+The Code of Conduct governs how we behave in public or in private
+whenever the project will be judged by our actions.
+We expect it to be honored by everyone who represents the project
+officially or informally,
+claims affiliation with the project,
+or participates directly.
+
+We strive to:
+
+* **Be open**: We invite anybody to participate in any aspect of our projects.
+ Our community is open, and any responsibility can be carried
+ by any contributor who demonstrates the required capacity and competence.
+* **Be empathetic**: We work together to resolve conflict,
+ assume good intentions,
+ and do our best to act in an empathic fashion.
+ By understanding that humanity drops a few packets in online interactions,
+ and adjusting accordingly,
+ we can create a comfortable environment for everyone to share their ideas.
+* **Be collaborative**: We prefer to work transparently
+ and to involve interested parties early on in the process.
+ Wherever possible, we work closely with others in the open source community
+ to coordinate our efforts.
+* **Be decisive**: We expect participants in the project to resolve disagreements constructively.
+ When they cannot, we escalate the matter to structures
+ with designated leaders to arbitrate and provide clarity and direction.
+* **Be responsible**: We hold ourselves accountable for our actions.
+ When we make mistakes, we take responsibility for them.
+ When we need help, we reach out to others.
+ When it comes time to move on from a project,
+ we take the proper steps to ensure that others can pick up where we left off.
+
+This code is not exhaustive or complete.
+It serves to distill our common understanding of a
+collaborative, shared environment and goals.
+We expect it to be followed in spirit as much as in the letter.
+
+---
+
+*The Alamofire Software Foundation Code of Conduct is licensed under the [Creative Commons Attribution-Share Alike 3.0 License](https://creativecommons.org/licenses/by-sa/3.0/us/).*
+
+*Some of the ideas and wording for the statements above were based on work by [Mozilla](https://wiki.mozilla.org/Code_of_Conduct/Draft), [Ubuntu](http://www.ubuntu.com/about/about-ubuntu/conduct), and [Twitter](https://github.com/twitter/code-of-conduct). We thank them for their work and contributions to the open source community.*
@@ -0,0 +1,91 @@
+# Contributing Guidelines
+
+This document contains information and guidelines about contributing to this project.
+Please read it before you start participating.
+
+**Topics**
+
+* [Asking Questions](#asking-questions)
+* [Reporting Security Issues](#reporting-security-issues)
+* [Reporting Issues](#reporting-other-issues)
+* [Developers Certificate of Origin](#developers-certificate-of-origin)
+* [Code of Conduct](#code-of-conduct)
+
+## Asking Questions
+
+We don't use GitHub as a support forum.
+For any usage questions that are not specific to the project itself,
+please ask on [Stack Overflow](https://stackoverflow.com) instead.
+By doing so, you'll be more likely to quickly solve your problem,
+and you'll allow anyone else with the same question to find the answer.
+This also allows maintainers to focus on improving the project for others.
+
+## Reporting Security Issues
+
+The Alamofire Software Foundation takes security seriously.
+If you discover a security issue, please bring it to our attention right away!
+
+Please **DO NOT** file a public issue,
+instead send your report privately to <security@alamofire.org>.
+This will help ensure that any vulnerabilities that _are_ found
+can be [disclosed responsibly](http://en.wikipedia.org/wiki/Responsible_disclosure)
+to any affected parties.
+
+## Reporting Other Issues
+
+A great way to contribute to the project
+is to send a detailed issue when you encounter an problem.
+We always appreciate a well-written, thorough bug report.
+
+Check that the project issues database
+doesn't already include that problem or suggestion before submitting an issue.
+If you find a match, add a quick "+1" or "I have this problem too."
+Doing this helps prioritize the most common problems and requests.
+
+When reporting issues, please include the following:
+
+* The version of Xcode you're using
+* The version of iOS or OS X you're targeting
+* The full output of any stack trace or compiler error
+* A code snippet that reproduces the described behavior, if applicable
+* Any other details that would be useful in understanding the problem
+
+This information will help us review and fix your issue faster.
+
+## Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+- (a) The contribution was created in whole or in part by me and I
+ have the right to submit it under the open source license
+ indicated in the file; or
+
+- (b) The contribution is based upon previous work that, to the best
+ of my knowledge, is covered under an appropriate open source
+ license and I have the right under that license to submit that
+ work with modifications, whether created in whole or in part
+ by me, under the same open source license (unless I am
+ permitted to submit under a different license), as indicated
+ in the file; or
+
+- (c) The contribution was provided directly to me by some other
+ person who certified (a), (b) or (c) and I have not modified
+ it.
+
+- (d) I understand and agree that this project and the contribution
+ are public and that a record of the contribution (including all
+ personal information I submit with it, including my sign-off) is
+ maintained indefinitely and may be redistributed consistent with
+ this project or the open source license(s) involved.
+
+## Code of Conduct
+
+The Code of Conduct governs how we behave in public or in private
+whenever the project will be judged by our actions.
+We expect it to be honored by everyone who contributes to this project.
+
+See [CONDUCT.md](./CONDUCT.md) for details.
+
+---
+
+*Some of the ideas and wording for the statements above were based on work by the [Docker](https://github.com/docker/docker/blob/master/CONTRIBUTING.md) and [Linux](http://elinux.org/Developer_Certificate_Of_Origin) communities. We commend them for their efforts to facilitate collaboration in their projects.*
@@ -0,0 +1,149 @@
+# Governance
+
+## Technical Committee
+
+Projects maintained by the Alamofire Software Foundation
+are jointly governed by a Technical Committee (TC),
+which is responsible for high-level guidance of the project.
+
+The TC has final authority over this project including:
+
+* Technical direction
+* Project governance and process (including this policy)
+* Contribution policy
+* GitHub repository hosting
+* Conduct guidelines
+* Maintaining the list of additional Collaborators
+
+Initial membership invitations to the TC were given to individuals
+who had been active contributors to Alamofire projects,
+and who have significant experience with the management of open source projects.
+Membership is expected to evolve over time according to the needs of the project.
+
+For the current list of TC members, see [README.md](./README.md#people).
+
+## Collaborators
+
+The [Alamofire/Foundation](https://github.com/Alamofire/Foundation) GitHub repository
+is maintained by the TC and additional Collaborators
+who are added by the TC on an ongoing basis.
+
+Individuals making significant and valuable contributions
+are made Collaborators and given commit-access to the project.
+These individuals are identified by the TC,
+and their addition as Collaborators
+is discussed during the regular TC meeting.
+
+> If you make a significant contribution and are not considered for commit-access,
+> log an issue or contact a TC member directly
+> and it will be brought up in the next TC meeting.
+
+Modifications to the contents of the Alamofire/Foundation repository
+are made on a collaborative basis.
+Anybody with a GitHub account may propose a modification via pull request,
+which will then be considered by the project Collaborators.
+All pull requests must be reviewed and accepted by a Collaborator
+with sufficient expertise who is able to take full responsibility for the change.
+In the case of pull requests proposed by an existing Collaborator,
+an additional Collaborator is required for sign-off.
+Consensus should be sought if additional Collaborators participate
+and there is disagreement around a particular modification.
+See _Consensus Seeking Process_ below
+for further details on the consensus model used for governance.
+
+Collaborators may opt to elevate significant or controversial modifications,
+or modifications that have not found consensus
+to the TC for discussion by
+assigning the ***tc-agenda*** tag to a pull
+request or issue.
+The TC should serve as the final arbiter where required.
+
+## TC Membership
+
+TC seats are not time-limited.
+There is no fixed size of the TC.
+However, the expected target is between 3 and 6 members
+to ensure adequate coverage of important areas of expertise,
+balanced with the ability to make decisions efficiently.
+
+There is no specific set of requirements or qualifications
+for TC membership beyond these rules.
+
+The TC may add additional members to the TC by a standard TC motion.
+
+A TC member may be removed from the TC by voluntary resignation,
+or by a standard TC motion.
+
+Changes to TC membership should be posted in the agenda,
+and may be suggested as any other agenda item (see "TC Meetings" below).
+
+No more than 1/3 of the TC members may be affiliated with the same employer.
+If removal or resignation of a TC member,
+or a change of employment by a TC member,
+creates a situation where more than 1/3 of the TC membership shares an employer,
+then the situation must be immediately remedied
+by the resignation or removal of one or more TC members
+affiliated with the over-represented employer(s).
+
+## TC Meetings
+
+The TC meets regularly on a Google Hangout On Air,
+on a schedule decided by the TC.
+The meeting is run by a designated moderator approved by the TC.
+Each meeting should be published on YouTube.
+
+Items are added to the TC agenda which are considered contentious
+or are modifications of governance,
+contribution policy,
+TC membership,
+or release process.
+
+The intention of the agenda is not to approve or review all patches—
+that should happen continuously on GitHub and be handled by the larger
+group of Collaborators.
+
+Any community member or contributor can ask that something be added
+to the next meeting's agenda by logging a GitHub Issue.
+Any Collaborator, TC member or the moderator
+can add the item to the agenda by adding
+the ***tc-agenda*** tag to the issue.
+
+Prior to each TC meeting,
+the moderator will share the Agenda with members of the TC.
+TC members can add any items they like
+to the agenda at the beginning of each meeting.
+The moderator and the TC cannot veto or remove items.
+
+The TC may invite persons or representatives from certain projects
+to participate in a non-voting capacity.
+These invitees currently are:
+
+* A representative from [CocoaPods](https://github.com/CocoaPods)
+ chosen by that project.
+* A representative from [Carthage](https://github.com/Carthage)
+ chosen by that project.
+
+The moderator is responsible for summarizing the discussion of each
+agenda item and send it as a pull request after the meeting.
+
+## Consensus Seeking Process
+
+The TC follows a
+[Consensus Seeking](http://en.wikipedia.org/wiki/Consensus-seeking_decision-making)
+decision making model.
+
+When an agenda item has appeared to reach a consensus,
+the moderator will ask "Does anyone object?"
+as a final call for dissent from the consensus.
+
+If an agenda item cannot reach a consensus,
+a TC member can call for either a closing vote
+or a vote to table the issue to the next meeting.
+The call for a vote must be seconded by a majority of the TC
+or else the discussion will continue.
+Simple majority wins.
+
+---
+
+*Many of the ideas and much of the wording for the statements above were based on
+[io.js Governance](https://github.com/iojs/io.js/blob/v1.x/GOVERNANCE.md#readme). We thank them for their strong example of open-source governance.*
@@ -0,0 +1,19 @@
+Copyright (c) 2011–2015 Alamofire Software Foundation (http://alamofire.org/)
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.
Oops, something went wrong.

0 comments on commit a65d01e

Please sign in to comment.