# sktime community meeting notes

###### tags: `sktime`

Character limit reached in this doc, new document:
https://hackmd.io/W0pXd_AoSt-V9m7ZsrxpWQ

# sktime community meeting notes 2024-11-12

**Date:**
12/11/2024, 4:30pm UTC

**Attendees:** FK, FH, MR, UO

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. review of actions

* action UO: post on core dev channel to get input on best time for dev days 2025 and long advance planning to enable visa process timelines, see if there are candiates for conferences or internal conference

* action UO: proposal/process document on handling sktime funds via fiscal host GC.OS
* UO would like to meet with tax advisor in Germany
* proposes next two weeks
* action FK - get in contact to set this up
* Fk action - meeting with tax advisor

* action FK - add various admin content to repos
* elections results to elections repo
* PSF grant allocated/committed to grant page
* 2023 financial statements by UO to community-org

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* action MR: reach out to Ryuta Yoshimatsu

* FHN/FK - meeting for video editing & live streams

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year

* tracking KR - distance university
* question: how to continue this? KR not on council
* action MR: reach out to KR to see how to proceed with this

* action on MR: reach out to JS, BH, KR & core devs to ask if they want to continue being observers

* action MR: setting up events calendar - gmail

* FK: action, copy over Northampton contract draft to council discord channel

* FK: action to post explanation on engagement opportunities (study group etc) in council channel plus slides/brochure

* action on FK: set up governance working group - GC.OS, sktime, umbrella

4. reminder ongoing votes

5. collaborations and requests

* CodePeak IIT Guwahati, Patna

6. forecasting course

7. Conferences

* Warsaw python summit
* showcase at pydata NYC by Schneider Electric

8. AOB

## Notes

1. Review of agenda

2. Review of minutes

3. review of actions

* action UO: post on core dev channel to get input on best time for dev days 2025 and long advance planning to enable visa process timelines, see if there are candiates for conferences or internal conference
* track

* action UO: proposal/process document on handling sktime funds via fiscal host GC.OS
* UO would like to meet with tax advisor in Germany
* proposes next two weeks
* action FK - get in contact to set this up
* FK action - meeting with tax advisor
* FK: issue is we have no tax advisor yet (the contractual setup is not yet clear) - WIP from FK
* UO: should be done by end of year?
* track

* action FK - add various admin content to repos
* elections results to elections repo
* track
* PSF grant allocated/committed to grant page
* done
* 2023 financial statements by UO to community-org
* track

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* action MR: reach out to Ryuta Yoshimatsu
* MR: got ok, not set up date yet
* action FK: pin template for talk

* FHN/FK - meeting for video editing & live streams
* FK: FHN was there but no one else, did not go through - alt is connecting FHN with contributor that has a YT channel
* action FK: follow up on contributors that were interested in helping with video editing

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year
* FK: done, emailed sent with CC to sktime email

* tracking KR - distance university
* question: how to continue this? KR not on council
* action MR: reach out to KR to see how to proceed with this
* MR: asked but no teply, trac

* action on MR: reach out to JS, BH, KR & core devs to ask if they want to continue being observers
* MR: JS replied wanted to step down, KR no reply, did not reach out to BH & core devs, track

* action MR: setting up events calendar - gmail
* track

* FK: action, copy over Northampton contract draft to council discord channel
* FK: track

* FK: action to post explanation on engagement opportunities (study group etc) in council channel plus slides/brochure
* posted - also on webpage
* https://gc-os-ai.github.io/consulting

* action on FK: set up governance working group - GC.OS, sktime, umbrella
* to be scheduled, track

4. reminder ongoing votes
* Vote on open chanel, closes tomorrow
* Core-dev vote mentee from GCOS, closes in 4d

5. collaborations and requests

* CodePeak IIT Guwahati, Patna
* FK: student club, sent info on how it works, also a marketing event & merch & sponsorship for interviwing for roles
* FK: ask is for 400$ - required for participation or only merch?
* FK: more info in thread on CC
* FK: startd Dec 5th
* MR: if 400$ is for participation, unsure if to go through if it can be skipped would be ok
* action FK: ask if 400$ is participation or merch?

6. forecasting course
* FK: Evolution is tracked in hackmd - suggestion by member of working group is to record a marketing video for the course - draft proposal for review in CC channel - should be done?
* MR: other courses that are successful do not have a video, is it really required? I think it is maybe not, also not a lot of money in treasury - leaning to maybe not, should be convinced otherwise
* FK: current funds come from GSOC mainly
* track - should be put up for decision, 1 week to review material and evaluate if someone wants to propose it officially

7. Conferences

* Warsaw python summit
* FK: invitation for talk, virtual & in-person
* action FK: ask in dev channel about participation in Polish conf
* showcase at pydata NYC by Schneider Electric
* FK: reach out to presenter to see if they want
* Pydata global: have not heard from them yet

8. AOB

# sktime community meeting notes 2024-10-29

**Date:**
29/10/2024, 4:30pm UTC

**Attendees:** FHN, FK, UO, MR (joined during "review actions")
(MR excused late due to daylight saving time switch on previous week-end)

**Minuting:** FK

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. review of actions

* tracking KR - distance university
* question: how to continue this? KR not on council
* action MR: reach out to KR to see how to proceed with this

* action FK - add various admin content to repos
* elections results to elections repo
* PSF grant allocated/committed to grant page
* 2023 financial statements by UO to community-org

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* FK: written to some authors, half Nov but still missing slots
* action MR: reach out to Ryuta Yoshimatsu

* action MR: setting up events calendar - gmail

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year

* action UO: post on core dev channel to get input on best time for dev days 2025 and long advance planning to enable visa process timelines, see if there are candiates for conferences or internal conference

* action UO: proposal/process document on handling sktime funds via fiscal host GC.OS

* action on MR: reach out to JS, BH, KR to ask if they want to continue being observers

4. collaborations and requests

* Northampton open source course - contract and contract revision
* Waterloo Type 1 Diabetes

5. package transfer & maintenance - pykalman

6. conference updates

* pydata global 2024 submission

7. longer-term setup - governance design

8. AOB

## Notes

1. Review of agenda

looks good; moved MR actions to the end as he will be late

2. Review of minutes

UO: no comments; MR not present; auto-approve date is Nov 5

3. review of actions

* action UO: post on core dev channel to get input on best time for dev days 2025 and long advance planning to enable visa process timelines, see if there are candiates for conferences or internal conference
* not done yet, track

* action UO: proposal/process document on handling sktime funds via fiscal host GC.OS
* UO would like to meet with tax advisor in Germany
* proposes next two weeks
* action FK - get in contact to set this up
* UO proposed next steps
* to share draft on discord
* then discuss draft
* then meeting with tax advisor

* action FK - add various admin content to repos
* elections results to elections repo
* PSF grant allocated/committed to grant page
* 2023 financial statements by UO to community-org
* not done that, will do

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* FK: written to some authors, half Nov but still missing slots
* Arindam Jati Dec 6 - TinyTimeMixer
* action MR: reach out to Ryuta Yoshimatsu
* reached out couple days ago, no reply yet

* FHN comment: if talks happen, often hard to follow for people who have scheduling conflicts or incompatible time zoes, should we livestream on youtube or share videos there
* FK: good idea, have tried to recruit community members to do video cutting
* problem is, discord does not offer a recording option
* FK have been recording past events with consent of presenters and audience, but recordings are messy and need cutting
* 3 volunteers in a discord thread
* FHN: let's do livestream on discord! discord allows that
* FK: did not know that!! could you show hot it works? perhaps even running meeutps?
* FHN: can show separately
* FK: let's schedule a test session then
* FHN: Nov 4, 16 UTC
* FK: can see if we can invite volunteers for video cutting or running meetup
* FK: might have clash, FHN is ok anytime after
* FK will check with calendar and let FHN knoew

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year
* not done, will do

* tracking KR - distance university
* question: how to continue this? KR not on council
* action MR: reach out to KR to see how to proceed with this
* not done, will to

* action on MR: reach out to JS, BH, KR to ask if they want to continue being observers
* not done, will to

* action MR: setting up events calendar - gmail
* not done, will to

4. collaborations and requests

* Northampton open source course - contract and contract revision
* university has given support/consent
* with AI society
* first contract draft: had liability clause without limitation of liabilities
* new contract draft which looks fine
* MR: have not seen this, did not look in gmail
* FK: action, copy over to council discord channel (will look there anyway)
* Waterloo Type 1 Diabetes
* organized by society
* 20 students (out of which 4 senior) working on data with a company Gluroo on various learning tasks related T1D
* want to use sktime nad contribute back to sktime, sub-group of ca 5 software engineering (CS) students
* started last week
* FK committed to mentor on project management as well as methodology
* FK does not think there are contractual or IP implications, since collaboration will stay in "permissive license" space, and will add to sktime code base
* no contracts have been signed, no NDA etc, or will need to be signed
* collaborative group meets after meet-ups on Fri

