-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
126 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
# Collaborative Development | ||
|
||
Researchers who participate in the development of the Open Energy Family are | ||
known as "core developers". Their work involves capturing scientific processes | ||
that can be implemented in software, gathering requirements, and developing | ||
processes or artifacts such as software code and test results. | ||
Additionally, they contribute to the development of specific Family Members, | ||
like the ontology, drawing on their expertise in fields such as energy systems. | ||
Core developers collaborate with the open community to improve and maintain the | ||
software and troubleshoot any issues that arise. | ||
|
||
To ensure the transparency and accessibility of the development process, | ||
all developments are publicly planned, executed, and documented on GitHub and | ||
in development meetings. | ||
Core developers also have direct or indirect access to internal systems such as | ||
servers that cannot be publicly accessible for security reasons. | ||
|
||
While the core developers are responsible for the bulk of the development work, | ||
the Open Energy Family is open to participation from anyone interested in | ||
contributing. | ||
This includes stakeholders such as other researchers in the energy system | ||
domain who may not be directly involved in the research projects but have an | ||
interest in the tools and services offered by the framework. | ||
|
||
As the work of core developers requires significant effort, funding is crucial | ||
to ensure their continued participation. It is therefore essential that | ||
individuals are deployed as part of a research project that provides adequate | ||
funding for their work. By embracing the collaborative spirit of Open Science, | ||
the Open Energy Family is able to leverage the expertise and contributions of a | ||
diverse range of stakeholders to create a more sustainable and | ||
equitable energy system. | ||
|
||
<figure markdown> | ||
![Image title](../img/oef-concept-collaboration-developer.png){ width="600" } | ||
<figcaption>Image caption</figcaption> | ||
</figure> | ||
|
||
## Collab. SDP | ||
|
||
## GitHub Teams | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
# Community Management | ||
|
||
## Community Manager | ||
|
||
Community Management is critical for the success of the Open Energy Family. | ||
The Community Manager fosters a collaborative environment and communicates | ||
between the community and the development team. They gather feedback, | ||
prioritize requests, and organize events that facilitate engagement and | ||
collaboration. | ||
Effective Community Management ensures that the framework meets the needs of | ||
its users and adapts to the changing needs of the energy research community. | ||
|
||
## Steering Committees | ||
|
||
To accompany the ongoing development and success of the Community, | ||
two steering committees have been established: | ||
the OEO Steering Committee (OSO-SC) | ||
and the OEFamily Steering Committee (OEFamily-SC). | ||
Both steering committees play a critical role in guiding the development | ||
of the Open Energy Family and the OEO. | ||
Their oversight and strategic direction help to ensure that the framework | ||
and ontology remain relevant and useful to the energy research community. | ||
|
||
### OEFamily-SC | ||
|
||
The OEFamily-SC is responsible for the overall development and strategic | ||
direction of the Open Energy Family framework. | ||
The committee works closely with the core development team to ensure that the | ||
framework meets the needs of its users and remains aligned with the goals | ||
of the project. It meets regularly via conference calls and in-person meetings | ||
to exchange information and review planned and completed tasks. | ||
|
||
#### Tasks of the OEFamily-SC | ||
|
||
1. Maintain an overview of the OEFamily and its structure | ||
- Identify existing and planned functions and components | ||
- Determine responsibilities and time lines for development | ||
- Identify similar projects in the field | ||
2. Support the development of the OEFamily | ||
- Support in prioritizing tasks and decisions about the development progress | ||
- Ensuring the sustainability of the development through continuous feedback and testing | ||
3. Act as a mediator and decision-making body | ||
- Enforce the code of conduct for interpersonal issues | ||
- Utilize the Dev-Meeting processes for content-related disputes | ||
4. Support external communication efforts | ||
- Represent the OEFamily at conferences and public events | ||
- Maintain and expand networks, identifying key individuals and organizations who should be informed about the OEFamily and OEP | ||
- Foster connections between users and developers | ||
- Communicate with funding bodies and government ministries | ||
5. Develop and advance the vision of the OEFamily | ||
- Developing and pursuing strategies to expand and improve the functionality | ||
- Identifying future areas of application and integrating new technologies and developments | ||
|
||
### OSO-SC | ||
|
||
The OEO-SC is responsible for overseeing the development of the OEO | ||
and ensuring its adoption in currently running and planned projects. | ||
The committee meets regularly via conference calls and in-person meetings | ||
to exchange information and review planned and completed tasks. | ||
The committee also maintains a continuous exchange with ontology developers | ||
through GitHub. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# The Open Energy Family Community | ||
|
||
The Open Energy Family is developed by researchers from | ||
various institutions in different research projects. | ||
This open development approach ensures that the framework continues | ||
to evolve beyond the duration of individual projects. | ||
As a result, the Open Energy Family has fostered a vibrant community of | ||
researchers and users, including interested individuals and employees from companies. | ||
|
||
While there is often significant overlap between the groups of researchers | ||
and users, it is still relevant to distinguish between those who develop the | ||
framework and those who use it. | ||
This is especially true when it comes to understanding how users collaborate | ||
in the development process. To facilitate this, the community is subdivided | ||
based on their roles and responsibilities, allowing for greater clarity and | ||
coordination. | ||
|
||
Overall, this collaborative approach to development and community-building has | ||
been a critical factor in the success of the Open Energy Family. By encouraging | ||
participation from a diverse range of stakeholders, the framework has been able | ||
to evolve and adapt to the changing needs of the energy research community. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
# Knowlage transfer | ||
|
||
Tutorials and Training Course |