openscd / .community Goto Github PK

Issue here: https://github.com/lf-energy/tac/issues/new?assignees=&labels=1-new-project-wg&projects=&template=02-new-project-proposal.yml&title=New+Project+Proposal+-+PROJECT+NAME

WIKI for collaboration here: https://wiki.lfenergy.org/pages/resumedraft.action?draftId=81779345&draftShareId=e4ab7d7b-d37f-4177-80f5-ea72ccaceb06&

tbd.

As a member of the openscd organization interested in the Open SCD (Next) effort I would like to count on an organization-wide project that allows for following the progress of issues in all the repositories of the organization related to the migration

Acceptance criteria:

• Public for everyone
• Add them to .github as generic github action for the entire organization (https://docs.github.com/en/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization)

We have the following columns:

• Todo
• In Progress
• Done

We opened a PROS and CONS document on Google Docs containing the pros and cons and bullet points on why community is important:

https://docs.google.com/document/d/1lAFiq5eg6V9RWGBpii__rZ-7qRu1vMhqM3gsax0w7tc/edit

The discussion with stakeholders is still ongoing.

MeetUp, mainly OpenSCD/CoMPAS discussing documentation, future and some practical work

• what sessions do we have & scope
• how do we work with goals and how we refine the goals
• how do we collaborate
• how do we make decisions
• what communication channels do we have & how do we communicate with each other
• where do we store what type of information

The purpose of a Dojo is to improve our productive time on the projects.
The idea behind a Dojo is to gain expertise and experience through deliberate practice, (sometimes led by a Guide).
The result is an increase in quality and at the same time decreased time of solving problems.

• Target Audience
• Banner
• Posts LinkedIn etc.

As a contributor
I would like to know what it takes to get community growth and what services are needed to support the community
So I understand the relations between them

https://svelte.dev/
Tamás works a lot with Svelte and would like to present how they use it at SprintEins. @trusz can you describe, for the team, what you would like to explore and communicate with this workshop?

We currently use:

Wiki (end-user documentation)
Github issues (in every repositories)
Github discussions (every repositories)
ADR's
LF energy Confluence
Readme.md (in every repository)
Youtube tutorials

Acceptance critria:
Proposal: Where to locate what
Disable unwanted documentation locations

For the LF Energy proposal we need a Mission description. Reading through the history.md and a few other files I can read OpenSCD was started to overcome challenges, but it is difficult to describe the mission. I came up with:

Mission Statement
To provide a user-friendly, collaborative and standardized way of editing Substation Configuration Language (SCL) files

There are surely better ways to describe the Mission Statement

There is a shared Gdoc on how the OpenSCD community looks like here: https://docs.google.com/document/d/12EYdQzMPY1ocDtNMzURrwoXZ_zMUX7p-AS0R4N0fm2I/edit?pli=1

This describes the team, roles, and partners

As a community member I would like to have an overview of how the community is established, so I can reach out to people.

Acceptance criteria: Finished roles and responsibilities to the WIKI page

@Sander3003 can you elaborate or close?

The community needs a CoC to describe guidelines for expected behaviour.

A code of conduct is a document that establishes expectations for behavior for your project’s participants. Adopting, and enforcing, a code of conduct can help create a positive social atmosphere for your community.

The current CoC is too much focused on enforcement. We will go for another one that is more focused on motivational aspects.

In progress as #1278

The idea is start technical development with a technical kick-off.

How do we make discussions in OpenSCD?

For communication and attracting a wider community we should have a website that is not only technical, but communicates in human-readable terms what the project is about.

We already registered openscd.org, currently only containing a linktree instance with the most important links.

Initial thought here: https://docs.google.com/document/d/12EYdQzMPY1ocDtNMzURrwoXZ_zMUX7p-AS0R4N0fm2I/edit?pli=1

There were already suggestions on workshops around Svelte, Asciidoc and a number of other ideas.

What is the progress to go from idea to implementation ready issue?

Over the course of the past months, the OpenSCD team, consisting of product owners and developers of the various companies working on OpenSCD, have been discussing joining LF Energy. There are many upsides to joining LF Energy, like using their infrastructure, design resources, marketing etc. We have made sure in our discussions that everyone understands that LF Energy does not take any specific role in the project itself, but is just there to facilitate. Now we are at the point where all signs are green, and we would also like to confirm our intention with the community, so this is saved for generations to come ;)

A simple YES will do to confirm, but there is no-one stopping you to adding additional remarks in the form of nice words.

SAY YES HERE ⇩