Slack: Create a welcoming onboarding and introducing new channels
@Honyii arbeitet bereits daran.
Seit 29.10.2026.
Bewertung
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Anfängerfreundlichkeit
- 44/100
- Issue-Typ
- Feature
- Klarheit
- Größtenteils klar
- Aktivitätsstatus
- Aktiv
Rechercherichtung
Start by reviewing the Slack workspace settings and the onboarding and community channels described in the issue. Confirm the proposed welcome note, automatic #intros membership, community sharing and reading channels, and biweekly update with the project community; done means the onboarding steps and channel proposals have been agreed and put in place.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
The slack workspace is a great way to keep everyone informed with what we are building at OpenMBEE so creating a process where it's easy to get started is important.
To welcome new members
- Create a welcome note and publish
- Make the #intros channel active
- Sync with Chris to update the slack settings so @intros channel is added to the automatically added channel for new members.
- Ask the existing members to intro themselves in #intros so as to spark further intros.
New Channels & Ecosystem Experience
- Propose to add these two channels;
-
A channel where community members (personal/orgs) can share a link to their social post with the purpose for other community member to like, share, repost with the aim to amplify their post. This channel name can be #social-media/anything related.
-
A channel where community members can share their implementation of OpenSyml/related tools within OpenMBEE and OpenMBEE amplify it in their social pages. This channel name can be; #openmbee-community-builds; #openmbee-in-the-wild etc
- The implementation can be a tool, usecase or anything interesting and it should strongly be focused on any of the OpenMBEE project.
- There should be a public link for anyone to view; links e.g Github, website, etc.
-
A reading club channel, this channel should be informal and we can have a quarterly; "What are we reading" session/program from this.
-
A biweekly update on everything that has happened.
-
- Vorherrschende Sprache
- HTML
- Sterne
- 2
- Forks
- 0
- Ø Merge
- 15 Std. 17 Min.
- Gemergte PRs (30 T.)
- 5
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus Open-MBEE/opensysml.github.io
-
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 68/100
Open-MBEE/opensysml.github.io#20 · 1 Kommentar ·
-
Schwierigkeit 3/5 Ein halber Tag Anfängerfreundlichkeit 35/100
-
Repo naming conventions: Tier 1 GuidelineEvtl. vergeben @Honyii hat das vor 18 Tagen übernommen. Offen
Open-MBEE/opensysml.github.io#17 · 1 zugewiesene Person ·