docs: migrate links from EVerest/EVerest to everest-core and add TSC documentation (EVerest#1913)

- Update contribution, coding style, and community links to point to everest-core repo and everest.github.io docs
- Add TSC index page with committee members and meeting info
- Convert TSC meeting notes from Markdown to RST with auto-discovery
  toctree
- Add working group descriptions with chairs to community page
- Add technical charter reference to governance page

Signed-off-by: Piet Gömpel <pietgoempel@gmail.com>

Author: Pietfried

.github/pull_request_template.md

@@ -5,5 +5,5 @@
 ## Checklist before requesting a review
 - [ ] I have performed a self-review of my code
 - [ ] I have made corresponding changes to the documentation
-- [ ] I read the [contribution documentation](https://github.com/EVerest/EVerest/blob/main/CONTRIBUTING.md) and made sure that my changes meet its requirements
+- [ ] I read the [contribution documentation](https://everest.github.io/nightly/project/contributing.html) and made sure that my changes meet its requirements
 

README.md

@@ -48,6 +48,7 @@ way to start is with our [Getting Started Guides](https://everest.github.io/nigh
 # Community
 
 Find more information about the community and ways to get involved [here](https://everest.github.io/nightly/project/community.html).
+
 # Contributing to EVerest
 
 Anyone can contribute to EVerest! Learn more about getting involved

docs/images/bmwk-logo-incl-supporting.png

@@ -44,9 +44,9 @@ This is what to do:
 
 2. Create a GitHub issue
 
-   a. In the repository https://github.com/EVerest/EVerest, click on ``Issues``
+   a. In the repository https://github.com/EVerest/everest-core, click on ``Issues``
       and then ``New issue``.
-   b. Choose ``Documentation change request`` and fill out the title and
+   b. Choose ``Feature Request`` and fill out the title and
       the description fields. Answer the templated questions, which have already
       been added to the description text area.
    c. Also add a reference to any related documentation pages and describe how

docs/source/how-to-guides/documenting-everest/extending-everest-documentation.rst

@@ -7,6 +7,8 @@ Meet the EVerest Community
 There are quite some options to get involved in the EVerest community.
 The following sections will guide your way.
 
+.. _exp_community_zulip:
+
 Deep tech discussions: Zulip
 ============================
 
@@ -47,12 +49,6 @@ dedicated EVerest projects and topics.
 
 The working groups could change over time depending on the current needs of
 the community.
-Currently, we have the following working groups:
-
-* Car Communication (car/charger communication with topics ISO 15118, EXI, SLAC, CHAdeMO etc)
-* Cloud Communication (communication between charger and backends in cloud with topics OCPP 1.6, 2.0.1, 2.1 etc)
-* Energy Management
-* MCS (Megawatt Charging System)
 
 The links to the Zoom meetings of the working groups can also be found in the
 `official EVerest event calendar <https://zoom-lfx.platform.linuxfoundation.org/meetings/everest?view=week>`_.
@@ -62,18 +58,47 @@ groups, you can ask in Zulip or in the General Call for finding like-minded
 people and suggest creating a new working group.
 
 You might want to join the working group chat channels in Zulip.
-See the “Zulip chat” section above to see how to get there!
+See the :ref:`exp_community_zulip` to see how to get there!
+
+Car Communication
+-----------------
+
+This working groups focuses on the communication between the EV and the charger, with topics like 
+ISO 15118, EXI, SLAC and CHAdeMO.
+
+Chair & Tech Lead: Sebastian Lukas (`@SebaLukas <https://github.com/SebaLukas>`_)
+
+Cloud Communication
+-------------------
+
+This working group focuses on the communication between the charger and the cloud, with topics like
+OCPP, OCPI and EEBUS.
+
+Chair & Tech Lead: Piet Gömpel (`@Pietfried <https://github.com/pietfried>`_)
+
+Energy Management
+-----------------
+
+This working group focuses on the energy management within EVerest, including topics like
+load management, smart charging and V2G.
+
+Chair & Tech Lead: Piet Gömpel (`@Pietfried <https://github.com/pietfried>`_)
+
+MCS (Megawatt Charging System)
+------------------------------
+
+This working group focuses on the development and implementation of the Megawatt Charging System (MCS) standard,
+which is designed for high-power charging of electric vehicles.
+
+Chair & Tech Lead: Sebastian Lukas (`@SebaLukas <https://github.com/SebaLukas>`_)
 
 Technical Steering Committee (TSC)
 ==================================
 
-The Technical Steering Committee (TSC) is the governing body of the EVerest Project It is responsible for the overall
+The Technical Steering Committee (TSC) is the governing body of the EVerest Project. It is responsible for the overall
 project health and direction, coordination of activities, and working with other projects and committees as needed for
 the continued growth of the project.
 
-You can find more resources about the TSC here:
-https://github.com/EVerest/EVerest/tree/main/tsc
-
 .. _exp_community_mailinglist:
 
 Tech discussion for email lovers

docs/source/project/community.rst

@@ -106,8 +106,8 @@ If you need a label that doesn't exist, discuss with maintainers before creating
 Coding Style
 ------------
 
-Each contribution must meet the `Javascript <https://github.com/EVerest/EVerest/blob/main/.eslintrc.json>`_ or
-`C++ <https://github.com/EVerest/EVerest/blob/main/.clang-format>`_ *coding style* (part of every repository).
+Each contribution must meet the `Javascript <https://github.com/EVerest/everest-core/blob/main/.eslintrc.json>`_ or
+`C++ <https://github.com/EVerest/everest-core/blob/main/.clang-format>`_ *coding style* (part of every repository).
 
 License
 -------

docs/source/project/contributing.rst

@@ -10,6 +10,9 @@ benefit of the community. All participation in this project is open and not
 bound to corporate affiliation. Participants are bound to the project's
 :doc:`Code of Conduct </project/governance/code-of-conduct>`.
 
+Technical Charter can be found at 
+https://github.com/lf-energy/foundation/blob/main/project_charters/everest_charter.pdf.
+
 Project roles
 =============
 
@@ -101,8 +104,7 @@ TSC Members
 TSC Members have formal voting rights on TSC decisions. They can be elected by existing
 voting members. A simple majority of existing voting members is required for approval.
 
-See the `TSC MEMBERS file <https://github.com/EVerest/EVerest/blob/main/tsc/MEMBERS.md>`_
-for the current list of TSC members and their roles.
+You can find the current TSC members as part of the :ref:`TSC documentation <governance_tsc>`.
 
 TSC responsibilities
 ~~~~~~~~~~~~~~~~~~~~
@@ -134,7 +136,7 @@ TSC meetings and participation
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 TSC meetings are open to the community. See the
-`TSC README <https://github.com/EVerest/EVerest/blob/main/tsc/README.md>`_
+:ref:`TSC Documentation <governance_tsc>`
 for meeting minutes and how to participate.
 
 Release Process

docs/source/project/governance/governance.rst

@@ -0,0 +1,40 @@
+.. _governance_tsc:
+
+Technical Steering Committee (TSC)
+==================================
+
+The Technical Steering Committee (TSC) is the governing body of the EVerest Project. It is responsible for the overall
+project health and direction, coordination of activities, and working with other projects and committees as needed for
+the continued growth of the project.
+
+TSC Meetings
+------------
+
+TSC meetings are held regularly, typically on a monthly basis. The meetings are open to the community and provide an opportunity
+for TSC members to discuss project-related matters, make decisions, and coordinate activities.
+
+For joining us in the TSC meetings, find the links in the official
+`EVerest event calendar <https://zoom-lfx.platform.linuxfoundation.org/meetings/everest?view=week>`_.
+
+Find the recordings of the TSC meetings here on YouTube: https://www.youtube.com/@lfe_everest
+
+Find the minutes of the TSC meetings :doc:`here <meetings/index>`.
+
+Committee Members
+-----------------
+
+- (Chair) Marco Möller [Pionix] (`@caller <https://github.com/caller>`_)
+- Cornelius Claussen [Pionix] (`@corneliusclaussen <https://github.com/corneliusclaussen>`_)
+- Kai-Uwe Hermann [Pionix] (`@hikinggrass <https://github.com/hikinggrass>`_)
+- Anton Wöllert [Pionix] (`a-w50 <https://github.com/a-w50>`_)
+- Moritz Barsnick [Chargebyte] (`@barsnick <https://github.com/barsnick>`_)
+- Holger Rapp [qwello] (`@SirVer <https://github.com/SirVer>`_)
+- K. Shankari [Joint office of Energy and Transportation] (`@shankari <https://github.com/shankari>`_)
+
+**Last updated: 2026-03-04**
+
+.. toctree::
+    :hidden:
+    :maxdepth: 1
+
+    meetings/index

docs/source/project/governance/tsc/index.rst

@@ -0,0 +1,61 @@
+EVerest TSC Meeting - [30th Nov 2021]
+=====================================
+
+
+Attendance
+----------
+
+
+Voting Members
+~~~~~~~~~~~~~~
+
+- [ ] Marco Möller
+- [ ] Cornelius Claussen
+
+
+Other Attendees
+~~~~~~~~~~~~~~~
+
+- John Mertic
+
+
+Agenda
+------
+
+- Welcome/Introductions
+- Discuss the role of the TSC
+- Elect TSC Chairperson
+- Review `project intake progress <../README.md#project-intake-checklist>`_
+- Approved `Charter <https://github.com/EVerest/everest/blob/main/tsc/CHARTER.md>`_
+- Determine TSC meeting cadence and schedule future meetings
+
+
+Action Items
+------------
+
+
+Notes
+-----
+
+
+- Elect TSC Chairperson ==> Marco Möller got elected
+- Approved `Charter <https://github.com/EVerest/everest/blob/main/tsc/CHARTER.md>`_
+- next TSC on 26th of Jan 2022 - 1700-1800 CET, then monthly via Google Meet, invite is in the list.
+- UPDATE: changed to 27th of Jan 2022 - 1700-1800 CET!!!!
+- Code scan completed ==> on TODO list from John
+- 14th Dez, we will do a TAC presentation about that we achived Incubation stage - 5 minutes plus questions
+- TODO: short dec, outline acceptance criteria of incubation stage and that all of it is done, where are we, and what happens next
+- Badge done: https://bestpractices.coreinfrastructure.org/en/projects/5386#quality
+- open: how to transfer everest project over to LFE ?
+    - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63
+- open: how to transfer everest trademark (in Germany) over to LFE ?
+    - TODO John, lets find out how to do this
+- delayed
+    - [ ] Add project to `LFX Insights <https://insights.lfx.linuxfoundation.org/>`_ ( create [service desk request] to trigger )
+    - [ ] Add project to `LFX Security <https://security.lfx.linuxfoundation.org/>`_ ( create [service desk request] to trigger )
+    - [ ] Domain name ( create [service desk request] to create/transfer )
+    - [ ] Transfer Social media accounts ( create [service desk request] to setup/transfer - if needed )
+    - Logo will be transfered soon
+    - [ ] Project added to LF Energy properties
+    - [ ] Website ( https://lfenergy.org/projects )
+    - [ ] LF Energy landscape ( https://l.lfenergy.org )

docs/source/project/governance/tsc/meetings/2021-11-30.rst

@@ -0,0 +1,47 @@
+EVerest TSC Meeting - [27th Jan 2022]
+=====================================
+
+
+Attendance
+----------
+
+
+Voting Members
+~~~~~~~~~~~~~~
+
+- [x] Marco Möller
+- [x] Cornelius Claussen
+
+
+Other Attendees
+~~~~~~~~~~~~~~~
+
+- Benjamin Mosler / Pionix
+- Tim Valbert / Pionix
+- Julian Rädel / Pionix
+- Kai Herrmann / Pionix
+- Gabe Hege / volta.foundation
+- Gerardo Marin / Mexico
+
+
+Agenda
+------
+
+- Welcome / Introductions
+- Presentation of Project Scope + Roadmap + Current Status
+- Presentation of Pionix Development Kit and how to port EVerest to custom hardware
+- open discussion to onboard new members and answer questions
+
+
+Action Items
+------------
+- sent recording our to Gabe (Marco)
+
+
+Recording:
+----------
+- https://youtu.be/pLwfN55d-gc
+
+
+Notes
+-----