Skip to content

Commit

Permalink
update changes
Browse files Browse the repository at this point in the history
Signed-off-by: Laurie0131 <[email protected]>
  • Loading branch information
Laurie0131 committed May 21, 2020
1 parent 3b136bd commit f5e3195
Show file tree
Hide file tree
Showing 29 changed files with 838 additions and 23 deletions.
7 changes: 2 additions & 5 deletions _includes/site-vars.liquid
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
{% capture prevent_newlines %}
{% if site.github.url %}
{% assign baseurl = site.github.url %}
{% endif %}
{% assign wiki = "https://github.com/Laurie0131/tianocore/wiki" %}
{% assign gitbook = "https://www.gitbook.com/@edk2-docs" %}
{% assign wiki = "https://github.com/tianocore/tianocore.github.io/wiki" %}
{% assign gitbook = "https://legacy.gitbook.com/@edk2-docs" %}
{% assign edk2files = "http://sourceforge.net/projects/edk2/files" %}
{% assign edk2github = "https://github.com/tianocore/edk2" %}
{% comment %}{% assign laurieadminemail = "[email protected]" %}{% endcomment %}
Expand Down
6 changes: 6 additions & 0 deletions bug-triage/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Refresh" content="0;url=https://github.com/tianocore/tianocore.github.io/wiki/Bug-Triage" />
</head>
</html>
6 changes: 6 additions & 0 deletions community-meeting/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Refresh" content="0; url=https://github.com/tianocore/tianocore.github.io/wiki/Community-Virtual-Meetings" />
</head>
</html>
6 changes: 6 additions & 0 deletions community-meetings/index.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Refresh" content="0; url=https://github.com/tianocore/tianocore.github.io/wiki/Community-Virtual-Meetings" />
</head>
</html>
10 changes: 4 additions & 6 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,7 @@ id: documentation
{% include site-links.md %}

The [TianoCore wiki on github]({{wiki}}){:target="_blank"} is the central repository for project information. Some project information is available as specifications or whitepapers (PDF & GitBook format).
* [EDK II Specifications]({{wiki}}/EDK-II-Specifications){:target="_blank"}
* [EDK II User Documentation]({{wiki}}/EDK-II-User-Documentation){:target="_blank"}
* [EDK II Libraries and Helper files]({{wiki}}/EDK-II-Libraries-and-Helper-files){:target="_blank"}
* [EDK II White papers]({{wiki}}/EDK-II-white-papers){:target="_blank"}
* [EDK II Driver Developer Page]({{wiki}}/Driver-Developer){:target="_blank"}
* [EDK II Documents on GitBook]({{gitbook}}){:target="_blank"}

Please see the wiki page for a complete list of EDK II related documents

* [EDK II Documents wiki page]({{wiki}}/EDK-II-Documents){:target="_blank"}
3 changes: 1 addition & 2 deletions edk2/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,7 @@ EDK II is a modern, feature-rich, cross-platform firmware development
environment for the UEFI and PI specifications.

