Date   

Re: Zoom Service Blocked by China

Stephano Cetola
 

On 9/17/2019 2:58 PM, Stephano Cetola wrote:
Assuming these meetings go smoothly this week, I will move the EMEA meetings as well as the monthly community meetings over to BlueJeans.
The Bug Triage went "smoothly", eventually. :)

One note, for those of us lucky enough to be running Windows 10 Corporate Build, the web app did not work well.

https://www.bluejeans.com/downloads

The desktop app seemed to work much better for us.

One user confirmed that the iOS app worked well.

Cheers,
Stephano


Re: Zoom Service Blocked by China

Stephano Cetola
 

On 9/10/2019 8:01 AM, Stephano Cetola wrote:
I'd like to propose BlueJeans as a replacement. AFAIK, they support web clients (no binary needed), Android, and iOS.
We ran a preliminary test of BlueJeans yesterday and it seems to meet our needs rather well.

As such, I've updated the two APAC meetings (on our Groups.io calendar) to use BlueJeans:

https://edk2.groups.io/g/devel/message/47435

https://edk2.groups.io/g/devel/message/47437

Assuming these meetings go smoothly this week, I will move the EMEA meetings as well as the monthly community meetings over to BlueJeans.

For those of you attending the APAC meetings this week, please do ping me with any feedback.

Cheers,
Stephano


Re: Zoom Service Blocked by China

Liming Gao
 

Stephano:
I can access https://www.bluejeans.com/. Can you set up one meeting in bluejeans for test? I will join in it from China.

Thanks
Liming

-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Tuesday, September 10, 2019 11:01 PM
To: announce@edk2.groups.io
Cc: Laszlo Ersek <lersek@...>; Kinney, Michael D <michael.d.kinney@...>; Leif Lindholm <leif.lindholm@...>;
Andrew Fish <afish@...>
Subject: [edk2-announce] Zoom Service Blocked by China

Hi All,

https://status.zoom.us/incidents/xbmxyfpnv4jq

It would seem that on Monday China blocked Zoom, our preferred
conference software.

This is an off week (luckily) for APAC meetings, so this should not
immediately effect us.

I'd like to propose BlueJeans as a replacement. AFAIK, they support web
clients (no binary needed), Android, and iOS. Also, I believe they will
work well in China:

https://support.bluejeans.com/s/article/Premium-Access-for-China

Cheers,
Stephano

An nescis, mi fili, quantilla prudentia mundus regatur?
--Axel Oxenstierna


Re: Zoom Service Blocked by China

Stephano Cetola
 

On Sep 11, 2019, at 1:27 PM, rebecca@... wrote:

