Official Policies for the Alamofire Software Foundation

README.md

Alamofire Software Foundation

The Alamofire Software Foundation is a 501(c)(3) non-profit with the purpose of promoting, supporting, and advancing its open-source software projects.

Specifically, the foundation's goals are to:

  • Support development of Alamofire by sponsoring sprints, meetups, gatherings and community events
  • Promote the use of Alamofire software among the application developer community
  • Protect the intellectual property and the framework's long-term viability
  • Advance the state of the art in application development

Projects

The Alamofire Software Foundation are the owners and maintainers of Alamofire as well as AFNetworking and its ecosystem of extensions.

All projects owned and maintained by the Alamofire Software Foundation are released under the MIT License.

See LICENSE.md for details.

Swift

Objective-C

Governance

Each project maintained by the Alamofire Software Foundation is governed by a Technical Committee (TC), which operates under a Consensus Seeking decision making model.

See GOVERNANCE.md for details.

We are actively working to transition projects into this new governance structure. As no formal processes existed previously for these projects, we anticipate a brief transitionary period before these policies are fully implemented. In the interim, the Alamofire Software Foundation members will serve as the TC for each project. The progress of each project's adoption of a formal Technical Committee will be tracked by GOVERNANCE.md.

Code of Conduct

Our 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.

See CONDUCT.md for details.

Members

The Alamofire Software Foundation is represented by a board of directors, who provide logistical and financial oversight over the organization itself.

The following individuals serve as founding members:

Kyle Fuller

Kyle Fuller started developing Swift the very day it was announced and he hasn’t looked back since. He’s an active contributor in the open-source Swift scene and the technical lead behind CocoaPods -- The Dependency manager for Cocoa. By day he focuses on API Blueprint, an API description language at Apiary.

Kevin Harwood

Kevin Harwood is a Consulting Architect at Mutual Mobile, a tech agency partnering with some of the biggest companies in the world. Kevin is a seasoned mobile developer and software engineer, having created various mobile applications that span different industries and consumer segments – from wearables, retail, health and fitness, connected home and much more. Kevin first starting contributing to AFNetworking back in July of 2012, and has also worked on many other well known, open source libraries. Kevin also currently serves on the Industry Advisory Board for Software Engineering at Auburn University.

Christian Noon

Christian Noon is a Lead iOS Engineer at Nike, focusing on creating the next generation of sport, health and fitness apps. Christian’s background began in virtual reality and computer graphics at the Iowa State Virtual Reality Applications Center (VRAC) and eventually spawned off into Mac and iOS development. He has worked at several large companies (Dreamworks Animation, Nike) building apps ranging from intricate rendering pipeline tools to mobile and wearable apps used by millions. Christian has been an active contributor to open source libraries for many years across multiple languages. He first started contributing to Alamofire shortly after its initial release, and has been actively involved ever since.

Communication

For general inquiries, feel free to get in touch with us over email, at info@alamofire.org.

For security disclosures or other related matters, please email security@alamofire.org.

For usage questions regarding any individual project, please ask a question on Stack Overflow.

To report a bug or request a feature for a particular project please open an Issue on its GitHub project page.