* MR: Electrolux - there may be interest organizing a data driven modelling competition plus contribution to sktime, kaggle style. Could be win-win if run directly by package used (sktime)
* FHN: things this is interesting, should explore how to set up framework that is attractive for students
* FK: similar to study groups (data or european study groups) - block week event, ran by FK at UK/Turing institute
* MR: was thinking of async, competition framework similar to kaggle; "intense" feels more appealing
* FK: study groups were framed as collaborative hackathon
* open to explore either setup
* MR: suggest to discuss particulars, interested about short thing
* FK: action to post explanation in council channel plus slides/brochure

5. package transfer & maintenance - pykalman

* ceased being active ca a year ago
* multiple forks emerged, unclear status
* ultimately forked into `sktime` for security concerns
* owners did not reply for >6 months
* FK requested PEP 541 transfer
* now `pypi` maintainer was checking on the thread
* this unblocked the situation
* package now transferred to FK in first instance
* two options: restore package and fold the sktime vendor library back; or sundown package and move users to sktime fork
* FK thinks restoring the original package would be better for users and the more "solid" alternative
* discussion opened in core dev channel
* FK thinks positive development, allows to reconverge the multiple forks into one package
* MR: we need umbrella governance idea, more and more packages
* need to think about this
* FK: it is on today's agenda :-) point 7

6. conference updates

* pydata global 2024 submission
* joint skchange/sktime - primarily skchange to pydata global
* in collaboration with NR and Martin Tveten

7. longer-term setup - governance design

* FK: need to get to a plan to get this sorted - there are some short-term issues and mid-term
* MR: question about umbrella structures vs individual package maintenance, e.g., sktime
* with an umbrella, each project could have its own governance
* FK: complexity-capacity trade-off, the more "layers" there are, the more people, admin capacity, bureaucracy
* might be wise to not scale complexity faster than the total number of people who are actually doing admin
* MR: we should think about extensibility of infrastructure of new joiner projects, who wlil want to retain their own governance
* cannot impose sktime governance on all new projects
* assume there are already one maintainer or a group forming a council for new projects
* FK: you are right, we have a few projects who want to join and where this might be a question for them
* FK: who drives this to completion? volunteers?
* MR: reservations about own availability
* FHN: new and lack of governance experience, but would be interested to participate
* UO: hopes we can get a resident administrator for these kind of tasks - umbrella is growing, complexity as well
* need funding structure for this
* current sktime council should be gov working group, also on behalf of GC.OS
* FK: makes sense, happy to drive, will expect and try also to pull in wider community (core devs)
* MR: we should try to timebox end of 2024
* UO: agrees, new year good pacing to implement
* action on FK to think about framing, setup, planning

8. AOB
9

# sktime community meeting notes 2024-10-22

**Date:**
22/10/2024, 4:30pm UTC

**Attendees:** FK, MR, UO
(FHN excused/absent)

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. review of actions

* tracking KR - distance university
* question: how to continue this? KR not on council
* action MR: reach out to KR to see how to proceed with this

* action FK - elections comms pack
* done, elections over
* action FK: results details to elections repo

* action FK: move budget to community-org repository
* track

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* FK: written to some authors, half Nov but still missing slots
* action MR: reach out to Ryuta Yoshimatsu

* action FK: setting up events calendar - gmail
* not done, track
* action MR: take this action from FK

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year
* UO: new org enables visa application and unlocks funds for external (and even internal) events - FK agrees, great idea
* action UO: post on core dev channel to get input on this idea, see if there are candiates for conferences or internal conference

4. some short-term actions to discuss

* handling incoming funds
* FK: new tax exemption - now confirmed due to incorporation as non profit. Requirement on budgets for in/out - asks UO about details on accounting
* UO: fiscal sponsorship a la OCE - since its non-profit it is a "project" based accounting which accumulates assets.
* FK: suggestions for doing this practically?
* action UO: will prepare some doc about this
* FK: GSOC funds issue due to asking security questions which he did not set - currently trying to solve this
* action FK: progress scipy & ODSC payments
* council observers -> async decision
* FK: reconfirm observers
* MR: ask existing first? - FK agrees
* FK: sequencing: existing > vote > rules > core dev
* MR: sequencing: existing > vote > core dev > rules
* FK agrees with MR approach
* action on MR: reach out to JS, BH, KR to ask if they want to continue being observers

5. suggested decisions to table async - partly reserved

6. AOB

## Notes

# sktime community meeting notes 2024-10-15

**Date:**
15/10/2024, 4:30pm UTC

**Attendees:** FK, MR, FH (Felix Hirwa), BH, Julian Fong (JF), PP (Pranav Prajapati)

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Inauguration - Welcome new council members, introductions

2. Valediction - Thanks to council members stepping down

3. handover dossier walkthrough (partially reserved)

4. planning for short-term actions arising

5. AOB

## Notes

## Agenda

1. Inauguration - Welcome new council members, introductions

2. Valediction - Thanks to council members stepping down

3. handover dossier walkthrough (partially reserved)
* FK: rundown of handover pack:
* Incorporation in Germany - legal entity coverage for grants & funds etc - still open how the org interactics with sktime and the other OS landscape
* Revenue - donation pipeline through incorporation & course development
* Engagement. - vacant seats for 3 remaining council & how to increase engagement for admin tasks
* OS and competing landscape - sktime is the market leader but also tthe only one not comercially/enterprise backed
* Visibility & PR - particularly social media
* Short term items in the handover pack:
* Incorporation - usage of org for incomming funds - idea is use accounts of the org to reduce feeds from OC (Open Collective)
* Reconfirmation of concil observers - part of the council but not full council members (e.g. Jana, Benedikt)
* Forecasting course on Maven: structure changes
* Treasurer: compiling budgets - role needs to be confirmed
* Mid term issues in handover pack:
* Elections framework - handling of vacant seats and approach for filling those seats in the period between elections
* pytorch forecasting

4. planning for short-term actions arising
* FK: topics that need immediate decision - makes sense to give some time for consideration of actions, current meeting can be considered more of a intro meeting - MR, FH agree
* action CC: extra meeting next week

5. AOB

# sktime community meeting notes 2024-10-01

**Date:**
01/10/2024, 4:30pm UTC

**Attendees:** MR, FK (elections committee)

## Agenda

1. Elections ongoing, discussion of any actions

2. Planning council handover, date for handover

3. AOB

Other items deferred until Oct 8 and after

## Notes

1. Elections ongoing, discussion of any actions

* discussing corner cases
* MR: what if low votes or no votes, tie breaking
* FK: algorithm seems robust
* in current case, less applicants than seats
* tie breaking may be necessary
* discussion of options - seniority (hours on project), or casting a lot
* agree - casting a lot in case of ties
* FK: another "low sample" corner case could arise as follows:
* all candidates with votes eliminated by seat n, n>2
* "preference ordering" too short
* "top n" for seat n would solve this issue, but too late for this round - to be discussed for next elections
* tie breaking at least leads to result

2. Planning council handover, date for handover

* MR: Oct 8 for meeting may be too early and is off-schedule
* FK: how about compiling documents and sharing early, then meeting on Oct 15 with past & future council?
* agree - Oct 15 for next meeting
* MR: handover, onboarding docs
* existing thread with collected items
* https://discord.com/channels/1075852648688930887/1100140983854829711/1286404499019272315
* action FK - compile handover dossier, guide

3. AOB
* FK: noticed discrepancy between election process document and readme
* readme states there are 3 seats with 3 years, 2 seats with 2 years, 2 with 1 years
* statutes state there are 2 seats with 3 years, 3 with 2 years, 2 with 1 years
* MR: pros/cons can be made for either, but we need to pick one
* FK: readme version gives more power to current council, because the difference is in seat 3. "no detriment" argument, applied to electorate (not hurting the electorate), would indicate we should go with statues version
* FK: another argument for statutes, this is the referred-to "ground truth" document in multiple places
* FK: what are the arguments in favour of the readme version?
* FK: readme is more "visible" version
* FK: "no detriment" argument applied to whoever gains seat 3, going with statutes version would hurt person in seat 3
* MR: thinks "ground truth" argument is strongest
* FK: agrees, this is the strongest formal argument
* MR: although not too string, it is clea rcut
* agreed - statutes version counts, i.e., 2 seats with 3 years, 3 seats with 2 years, 2 seats with 1 years
* for 4 candidates, that means 2 seats with 3 years and 2 with 2 each

# sktime community meeting notes 2024-09-17

**Date:**
17/09/2024, 4:30pm UTC

**Attendees:** MR, FK, UO, BH, FS

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. welcome & Q/A with sktime council and Business Park Ehingen/Donau representatives

4. review of actions