#### License information:
[BSD](http://www.opensource.org/licenses/bsd-license.php)

[BSD+Patent]((https://opensource.org/licenses/BSDplusPatent)

#### Source repositories:
* edk2 main repository - [https://github.com/tianocore/edk2](https://github.com/tianocore/edk2)
Expand Down
2 changes: 1 addition & 1 deletion faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,6 @@ redirect_from:

TianoCore has accumulated a lot of information over the years. We keep several FAQs on the wiki, organized by topic. The [Member FAQ]({{wiki}}/Member-FAQ){:target="_blank"} is a good starting point. You may also want to review the [EDK II FAQ]({{wiki}}/EDK-II-FAQ){:target="_blank"}, and the [Acronyms and Glossary]({{wiki}}/Acronyms-and-Glossary){:target="_blank"} page.

If you have a question and cannot find the answer, please try the [EDK II developer email list]({{wiki}}/edk2-devel){:target="_blank"}. You can also search the [e-mail list archive](https://lists.01.org/pipermail/edk2-devel/){:target="_blank"} for questions already asked in email. You can also search the developer [tianocore wiki]({{wiki}}/How-to-Search){:target="_blank"} pages using the github search.
If you have a question and cannot find the answer, please try the [EDK II developer email list]({{wiki}}/edk2-devel){:target="_blank"}. You can also search the [e-mail list archive](https://lists.01.org/pipermail/edk2-devel/){:target="_blank"} for questions already asked in email. You can also search the developer [TianoCore wiki]({{wiki}}/How-to-Search){:target="_blank"} pages using the github search.

In June 2017, TianoCore added a [Code of Conduct]({{baseurl}}/coc.html) to guide project participation. The code of conduct describes how participants behave in public or in private, whenever the project will be judged by their actions. We expect it to be honored by everyone who represents the project officially or informally, claims affiliation with the project, or participates directly.
Binary file added files/TianoCoreHackathonRegistrationOSFC.pdf
Binary file not shown.
Binary file added images/GDB_QEMU.JPG
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added images/UEFI-Payload.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
2 changes: 1 addition & 1 deletion index.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ redirect_from:
Welcome to TianoCore, the community supporting an open source implementation of the Unified Extensible Firmware Interface ([UEFI]({{wiki}}/UEFI){:target="_blank"}). [EDK II]({{wiki}}/EDK-II){:target="_blank"} is a modern, feature-rich, cross-platform firmware development environment for the UEFI and UEFI Platform Initialization ([PI]({{wiki}}/PI){:target="_blank"}) specifications. We hope that you’ll review our [wiki]({{wiki}}){:target="_blank"} documentation, use TianoCore for platform firmware, [report any issues]({{wiki}}/Reporting-Issues){:target="_blank"} you find, and contribute to the community.

## Projects and Downloads
If you want to compile firmware or utilities, we recommend the [Getting Started]({{baseurl}}/getting-started.html) page. This provides an overview of how to download [EDK II from github]({{wiki}}/Getting-Started-with-EDK-II){:target="_blank"}, building a platform or sample application, and [reporting issues in Bugzilla]({{wiki}}/Reporting-Issues){:target="_blank"}.
If you want to compile firmware or utilities, we recommend the [Getting Started]({{baseurl}}/getting-started.html) page. This provides an overview of how to download [EDK II from github]({{wiki}}/Getting-Started-with-EDK-II){:target="_blank"}, and [reporting issues in Bugzilla]({{wiki}}/Reporting-Issues){:target="_blank"}.

## Background
In June of 2004, Intel announced that it would release the “Foundation Code” of its Extensible Firmware Interface (EFI), a successor to the 16-bit x86 “legacy” PC BIOS, under an open source license. This Foundation Code, developed by Intel as part of a project code named Tiano, was Intel’s “preferred implementation” of EFI. This evolved into EDK, EDK II, and other open source projects under the TianoCore community.
Expand Down
3 changes: 2 additions & 1 deletion legalese.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ title: Legal

## Licenses for TianoCore Contributions

The preferred license for TianoCore is [BSD-2-Clause]({{wiki}}/BSD-License){:target="_blank"}. The [TianoCore contributors agreement](https://raw.githubusercontent.com/tianocore/edk2/master/MdePkg/Contributions.txt){:target="_blank"} describes acceptable licenses for community contributions.
The preferred license for TianoCore is [BSD+Patent]({{wiki}}/BSD-Plus-Patent-License){:target="_blank"}. When that is not possible, then contributions using
the following licenses can be accepted:
* BSD (2-clause): [http://opensource.org/licenses/BSD-2-Clause](https://opensource.org/licenses/BSD-2-Clause){:target="_blank"}
* BSD (3-clause): [http://opensource.org/licenses/BSD-3-Clause](http://opensource.org/licenses/BSD-3-Clause){:target="_blank"}
* MIT: [http://opensource.org/licenses/MIT](http://opensource.org/licenses/MIT){:target="_blank"}
Expand Down
237 changes: 237 additions & 0 deletions minutes/Community-2018-12.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,237 @@
<html>

<head>
<title>TianoCore Meeting Minutes</title>
<basefont face="Segoe UI" size="2" />
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="exporter-version" content="Evernote Windows/308094 (en-US, MWS); Windows/10.0.0 (Win64);" />
<style>
body,
td {
font-family: Segoe UI;
font-size: 10pt;
}
</style>
</head>

<body>
<a name="733" />

<div>
<span><div><div><span style="font-weight: bold;">Community Updates</span></div>
<div>We have talks submitted to both FOSDEM and the OCP Summit:</div>
<div><a href="https://fosdem.org/2019/">https://fosdem.org/2019/</a></div>
<div><a href="https://www.opencompute.org/summit/global-summit">https://www.opencompute.org/summit/global-summit</a></div>
<div>
<br/>
</div>
<div>FOSDEM Topics</div>
<div>UEFI Capsule Update</div>
<div>UEFI Overview - TianoCore &amp; U-Boot</div>
<div>
<br/>
</div>
<div>OCP Topics</div>
<div>TianoCore Roadmap</div>
<div>
<br/>
</div>
<div>At the start of the community meetings, please feel free to introduce yourself if you'd like your attendance to be recorded in the minutes. This can be done on IRC (OFTC - #edk2) or on the zoom chat feature.</div>
<div>
<br/>
</div>
<div>Please send feedback to me regarding the dates / times of these meetings. If no comments are heard I will assume that these dates and times are good.</div>
<div>
<br/>
</div>
<div>January and February's meetings will both be held on *the second week* of the month to accommodate holidays.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">Opens</span></div>
<ul>
<li>
<div>We would like to setup demos of the current patch systems specific companies are using and record those sessions. Nate can do this for Gerrit and the folks at Microsoft can do the same for Github. John from MS volunteered to do a walk-through of the patch review system as well as CI. Stephano will contact potential demo hosts and setup a time that works for them as well as discuss any concerns with recording the session.</div>
</li>
<li>
<div>There were questions about the release process, specifically the differences between the UDK release and Stable Tag releases.</div>
</li>
<ul>
<li>
<div>For details on Stable Tags, please see the following links:</div>
</li>
<ul>
<li>
<div><a href="https://github.com/tianocore/tianocore.github.io/wiki/EDK-II#stable-tags">https://github.com/tianocore/tianocore.github.io/wiki/EDK-II#stable-tags</a></div>
</li>
<li>
<div><a href="https://github.com/tianocore/tianocore.github.io/wiki/HardFeatureFreeze">https://github.com/tianocore/tianocore.github.io/wiki/HardFeatureFreeze</a></div>
</li>
<li>
<div><a href="https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze">https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze</a></div>
</li>
</ul>
<li>
<div>A Stable Tag is more frequent than the UDK release. It is a demand based branch rather than a cadence.</div>
</li>
<li>
<div>If a branch is created by the community, is that branch maintained, curated, and allowed to have future versions?</div>
</li>
<ul>
<li>
<div>The community we will discuss how this is addressed.</div>
</li>
<li>
<div>For now, much like the UDK, only critical fixes would be maintained.</div>
</li>
<li>
<div>Please feel free to send additional questions / comments on a new thread.</div>
</li>
</ul>
</ul>
<li>
<div>Build system changes, optimizations of the build system, possibly moving to the make files:</div>
</li>
<ul>
<li>
<div>There are some Bugzilla entries for this concept:</div>
</li>
<ul>
<li>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=1378">https://bugzilla.tianocore.org/show_bug.cgi?id=1378</a></div>
</li>
</ul>
</ul>
<ul>
<ul>
<li>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=1302">https://bugzilla.tianocore.org/show_bug.cgi?id=1302</a></div>
</li>
</ul>
</ul>
<ul>
<ul>
<li>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=1301">https://bugzilla.tianocore.org/show_bug.cgi?id=1301</a></div>
</li>
</ul>
</ul>
<ul>
<ul>
<li>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=1288">https://bugzilla.tianocore.org/show_bug.cgi?id=1288</a></div>
</li>
</ul>
</ul>
<ul>
<ul>
<li>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=972">https://bugzilla.tianocore.org/show_bug.cgi?id=972</a></div>
</li>
</ul>
</ul>
<ul>
<li>
<div>In the upcoming design meetings (TBD) we can discuss those bugs and review possible changes.</div>
</li>
<li>
<div>Community members should feel free to comment on those bugs directly.</div>
</li>
</ul>
</ul>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">License Change</span></div>
<div>Mark Doran has made it clear that we'll be moving to an Apache 2.0 license. There is an RFC with a detailed proposal here:</div>
<div><a href="https://lists.01.org/pipermail/edk2-devel/2018-October/030385.html">https://lists.01.org/pipermail/edk2-devel/2018-October/030385.html</a></div>
<div>
<br/>
</div>
<div>If you are a copyright holder, please look at the RFC, give comments, and if there is a legal process for approval on your end, please start that process. Let us know if there are any concerns from your legal department. There is also a Bugzilla entry for details on code changes:</div>
<div><a href="https://bugzilla.tianocore.org/show_bug.cgi?id=1373">https://bugzilla.tianocore.org/show_bug.cgi?id=1373</a></div>
<div>
<br/>
</div>
<div>There will be a branch that Mike Kinney will create soon so that folks can review the changes to ensure that nothing is incorrect or might cause a build break. There is a script making this change, so the manual review of all these files will be difficult. Community assistance in reviewing those changes is appreciated.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">Public Design and Bug Scrub Meetings</span></div>
<div>Stephano will send out an RFC to find a frequency and dates/times so that we can setup public design and bug scrub meetings. These are not meetings that everyone needs to join each occurance, however there will be required reviewers identified for specific features and bugs. There will be two meetings held, much like the Community Meeting format, to accommodate different time zones. Current thoughts are that Thursday AM (PST) for EMEA and PM (PST Friday AM Asia) would work, but please comment when the RFC is sent out if you have questions or comments. Making the design and bug scrub meeting agendas clear ahead of time is ideal. Stephano will head up that effort. Also, in each meeting we will collect the next week's possible topics.</div>
<div>
<br/>
</div>
<div>//COMMENT</div>
<div>We need to have a process for the best way to begin a new design idea. We do have a &quot;feature request&quot; in Bugzilla. We also need a way to share documentation in terms of design. Stephano will send out an RFC regarding options for ways of sharing these documents. The design meeting can act as a clarification to possible new feature questions.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">Patch Review Update</span></div>
<div><span style="font-weight: bold;">GitHub</span></div>
<div>Laszlo has been reviewing GitHub with the help of several folks at Microsoft. Microsoft currently relies on the Web UI of GitHub to archive all the details of their process. Laszlo did find some places where a &quot;force commit&quot; (as one example, there are others) would be visible only for a period of time, but will eventually be lost. There is a concern that the community may not find this level of logging acceptable. </div>
<div>
<br/>
</div>
<div>Offline use has also been brought up as an issue for those traveling regularly or with intermittent internet connections in their location. We want the TianoCore community to remain open for all to contribute regardless of their location or access to reliable internet. </div>
<div>
<br/>
</div>
<div>Stephano will send out a RFC, regarding both these issues. Please look at Laszlo's emails (they will be linked) and comment as to how these issues might effect your workflows. Details on any workarounds to these issues that folks have used or have researched are also appreciated.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">GitLab</span></div>
<div>Philippe Mathieu-Daudé has volunteered to facilitate a review of GitLab and has invited Laszlo to participate. We do not want to overload Laszlo with review tasks so we ask that any community members who have time to work on reviewing this system to please contact Stephano. Ideally this person should be very familiar with our patch review process so that they can give detailed, objective insight into the functionality of the system.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">Phabricator</span></div>
<div>Laszlo is currently working with Rebecca Cran to evaluate the features of Phabricator and there will be more info on this in upcoming emails.</div>
<div>
<br/>
</div>
<div>//COMMENT</div>
<div>CI will be included in our discussion eventually, however we are focusing on patch review for now.</div>
<div>
<br/>
</div>
<div>//COMMENT</div>
<div>There are future features in both GitLab and Phabricator that will be coming out in the near future. Also, if we could summarize the GitHub issues we could post them to their respective sites as feature requests. In the end, it is important to note which systems have features on the road map and which need feature request submitted. This will be called out in future summary emails / shared documents.</div>
<div>
<br/>
</div>
<div><span style="font-weight: bold;">Collaboration Software</span></div>
<div>We will be assessing several collaboration software possibilities. We will proceed with testing these options on specific discussion topics, and those discussions will be logged and summarized for the mailing list so as not to lose any information.</div>
<div>
<br/>
</div>
<div>Stephano will start discussions shortly on GitHub &quot;Team Discussions&quot;. This discussions will cover our use of line endings as well as the possible use of standard C types. More of these tests will be forthcoming.</div>
<div>
<br/>
</div>
<div>Thank you all for joining. As always, please feel free to email the list or contact me directly with any questions or comments.</div>
<div>
<br/>
</div>
<div>Kind Regards,</div>
<div>Stephano Cetola</div>
<div>TianoCore Community Manager</div>
<div>
<br/>
</div>
<div>
<br/>
</div>
<div>
<br/>
</div>
</div>
<div>
<br/>
</div>
</span>
</div>
</body>

</html>
Loading

0 comments on commit f5e3195

Please sign in to comment.