1. Summary
  2. Files
  3. Support
  4. Report Spam
  5. Create account
  6. Log in

About The Community

From tianocore

Jump to: navigation, search

There is a lot to learn about the the EFI and Framework open source community. Without actually joining the community, you still have access to the documentation, source and binaries available on the EFI and Framework Open Source Community Website. However, your involvement will be limited to read-only access to the tools provided by the community. The real magic of any community is when you join and have full access to the tools that the community drivers use to evolve and make their application and its accompanying documentation and tooling. As a community member, you will have access to the following:

  • Forums - Used for a traceable dialog between community members.
  • Issue Tracking - This helps keep track of feature requests, tasks and issues with the respective project.
  • Mailing Lists - Like forums but handled via email instead of web forms.
  • RSS Feeds - You can subscribe to RSS feeds for news, forums and mailing lists.
  • Source Control - All Projects use Subversion to keep track of different versions of software source code.

As you can see, there is a lot at your disposal as a community member. Excited yet? If so, learn how to get involved here.

Background

In June of 2004 Intel announced that it would release the "Foundation Code" of its next generation firmware technology - a successor to the PC BIOS - under an open source license later in the year. The Foundation Code, developed by Intel as part of a project code named Tiano, is Intel's "preferred implementation" of the Extensible Firmware Interface (EFI) Specification. The code to be released includes the core of the Foundation Code as well as a driver development kit. To follow through with its intentions to release the code as open source, Intel partnered with Collabnet, an industry leader in providing tools and services to support an open source initiative, to create a community for this effort. The result of this partnership is this Open Source Website.

Since there are more projects that are EFI-based working in parallel with the Foundation Code, it was decided to release the EFI Shell Application and the EFI Self Certification Test (SCT) project to the open source community.

Philosophy and Vision

It is Intel's hope that the EFI and Framework Open Source Community website will promote collaboration and innovation around the open source code contained with it, as well as the EFI Specification in general. Intel is dedicated to fostering the growth of this community through shared governance with key individuals and companies involved in evolution of pre-boot firmware, with a goal to support the investment in innovation of all modern platform, silicon and systems vendors worldwide. As such the primary focus of the EFI community is to:

  • Foster collaboration around the projects on this website, which at present include:
    • EFI Developer Kit (EDK project) which includes the Foundation code
    • EFI Developer Kit II (EDK II project) which includes a new implementation of the Foundation code focusing on new build tools and responding to past feedback from the EFI community
    • EFI Shell Application (EFI-SHELL project)
    • EFI Self-certification Test (EFI-SCT project)
    • EFI Toolkit for application development (EFI-TOOLKIT project)
  • Provide an environment to stimulate innovation and evolution of the EDK and the other EFI-based projects contained on the site.
  • Provide a mechanism for the free exchange of thoughts, ideas, concerns etc surrounding this effort, EFI and the concept of next-generation firmware in general.
  • Encourage collaboration within the community on creation of other open-source firmware projects.

As the EDK and other EFI-based projects constitute the primary focus of the EFI and Framework Open Source Community, the key objectives for these projects are:

  • Strong emphasis on portability
  • Strong emphasis on stability
  • Strong emphasis on firmware security
  • Adherence to the EFI Specification
  • Adherence to quality C coding standards
Personal tools