JuliaCon 2020 (times are in UTC)

Julia's package ecosystem makes it fairly easy for private organizations to redistribute code back to the Julia community, and we've found there are numerous benefits to routinely open-sourcing internally developed packages:

• great for recruiting both community collaborators and future FTEs
• encourages well-scoped, composable APIs and discourages overcoupling of orthogonal functionality
• encourages structuring/maintaining the project in a manner that keeps the contribution/collaboration barrier low
• positively contributes to the health/growth of the Julia ecosystem that we all rely on; a more robust/featureful ecosystem attracts more great community members and improves productivity for existing community members.

However, it can be difficult to implement effective internal practices that enable internal code to smoothly transition into high quality, open-source contributions. In this BoF, we'll swap techniques for maximizing open-source impact in the Julia ecosystem while minimizing refactor time/effort and code churn. Discussion points include:

• developing Julia packages with upfront "intent to open-source"
• the benefits/challenges of piecemeal upstreaming to existing packages
• identifying/mitigating common pain points w.r.t. internal code churn
• managing internal dependency graphs when nodes are open-sourced
• the interplay between private CI/CD and open CI/CD for Julia packages
• git history/metadata preservation
• the role of GitHub in the Julia community, and open-sourcing non-GitHub-hosted projects
• software licensing