[edk2-devel] TianoCore Community Meeting Minutes - November 2021

[Teng, Lynn L]

# TianoCore Community Meeting
November 4, 2021

**Highlights:**  
* **Python 3 is here and the removal of Python 2 is coming soon**  
* **Our Inclusive Language commitment and activities will begin soon**  
* **Request to the Community**: Please review the list of features on [Bugzilla](https://bugzilla.tianocore.org/show_bug.cgi?id=3446) to have them ready for 2.8  
* **Request to the Community**: When can we delete the Python BaseTool source from the EDK II repo and move towards using the Python BaseTools PIP Install?  
* **Request to the Community**: Help identify the status of each EDK II Platform and who are the maintainers?  
* **Request to the Community**: Evaluate the source format being produced by Uncrustify and how it works.  If you have any questions or issues with either, please let us know by the beginning of December.


# Meeting Minutes:

1) **Event Updates (_5 minutes_)**
   - No Updates

2) [**Stable Tag Updates (_5 minutes_)**](https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Release-Planning)
   - 2021-11-08 Soft Feature Freeze
   - 2021-11-12 Hard Feature Freeze
   - 2021-11-26 Release

3) **Stewards Download (_20 minutes_)**
   - UEFI 2.8 report
      - **Request to the Community**: Please review the list of features on Bugzilla to have them ready for 2.8
         - Targeting first release in 2022 to have all UEFI 2.8 features done ([Bugzilla 3446](https://bugzilla.tianocore.org/show_bug.cgi?id=3446))
   - Python for BaseTools are ready for PIP install
      - Our goal is to move everyone to pip installing rather than maintaining a duplicate copy of the sources/repos
      - We would like to delete the Python BaseTools source from the EDK II repo
      - **Question from Community**: Would it be possible to full BaseTools from a submodule?
      - **Request to the Community**: When can we delete the Python BaseTool source from the EDK II repo and move towards using the Python BaseTools PIP Install?
   - EDK II Platforms Repository
      - We have stable tags for EDK II, but not EDK II Platforms
      - Each platform is at a different level of maintenance
      - Only keep maintained platforms in master (to be renamed to main)
      - Having a separate branch for unmaintained stable branches, _different from under development branches_
      - Establish stable tag for EDK II Platforms
      - **Request to the Community**: Help identify the status of each EDK II Platform and who are the maintainers? 
         - Bring the platforms up to being compatible with latest the EDK II.  
         - Would like to have a stable tag and CI to the Platforms to improve maintainability.
      - **Question from Community**: What to do about platforms that haven't been touched in years, but developers would like to use?
      - **Discussion**: Having an inventory of physical platforms owned by individual platform owners
         - Would be good to document a process for adding physical platforms for the community to access
         - Standardize API for connecting and getting simple status from those physical platforms
   - Uncrustify (_a code clean up tool_)
      - A version is being created to clean EDK II code
      - We would like to ensure that any clean up of the EDK II source does not affect its functionality
      - Our target to begin cleaning is after the next stable tag release
      - **Request to the Community**: Evaluate the source format being produced by Uncrustify and how it works.  If you have any questions or issues with either, please let us know by the beginning of December.

4) **Opens (_30 minutes_)**
   - **Python 3 is here and the removal of Python 2 is coming soon**
   - Our Inclusive Language commitment and activities will begin soon
      - Master will be renamed to Main in git
         - First we need to do the full evaluation of how changing the name will affect the repositories
         - We will proceed with repository renaming in a layered approach
            1. All new repositories must be named Main
            2. Convert repositories that don't have active CI
            3. Convert the rest of the repositories when possible
         - All developers will be informed when a repo is going being changed and how to handle the change
      - All other Inclusive Language commits will begin as community code reviews for catching banned words
      - We will build a wiki page with a task list of work to be done
   - **Question from Community**: Should we formalize the "Get Started with Git" and clean it up/raise awareness?
      - **Answer**: The community has write permissions to update any wiki pages, so we can work together to update and maintain it
   - **Question from Community**: Is there an update on the pull request feature for switching email based patches to pull requests?
      - **Answer**: We do not have update on that currently, but it's on the to do list


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#83528): https://edk2.groups.io/g/devel/message/83528
Mute This Topic: https://groups.io/mt/86943410/1813853
Group Owner: devel+owner at edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [edk2-devel-archive at redhat.com]
-=-=-=-=-=-=-=-=-=-=-=-