* tracking KR - distance university

* action FK - elections comms pack
* candidate form and pack
* sent out, done
* next: candidate statements

* action FK: move budget to community-org repository

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* ongoing - Sep, Oct slots
* Sep 20 - Simon Blanke, hyperactive
* Oct 4 - Martin Tveten, skchange
* Continue to track

* action FK: setting up events calendar - gmail
* not done, track

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year
* publish committed/allocated on grant page

5. FK - financials, use of gGmbH incorporated structures?

* sponsored status for sktime?
* no 8 or 10% cut as for OCE
* incoming funds from ODSC and scipy 2024
* leave existing funds on OCE
* suggest: handle one-off until full structures are in place?

6. MR - elections planning update
* encouraging eligible candidates
* comms pack

7. AOB

## Notes

1. Review of agenda
* 3rd Sept minutes auto approved

2. Review of minutes

3. welcome & Q/A with sktime council and Business Park Ehingen/Donau (BPED) representatives
* Florian Schraepler
* FK: Office of the mayor & BPED made press statement about incorportation to be (not registered yet ETA end on current week) - transfer of intial funds is what is holding up finishing the process
* FK: Office space & physical address (for legal entity/transfer assets/chariatable funds) provided
* FK: Relation between German entity and tech org to be defined after elections - outcome of elections 2nd week of october
* FK: notes how quickly the process came through
* FS: notes willingess to further speed up the process by digitalization of docs
* FK: newspaper wrote about the story - opportunity to capture the attention
* FK: Sept 24 event is public and local stakeholders will attend - had publicity from linedin & newspapers
* FK: encompass broader landscape of ML/AI is key for growth of the org

4. review of actions

* tracking KR - distance university
* KR not here, keep tracking

* action FK - elections comms pack
* candidate form and pack
* sent out, done
* next: candidate statements
* FK: sent out candidate comms pack - next is collect statements - only after Sept 23

* action FK: move budget to community-org repository
* track

* action FK: moved minutes to repo

* tracking & action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* ongoing - Sep, Oct slots
* Sep 20 - Simon Blanke, hyperactive
* hyperactive 2nd largest optimization lib
* Oct 4 - Martin Tveten, skchange
* Continue to track

* action FK: setting up events calendar - gmail
* not done, track
* action FK: needs to check, there was a modification to it but potentially still not done

* action FK: PSF funds
* contact PSF and update with committed/allocated; that spend will move to next year
* publish committed/allocated on grant page
* track

5. FK - financials, use of gGmbH incorporated structures?
* sponsored status for sktime?
* no 8 or 10% cut as for OCE
* incoming funds from ODSC and scipy 2024
* leave existing funds on OCE
* suggest: handle one-off until full structures are in place?
* FK: now we have a bank account in german org it can be used - potential risk due to FK being only director and account owner no checks & balances
* FK: use new bank account to share with Sankalp for ODSC funds (avoids OCE cut)
* FK: probably should be a council decision
* MR: avoid wait by voting in current council, then define it as a handover item for new council
* action FK: put up for vote

6. MR - elections planning update
* encouraging eligible candidates
* comms pack
* action FK, MR: elections committee for draft up the list and send it over
* note: non-recipient does not mean uneligible formally, e.g., borderline cases may have to go through detail review

7. AOB
* MR: handover/onboarding/induction pack for new council - FK agrees
* action on everyone: what should go in the induction?
* action on MR: open a thread to discuss this

# sktime community meeting notes 2024-09-03

**Date:**
03/09/2024, 4:45pm UTC

**Attendees:** FK, KR, UO, MR

**Minuting:** MR, FK (in places where MR dropped out due to connection probs)

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track

* action FK - elections comms pack
* sent out
* next stage: candidate pack

* action UO: update financial budgets and statements and send to CC for review
* Action UO: add legal expenses
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1240360027899035648/1265304465179938829)
* FK: posted updated budget
* Action on all: review current version

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* ongoing - Sep, Oct slots

* action FK: setting up events calendar
* FK: discord calendar set but another calendar (google etc) should be also made. Linkedin and discord calendar can be substribed to now.
* still open - gmail

* action FK: funding for dev days
* FK: PSF have not come back since July 2nd. Visa related timelines are starting to get complicated, should be closed in ~week or people will not be able to travel.
* still open - reach out to them again

4. financials
* handling incoming payments
* scipy 2024
* PSF
* ODSC
* publishing the budget

5. update on conferences
* EuroSciPy, pycon PL, ODSC
* ODSC blogpost

6. reserved items

7. AOB

## Notes

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* KR: followed up: uni contact will talk to higher-ups, still tracking

* action FK - elections comms pack
* sent out
* next stage: candidate pack
* FK: open question: where & how & when to publish candidate statements?

* action UO: update financial budgets and statements and send to CC for review
* Action UO: add legal expenses
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1240360027899035648/1265304465179938829)
* FK: posted updated budget
* Action on all: review current version
* Done

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* ongoing - Sep, Oct slots
* Sep 13 -
* Sep 20 - Simon Blanke, hyperactive
* Oct 4 - Martin Tveten, skchange
* Continue to track

* action FK: setting up events calendar
* FK: discord calendar set but another calendar (google etc) should be also made. Linkedin and discord calendar can be substribed to now.
* still open - gmail
* not done, track

* action FK: funding for dev days
* FK: PSF have not come back since July 2nd. Visa related timelines are starting to get complicated, should be closed in ~week or people will not be able to travel.
* still open - reach out to them again
* update: was approved late July, ran call, and received funds via Open Collective (5000 USD) - but too late as people were unable to get visa. Only small fraction of what was committed was used. But application already mentioned visa timelines, so we can use the funds later for another community meetup
* action: need to summarize back to them via accountability email
* FK needs to do this since ran the call and funding admin - write email and show council for review
* MR: is deferring to next year ok?
* FK: should be, but need to communicate with them

4. financials
* handling incoming payments
* scipy 2024
* FK: problem with filling out tax forms, should be filled by OCE. OCE required alt contract to fill in forms; on short notice it was not accepted. Sankalp filled it and funds will be splitted 1/2, which he will transfer as donation. Waiting to recieve this half as donation to OCE.
* Action FK: forward emails on the above
* PSF
* FK: Donated and recieved via OCE, as per point above we need to fill in acountability report (not all was spent)
* ODSC
* FK: Payment depends on number of registrations, so payment is after the event.
* Publishing the budget
* MR: separate github repo?
* FK: visibility is poorer and all docs are inside community-org so maybe should still be there?
* MR: agree with higher visibility in community-org, UO agrees
* action FK: publish budget to new folder in community-org repo

5. update on conferences
* EuroSciPy, pycon PL, ODSC
* ODSC blogpost

6. elections next steps
* FK: Options
* 1) PR/issue to elections repo in github
* visibility can be modified but it will be there always so more open/transparent
* async time alignment
* 2) Submit via Google Forms, then we compile and release
* advantage to administratord of the process, give us advanced view of it. Responsability is on us to do this correctly
* all published at the same time
* decision: go with #1, FK, MR & UO agree

7. reserved items

8. AOB

# sktime community meeting notes 2024-08-06

**Date:**
06/08/2024, 4:30pm UTC

skipped due to holiday schedules. Next Sep 3

**Attendees:**

**Minuting:**

**Moderator:**

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track

* action FK - elections comms pack
* sent out
* next stage: candidate pack

* action UO: update financial budgets and statements and send to CC for review
* Action UO: add legal expenses
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1240360027899035648/1265304465179938829)
* FK: posted updated budget
* Action on all: review current version

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* ongoing - Sep, Oct slots

* action FK: setting up events calendar
* FK: discord calendar set but another calendar (google etc) should be also made. Linkedin and discord calendar can be substribed to now.
* still open - gmail

* action FK: funding for dev days
* FK: PSF have not come back since July 2nd. Visa related timelines are starting to get complicated, should be closed in ~week or people will not be able to travel.
* still open - reach out to them again

4. handling incoming payments
* scipy 2024
* PSF

5. update on conference planning
* EuroSciPy, pycon PL, ODSC
* ODSC blogpost

6. reserved items

7. AOB

## Notes

Holiday schedules and absences - skipped

# sktime community meeting notes 2024-07-23

**Date:**
23/07/2024, 4:30pm UTC

**Attendees:** FK, MR, UO

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* FK: KR not present, track

* action FK - elections comms pack
* FK: initial post with suggested timelines is posted for internal discussion
* https://discord.com/channels/1075852648688930887/1260273638201098320
* action - finalize

* action UO: update financial budgets and statements and send to CC for review
* Action UO: add legal expenses
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1240360027899035648/1265304465179938829)

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)

* action FK: funding for dev days

* action FK: setting up events calendar

* Action FK: check with different people re travel schedule for confs
* need full point below, 4

