sktime / sktime/mentoring

[MENTEE] Ryan Kuhns

Open
#2 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

mentoring
Dominant language
No language data
Stars
44
Forks
19
PR merge metrics
No merged PRs in 30d

Description

Mentee:
Ryan Kuhns (@RNKuhns and LinkedIn)

Mentor(s):
@mloning

Why did you join sktime's mentorship program?
To learn about contributing to opensource projects and of course to learn more about timeseries algorithms!

What topics are you working on?
I'm currently focused on adding additional forecasting performance metrics (https://github.com/alan-turing-institute/sktime/pull/672, https://github.com/alan-turing-institute/sktime/issues/712).

I've contributed to data processing previously (https://github.com/alan-turing-institute/sktime/pull/553).

What are your learning goals?

I'd like to learn more about the design/thought process of how to go from a desired timeseries pipeline and/or algorithm to code. My other goal is to contribute common economic forecasting functionality so I can use sktime for economic forecasting and forecast evaluation.

What's next for you after the mentorship program?

I'm still going through the mentoring program, but once it wraps up I'm hoping to use what I learned to continue contributing to sktime. I'd also like to use sktime's functionality in a couple research projects I'd like to start.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This issue is a mentorship introduction rather than a scoped coding task. Start with the linked forecasting-metrics pull request and issue to find the active work; no file, test, or completion criterion is provided here, so this issue itself has no defined contribution to complete.

Written by the indexing model from the issue text.

Assessment

Domain
developer-experience
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.