/
How To Run Implementers (draft)

How To Run Implementers (draft)

Dec 10, 2024

Congratulations! You're running Implementers now. Here's what you need to know.

Your Role

You are the "Convener" of Implementers. You can find a definition of what a convener does here: SIG convener tasks

You are responsible for:

  • Soliciting agenda topics

  • Setting up the meeting agendas

  • Publicizing the meetings

  • Leading/facilitating the meetings

  • Deciding if/when we cancel meetings

  • Taking and posting notes from our meetings

  • Attending Product Council once a month to report on the group's activities

  • Keeping an eye on the #folio-implementers channel

  • Finding your replacement when your year-long term is up. (Start asking in August)

This group is also responsible for:

Traditionally we have also:

  • Held a coworking session during each bugfest, to help novice testers get comfortable

  • Taken requests from other SIGs and POs seeking to connect with implementing libraries

That said, this group is pure Calvinball, you will by design never have a consistent group of attendees (and if you do, not for long), so mostly just have fun and change whatever you want above.

Some logistics

Time Commitment

This role will take (???) hours per week. A significant portion of that will be taking notes.

Term

The Implementers Convener serves for a calendar year. No one knows why, but it's nice to have new voices in the role, as so much is organizing content.

How To Plan Sessions

Implementers talks about whatever implementers wants to talk about. It's helpful for attendees to know what the sessions are in advance.

<<Go over step by step, and the agenda template.>>

 

For meetings with topics with speakers

  • Set the topic

  • Get any needed speakers (2-3 weeks in advance)

  • Announce the topic on relevant channels

  • Set up the agenda

    • Including resources and pre-reads

  • Send a reminder (at the end of our programming board meeting)

  • Run the meeting

  • Close out with the speakers

    • Say thank you, ask for slides, etc

  • Review and add in the AI notes

  • Create any documentation from the meeting (guides, tools, etc)

 

For working meetings

  • Set the topic

  • Announce the topic on relevant channels

  • Send out homework (A week before at the end of programming board, and also a reminder the DAY BEFORE)

  • Prep the agenda

  • Run the meeting

  • Review and add in the AI notes

  • Create any documentation from the meeting (guides, tools, etc)

 

Standing business for the board

  • CHECK IF THERE ARE PC NOTES TO ADD

 

 

 

Meetings you will want to attend

  • Product Council: once per month, you will need to attend product council to report on what Implementers is up to. It's typically the second Thursday of the month, but you will also see a post go up on #folio-product-council

  • Product Owners: You are not a product owner, but hearing what the product owners are talking about will help you immensely. You won't need to talk, just listen. There is a product owners channel–ask your predecessor or any product owner to add you.

  • FOLIO Forums (when they happen)

  • WOLFcon if possible

No one person can follow everything, but I'd recommend familiarizing yourself with the slack channels of the major SIGs. When you plan sessions, you'll want to make sure there isn't too much overlap, and you'll also want to cross-post relevant sessions in their channels. The big ones are:

<<List the big slack channels here>>

Previous Conveners

Try reaching out on slack if you need help.

  • Tara Barnett (current, 2023)

  • Ian Walls (2022)

  • ???

Random Questions

Q: Why is our wiki called COHORT2019?

A: Because Confluence makes it hard to change the space name. Originally, this group was meant to work in cohorts–there would have been a cohort 2019, 2020, etc. It did not work out that way–we've been a rolling group of attendees for some time. And yet, the name lives on.