4. Events and presentations over summer
* debrief ISF 2024, scipy 2024
* ODSC blogpost
* dev days, travel
* Conferences (planned & submitted):
* euroscipy - Poland, Szczecin, Aug 26 - 30. Possible location for dev sprint (Aug 29, 30)
* pycon poland - Poland, Gliwice, Aug 29 - Sep 1
* ODSC Europe, London, Sep 5 - 6
* pycon India, Bengaluru, Sep 20 - 23 (not confirmed yet)
* pydata Paris, Sep 25 - 26
* GSoC mentors summit, California, Oct 2 - 3

5. reserved item

6. AOB

## Notes

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* FK: KR not present, track

* action FK - elections comms pack
* FK: initial post with suggested timelines is posted for internal discussion
* https://discord.com/channels/1075852648688930887/1260273638201098320
* action - finalize
* FK: PR not merged on MR comments (Feb 2024). Dates are now updated and based on timebox should be up when ready - ETA ~couple days.

* action UO: update financial budgets and statements and send to CC for review
* Action UO: add legal expenses
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1240360027899035648/1265304465179938829)
* FK: posted updated budget
* Action on all: review current version

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* FK: august slots filled; Ivan confirmed, person from Amazon also confirmed - probably can fill until ~September.

* action FK: setting up events calendar
* FK: discord calendar set but another calendar (google etc) should be also made. Linkedin and discord calendar can be substribed to now.
* still open - gmail

* action FK: funding for dev days
* FK: PSF have not come back since July 2nd. Visa related timelines are starting to get complicated, should be closed in ~week or people will not be able to travel.
* still open - reach out to them again
* if we do not get it this year, apply for next year now

* Action FK: check with different people re travel schedule for confs
* need full point below, 4
* FK: confirmation from previous conference plan
* Benedikt confirmed (as in last minutes)
* no reply from Kiril (personal absence)

4. Events and presentations over summer
* debrief ISF 2024, scipy 2024
* FK: ISF very positive overall. Academic community which sktime has not had relationship with. Opens new collab relationship. This Friday's talk is from py package dev. sktime as marketplace was enticing. Benedikt's talk well recieved and interesting & positive feedback
* scipy 2024
* FK: tutorial not well attended because LLM tutorial at same time; another tutorial (not given by us) used sktime, that was well attended!
* FK: 500 USD should be paid to us, but there is no admin info or email chain
* admin was handled by Sankalp Gilda
* FK: ran sprint on the weekend, good attendance! 6 different people contributed PR, mix of newcomers and very experienced coders
* ODSC blogpost
* action FK: first draft of blogpost
* dev days, travel
* Covered in action above re. funding status - also would require who is travelling
* Conferences (planned & submitted):
* euroscipy - Poland, Szczecin, Aug 26 - 30. Possible location for dev sprint (Aug 29, 30)
* pycon poland - Poland, Gliwice, Aug 29 - Sep 1
* ODSC Europe, London, Sep 5 - 6
* pycon India, Bengaluru, Sep 20 - 23 (not confirmed yet)
* FK: delays and moved deadlines, still waiting for confirmation
* pydata Paris, Sep 25 - 26
* GSoC mentors summit, California, Oct 2 - 3

5. reserved item

6. AOB

# sktime community meeting notes 2024-07-09

**Date:**
09/07/2024, 4:30pm UTC

**Attendees:** FK, MR, UO

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

* minutes of May 28 lost?
* Period for review closed (until June 25)

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track

* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)

* action MR: open thread on fundraising brainstorm

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)

* action FK: funding for dev days

4. Elections timelines, comms

5. Reserved item

6. Events and presentations over summer
* ODSC blogpost
* dev days, travel
* Conferences (planned & submitted):
* euroscipy - Poland, Szczecin, Aug 26 - 30. Possible location for dev sprint (Aug 29, 30)
* pycon poland - Poland, Gliwice, Aug 29 - Sep 1
* ODSC Europe, London, Sep 5 - 6
* pycon India, Bengaluru, Sep 20 - 23 (not confirmed yet)
* pydata Paris, Sep 25 - 26
* GSoC mentors summit, California, Oct 2 - 3

7. Maven course

8. FK - status update GSoC, mentoring

10. AOB

## Minutes

1. Review of agenda

2. Review of minutes
* FK: minutes of May 28
* still lost for, but completed by memory (see previous minutes)
* Action on all: until next meeting to review/add any comments
* FK: June 11th approved (default)

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* FK: KR not present, track

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track
* FK: initial post with suggested timelines is posted for internal discussion
* https://discord.com/channels/1075852648688930887/1260273638201098320

* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)
* FK: check if legal expenses added | UO: KR & other mentioned feedback - review period is over, so oficially closed then for review.
* Action UO: add legal expenses

* action MR: open thread on fundraising brainstorm
* MR: done

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* FK: some activity regarding invitations but too many, make a calendar? MR agrees | added to agenda for discussion

* action FK: funding for dev days
* FK: accepted for talk at euroscipy but not heard back for dev track - no reply from them yet. Assumption we at least get a sprint.
* FK: Submitted application to python software foundation (PSF), which has been recieved and some questions asked from them. Currently beeing considered for 5000$ for travel and lodging for mentees and attendees. Defined as open to apply, similar to previous years. Expectation from PSF on us to run a fair application process.
* MR: timelines? FK: ~couple of weeks, but good that already had quick response with questions

4. Elections timelines, comms
* FK: first post drafted and up for internal review. Timelines suggested in post. Time to raise awareness & ensure that mentees have finished so they have time to decide adn get engages without feeling pressured. Opening after mentoring period (last mentee finishes Aug 21st), but announcing before. Potentially can add voter registration earlier. Potential options:
* Option 1:
* from now: comms starts
* Sep 8 - candidate registration open
* Sep 22 - candidate registration deadline
* **voter registration same as candidate registration**
* until Oct 1 - candidate statements
* Oct 1 - 7 election period
* results announced Oct 10
* Option 2:
* **open voter registration already now**
* voter registration deadline Sep 22
* rest same
* Option 3 etc
* sth else
* e.g., move to Sep 1?
* too close to dev days, logistic overload?
* UO: do we have voter registration tech in place?
* FK: similar form (user registration), can be used as template
* action FK: voter registration form
* MR: suggests option 2 as a way for menteed to commit to voting while still working on their project and motivated
* Action on all: timebox to end of this week for review Friday 12

5. Reserved item

6. Events and presentations over summer
* ODSC blogpost
* FK: what should be the topic? Environment integration is the suggestion, as reson for "why sktime"
* dev days, travel
* FK: encourage coredevs / CC members to travel, would require visa
* UO: issues with US travel, ~6 mo lead time (though unrelated as dev days is PL)
* FK: ~2 weeks visa for mentees based in India, so should be easy
* Conferences (planned & submitted):
* euroscipy - Poland, Szczecin, Aug 26 - 30. Possible location for dev sprint (Aug 29, 30)
* FK: Benedikt can attend this one but not pycon as has to be back in Germany by ~31st
* pycon poland - Poland, Gliwice, Aug 29 - Sep 1
* FK: clash between PL conferences
* FK: Kiril could attend but unclear
* FK: try to get presentation on last day
* ODSC Europe, London, Sep 5 - 6
* FK: Sankalp can attend as in EU in Sept. Option for ODSC and/or Paris, not india
* FK: almost certain will attend
* pycon India, Bengaluru, Sep 20 - 23 (not confirmed yet)
* FK: anirban cannot attend, maybe mentor?
* pydata Paris, Sep 25 - 26
* FK: Benedikt mentioned he could attend and also is close on the topic, could attend
* GSoC mentors summit, California, Oct 2 - 3
* FK: will attend, but cannot attend 2 previous
* managing meetup invitations, calendar

* FK: possible solution to the puzzle?
* try to get Gliwice presentation on Sep 1
* FK leads ODSC Europe
* BH leads Paris pydata
* FK travels to California via India
* euroscipy for dev days
* MR: would leave pycon poland unclear
* FK: can travel from Szczecin to Gliwice, not far
* assuming presentation is on Sep 1
* or check with Kiril, Gliwice (relatively) close to Bulgaria (1-2k km)
* Action FK: check if the above works
* action FK - meetup events calendar on gmail/google calendar

7. Maven course
* on track for now
* check in closer to the date with FK, Sankalp

8. FK - status update GSoC, mentoring
* FK: midterm evals this week, all on tracks. Ensuring correct mentor assignments and submitting evals on time is key as funding is dependant on this.

10. AOB

# sktime community meeting notes 2024-06-11

**Date:**
11/06/2024, 4:30pm UTC

**Attendees:** FK, KR, MR, BH, UO, SG (from 5pm)

**Minuting:** MR

**Moderator:** KR

## Agenda

1. Review of agenda

2. Review of minutes

