Slack: Create a welcoming onboarding and introducing new channels
@Honyii ci sta già lavorando.
Dal 29/10/2026.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 44/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
-
- Lingua principale
- HTML
- Stelle
- 2
- Fork
- 0
- Merge medio
- 15h 17m
- PR unite (30g)
- 5
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Open-MBEE/opensysml.github.io
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 68/100
Open-MBEE/opensysml.github.io#20 · 1 commento ·
-
Difficoltà 3/5 Mezza giornata Idoneità per principianti 35/100
-
Repo naming conventions: Tier 1 GuidelineForse già presa @Honyii l’ha presa 18 giorni fa. Aperta
Open-MBEE/opensysml.github.io#17 · 1 assegnatario ·