Another alternative might be Jitsi (https://jitsi.org/).

“Multi-platform open-source video conferencing
At Jitsi, we believe every video chat should look and sound amazing, between two people or 200. Whether you want to build your own massively multi-user video conference client, or use ours, all our tools are 100% free, open source, and WebRTC compatible.”
Interesting, I haven’t heard of Jitsi.

I’ll have a look at this and see if it meets all our requirements.

—S


Re: Zoom Service Blocked by China

rebecca@...
 

Another alternative might be Jitsi (https://jitsi.org/).

“Multi-platform open-source video conferencing
At Jitsi, we believe every video chat should look and sound amazing, between two people or 200. Whether you want to build your own massively multi-user video conference client, or use ours, all our tools are 100% free, open source, and WebRTC compatible.”

Rebecca Cran

On Sep 11, 2019, at 7:22 AM, Laszlo Ersek <lersek@...> wrote:

On 09/10/19 17:01, stephano wrote:
Hi All,

https://status.zoom.us/incidents/xbmxyfpnv4jq

It would seem that on Monday China blocked Zoom, our preferred
conference software.

This is an off week (luckily) for APAC meetings, so this should not
immediately effect us.

I'd like to propose BlueJeans as a replacement. AFAIK, they support web
clients (no binary needed), Android, and iOS. Also, I believe they will
work well in China:

https://support.bluejeans.com/s/article/Premium-Access-for-China
Generally speaking, I'm fine with the BlueJeans platform -- I use my
company-issued PolyCom handset for dialing a "BlueJeans bridge" (using
an internal extension), and then I participate as a voice-only
participant. (I don't like installing proprietary browser plugins, and I
wouldn't enable video anyway.) AFAIR I can see -- consume -- screens
shared by others, in Firefox, without installing the plugin; so that
should work for me too.

Thanks!
Laszlo



Re: Zoom Service Blocked by China

Laszlo Ersek
 

On 09/10/19 17:01, stephano wrote:
Hi All,

https://status.zoom.us/incidents/xbmxyfpnv4jq

It would seem that on Monday China blocked Zoom, our preferred
conference software.

This is an off week (luckily) for APAC meetings, so this should not
immediately effect us.

I'd like to propose BlueJeans as a replacement. AFAIK, they support web
clients (no binary needed), Android, and iOS. Also, I believe they will
work well in China:

https://support.bluejeans.com/s/article/Premium-Access-for-China
Generally speaking, I'm fine with the BlueJeans platform -- I use my
company-issued PolyCom handset for dialing a "BlueJeans bridge" (using
an internal extension), and then I participate as a voice-only
participant. (I don't like installing proprietary browser plugins, and I
wouldn't enable video anyway.) AFAIR I can see -- consume -- screens
shared by others, in Firefox, without installing the plugin; so that
should work for me too.

Thanks!
Laszlo


Zoom Service Blocked by China

Stephano Cetola
 

Hi All,

https://status.zoom.us/incidents/xbmxyfpnv4jq

It would seem that on Monday China blocked Zoom, our preferred conference software.

This is an off week (luckily) for APAC meetings, so this should not immediately effect us.

I'd like to propose BlueJeans as a replacement. AFAIK, they support web clients (no binary needed), Android, and iOS. Also, I believe they will work well in China:

https://support.bluejeans.com/s/article/Premium-Access-for-China

Cheers,
Stephano

An nescis, mi fili, quantilla prudentia mundus regatur?
--Axel Oxenstierna


EDK II Stable Tag release edk2-stable201908 completed

Liming Gao
 

Hi, all

The tag edk2-stable201908 has been created. https://github.com/tianocore/edk2/releases/tag/edk2-stable201908
git clone -b edk2-stable201908 https://github.com/tianocore/edk2.git

The tag edk2-stable201908 has been added into the main EDK II Wiki page.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II

The quiet period has now ended. Thank you for your cooperation and patience. Normal commits can now be resumed.

Next edk2 stable tag (edk2-stable201911) planning has been added into wiki page.
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning.

If you have ideas for features in the next stable tag, please enter a Bugzilla for evaluation. Please let me know if there are existing open Bugzilla entries that should be targeted at this next stable tag.

Thanks
Liming


EDK II Stable Tag edk2-stable201908 will be created based on commit 37eef91017ad042035090cae46557f9d6e2d5917

Liming Gao
 

Hi, all

Today, I review all patches in edk2 mail list. There is no patches for EDK II Stable Tag edk2-stable201908. Based on edk2-stable201908 tag planning, it will be released at 2019-08-30. So, I plan to create edk2-stable201908 based on current edk2 trunk (https://github.com/tianocore/edk2/commit/37eef91017ad042035090cae46557f9d6e2d5917 BaseTools: Fixed regression issue for building !x86 builds) on UTC - 8 00:00 of 2019-08-30. If you have any comments, please reply the mail. If no concern or objection, I will create tag and send another announce mail that edk2-stable201908 is completed and normal commit is resumed.

Thanks
Liming


Community Meeting - Next Week, or Not?

Stephano Cetola
 

With OSFC being next week, I've canceled the two community meetings.

We can handle this one of two ways:
If there are a lot of folks at the conference that want to meet in person, we can do that. I'm only there Thursday PM) and Friday (AM), so that limits our options. If it works out I'll stream the meeting on Zoom and take minutes for those who cannot attend.

If we don't have "critical mass", I'll reschedule for later in September.

Feel free to comment on this thread.

Cheers,
Stephano


TianoCore Community Design Meeting Minutes - Aug 22

Ni, Ray
 

1. Re-architecture of Intel edk2 Redfish POC code on edk2 staging (HPE)
Presenter: Chang Abner
Slides: https://edk2.groups.io/g/devel/files/Designs/2019/0823

* Background:
Redfish project started in early 2017 and HPE is working with Intel since then.
Intel pushed code to edk2-staging repo.
POC in Nt32, but servers with BMC has their own implementations.
Re-architecture is needed to make it more flexible and easily adoptable.

Configuration without EDKII redfish: HII/form. (page #2)
With redfish: redfish links to x-UEFI keyword based HII configuration. (page #3)
Current EDK2 Redfish POC code implementation. (page #5 ~ #12)

* Proposals / changes
(1). Feature drivers have schema associated. Use schema as the driver name.
Boot Info DXE driver -> Computer System DXE driver
@Jiaxin: Boot Info is sub-set of ComputerSystem.
@Abner: Agree to keep BootInfo as the driver name.

(2). Redfish Discover Protocol discovers redfish services and creates instance of redfish for RedfishConfigDriver. (page #14)
(3). RedfishHostInterfaceDxe generic driver contains the generic code to create SMBIOS type 42 record. (page #14)
(4). RestEx driver talks to platform-specific Platform REST when it exists. (page #15)
@Siyuan: REST EX depends on platform-specific protocol, which makes NetworkPkg depends on platform. It's not good.
@Abner: will sync it later offline how to maximumly share the code without introducing the platform dep.
(5). Change Credential protocol to static library to avoid invocation from 3rd party code(PCI Option ROM) at runtime. (page #16)
@Siyuan: StopServices in credential protocol can stop the credential services after end-of-dxe.
@Ray: Entrypoint of oprom is not called before end-of-dxe.
@Abner: Will double-confirm and keep protocol design if no security concern.
(6). Add build time redfish BIOS resource generator. (page #17)

* Opens
@Ray: Will code be moved to edk2 repo after this re-architecture?
@Abner: HPE will work on staging repo and won't do the move.

@Jiaxin: Would like to keep the simulator-based implementation.
@Siyuan: Nt32Pkg is removed.
@Ray: EmulatorPkg network can be enabled.

@Abner: Tech discussion with Intel on Redfish design should go in public mailing list or not?
@Mike: Please follow the staging repo development process and communicate to community when moving to edk2 repo.

Thanks,
Ray


Hard Feature Freeze start now for edk2-stable201908

Liming Gao
 

Hi, all
Today, we will enter into Hard Feature Freeze phase until edk2-stable201908 tag is created at 2019-08-30. In this phase, there is no feature to be pushed. The critical bug fix is still allowed.

If the patch is sent after Hard Feature Freeze, and plans to catch this stable tag, please add edk2-stable201908 key words in the patch title and BZ, and also cc to Tianocore Stewards, then Stewards can give the comments.

Below is edk2-stable201908 tag planning.
Date (00:00:00 UTC-8) Description
2018-06-06 Beginning of development
2019-08-16 Soft Feature Freeze
2019-08-23 Hard Feature Freeze
2019-08-30 Release

Thanks
Liming


Re: Soft Freeze starts in 1 week for edk2-stable201908

Stephano Cetola
 

On 8/16/2019 8:52 AM, Laszlo Ersek wrote:
On 08/15/19 04:36, Gao, Liming wrote:
Stephano:
I have one proposal to add another date for Feature Planning Freeze. This date is ahead of 2 weeks to code Soft Feature Freeze. If the feature is missed in the Feature Planning Freeze date, the feature owner should ask the request for Tianocore Stewards and get the approve. I would suggest to add this date from next stable tag edk2-stable2019011.
I would not object to that.
(responding to announce@ as I think that is presently the expected user
behavior)
Thanks,
Laszlo
Yes, I agree as well.

Unless anyone objects, I'll add this to the wiki and to our next release planning page.

Cheers,
Stephano


Re: Soft Freeze starts in 1 week for edk2-stable201908

Laszlo Ersek
 

On 08/15/19 04:36, Gao, Liming wrote:
Stephano:
I have one proposal to add another date for Feature Planning Freeze. This date is ahead of 2 weeks to code Soft Feature Freeze. If the feature is missed in the Feature Planning Freeze date, the feature owner should ask the request for Tianocore Stewards and get the approve. I would suggest to add this date from next stable tag edk2-stable2019011.
I would not object to that.

(responding to announce@ as I think that is presently the expected user
behavior)

Thanks,
Laszlo

-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Monday, August 12, 2019 2:32 AM
To: Gao, Liming <liming.gao@...>
Cc: announce@edk2.groups.io
Subject: Re: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The soft freeze is for features only. Bug fixes are still allowed. You
can read more here:

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze
https://github.com/jljusten/tianocore/wiki/HardFeatureFreeze

The hard freeze will only allow critical bug fixes, and even then only
with the steward's approval.

If you have a feature you'd like to get in to the stable tag, but it's
not on the current feature list, I'd recommend sending in an RFC to both
the RFC list and CC the devel list.

The hope here is really just to ease the pain of last-minute features
being added to a stable tag. We realize this sort of thing will happen,
but we'd like to be sure there is as much communication around these
types of feature requests as possible.

Cheers,
Stephano

On 8/9/2019 7:59 AM, Liming Gao wrote:
Stephano:
Is it for bug or features or both? Send RFC to announce@edk2.groups.io or devel@edk2.groups.io or both?

Thanks
Liming
-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Friday, August 9, 2019 10:52 PM
To: announce@edk2.groups.io
Subject: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The edk2-stable201908 tag is on it's way! Soft feature freeze starts
next week. If you have something you're looking to get into this
release, now's a great time to email the list with an RFC!

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

Cheers,
Stephano





Soft Feature Freeze starts now for edk2-stable201908

Liming Gao
 

Hi, all
Now, we enter into Soft Feature Freeze phase. In this phase, the feature under review will not be allowed to be pushed. The patch review can continue without break in edk2 community.

If the patch is sent before Soft Feature Freeze, and plans to catch this stable tag, the patch contributor need reply to the mail list https://edk2.groups.io/g/devel/message/45805 and notify the community.
If the patch is sent after Soft Feature Freeze, and plans to catch this stable tag, please add edk2-stable201908 key words in the patch title and BZ, so the community know this patch target and give the feedback.

Below is edk2-stable201908 tag planning.
Date (00:00:00 UTC-8) Description
2018-06-06 Beginning of development
2019-08-16 Soft Feature Freeze
2019-08-23 Hard Feature Freeze
2019-08-30 Release

Thanks
Liming


Re: Soft Freeze starts in 1 week for edk2-stable201908

Liming Gao
 

Stephano:
I have one proposal to add another date for Feature Planning Freeze. This date is ahead of 2 weeks to code Soft Feature Freeze. If the feature is missed in the Feature Planning Freeze date, the feature owner should ask the request for Tianocore Stewards and get the approve. I would suggest to add this date from next stable tag edk2-stable2019011.

Thanks
Liming

-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Monday, August 12, 2019 2:32 AM
To: Gao, Liming <liming.gao@...>
Cc: announce@edk2.groups.io
Subject: Re: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The soft freeze is for features only. Bug fixes are still allowed. You
can read more here:

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze
https://github.com/jljusten/tianocore/wiki/HardFeatureFreeze

The hard freeze will only allow critical bug fixes, and even then only
with the steward's approval.

If you have a feature you'd like to get in to the stable tag, but it's
not on the current feature list, I'd recommend sending in an RFC to both
the RFC list and CC the devel list.

The hope here is really just to ease the pain of last-minute features
being added to a stable tag. We realize this sort of thing will happen,
but we'd like to be sure there is as much communication around these
types of feature requests as possible.

Cheers,
Stephano

On 8/9/2019 7:59 AM, Liming Gao wrote:
Stephano:
Is it for bug or features or both? Send RFC to announce@edk2.groups.io or devel@edk2.groups.io or both?

Thanks
Liming
-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Friday, August 9, 2019 10:52 PM
To: announce@edk2.groups.io
Subject: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The edk2-stable201908 tag is on it's way! Soft feature freeze starts
next week. If you have something you're looking to get into this
release, now's a great time to email the list with an RFC!

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

Cheers,
Stephano





Re: Soft Freeze starts in 1 week for edk2-stable201908

Stephano Cetola
 

The soft freeze is for features only. Bug fixes are still allowed. You can read more here:

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze
https://github.com/jljusten/tianocore/wiki/HardFeatureFreeze

The hard freeze will only allow critical bug fixes, and even then only with the steward's approval.

If you have a feature you'd like to get in to the stable tag, but it's not on the current feature list, I'd recommend sending in an RFC to both the RFC list and CC the devel list.

The hope here is really just to ease the pain of last-minute features being added to a stable tag. We realize this sort of thing will happen, but we'd like to be sure there is as much communication around these types of feature requests as possible.

Cheers,
Stephano

On 8/9/2019 7:59 AM, Liming Gao wrote:
Stephano:
Is it for bug or features or both? Send RFC to announce@edk2.groups.io or devel@edk2.groups.io or both?
Thanks
Liming
-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Friday, August 9, 2019 10:52 PM
To: announce@edk2.groups.io
Subject: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The edk2-stable201908 tag is on it's way! Soft feature freeze starts
next week. If you have something you're looking to get into this
release, now's a great time to email the list with an RFC!

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

Cheers,
Stephano



Re: Soft Freeze starts in 1 week for edk2-stable201908

Liming Gao
 

Stephano:
Is it for bug or features or both? Send RFC to announce@edk2.groups.io or devel@edk2.groups.io or both?

Thanks
Liming

-----Original Message-----
From: announce@edk2.groups.io [mailto:announce@edk2.groups.io] On Behalf Of Stephano Cetola
Sent: Friday, August 9, 2019 10:52 PM
To: announce@edk2.groups.io
Subject: [edk2-announce] Soft Freeze starts in 1 week for edk2-stable201908

The edk2-stable201908 tag is on it's way! Soft feature freeze starts
next week. If you have something you're looking to get into this
release, now's a great time to email the list with an RFC!

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

Cheers,
Stephano



Soft Freeze starts in 1 week for edk2-stable201908

Stephano Cetola
 

The edk2-stable201908 tag is on it's way! Soft feature freeze starts next week. If you have something you're looking to get into this release, now's a great time to email the list with an RFC!

https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning

https://github.com/tianocore/tianocore.github.io/wiki/SoftFeatureFreeze

Cheers,
Stephano


TianoCore Community Design Meeting Minutes - Jul 26

Ni, Ray
 

1. Edk2 Build Cache Enhancement
Presenter: Steven Shi
Slides: https://edk2.groups.io/g/devel/files/Designs/2019/0726/Edk2BuildCacheEnhancement-v1.pdf

* Background (page #2 - #8)
Build cache is enabled already in today's build tool.
Hash depends on unnecessary inputs.
Cache is very easy to miss.

* Proposal (page #9 - #12)
Fine-grain and precise hash is needed -> Post-makefile Cache checkpoint
Today's coarse hash is still needed to quickly bypass no source change -> Pre-makefile Cache checkpoint
Question to page #3: The proposal is to improve the cache hit rate through Fine-grain and precise hash. When cache is hit, build task directly jumps from AutoGen to GenFds. Do we have plans to consider jumping from AutoGen to other phases?
Answer: We call it multiple-level build caches. Refer to last page. Today focuses on improving the cache hit rate only.
No build options to enable it individually.
Question to page #10: What Others in AutoGen mean?
Answer: Others can be removed in the flow chart. Post-makefile Cache checkpoint is the last step in AutoGen.
Module Post-makefile hash = Hash(Makefile content) + Hash (include headers contents) + hash (AutoGen files contents) + lib Post-makefile hash + Hash (Module files contents)

* Performance (page #13)
With only pre-makefile cache checkpoint, build is fast (<30s) without changes, but slow (2-3mins) with DSC changes.
With both pre&post-makefile cache checkpoint, build is fast (~40s) with DSC changes.
Question: What's the penalty (extra time if all modules post-makefile cache miss against cache disable) of post-makefile cache checkpoint?
Answer: Haven't collected the data. Will collect and present.

* Open
Question: Cache can be shared across platforms or is bound to a specific platform?
Answer: No share across platforms. But a good timing to consider the share across platforms with the new fine-grain and precise hash. Share is possible if the output path can be excluded from hash.
No support of debug symbol cache.

2. Open: Seeking tasks for Google Summer of Code (Stephano Cetola)
Who will investigate "BZ1959 BaseLib.h linked list macros EFI_LIST_FOR_EACH_SAFE"? Pkg maintainers or new comers to work on?
Liming will have a look at it.
Google Summer of Code looks for projects that students can learn from. EDKII Bugzilla is a good candidate.

3. Open: HPE will bring Redfish topics to this meeting in future (Abner Chang)

Thanks,
Ray

241 - 260 of 309