* minutes of May 28 lost?
* hackmd was empty
* last revertable state was agenda without minutes
* FK added based on memory
* for review until June 25

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track

* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)

* action MR: open thread on fundraising brainstorm

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)

* action FK: funding for dev days

4. scheduling

- internal social - repeat?
- roadmap planning 2024-2025 - June 21 still good?

5. FK - status update GSoC, mentoring

6. FK - updates on conferences, workshops

* accepted: pycon PL (workshop, intro) -> FK
* accepted: pydata Paris (talk: FM) -> Benedikt (needs to check with MB), possibly FK
* submitted: pycon IN (mentees: Felix, Pranav)

7. FK, SG - fundraising updates (reserved)

8. AOB

## Minutes

1. Review of agenda

2. Review of minutes

* minutes of May 28 lost?
* hackmd was empty
* last revertable state was agenda without minutes
* FK added based on memory
* for review until June 25
* Action UO, MR to review

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* KR: university did come back but had doubts on how to structure - wanted to include other dpts/colleagues | KR replied ok to this - waiting for next reply - track

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track
* FK: should be completed today and will share for review - timelines should be out soon but 1 mo buffer before actual activities.

* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)
* action on all: still in review period

* action MR: open thread on fundraising brainstorm
* MR: will close today

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)
* KR: contact with tech incubator in Rome where there is an option to co-present - will start a thread on this
* MR: contacted Ivan

* action FK: funding for dev days
* FK: not done, track

4. scheduling

- internal social - repeat?
* FK: June 3rd - well recieved but not all atended and one FK and UO attended.
* FK: June 21 8 UTC (early) as option? See below - conclusion is not social on 21st
- roadmap planning 2024-2025 - June 21 still good?
* Round table for availability:
* BH: will not be there but is ok with not rescheduling as wants mentees to be involved and this is a good slot for them
* FK: will have time on the full day
* KR: will be able to attend and is ok with not rescheduling
* MR: hard but not impossible to attend due to still being working hours
* UO: similar to MR, roadmap happens in working hours but will be able to at least attend partially
* Conclusion is keep roadmap planning but do not have social

5. FK - status update GSoC, mentoring
* FK: Menteed onboarded and started to code, some churn but some newcommers have filled the slots - all going well
* FK: admin email related to evaluations, ~3 weeks time

6. FK - updates on conferences, workshops

* accepted: pycon PL (workshop, intro) -> FK
* FK: planning to travel to PL
* KR: dates?
* FK: Aug 29 - Sept 1
* FK: should think of backup or copresenter
* KR: maybe? Track
* BH: Does this intersect with euroscipy?
* FK: Yes! Also, both in Poland
* BH: could be backup due to being in Berlin during that time if it is needed
* FK, KR: Maybe not needed but good b/c of unforseen issues (sickness) and how exhaustive a workshop can be
* accepted: pydata Paris (talk: FM) -> Benedikt (needs to check with MB), possibly FK
* FK: talk accepted (foundation models topic)
* BH: needs to check with employer
* FK: dates Sept 25 - 26
* FK: talk official confirmed after email lost and got back from orgs
* submitted: pycon IN (mentees: Felix, Pranav)
* FK: potentially be able to go if talk accepted, will
* FK - Others for which we are waiting: forecasting for social good, ODSC, Northampton
* FK: euroscipy dates Aug 26 - 30 (in Poland)

7. FK, SG - fundraising updates (reserved)

8. AOB

# sktime community meeting notes 2024-05-28

**Date:**
28/05/2024, 4:30pm UTC

**Attendees:** FK, MR, UO

**Minuting:** FK

**Moderator:** MR

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action FK open vote on automatic approval of minutes in decision channel
* FK: vote is open and ongoing

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track

* reserved action (see [CC channel](https://discord.com/channels/1075852648688930887/1084417014166212618/1242124782972174347))
* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)

* action MR: open thread on fundraising brainstorm

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)

* action FK: funding for dev days

4. scheduling

- internal social
- roadmap planning 2024-2025 - proposed June 21

5. reminder: ongoing votes and discussions (reserved)

6. FK - status update GSoC
- bonding period and onboarding ongoing
- Google/OCE transfer status
- mentors summit registration, wait list

7. UO - budgets and statements for review
* [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)

8. FK - updates on conferences, workshops

- scipy 2024
- ISF (International Symposium of Forecasters) 2024
- pending invitations - ODSC, DS for social good, Northampton
- pending applications (pycons)
- upcoming deadlines (euroscipy)

9. FK - academic publications strategy

10. summer programme planning

- experienced contributor onboarding
- mentee social (virtual?)
- developer days
- option - if materializes: euroscipy maintainer track
- date: late Aug, due to mentee availability?

11. fundraising updates

12. AOB

## Minutes

1. Review of agenda

2. Review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action FK open vote on automatic approval of minutes in decision channel
* FK: vote is open and ongoing

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* onboarding still ongoing (end of May), track

