Discussion - The future of CHAOSS Metrics and Models Working Group

Aperta
#724 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
20/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Ambito
content

Direzione di ricerca

Leggi il Google Document collegato, che tratta le riunioni della community del 22 e del 29 aprile, e confrontalo con i commenti evidenziati in questa issue. Determina se il gruppo ha concordato una direzione, un ambito, un approccio per le riunioni e un responsabile; completato significa documentare un percorso deciso e la responsabilità.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

From the community meeting on April 29th and April 22nd
https://docs.google.com/document/d/1PMDWc6xMe0fNE7shxTK5_HE_ykRBG5w55_Zx5hvzsEY/edit?tab=t.0

The Metrics and Models Work Group (now one group) has seen a decrease in participation

Questions:

  • Is Metric and Model work still important - would anyone like to lead this working group?
  • Should the group adopt different meeting processes or modalities?
  • Is the meeting time is confusing? (10 am US Central every other Thursday)
  • Is it at an inconvenient time?
  • Is the scope not clear?

Highlighted Comments From the Notes:

  • Metrics and Metrics Models meetings are very lightly attended --
  • Bi-weekly cadence isn’t currently serving the purpose.
  • Context WGs are trying to bring the metrics we have already defined forward in meaningful ways; this is where the interest seems to lie now
  • With this group, there seems to be a blocker with people actually doing the work and getting them written. We don’t seem to have the larger foundation of people who can work on this.
  • Earlier scope: we reviewed metrics that were in progress to finalize wording, we had active working sessions to create new metrics -- All this is contingent on someone with the time and drive to work on these
  • If the people with the ideas are not able to work on the metric, it creates an odd dynamic and adds to the list of work for others to do -- We really need that person to drive the work on the metric
  • Some metrics can be written in one session, with one session for review
  • Whoever is driving the metric could be the facilitator; if there is nothing to work on maybe there isn’t a meeting more ad hoc with a singular purpose. But this would be a little more legwork for that person
  • We talked about listening to what the new metric ideas are and encouraging folks to lead their development (liaisons)-- Maybe liaisons can listen and when a new metric is identified, we have a set of community members interested in defining that can work on it at an ad hoc meeting, invite the people who need the metric -- Probably a lot of people who identify a metric that needs to happen because of the work they’re doing in another working group
  • Let’s put these metrics on the agenda at the working group meetings, show the template, begin the work within that working group and be more deliberate about putting it on the agenda -- The metrics development group then becomes facilitators for helping the working groups create the metrics when needed (and we can’t provide coverage for all working groups right from the beginning).
  • Maybe the working group chooses a metric liaison to also drive the metric development and help balance the work for the facilitators
  • If we do move to an alternate modality, Lack of participation in the working group might still be a problem. We could still keep meeting to check in and share what we’re working on
Lingua principale
JavaScript
Stelle
109
Fork
189
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di chaoss/community

Tutte le issue di chaoss/community

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.