:wave: It's been a while since I've visited this ...
# dev-metaflow
e
๐Ÿ‘‹ It's been a while since I've visited this channel but curious to get a high-level understanding of the latest technical direction(s) that Metaflow would be taking over the next quarter? Thanks in advance. ๐Ÿ˜‡ Congrats on all the amazing work that has been ongoing - core convergence, metaflow bot, k8s, awslambda support and I'm sure so much more! ๐Ÿฅณ
๐Ÿ‘‹ 3
โœ… 1
d
Ravi, fancy seeing you here :). I havenโ€™t yet thought too much about next quarter for public features but we are planning now so hopefully more soon
๐Ÿ™Œ 1
e
I love this channel and all of our amazing community! Just wasn't sure what is the best way in which I can still contribute that my day job would allow. However, hopefully I can still stay (somewhat) subscribed and informed at least on the overall direction of the project and our offerings! ๐Ÿ˜…
s
I presented this deck earlier this week which showcases upcoming features that are backed by soon-to-be-merged PRs https://docs.google.com/presentation/d/1V2R-RFKCNQy4PK1HF_WIlFdNCA8apsJf25viQtjvBEU/edit#
๐Ÿ‘ 1
๐Ÿš€ 2
๐Ÿ™ 1
of course the list is not exhaustive - in particular the massive amount of work (mostly by @dry-beach-38304 ๐Ÿ™‡) that went into core convergence, datastore refactoring,
metaflow_custom
etc. is not featured, as it is less user-visible
d
Lol. My brothers say that I am a โ€œbasementโ€ kind of guy. Think IT crowd :). I like the basement :).
๐Ÿฆ‰ 1
๐Ÿ˜‚ 1
s
@early-motorcycle-1160 or anyone else who wants to consider contributing, you can take a look at this fun list of researchy projects related to Metaflow https://docs.google.com/document/d/1HalfutmPZ0FG7jJ-RpQ3oOIGgktg92xqb3u7YfWLbP8/edit
โœ… 1
๐Ÿ™Œ 3
...or propose a better idea ๐Ÿ™‚
d
May I remake my suggestions to have all these docs in one easy to find place :).
๐Ÿ’ฏ 1
๐Ÿ‘ 1
f
๐Ÿคค
โค๏ธ 3
Agreed on making these docs more accessible, awesome stuff!
๐Ÿ™Œ 1
c
Love everything about everything here, especially that dashboard. Do y'all have any R-specific improvements in mind, or any obvious gaps between Metaflow Python and Metaflow R? Something I can bite into?
a
@calm-motorcycle-38345 There are a few gaps between the Pythonic implementation and R implementation - @project etc. Also, the metaflow package is actually not available in CRAN at the moment, besides some more tech debt items. Let me know if any of these sound interesting to you and I can send a 1-pager summary to you.
c
@square-wire-39606 please do! In particular, I think keeping decorators like @project between the two languages at parity will always be a challenge.
a
Yep, getting @conda (or renv) to work for R would be non-trivial but @project should be relatively straightforward - just like the @retry decorator.
f
hey @calm-motorcycle-38345 ๐Ÿ‘‹๐Ÿฝ - one fairly major bit that is missing from the R side is the metaflow.s3 client (havenโ€™t looked at the R package for a while but think this isnโ€™t implemented yet) - interested to get your thoughts about how to tackle this one
๐Ÿ‘ 1
c
I think the first step is making some GitHub Issues! Iโ€™ll get to it.