* reserved action (see [CC channel](https://discord.com/channels/1075852648688930887/1084417014166212618/1242124782972174347))
* action UO: update financial budgets and statements and send to CC for review
* done, here, please review prior to publication - [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)

* action MR: open thread on fundraising brainstorm

* action on all: think about people that could be invited for talk in meetup (research talk, present package, etc)

* action FK: funding for dev days

4. scheduling

- internal social
- suggestion FK: together with mentees
- all agree: good suggestion
- planned for tech meeting June 3

- roadmap planning 2024-2025 - proposed June 21
- FK, on reasons: conference round trip starts week after; would be good to have roadmap finalized or a good draft; June 7, 14 occupied with meetup talks already
- June 21 agreed

5. reminder: ongoing votes and discussions (reserved)

6. FK - status update GSoC
- bonding period and onboarding ongoing
- complete, official coding starts May 27
- mentees onboarded to regular meets, standups
- Google/OCE transfer status
- UO sent email, received and confirmed
- mentors summit registration, wait list

7. UO - budgets and statements for review
* [CC channel link](https://discord.com/channels/1075852648688930887/1084417014166212618/1240360027899035648)
* UO will add legal expenses
* any other updates, please comment

8. FK - updates on conferences, workshops

- scipy 2024
- ISF (International Symposium of Forecasters) 2024
- pending invitations - ODSC, DS for social good, Northampton
- pending applications (pycons)
- upcoming deadlines (euroscipy)

9. FK - academic publications strategy
- opening internal channel to discuss and coordinate

10. summer programme planning

- experienced contributor onboarding
- planned for May 21
- mentee social (virtual?)
- combined with internal social
- developer days
- option - if materializes: euroscipy maintainer track
- date: late Aug, due to mentee availability?

11. fundraising updates
- reserved

12. AOB

# sktime community meeting notes 2024-05-07

**Date:**
07/05/2024, 4:00pm UTC

**Attendees:** FK, MR, SG (Sankalp Gilda), UO (5pm)

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. review of minutes

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action FK open vote on automatic approval of minutes in decision channel

* action FK - meet-up slot poll (re time zone)
* action FK: action on repeating the poll
* update: done based on mentees, mentee induction meeting, time moves to 1pm UTC

* action FK - elections comms pack
* reserved action

4. FK - update on GSoC, summer mentorships
* 5 fully funded stipends
* 10 mentees (part time, avg 15 hrs/week)
* 3700 USD compensation (donated), UO in contact with OCE

5. FK - update on conferences, workshops
* scipy 2024 - workshop accepted
* international symposion on forecasting - talk accepted
* ODSC 2024 - invitation to give 2h workshop
* upcoming deadlines and submissions (pycon, pydata, euroscipy)

6. Sankalp Gilda - introduction, events, reserved items

7. financial document drafts by UO - next steps
* budget sheet template
* management report template
* FK - this was ready, should we finalize and publish?

8. fundraising

9. socials, events
* meet-ups talks outreach
* developer days planning

10. AOB

## Minutes

1. Review of agenda

2. review of minutes
- April 9: FK changed time due to UTC confusion, otherwise fine

3. Review of actions

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action FK open vote on automatic approval of minutes in decision channel
* FK: Track as busy with GSOC

* action FK - meet-up slot poll (re time zone)
* action FK: action on repeating the poll
* update: done based on mentees, mentee induction meeting, time moves to 1pm UTC
* FK: brought up in meetign with mentees - base this on mentees' location? May come out differently. Tentatively to 1PM UTC as seen above
* action MR: look at this in CC
* action FK: post again
* FK: believes 1PM slot works well with US/Asia so tentatively keep if over the summer, MR agrees

* action FK - elections comms pack
* FK: track - busy with gsoc, but this is prio after onboarding
* reserved action

4. FK - update on GSoC, summer mentorships
* 5 fully funded stipends
* 10 mentees (part time, avg 15 hrs/week)
* 3700 USD compensation (donated), UO in contact with OCE
* FK: mentor convention: org admin gets to travel to this event, FK will probably go
* UO: OpenCollective europe - postive reply

5. FK - update on conferences, workshops
* scipy 2024 - workshop accepted
* FK: ~1000$ to sktime
* international symposion on forecasting - talk accepted
* FK: ~600$ to ISF
* ODSC 2024 - invitation to give 2h workshop
* FK: replied to email with ask about compensation; no reply yet - seems like an open invite
* upcoming deadlines and submissions (pycon, pydata, euroscipy)
* FK: PyCon Poland proposal will be sent, Euroscipy (DL: end of may)

6. Sankalp Gilda - introduction, events, reserved items

7. financial document drafts by UO - next steps
* budget sheet template
* management report template
* FK: almost complete except for GSOC income
* UO: added GSOC income (for november)
* FK: we should be in the 2nd cohort?
* UO: will put it in August as projection (move from November), will add it soon
* action UO: update and send to CC
* action on all: review once posted

8. Fundraising
* action MR: open thread on fundraising brainstorm

9. socials, events
* FK: date for internal social? Tuesday? MR, FK agree
* meet-ups talks outreach
* FK: options for May and June still open
* action on all: think about people that could be invited to talk
* developer days planning
* FK: Friday event for mentee onboading; suggestion for more dev focused event
* FK: dev days? July or August are good options - also prefered in poll
* FK: python software foundation for funds?
* MR: tried before?
* FK: no, but could be feasible
* action FK: think about asking for the above

10. AOB

# sktime community meeting notes 2024-04-09

**Date:**
09/04/2024, 4:00pm UTC

**Attendees:** MR, KR, FK, JS

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes
* minutes from Feb 28 5pm meeting continuation missing?

3. Review of actions

Tracking

* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* KR: spoke to head at Berlin, sounded excited about colab; wanted to even go more national; send email after talk but have not heard back; will call again soon - track
* action Jana - open vote on automatic approval of minutes in decision channel

* action FK - meet-up slot poll (re time zone)
* done, current slot got most votes, so nothing changes
* reserved action

4. FK - update on GSoC

* large contributor influx
* +400 on discord in 2 months
* increased PR review load
* interviews underway, update on selection process
* short-term events (meet-up schedule, intro to contrib)

5. FK - summer programme planning

* meet-ups - more pre-planning agendas, presentations?
* some volunteers from events poll
* FK: inviting speakers
* summer developer sprint planning
* workstream onboarding events, project management
* socials

6. update from elections working group meeting

* discussing timelines

7. reserved items

8. FK - update on funding, fundraising

* current applications
* discussing next steps?

9. financial document drafts by UO - next steps
* budget sheet template
* management report template

10. AOB

## Minutes

1. Review of agenda
- MR: bump elections before fundraising

2. Review of minutes
* minutes from Feb 28 5pm meeting continuation missing?
* FK: UO, KR attended the carried-over session, are there meeting notes?
* KR: maybe - need to check
* action KR, UO: check if you have local version of meeting, if will be considered not lost

3. Review of actions

Tracking

* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* FK: suggests to drop due to long pause
* KR, JS: agree, action is dropped
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action ~~Jana~~ FK- open vote on automatic approval of minutes in decision channel
* JS: suggest shifting action due to permissions requirements
* FK: takes action
* action FK - meet-up slot poll (re time zone)
* done, current slot got most votes, so nothing changes
* MR asks if current time was defined so voters were "primed" to select the current time, FK shows the current date undiscoled so no
* FK: suggest repeating due to large influx, MR agrees
* action FK: action on repeating the poll
* reserved action

4. FK - update on GSoC
* large contributor influx
* +400 on discord in 2 months
* increased PR review load
* FK: since end of Feb (announcement of GSOC acceptance) large inflow in discord & PRs in Github. PR are from beginners, which require more time for supervision
* interviews underway, update on selection process
* FK: April 2 was DL for proposal submission - April 24 is DL for ranking to google
* FK: short on interviewers at the moment and co-mentors are appreciated
* FK: interviews in April 15-16
* KR, MR can attend as interviewers
* FK will send emailsnd
* short-term events (meet-up schedule, intro to contrib)
* FK: 3 works strems 5 people on each - requires some PM, particularly at the beginning

5. FK - summer programme planning

* meet-ups - more pre-planning agendas, presentations?
* some volunteers from events poll
* FK: inviting speakers
* FK: proposals to host or speak on meetups is appreciated
* FK: low number of female respondants to forms, probably good idea to highlight women leading OS
* summer developer sprint planning
* workstream onboarding events, project management
* socials
* FK: proposal for social, structure or unstructures?
* MR, JS agree on unstructured
* FK: when?
* All agree in 3 weeks due to interviews beginning next week

9. update from elections working group meeting
* discussing timelines
* FK: converged on process, ready to run elections at the moments. Repo `elections` is up and everyone should have access. Conclude interview process first (end of April). Mid May is good aim.
* FK: good engagement process for tech side, but there is a gap for how to get people engaged in community tasks. Follow the tech model? Ideas welcome
* FK: more hands on process but also as we are not incorporated it is not crucial that all goes 100% well. We should adhere to structure but it will be a test run
* actions FK: send messages comms pack and docs about procedure

7. reserved items

6. FK - update on funding, fundraising

* current applications
* discussing next steps?

8. financial document drafts by UO - next steps
* budget sheet template
* management report template

10. AOB

# sktime community meeting notes 2024-03-12

Low attendance due to sickness, professional workload, and/or holidays.

After text message discussion on discord:
CC meetings paused until this changes, likely after easter holidays.

# sktime community meeting notes 2024-02-27

**Date:**
27/02/2024, 5:00pm UTC

**Attendees:** FK, MR, KR, UO

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

Tracking

* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action Jana - open vote on automatic approval of minutes in decision channel

4. FK update - events poll, sponsored projects and workstreams

* possible attendance today, and Q&A for interested contributors

5. update on GSoC

* accepted, timelines
* large contributor influx
* short-term events (meet-up schedule, intro to contrib)

6. reserved items

7. financial document drafts by UO - review, discussion
* budget sheet template
* management report template

8. update from elections working group meeting

9. FK - if time: preliminary results from events poll (still ongoing)

10. AOB

## Minutes

1. Review of agenda
- FK: move financial after reserve
- MR: agrees

2. Review of minutes

3. Review of actions

Tracking

* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* action Jana - open vote on automatic approval of minutes in decision channel

- FK: skip all actions, still tracking

4. FK update - events poll, sponsored projects and workstreams

* possible attendance today, and Q&A for interested contributors
* FK: forms online in landing page and linkedin (with GSoC)
* MR: how many responses?
* FK: ~12
* FK: introduction, show & tell - these are main interests from responses
* FK: people that are not involved would like to help out, including org an in person event.
* FK: sponsored project just 1 day ago, already have responses. Dealine align with intership

5. update on GSoC

* accepted, timelines
* large contributor influx
* short-term events (meet-up schedule, intro to contrib)
* FK: few framework projects, ~80 people in latest week
* FK: freq questions about how to get started with contributing, we could run an intro to this? MR agrees
* FK: large portion of new joiners from India but time-zone for them in not convenient - set up a poll on time? MR agrees
* action: set up poll for intro meeting time -> then next meetups would be at the suggested time - A good option is noon UTC (12-15) as it works for both US and India

6. reserved items

7. financial document drafts by UO - review, discussion
* budget sheet template
* management report template

moved to 5pm UTC Feb 28

8. update from elections working group meeting

9. FK - if time: preliminary results from events poll (still ongoing)

10. AOB

# sktime community meeting notes 2024-02-13

**Date:**
13/02/2024, 5:00pm UTC

**Attendees:** FK, JS, KR (left after 10min), MR, UO

**Minuting:** FK

**Moderator:** MR

## Agenda
1. Review of agenda

2. Review of minutes

3. Review of actions
* action Jana - open vote on automatic approval of minutes in decision channel
* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* Action on everyone: Brainstorm on events for summer internships, post interesting links in CC
* FK, MR: no engagement on this yet - track
* Action on everyone: look at repository with draft for elections and give feedback
* action MR: review FK comments on feedback
* Action on FK: create a poll for interests of community regarding events
* FK - as posted

4. Conference/event planning
* scipy 2024
* https://www.scipy2024.scipy.org/
* option to submit 4h workshop - pays 1k USD
* talk with tsbootstrap
* GSoC update
* events poll

5. reserved

6. UO: finances

7. MR: community events

8. AOB

## Notes
1. Review of agenda
* inconsistency of items between agenda above and posted in channel - fixed

2. Review of minutes
* skipped (?)

3. Review of actions
* action Jana - open vote on automatic approval of minutes in decision channel
* not done, todo
* unclear how to do with the easypoll bot
* Fk can show after meeting
* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* contact initiated, next steps follow - track
* Action on everyone: Brainstorm on events for summer internships, post interesting links in CC
* FK, MR: no engagement on this yet - track
* Action on everyone: look at repository with draft for elections and give feedback
* action MR: review FK comments on feedback
* done, few open points
* FK - how about a sync meeting to wrap up?
* MR - tomorrow (Feb 14 evening) would be ok
* FK - ok, 5pm UTC
* Action on FK: create a poll for interests of community regarding events
* FK - as posted
* https://discord.com/channels/1075852648688930887/1084417014166212618/1205185769782644746
* (on internal discord channel)
* gmail form link is not working
* FK share participant link
* presentation
* discussion points:
* should be anonymous (consensus)
* MR - how to send it
* FK: discord announcements, linkedin
* MR - timing
* FK: soon

4. Conference/event planning
* scipy 2024
* https://www.scipy2024.scipy.org/
* option to submit 4h workshop - pays 1k USD
* talk with tsbootstrap
* FK: check if they have travel funding
* action to track!
* GSoC update
* submitted
* under review
* summer projects updated in last week's dev meeting
* events poll
* discussed above

5. reserved

6. UO: finances
* ongoing, draft to be shared for review in council channel
* MR: we should track fundraising
* FK: proposed next steps? perhaps based on projections?
* MR: yes, also needs thinking about where fundraising sits - workstream, treasurer role
* MR: has done fundraising in previous jobs. Someone ought to coordinate, and we should collect excel with options
* UO: first need to define revenue targets for 2024, based on that
* e.g., number of interns, define set of events and required support. plan with that and communicate to potential funders
* all agree

7. MR: community events
* next step is send out comms re poll
* then follow through, track
* MR also wants to check in personal network about interest

8. AOB

# sktime community meeting notes 2024-01-30

**Date:**
30/01/2024, 5:00pm UTC

**Attendees:** FK, MR, UO, KR

**Minuting:** MR

**Moderator:** FK

## Agenda
1. Review of agenda

2. Review of minutes

3. Review of actions

* action Jana - open vote on automatic approval of minutes in decision channel
* action FK re legal review prepare contact draft and share internally (also end of this week)
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* Action on everyone: Brainstorm on events for summer interships, post intersting links in CC
* Action on everyone: look at repository with draft for elections and give feedback
* Action on MR: create a poll for interests of community regarding events

4. Conference/event planning
* pydata
* GSoC

5. FK: reserved item

6. UO: finances

7. MR: community events

8. AOB

## Minutes
1. Review of agenda

2. Review of minutes
* 2024-01-16
* All agree with current minutes

3. Review of actions

* action Jana - open vote on automatic approval of minutes in decision channel
* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: suggests pausing for now - track
* action KR: send email to distance university, check if sktime session are feasible - track for next time
* Action on everyone: Brainstorm on events for summer internships, post interesting links in CC
* FK, MR: no engagement on this yet - track
* Action on everyone: look at repository with draft for elections and give feedback
* FK: replied to MR
* action MR: review FK comments on feedback
* Action on MR: create a poll for interests of community regarding events
* MR: currently high workload so did not prioritize
* FK: suggests to help in early steps (draft)

4. Conference/event planning
* pydata
* FK: reviews ongoing for Berlin
* scipy 2024
* FK: Tacoma - Sankalp lead re tsbootstrap-sktimw intgration
* GSoC
* FK: deadline for application 06-Feb, review of projects and mentors would be appreciated
* MR: What does being mentor entail?
* FK: no strict reqs - weekly engagements, reply within 3 days, daily standup (recommended)
* MR: Project proposal guidelines, example of sktime project?
* FK: links to Q above
* https://summerofcode.withgoogle.com/how-it-works
* https://github.com/sktime/mentoring
* past projects: https://github.com/sktime/mentoring/blob/main/internships/projects_2023.md
* action MR: look at docs and suggest GSOC project
* MR: duration?
* FK: 12 weeks
* MR: GSoC drives engagement, we should apply for sure
* FK: chances are ok, but less than before
* KR: skeptical on chances
* UO: start date?
* FK: timeline below
* https://developers.google.com/open-source/gsoc/timeline
* MR: who decides on applicant?
* FK: we send list, Google decides

5. FK: reserved item

6. UO: finances
* UO: presents quickbook accounting balance for sktime

7. MR: community events

8. AOB

# sktime community meeting notes 2024-01-16

**Date:**
16/01/2024, 5:00pm UTC

**Attendees:** KR, FK, MR (until 5:30), UO, JS

**Minuting:** JS

**Moderator:** KR

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* action to track: idea of internal calendar
* (general idea to track)
* Jana suggestion: automatic minutes approval after 1 month?
* action Jana - open vote on this in decision channel

* action JS - summarize governance next steps in private channel

* action FK re legal review prepare contact draft and share internally (also end of this week)

* FK will reach out again

* action FK - contact JB re commitments of treasurer role

* action KR: send email to distace university, check if sktime session are feasible - track for next time

4. Conference/event planning
* pydata
* scipy
* sklearn sprint

5. reserved item - FK

6. next steps gov - JS, FK
* reserved item
* elections org

7. summer internships - application deadlines

8. MR: community events

10. AOB

## Notes

Actions
Action on MR: create a poll for intersts of community regarding events
Action on everyone: look at repository with draft for elections and give feedback
Action on FK re legal review prepare contact draft and share internally (also end of this week)
Action KR: give feedback regarding answer from distance university if there is an answer
Action on everyone: Brainstorm on events for summer interships, post intersting links in CC

-> Other reserved actions in the reserved channel

1. Review of agenda

* accepted

2. Review of minutes

* Minutes accepted

3. Review of actions

* action to track: idea of internal calendar
* (general idea to track)
* Jana suggestion: automatic minutes approval after 1 month?
* action Jana - open vote on this in decision channel
* Thread opened, poll will be created by JS with help of FK
* action JS - summarize governance next steps in private channel
* Done

* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK will reach out again

* action FK - contact JB re commitments of treasurer role
* JB did not reply, no answer for 2 months
* reserved item later

* action KR: send email to distance university, check if sktime session are feasible - track for next time
* Email written by KR, waiting for feedback
* Will track further

4. Conference/event planning
* pydata
* scipy
* sklearn sprint

5. reserved item - FK
n/a

6. next steps gov - JS, FK
* reserved item
* elections org
* async
* https://github.com/sktime/elections
* discussions are converging, aim for go live in few weeks
* Marc has commented in detail

Action on everyone: look at repository with draft and give feedback

7. summer internships - application deadlines

* FK: Update, applications open in next weeks, only one council meeting for Google Summer of Code are; use the application documents we had in the years before and apply
* FK: timelines
* https://summerofcode.withgoogle.com/programs/2024 (Feb 6)
* https://fellowship.mlh.io/programs/open-source
* https://developers.google.com/season-of-docs/docs/timeline (Mar 24)
* KR: offers to help with interviews (in May, late April)
* Brainstorming on other events we can apply to

Action on everyone: Brainstorm on events, post intersting links in CC

* JS: Idea to post actions to Discord in #actions

8. MR: community events

* idea from MR: idea to have more engagement, provide different opportunities
* MR would offer to plan and post, needs a bit more help, short term: create a draft for communication on it, form to get involved, move it forward; open for input
* Type of event? Option 1: in-person Option 2: online
* FK: in-person event funding is important, Python coding events through Python foundation or EuroSciPy -> follow up with an action on these
* MR: create a poll
* JS: sign up for random virtual coffee

Action on MR: create a poll for intersts of community
Action on FK: follow up on inperson meeting

10. AOB

n/a

# sktime community meeting notes 2023-12-19

**Date:**
19/12/2023, 5:00pm UTC

**Attendees:** FK, MR, JS, UO, KR (from 5:20)

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* delayed publication vote
* open until Dec 12

* action FK re legal review prepare contact draft and share internally (also end of this week)
* shared, and also sent
* track for response

* action to track: idea of internal calendar
* (general idea to track)

4. Conference planning update
* pydata global debrief
* sklearn sprint

5. next steps gov - JS, FK

7. MR: brainstorm community events

8. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)

10. AOB

## Minutes

1. Review of agenda

2. Review of minutes

* 3 sets to review (see below): MR, JS, FK, agree to minutes, nothing to add
* https://github.com/sktime/community-org/blob/main/community_council/previous_meetings/20231031-meeting.md
* https://github.com/sktime/community-org/blob/main/community_council/previous_meetings/20231121-meeting.md
* https://github.com/sktime/community-org/blob/main/community_council/previous_meetings/20231205-meeting.md

* Jana suggestion: automatica approval after 1 month?
* MR, FK - good idea
* action Jana - open vote on this in decision channel

3. Review of actions
* delayed publication vote
* open until Dec 12
* closed with agreenent
* FK: where to document this?
* Appendix to minutes, see below

* action FK re legal review prepare contact draft and share internally (also end of this week)
* shared, and also sent
* Still no response: continue tracking
* FK: follow up now? JS agrees, FK will reach out again

* action to track: idea of internal calendar
* (general idea to track)
* Drop above action as of 21-11 minutes

4. Conference/event update
* pydata global debrief
* FK: both presentation went well.
* Tutorial was 2nd highest attendance (~200 participants) - FK had to cover some point but did not get there in time, Benedikt covered and went well
* "sktime saga": good feedback from other projects in similar situations, in particular sklearn group
* sklearn sprint
* FK: meet with sklearn people in Paris and idea of joint sprint came up, sometime in spring. Located somewhere in France; unformied but great proposal from them. Technical integration (skbase - design, skproba - not covered by sklearn) would be a good topic to cover.
* Details/logistics unclear at the moment, continue to track
* KR asks about details of scikit-learn incorporation; FK on their incorporation model (see link below):
* https://scikit-learn.fondation-inria.fr/home/ - OS project, non-profit/IRO sub-incorpoation (FK - afaik); new body "probabl" - co-owned for-profit; relation between two currently in shaping
* FK: sklearn (Goupil) suggested connect with Gael Varoquaux

5. next steps gov - JS, FK
(reserved)

action JS - summarize in private channel

6. MR: brainstorm community events

* moved to developer meeting (Dec 22 @ 4PM ~30 mins)

7. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)

* action FK - contact JB re commitments of role

8. AOB
* KR: idea about sktime sessions at Distance University in Germany - good demographic as students are eager to break into the industry
* action KR: send email to check if sktime session are feasible - track for next time

next meeting Jan 9

#### appendix A - delayed publication

Background
Sometimes decisions within the sktime project involve sensitive information that necessitates confidentiality for a specific period. However, the decision should always be made public to enforce transparency. To address this, we propose the implementation of a mechanism for decision making that allows for the delayed announcement of decisions. This balances the need for transparency with the requirement to protect time-sensitive information.

Proposed Procedure
Initial Public Notification
When a reserved decision is under consideration, an initial public announcement will be made in the meeting notes of the council.

Confidential Decision Period
During the confidential decision period, details of the decision, including sensitive information, will be discussed and documented in the minutes. This period allows for thorough consideration without immediate public disclosure.

Scheduled Announcement
These minutes will include a clearly defined time when the decision will be made public and the reason for this period.

Public Disclosure
Upon reaching the scheduled announcement time, all relevant information and minutes pertaining to the decision will be made public. If the minutes still contain sensitive information that is not time bound (e.g. personal sensitive data) this can be redacted. These redactions should be kept as a minimum and should not be used to obscure details of the decision process.

# sktime community meeting notes 2023-12-05

**Date:**
05/12/2023, 5:00pm UTC

**Attendees:** FK, UO, KR

**Minuting:** FK

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* delayed publication vote
* https://github.com/sktime/community-org/issues/56
* action MR: put this up for voting, write final form

* Action UO: reach out to content creators to update code to recent main
* Joanna Lenczuk
* FK proposed to bring in to repo to test continuously
* suggested action UO: PR to repo once notebook is done
* action FK after that: review & integrate to CI

* action FK re legal review prepare contact draft and share internally (also end of this week)

* action to track: idea of internal calendar
* (general idea to track)

4. Elections
* timelines, feedback
* reminder

5. Conference planning update
* pydata NY debrief
* pydata global

7. MR: brainstorm community events?

8. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)

