From a1c94b4e09e84bdb5b8958a189ea5c41bd6dbddd Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Tue, 12 Jan 2021 19:34:29 -0500 Subject: [PATCH 01/13] wip --- blog/2021/01/contributhon.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 blog/2021/01/contributhon.md diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md new file mode 100644 index 0000000000..b86dc7559a --- /dev/null +++ b/blog/2021/01/contributhon.md @@ -0,0 +1,30 @@ +@def title = "The 2020 Industry Julia Users Contributhon" +@def authors = "TODO" +@def published = "TODO" +@def rss_pubdate = TODO +@def rss = """A Look Back At The 2020 Industry Julia Users Contributhon""" + +A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's OSS ecosystem. The blog post summarized a few key issues that our discussion group felt served as real hurdles to meaningful OSS contribution from within private organizations. The post concluded by announcing our attempt to jump these hurdles: the Industry Julia Users Contributhon, a hackathon where participating industry organizations could come together to contribute back to the Julia ecosystem. + +This event's goals were to... + +> - ...foster/strengthen collaboration across organizational boundaries, and reduce potentially duplicated efforts. +> - ...both push forward and prove the Julia ecosystem’s readiness for “production” use. +> - ...provide a nice promotional incentive for the involved organizations to dedicate time to and participate in OSS efforts. +> - ...provide promotional and technical benefits to the Julia community as whole. +> - ...have a huge amount of fun! + +Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at Beacon Biosignals, Invenia, TriScale innov, PumasAI, and RelationalAI (TODO: add links). All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. Here's a sampling of the standouts: + +- TODO: add items :) + +## Stuff We Learned + +TODO: flesh out + convert this section to prose + +- gather.town was fun; Beacon now has an internal one +- cross-org collaboration was fun +- Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! +- the event was a great "OSS onboarding ramp" for awesome senior engineering staff that hadn't previously contributed to OSS, translating their internal impact into external impact + +Have thoughts/questions about this blog post, the Contributhon, and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! \ No newline at end of file From fa2d45086796d16cb9c47e0dcd0ddb15e1a36dec Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 11:30:30 -0500 Subject: [PATCH 02/13] Update blog/2021/01/contributhon.md Co-authored-by: mattBrzezinski --- blog/2021/01/contributhon.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index b86dc7559a..283d10a52e 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -4,7 +4,9 @@ @def rss_pubdate = TODO @def rss = """A Look Back At The 2020 Industry Julia Users Contributhon""" -A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's OSS ecosystem. The blog post summarized a few key issues that our discussion group felt served as real hurdles to meaningful OSS contribution from within private organizations. The post concluded by announcing our attempt to jump these hurdles: the Industry Julia Users Contributhon, a hackathon where participating industry organizations could come together to contribute back to the Julia ecosystem. +A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's open source software (OSS) ecosystem. +The blog post summarized a few key issues that our discussion group felt served as real hurdles to meaningful OSS contribution from within private organizations. +The post concluded by announcing our attempt to jump these hurdles: the Julia Industry Users Contributhon, a hackathon where participating industry organizations could come together to contribute back to the Julia ecosystem. This event's goals were to... @@ -27,4 +29,4 @@ TODO: flesh out + convert this section to prose - Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! - the event was a great "OSS onboarding ramp" for awesome senior engineering staff that hadn't previously contributed to OSS, translating their internal impact into external impact -Have thoughts/questions about this blog post, the Contributhon, and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! \ No newline at end of file +Have thoughts/questions about this blog post, the Contributhon, and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! From b9734854db204176c57b81f877b74d8e7309b07a Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 11:31:25 -0500 Subject: [PATCH 03/13] Update blog/2021/01/contributhon.md Co-authored-by: mattBrzezinski --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 283d10a52e..fc5f249be9 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -14,7 +14,7 @@ This event's goals were to... > - ...both push forward and prove the Julia ecosystem’s readiness for “production” use. > - ...provide a nice promotional incentive for the involved organizations to dedicate time to and participate in OSS efforts. > - ...provide promotional and technical benefits to the Julia community as whole. -> - ...have a huge amount of fun! +> - ...and have a huge amount of fun! Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at Beacon Biosignals, Invenia, TriScale innov, PumasAI, and RelationalAI (TODO: add links). All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. Here's a sampling of the standouts: From 8de138cf8d6747b1f173359faba0580d5ffaf1fc Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 11:31:37 -0500 Subject: [PATCH 04/13] Update blog/2021/01/contributhon.md Co-authored-by: mattBrzezinski --- blog/2021/01/contributhon.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index fc5f249be9..f00cde1b0e 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -16,7 +16,9 @@ This event's goals were to... > - ...provide promotional and technical benefits to the Julia community as whole. > - ...and have a huge amount of fun! -Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at Beacon Biosignals, Invenia, TriScale innov, PumasAI, and RelationalAI (TODO: add links). All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. Here's a sampling of the standouts: +Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at Beacon Biosignals, Invenia, TriScale innov, PumasAI, and RelationalAI (TODO: add links). +All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. +Here is a sampling of the standouts: - TODO: add items :) From 8e55c532a59177f88091afa326419b6bb0369c55 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 12:46:26 -0500 Subject: [PATCH 05/13] wip --- blog/2021/01/contributhon.md | 30 +++++++++++++++++++++++++----- 1 file changed, 25 insertions(+), 5 deletions(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index f00cde1b0e..6d3b459423 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -4,8 +4,8 @@ @def rss_pubdate = TODO @def rss = """A Look Back At The 2020 Industry Julia Users Contributhon""" -A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's open source software (OSS) ecosystem. -The blog post summarized a few key issues that our discussion group felt served as real hurdles to meaningful OSS contribution from within private organizations. +A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's open source software (OSS) ecosystem. +The blog post summarized a few key issues that our discussion group felt served as real hurdles to meaningful OSS contribution from within private organizations. The post concluded by announcing our attempt to jump these hurdles: the Julia Industry Users Contributhon, a hackathon where participating industry organizations could come together to contribute back to the Julia ecosystem. This event's goals were to... @@ -16,11 +16,29 @@ This event's goals were to... > - ...provide promotional and technical benefits to the Julia community as whole. > - ...and have a huge amount of fun! -Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at Beacon Biosignals, Invenia, TriScale innov, PumasAI, and RelationalAI (TODO: add links). -All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. +Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at [Beacon Biosignals](https://beacon.bio/), [Invenia](https://www.invenia.ca/), [TriScale innov](https://www.triscale-innov.com/), [RelationalAI](https://www.relational.ai/), and [PumasAI](https://pumas.ai/). +All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. + Here is a sampling of the standouts: -- TODO: add items :) +- [Lighthouse.jl](https://github.com/beacon-biosignals/Lighthouse.jl), which provides a minimal framework-agnostic interface to standardize/automate performance evaluation for multiclass, multirater classification models (Beacon Biosignals) +- [SerializationCaches.jl](https://github.com/beacon-biosignals/SerializationCaches.jl), which provides a simple, composable mechanism for caching objects that take significantly longer to compute from scratch than to (de)serialize from disk (Beacon Biosignals) +- [K8sClusterManagers.jl](https://github.com/beacon-biosignals/K8sClusterManagers.jl), which provides mechanisms to dynamically provision Julia workers overtop a K8s cluster (Beacon Biosignals) +- [KeywordSearch.jl](https://github.com/beacon-biosignals/KeywordSearch.jl), which leverages [StringDistances.jl](https://github.com/matthieugomez/StringDistances.jl) to provide a nice interface for fuzzy document searches. +- [PyMNE.jl](https://github.com/beacon-biosignals/PyMNE.jl), an interface to [MNE](https://mne.tools/stable/index.html) built on top of [PyCall](https://github.com/JuliaPy/PyCall.jl) (Beacon Biosignals) +- myriad JuliaPlots contributions (Beacon Biosignals): [AbstractPlotting.jl#569](https://github.com/JuliaPlots/AbstractPlotting.jl/pull/569), [AbstractPlotting.jl#570](https://github.com/JuliaPlots/AbstractPlotting.jl/pull/570), [WGLMakie.jl#71](https://github.com/JuliaPlots/WGLMakie.jl/pull/71), [JSServe.jl#76](https://github.com/SimonDanisch/JSServe.jl/pull/76) +- improved [RegistryCI.jl support for private package registries](https://github.com/JuliaRegistries/RegistryCI.jl/pull/306) (Beacon Biosignals) +- myriad AWS-related contributions (Invenia, Beacon Biosignals):, [AWSS3.jl#118](https://github.com/JuliaCloud/AWSS3.jl/pull/118), [AWSS3.jl#119](https://github.com/JuliaCloud/AWSS3.jl/pull/119), [AWSS3.jl#120](https://github.com/JuliaCloud/AWSS3.jl/pull/120), [AWSS3.jl#121](https://github.com/JuliaCloud/AWSS3.jl/pull/121), [AWSS3.jl#124](https://github.com/JuliaCloud/AWSS3.jl/pull/124), [AWS.jl#257](https://github.com/JuliaCloud/AWS.jl/pull/257), [AWS.jl#260](https://github.com/JuliaCloud/AWS.jl/pull/260), [AWS.jl#262](https://github.com/JuliaCloud/AWS.jl/pull/262), [AWS.jl#265](https://github.com/JuliaCloud/AWS.jl/pull/265) +- [DateSelectors.jl](https://github.com/invenia/DateSelectors.jl), which provides utilities for partitioning dates into test/train/validation/etc. sets for time-series machine learning (Invenia) +- [Cliquing.jl](https://github.com/invenia/Cliquing.jl), which implements various algorithms for finding a non-overlapping set of cliques in a graph (Invenia) +- [Checkpoints.jl](https://github.com/invenia/Checkpoints.jl), which provides mechanisms for dynamically checkpointing Julia program state (Invenia) +- [PDMatsExtras.jl](https://github.com/invenia/PDMatsExtras.jl), which extends [PDMats.jl](https://github.com/JuliaStats/PDMats.jl) with a couple different positive (semi-)definite matrix types that [nicely interopate with Distributions.jl](https://github.com/JuliaStats/Distributions.jl/issues/1219). +- [RegistryCLI.jl](https://github.com/triscale-innov/RegistryCLI.jl), a tool for easily managing private package registries directly from the command line (TriScale innov) +- [XUnit.jl](https://github.com/RelationalAI-oss/XUnit.jl), a unit test framework with nice parallelization capabilities (RelationalAI) +- Compiler support for compilation profiling during inference/LLVM optimization, [enabling cool new SnoopCompile.jl features](https://timholy.github.io/SnoopCompile.jl/stable/snoopi_deep/) (RelationalAI) +- Various quality-of-life improvements to [PProf.jl](https://github.com/JuliaPerf/PProf.jl), including flame graph support. (RelationalAI) + +...and so many more issues/PRs/etc. that I couldn't fit here! ## Stuff We Learned @@ -31,4 +49,6 @@ TODO: flesh out + convert this section to prose - Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! - the event was a great "OSS onboarding ramp" for awesome senior engineering staff that hadn't previously contributed to OSS, translating their internal impact into external impact +Thanks to everybody that made this event so fun and productive! + Have thoughts/questions about this blog post, the Contributhon, and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! From 0fd1d012105cb8caec959d7de8767039ccd62897 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 12:47:45 -0500 Subject: [PATCH 06/13] wip --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 6d3b459423..42ffcf8594 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -32,7 +32,7 @@ Here is a sampling of the standouts: - [DateSelectors.jl](https://github.com/invenia/DateSelectors.jl), which provides utilities for partitioning dates into test/train/validation/etc. sets for time-series machine learning (Invenia) - [Cliquing.jl](https://github.com/invenia/Cliquing.jl), which implements various algorithms for finding a non-overlapping set of cliques in a graph (Invenia) - [Checkpoints.jl](https://github.com/invenia/Checkpoints.jl), which provides mechanisms for dynamically checkpointing Julia program state (Invenia) -- [PDMatsExtras.jl](https://github.com/invenia/PDMatsExtras.jl), which extends [PDMats.jl](https://github.com/JuliaStats/PDMats.jl) with a couple different positive (semi-)definite matrix types that [nicely interopate with Distributions.jl](https://github.com/JuliaStats/Distributions.jl/issues/1219). +- [PDMatsExtras.jl](https://github.com/invenia/PDMatsExtras.jl), which extends [PDMats.jl](https://github.com/JuliaStats/PDMats.jl) with a couple different positive (semi-)definite matrix types that [nicely interopate with Distributions.jl](https://github.com/JuliaStats/Distributions.jl/issues/1219) (Invenia) - [RegistryCLI.jl](https://github.com/triscale-innov/RegistryCLI.jl), a tool for easily managing private package registries directly from the command line (TriScale innov) - [XUnit.jl](https://github.com/RelationalAI-oss/XUnit.jl), a unit test framework with nice parallelization capabilities (RelationalAI) - Compiler support for compilation profiling during inference/LLVM optimization, [enabling cool new SnoopCompile.jl features](https://timholy.github.io/SnoopCompile.jl/stable/snoopi_deep/) (RelationalAI) From d8d9c3b42724859a232db43ed898a50c582e2674 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 13:17:52 -0500 Subject: [PATCH 07/13] wip --- blog/2021/01/contributhon.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 42ffcf8594..5461562959 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -40,15 +40,14 @@ Here is a sampling of the standouts: ...and so many more issues/PRs/etc. that I couldn't fit here! -## Stuff We Learned +On top of the contributions themselves, this event taught us about (or in some cases, reminded us of) a few valuable points: -TODO: flesh out + convert this section to prose - -- gather.town was fun; Beacon now has an internal one -- cross-org collaboration was fun - Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! -- the event was a great "OSS onboarding ramp" for awesome senior engineering staff that hadn't previously contributed to OSS, translating their internal impact into external impact +- Having a well-documented, battle-tested internal process for safely open-sourcing private code drastically lowers the barrier to actually doing so. +- [Gather](https://gather.town/) is actually a pretty useful platform for collaboration! Adding a spacial component to video chat really goes a long way towards recreating the vibe of a shared workspace. After having a great experience using it to host the event, we at Beacon Biosignals created our own internal Gather space that we hang out in daily. +- Cross-org collaboration has always been a huge development driver in the Julia community, and this event was no different! It was fun to discover the various points of intersection between our orgs' tech stacks, and start working together directly on these tools. The JuliaCloud ecosystem (especially [AWS.jl](https://github.com/JuliaCloud/AWS.jl)) turned out to be of particular interest across participants. +- There are a lot of amazing engineers out there who, before joining an OSS-friendly company, never had an opportunity to contribute to OSS as part of their day-job. This event served as a great OSS onboarding ramp by enabling these individuals to translate pre-existing internal work into impactful external contributions. -Thanks to everybody that made this event so fun and productive! +All in all, I'd say the Contributhon was a success, and established a few points of collaboration between industry Julia users that I suspect will carry on for quite some time. More importantly, it was a whole lot of fun. Thanks to everybody that attended, everybody that facilitated, and all the wonderful folks in OSS community whose projects support Julia's continued rise in industry! -Have thoughts/questions about this blog post, the Contributhon, and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! +Have thoughts/questions about this blog post and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! From 63993debea848d033f1785df86d706480d216d0f Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 13:24:42 -0500 Subject: [PATCH 08/13] wip --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 5461562959..91d2aa9fd6 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -48,6 +48,6 @@ On top of the contributions themselves, this event taught us about (or in some c - Cross-org collaboration has always been a huge development driver in the Julia community, and this event was no different! It was fun to discover the various points of intersection between our orgs' tech stacks, and start working together directly on these tools. The JuliaCloud ecosystem (especially [AWS.jl](https://github.com/JuliaCloud/AWS.jl)) turned out to be of particular interest across participants. - There are a lot of amazing engineers out there who, before joining an OSS-friendly company, never had an opportunity to contribute to OSS as part of their day-job. This event served as a great OSS onboarding ramp by enabling these individuals to translate pre-existing internal work into impactful external contributions. -All in all, I'd say the Contributhon was a success, and established a few points of collaboration between industry Julia users that I suspect will carry on for quite some time. More importantly, it was a whole lot of fun. Thanks to everybody that attended, everybody that facilitated, and all the wonderful folks in OSS community whose projects support Julia's continued rise in industry! +All in all, I'd say the Contributhon was a success, and established some key points of collaboration between industry Julia users that I suspect will carry on for quite some time. More importantly, it was a whole lot of fun. Thanks to everybody that attended, everybody that facilitated, and all the wonderful folks in OSS community whose projects support Julia's continued rise in industry! Have thoughts/questions about this blog post and/or the use of Julia in industry? Come join the discussion in [the Julia Slack's](https://julialang.slack.com/join/shared_invite/zt-ggsythg2-qYjdCBzGPeXceYCnCfpKsQ#/) `#industry-users` channel! From 9f7333e71f558107559382ca4a6e054fbee91f80 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 13:37:47 -0500 Subject: [PATCH 09/13] wip --- blog/2021/01/contributhon.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 91d2aa9fd6..86464b9467 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -38,12 +38,12 @@ Here is a sampling of the standouts: - Compiler support for compilation profiling during inference/LLVM optimization, [enabling cool new SnoopCompile.jl features](https://timholy.github.io/SnoopCompile.jl/stable/snoopi_deep/) (RelationalAI) - Various quality-of-life improvements to [PProf.jl](https://github.com/JuliaPerf/PProf.jl), including flame graph support. (RelationalAI) -...and so many more issues/PRs/etc. that I couldn't fit here! +...and so many more issues/PRs/etc. that I couldn't fit here - especially the important work that went into [public OSS backlog creation](https://docs.google.com/document/d/16Rwkr5u8WdPh-AHVJHs2D2e-0SrUHQS_ZTB0fiepsmU/edit). On top of the contributions themselves, this event taught us about (or in some cases, reminded us of) a few valuable points: - Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! -- Having a well-documented, battle-tested internal process for safely open-sourcing private code drastically lowers the barrier to actually doing so. +- Having a well-documented, battle-tested internal process for safely open-sourcing private code drastically lowers the barrier to actually doing so. Creating an explicit (and if possible, public) "OSS backlog" is a great way to kickstart the development of an internal process. - [Gather](https://gather.town/) is actually a pretty useful platform for collaboration! Adding a spacial component to video chat really goes a long way towards recreating the vibe of a shared workspace. After having a great experience using it to host the event, we at Beacon Biosignals created our own internal Gather space that we hang out in daily. - Cross-org collaboration has always been a huge development driver in the Julia community, and this event was no different! It was fun to discover the various points of intersection between our orgs' tech stacks, and start working together directly on these tools. The JuliaCloud ecosystem (especially [AWS.jl](https://github.com/JuliaCloud/AWS.jl)) turned out to be of particular interest across participants. - There are a lot of amazing engineers out there who, before joining an OSS-friendly company, never had an opportunity to contribute to OSS as part of their day-job. This event served as a great OSS onboarding ramp by enabling these individuals to translate pre-existing internal work into impactful external contributions. From aea08ee6dd612b596ea616e50e1be7a264775084 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Sun, 17 Jan 2021 13:41:13 -0500 Subject: [PATCH 10/13] wip --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 86464b9467..9710d66ed9 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -24,7 +24,7 @@ Here is a sampling of the standouts: - [Lighthouse.jl](https://github.com/beacon-biosignals/Lighthouse.jl), which provides a minimal framework-agnostic interface to standardize/automate performance evaluation for multiclass, multirater classification models (Beacon Biosignals) - [SerializationCaches.jl](https://github.com/beacon-biosignals/SerializationCaches.jl), which provides a simple, composable mechanism for caching objects that take significantly longer to compute from scratch than to (de)serialize from disk (Beacon Biosignals) - [K8sClusterManagers.jl](https://github.com/beacon-biosignals/K8sClusterManagers.jl), which provides mechanisms to dynamically provision Julia workers overtop a K8s cluster (Beacon Biosignals) -- [KeywordSearch.jl](https://github.com/beacon-biosignals/KeywordSearch.jl), which leverages [StringDistances.jl](https://github.com/matthieugomez/StringDistances.jl) to provide a nice interface for fuzzy document searches. +- [KeywordSearch.jl](https://github.com/beacon-biosignals/KeywordSearch.jl), which leverages [StringDistances.jl](https://github.com/matthieugomez/StringDistances.jl) to provide a nice interface for fuzzy document searches (Beacon Biosignals) - [PyMNE.jl](https://github.com/beacon-biosignals/PyMNE.jl), an interface to [MNE](https://mne.tools/stable/index.html) built on top of [PyCall](https://github.com/JuliaPy/PyCall.jl) (Beacon Biosignals) - myriad JuliaPlots contributions (Beacon Biosignals): [AbstractPlotting.jl#569](https://github.com/JuliaPlots/AbstractPlotting.jl/pull/569), [AbstractPlotting.jl#570](https://github.com/JuliaPlots/AbstractPlotting.jl/pull/570), [WGLMakie.jl#71](https://github.com/JuliaPlots/WGLMakie.jl/pull/71), [JSServe.jl#76](https://github.com/SimonDanisch/JSServe.jl/pull/76) - improved [RegistryCI.jl support for private package registries](https://github.com/JuliaRegistries/RegistryCI.jl/pull/306) (Beacon Biosignals) From 72ff7ad70af0bdd1a83e3b35cd1dfaa05c75b46d Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Tue, 19 Jan 2021 18:31:49 -0500 Subject: [PATCH 11/13] Update blog/2021/01/contributhon.md --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 9710d66ed9..7ca6608ac8 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -44,7 +44,7 @@ On top of the contributions themselves, this event taught us about (or in some c - Julia's package manager works seamlessly even when a single package's registered versions are split across private and public registries. In a lot of cases, this made it super easy to upgrade downstream internal packages to the now-open versions of their upstream dependencies - it just required a version bump! - Having a well-documented, battle-tested internal process for safely open-sourcing private code drastically lowers the barrier to actually doing so. Creating an explicit (and if possible, public) "OSS backlog" is a great way to kickstart the development of an internal process. -- [Gather](https://gather.town/) is actually a pretty useful platform for collaboration! Adding a spacial component to video chat really goes a long way towards recreating the vibe of a shared workspace. After having a great experience using it to host the event, we at Beacon Biosignals created our own internal Gather space that we hang out in daily. +- [Gather](https://gather.town/) is actually a pretty useful platform for collaboration! Just like at JuliaCon, it was fun to meet and hang out with the actual people behind the GitHub handles you come across day-to-day in the online Julia community. Also, adding a spacial component to video chat really goes a long way towards recreating the vibe of a shared workspace. After having a great experience using it to host the event, we at Beacon Biosignals created our own internal Gather space that we hang out in daily. - Cross-org collaboration has always been a huge development driver in the Julia community, and this event was no different! It was fun to discover the various points of intersection between our orgs' tech stacks, and start working together directly on these tools. The JuliaCloud ecosystem (especially [AWS.jl](https://github.com/JuliaCloud/AWS.jl)) turned out to be of particular interest across participants. - There are a lot of amazing engineers out there who, before joining an OSS-friendly company, never had an opportunity to contribute to OSS as part of their day-job. This event served as a great OSS onboarding ramp by enabling these individuals to translate pre-existing internal work into impactful external contributions. From 675ff7af8a81f39aad199a83bdb0d53ebb298884 Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Tue, 19 Jan 2021 18:32:02 -0500 Subject: [PATCH 12/13] Update blog/2021/01/contributhon.md Co-authored-by: Nathan Daly <44379820+rai-nhdaly@users.noreply.github.com> --- blog/2021/01/contributhon.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 7ca6608ac8..9a6b7c503d 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -36,7 +36,7 @@ Here is a sampling of the standouts: - [RegistryCLI.jl](https://github.com/triscale-innov/RegistryCLI.jl), a tool for easily managing private package registries directly from the command line (TriScale innov) - [XUnit.jl](https://github.com/RelationalAI-oss/XUnit.jl), a unit test framework with nice parallelization capabilities (RelationalAI) - Compiler support for compilation profiling during inference/LLVM optimization, [enabling cool new SnoopCompile.jl features](https://timholy.github.io/SnoopCompile.jl/stable/snoopi_deep/) (RelationalAI) -- Various quality-of-life improvements to [PProf.jl](https://github.com/JuliaPerf/PProf.jl), including flame graph support. (RelationalAI) +- Various quality-of-life improvements to [PProf.jl](https://github.com/JuliaPerf/PProf.jl), including interoperability with FlameGraphs.jl and SnoopCompile.jl. (RelationalAI) ...and so many more issues/PRs/etc. that I couldn't fit here - especially the important work that went into [public OSS backlog creation](https://docs.google.com/document/d/16Rwkr5u8WdPh-AHVJHs2D2e-0SrUHQS_ZTB0fiepsmU/edit). From deccf60ce6ec40fa17633931387c7c4c4bf8770a Mon Sep 17 00:00:00 2001 From: Jarrett Revels Date: Tue, 19 Jan 2021 18:38:47 -0500 Subject: [PATCH 13/13] update --- blog/2021/01/contributhon.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/blog/2021/01/contributhon.md b/blog/2021/01/contributhon.md index 9a6b7c503d..f0581df6d3 100644 --- a/blog/2021/01/contributhon.md +++ b/blog/2021/01/contributhon.md @@ -1,7 +1,7 @@ @def title = "The 2020 Industry Julia Users Contributhon" -@def authors = "TODO" -@def published = "TODO" -@def rss_pubdate = TODO +@def authors = "Jarrett Revels" +@def published = "20 January 2021" +@def rss_pubdate = Date(2021, 1, 20) @def rss = """A Look Back At The 2020 Industry Julia Users Contributhon""" A few months ago, I wrote [a blog post](https://julialang.org/blog/2020/09/juliacon-2020-open-source-bof-follow-up/) reflecting on an interesting JuliaCon 2020 discussion between a group of industry-focused Julia users that focused on the interplay between closed-source proprietary software development and Julia's open source software (OSS) ecosystem. @@ -16,7 +16,7 @@ This event's goals were to... > - ...provide promotional and technical benefits to the Julia community as whole. > - ...and have a huge amount of fun! -Now, in 2021, I'm happy to report on all of the great contributions made by the wonderful folks at [Beacon Biosignals](https://beacon.bio/), [Invenia](https://www.invenia.ca/), [TriScale innov](https://www.triscale-innov.com/), [RelationalAI](https://www.relational.ai/), and [PumasAI](https://pumas.ai/). +Now, in 2021, I'm happy to report on all of the great contributions made as part of the event last month by the wonderful folks at [Beacon Biosignals](https://beacon.bio/), [Invenia](https://www.invenia.ca/), [TriScale innov](https://www.triscale-innov.com/), [RelationalAI](https://www.relational.ai/), and [PumasAI](https://pumas.ai/). All shapes and sizes of contribution were welcome at the event: we released whole packages, made PRs, caught bugs, started new projects, and planned out our OSS roadmaps/backlogs for future work. Here is a sampling of the standouts: