d398a6ced2
- CitrineOS core extracted (CSMS OCPP 2.0.1) - OpenOCPP extracted (firmware OCPP 1.6J/2.0.1) - ShapeShifter library installed (pip install -e) - ShapeShifter specification extracted - EVerest extracted TODO updated with progress
150 lines
5.2 KiB
ReStructuredText
150 lines
5.2 KiB
ReStructuredText
.. _project-community:
|
|
|
|
##########################
|
|
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
|
|
============================
|
|
|
|
The main area for tech talk and discussing questions is Zulip:
|
|
|
|
`EVerest Zulip <https://lfenergy.zulipchat.com/>`_
|
|
|
|
You can find chat channels there for different topics all around EVerest.
|
|
|
|
Feel free to drop your own questions and dive into the communication with
|
|
other EVerest enthusiasts.
|
|
|
|
Read the README channel in Zulip for more information about the different
|
|
channels.
|
|
|
|
|
|
Live calls by core developers: Working groups
|
|
=============================================
|
|
|
|
We also have online video meetings for a more personal way of exchange.
|
|
|
|
The General EVerest Welcome Call is a format since the beginning of 2025.
|
|
If these documentation pages at hand leave some questions open about how the
|
|
EVerest community works, and you want to clarify that in person, you can join
|
|
us in a weekly (non-technical) meeting.
|
|
|
|
We can answer question all around the EVerest community and show you the way
|
|
to go with your specific scenario.
|
|
|
|
The General EVerest Welcome Call is each Tuesday at 11am CE(S)T.
|
|
|
|
For joining us in the Zoom meetings, find the links in the official
|
|
`EVerest event calendar <https://zoom-lfx.platform.linuxfoundation.org/meetings/everest?view=week>`_.
|
|
|
|
Further live meetings we regularly have are the working group meetings.
|
|
In the working groups, developers meet for exchanging the status quo of
|
|
dedicated EVerest projects and topics.
|
|
|
|
The working groups could change over time depending on the current needs of
|
|
the community.
|
|
|
|
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>`_.
|
|
|
|
If you work on a topic that does not fit in the current list of working
|
|
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 :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
|
|
project health and direction, coordination of activities, and working with other projects and committees as needed for
|
|
the continued growth of the project.
|
|
|
|
.. _exp_community_mailinglist:
|
|
|
|
Tech discussion for email lovers
|
|
================================
|
|
|
|
Another way to connect to the steadily growing EVerest community is
|
|
the mailing list.
|
|
|
|
Traffic decreased steadily since the introduction of Zulip, but if email is
|
|
your favourite choice of communicating, here's the way to go.
|
|
|
|
We have set up two separate mailing lists:
|
|
|
|
The most important one is the announcement list.
|
|
Important news or events all around EVerest are shared there.
|
|
|
|
Subscribe here:
|
|
`EVerest announcement list <https://lists.lfenergy.org/g/everest-announce>`_ .
|
|
|
|
Optionally, you can subscribe to the mailing list with more tech focus:
|
|
`EVerest mailing list <https://lists.lfenergy.org/g/everest>`_ .
|
|
|
|
|
|
Beyond EVerest: Special Interest Group
|
|
======================================
|
|
|
|
Linux Foundation Energy (LFE) is growing.
|
|
As the EVerest project (and all other LFE projects) have several connecting
|
|
points to other projects in the same field, a Special Interest Group (SIG) has
|
|
been created for
|
|
|
|
* exchanging thoughts and experiences,
|
|
* share best practices,
|
|
* discuss industry trends and
|
|
* tackle challenges together.
|
|
|
|
If you work in the field of EV charging and you are interested in open source
|
|
software / projects, join the SIG calls.
|
|
They are free to access and open to all interested parties.
|
|
|
|
Join the mailing list
|
|
`https://lists.lfenergy.org/g/ev-charging-sig <https://lists.lfenergy.org/g/ev-charging-sig>`_
|
|
and check out the zoom meetings via
|
|
`https://zoom-lfx.platform.linuxfoundation.org/meetings/ev-charging-sig <https://zoom-lfx.platform.linuxfoundation.org/meetings/ev-charging-sig>`_.
|
|
|
|
----
|
|
|
|
**Authors**: Manuel Ziegler, Andreas Heinrich
|