10. AOB

## Minutes

1. Review of agenda

* shortened where relevant people not in attendance
* FK: some points copied over by accident, updated

2. Review of minutes

* FK suggest, push until majority attends
* agreed

3. Review of actions

* delayed publication vote
* https://github.com/sktime/community-org/issues/56
* action MR: put this up for voting, write final
* this is now up, https://discord.com/channels/1075852648688930887/1173921014284025886/
* at usual timelines, open until Dec 12

* Action UO: reach out to content creators to update code to recent main
* Joanna Lenczuk
* FK proposed to bring in to repo to test continuously
* suggested action UO: PR to repo once notebook is done
* action FK after that: review & integrate to CI
* done by UO, PR is now open for review by others

* action FK re legal review prepare contact draft and share internally (also end of this week)
* shared, and also sent
* track for response

* action to track: idea of internal calendar
* (general idea to track)

4. Elections
* timelines, feedback
* MR put feedback in writing on branch of private repo (not present)
* Kiril: agrees with moving or extending timelines to Jan due to holidays
* strong opinion
* also with MR specific timeline
* FK also agrees (see discord)
* Ugo - also agrees with MR proposed timeline
* FK - will then redraft and propose updated timeline given current material
* FK: any feedback on content, material, other than timeline?
* KR: no
* UO: suggest more clarifications on which council positions (length of tenure) in different groups
* action FK - update material, reshare, check confirmations for plan
* reminder to all, any further comments in repo
* agreed on updated timeline
* no major comments regarding material from those present

