---
# System prepended metadata

title: Community Team Meeting

---

# Community Team Meeting

**:calendar:** Apr 8, 2022

### :wave: Attendees

- [name=Guzal]
- [name=Lovkush]
- [name=Franz]
- [name=Lukasz]

### :pencil: Agenda
:::info
1. Review of [last meeting's md](https://github.com/sktime/community-org/blob/main/community_team/previous_meetings/20220401-meeting.md), review of actions
    - action FK: announce the dates on pyData
    - action GB: announce the dates on social media
    - action Lukasz: create a landing page on sktime.org to reference to mentorship (under Events?)
    - action GB: post a link with relevant GSoC info on Twitter
    - action FK: find and share any presentations related to onboarding days with LM and rest
    - action FK: share last year interview materials & panel org materials with LA (and rest)
    - action LA: PR to remove 'top three' distinction in information to candidates
    - action LA: organise interviews
    - action FK, MW, GB: ask NumFocus during the next CC meeting regarding the LinkedIn account for sktime
    - action FK: check with Tony why MW doesn't get the info@sktime.org emails
    - FK: I think it´s better if MW and TB just directly connect
        
3. **pyData Berlin**
    * 
5. GSoC
    * interview panels
4. **LinkedIn account for sktime**
    * revisit

4. **AOB**
:::

### :construction: Reference links
*relevant documents*
1. [Previous meeting's HackMD](https://github.com/sktime/community-org/blob/main/community_team/previous_meetings/20220401-meeting.md)
2. https://github.com/sktime/mentoring/blob/main/internships/gsoc2022.md


### Notes
1. Review of last meeting's md, review of actions
- on last meeting's hackmd: agreed
- action FK: announce the dates on pyData
    - pydata will be Apr 11, will annoucne proposed dates
    - May 25-27th for onboarding days
    - June 27 to July 1 for the dev-days
- action GB: announce the dates on social media
    - will do on Mon 11th
- action Lukasz: create a landing page on sktime.org to reference to mentorship (under Events?)
    - done, merged
- action GB: post a link with relevant GSoC info on Twitter
    - will do before Monday 11th
- action FK: find and share any presentations related to onboarding days with LM and rest
    - not done, will do
- action FK: share last year interview materials & panel org materials with LA (and rest)
    - done
- action LA: PR to remove 'top three' distinction in information to candidates
    - done
- action LA: organise interviews
    - in the process, see agenda
- action FK, MW, GB: ask NumFocus during the next CC meeting regarding the LinkedIn account for sktime
    - till next time, meeting is on Apr 19
- action FK: check with Tony why MW doesn't get the info@sktime.org emails
    - FK: I think it´s better if MW and TB just directly connect   
    - MW wanted to do this, check with MW nex time

2. **pyData Berlin**
    * updates
        * notebook for conf under development here:
            * https://github.com/sktime/sktime-tutorial-pydata-berlin-2022
            * look in the PR for prob forecasting -> feedback on PR directly
            * look in main for hierarchy_global -> feedback in issue

3. **GSoC**
* LA: need people to give feedback on draft proposals between 12th and 15th
  * people willing to do this are:
      * Franz
      * Guzal
      * Lukasz
      * Lovkush
* LA: need people to process sktime applications and proposals between 19th and ~22nd april
  * people willing to do this are:
      * Franz
      * Lovkush
      * Guzal
      * Lukasz
* LA: need people to conduct interviews between 25th april and 8th may
  * people willing to do this along with estimate of days/hours are:
      * Franz, 2 days
      * Lovkush, ? days. happy to put in time
      * Lukasz
      * Guzal, 1 week day and one weekend (if be), happy to devote one whole day but need to know in advance
* LA: what is maximum number of people we will mentor? maximum we will interview?
  * maximum for mentoring
      * fk: with peer to peer mechanisms, up to 10. More likely, 5.
      * gb: 2 co-mentee
      * lm: 4 or 5 co mentee
      * la: 2 co mentees
  * maximum for interview
* LA: need to decide what are the skills/attributes we are looking for. here is my current thoughts:
    * python
    * collaborative coding, i.e. can use git/github to make pull requests, can set up environment, can follow contributor guidelines, etc
    * data science/ml.
    * understanding of sktime
    * suitable / sensible project
    * comfort with english
    * soft skills: follows code of conduct, can give and receive feedback, motivated, organised
    * FK: we should avoid to deviate from what we already published on gsoc page.
        * ... but there's no harm in becoming more specific, e.g., in an email that spells things out
    * FK: requirements are implicit in what we already published.
    * GB: python says "you like python", but expectation should perhaps be along the lines of capability in addition?
        * FK: implicit in other sections and GSoC requirements
    * NOTE: make the requirements more explicit next time (like coding in python - what is required level? so that candidates don't have to guess)
        * agreed for 2023 or winter round
* creation of interview questions etc. - Lovkush is on it
    * what is best way of discussing this, given we do not want this to be public? maybe organise a separate meeting?
        * FK: yes, makes sense.
        * GB: agree

4. **LinkedIn account for sktime**
    * revisit next next Friday Apr 22nd


4. **AOB**



:question: Next meeting & planning
---
### date: Apr 15, 5 pm UK time

### TO-DO before next meeting:
- action FK: announce the dates on pyData
    - pydata will be Apr 11, will annoucne proposed dates
    - May 25-27th for onboarding days
    - June 27 to July 1 for the dev-days
- action FK: share sktime gmail access with LA (& check with CC whether this is ok)
- action GB: announce the dates on social media
    - will do on Mon 11th
- action GB: post a link with relevant GSoC info on Twitter
    - will do before Monday 11th
- action FK: find and share any presentations related to onboarding days with LM and rest
    - not done, will do
- action MW: contact tony about access to info@sktime email
- action all: review notebooks
    * https://github.com/sktime/sktime-tutorial-pydata-berlin-2022
    * look in the PR for prob forecasting -> feedback on PR directly
    * look in main for hierarchy_global -> feedback in issue
- action LA: organise meeting for interview questions