5. Conference planning update
* pydata NY debrief
* FK: copy-paste error, already done last time?
* FK: no, Jonathan was not here, keep until here
* pydata global - update by FK
* currently finishing prep for tutorial on Dec 6
* talk rehearsal needs to be moved due to clash with tutorial rehearsals, and MR not here (planned originally for after this meeting) - FK suggest early Thu, Dec 7
* KR: when is rehearsal tomorrow, Dec 6?
* FK: for tutorial, 9am UTC discord
* for talk, not scheduled, propose Thu Dec 7
* UO: where is rehearsal?
* FK: feel free to join, rehearsal is in public discord channel, meet-up channel
* another one in 30min, around 6pm today

7. MR: brainstorm community events

* FK: MR not present, need to move to next time MR is here

8. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)

* FK: JB not present, need to move

10. AOB

* FK - next meeting, holidays?
* regular day, Dec 19, ok with all

# sktime community meeting notes 2023-11-21

**Date:**
21/11/2023, 5:00pm UTC

**Attendees:** FK, KR, MR, OU, BH

**Minuting:** MR

**Moderator:** FK

## Agenda

1. Review of agenda

2. Review of minutes

3. Review of actions

* delayed publication draft
* https://github.com/sktime/community-org/issues/56
* action MR: put this up for voting, write final form

* Action UO: reach out to content creators to update code to recent main
* Joanna Lenczuk
* FK proposed to bring in to repo to test continuously
* suggested action UO: PR to repo once notebook is done
* action FK after that: review & integrate to CI

* action FK re legal review prepare contact draft and share internally (also end of this week)

* action to track: idea of internal calendar
* (general idea to track)

4. Elections
* comms draft
* sklearn meeting

5. Conference planning update

* pydata global

7. MR: brainstorm community events?

8. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)

9. sklearn meeting

10. AOB

## Minutes

1. Review of agenda
* All ok

2. Review of minutes
* 2023-10-31: MR, FK, KR: ok

3. Review of actions

* delayed publication draft
* https://github.com/sktime/community-org/issues/56
* action MR: Done on draft, waiting for ok to go to vote
* https://discord.com/channels/1075852648688930887/1101599945842237491/1173921014284025886 on council discord
* action MR: put up for vote

* Action UO: reach out to content creators to update code to recent main
* UO: Joanna replied, info in discord
* UO: getting material (notebooks) ready by early December
* FK: move Joanna's nb to sktime repo?
* action UO: PR to add nb
* drop action on reach out to Alexandra Amidon
* action FK re legal review prepare contact draft and share internally (also end of this week)
* FK: continued actions on reserved channels

* action to track: idea of internal calendar
* (general idea to track)
* drop tracking, will add to community events (if many events would make sense)

4. Elections
* comms draft
* FK: next steps? Technical points like links, visibility, linkedin post, etc
* FK: any remaining open questions or concerns?
* MR: concern on engagement, but not necesarily related to any changes
* FK: keep open for 1/2 weeks, sync with pydata global?
* KR, BH, MR: agree
* action FK: *increasingly annoying* reminders to look into this
* action FK: plan timeline; communicate arround pydata, vote middle dec, key to catch announcements still on working time

5. Conference planning update
* pydata NY debrief: described in PM but not for everyone
* action JB: track
* pydata global
* FK: 2 slots (fully virtual)
* 1: Generic tutorial & new features
* Contacted core devs for tutorials, should be easy due to enough material
* 2: sktime saga talk
* Review material meeting: 28th Nov, 5th Dec (@5PM UTC)
* action FK: draft before above dates

6. Reserved item

7. MR: brainstorm community events?
* Not covered as meeting over time, track for next meeting

8. FK: JB treasurer check-in?
* 2023 statements
* fundraising
* 2024 projections (if any)
* Not covered as meeting over time, track for next meeting

9. sklearn meeting
* Not covered as meeting over time, track for next meeting

10. AOB