Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
60 changes: 57 additions & 3 deletions cfp.html
Original file line number Diff line number Diff line change
@@ -1,5 +1,59 @@
---
layout: cfp
---
<!doctype html>
<html lang="en">
<head>
<!-- Required meta tags -->
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="assets/css/style.css">
<title>PackagingCon 2023</title>
</head>
<body>
<header>
<div id="logo">
<img src="assets/images/logo_new.svg"/>
</div>
</header>
<div>
<h1 id="packaging-con-2023-call-for-presentations">Packaging Con 2023: Call for Presentations</h1>

<p>Today, practically every operating system, language ecosystem, and framework has one or more package managers. Package managers are a, if not the, major way of taming software complexity, integrating various ecosystems, components, and versions and ensuring they are managed (installed/updated/uninstalled) safely, reliably, and in a compatible manner on user systems.</p>

<p>Because package managers bridge the gap between developers and the end user, developing them requires a broad range of expertise in multiple areas, including language runtimes, OS policies, distribution management, dependency solving, and developer workflows.</p>

<p>Packaging Con seeks to bring various package management communities together, as a venue to discuss challenges and exchange ideas. What makes communities work together on a particular software ecosystem? Are the differences among package managers mainly in the implementation language, or are there other key distinctions to software management methodology? How can we get better interoperability and/or cooperation among package manager teams, and what's missing/required to enable that? Is dependency resolution fundamentally the same problem across systems, or does each package manager do it differently?</p>

<p>If any of these questions interest you, we want to hear from you! Packaging Con is a conference for developers of software package management tools, as well as software packagers and communities! Anyone is welcome to participate. Our mission is to bring different software ecosystems together: from Python’s <code class="language-plaintext highlighter-rouge">pip</code> to Rust’s <code class="language-plaintext highlighter-rouge">cargo</code>, from <code class="language-plaintext highlighter-rouge">apt</code>, <code class="language-plaintext highlighter-rouge">rpm</code>, and Nix to <code class="language-plaintext highlighter-rouge">conda</code> and <code class="language-plaintext highlighter-rouge">mamba</code>, and from <code class="language-plaintext highlighter-rouge">vcpkg</code> to <code class="language-plaintext highlighter-rouge">spack</code>, and from <code class="language-plaintext highlighter-rouge">fpm</code> to <code class="language-plaintext highlighter-rouge">npm</code>.</p>

<h2 id="topics">Topics</h2>

<p>We encourage submissions in a wide range of areas related to package management, including but not limited to:</p>

<ul>
<li>Deep dives on specific packaging systems
<li>Software supply chains, pipelines, and security
<li>Package build and release methodologies
<li>Modeling software ecosystems in package managers
<li>Modeling compatibility (semver, API/ABI analysis, etc.)
<li>Interactions between package managers
<li>Reproducibility in package managers
<li>Reliability/robustness of software ecosystems
<li>Dependency solving and management: modeling, methods, and scalability
</ul>

<p>This list is by no means exhaustive — any topic related to package management is welcome to attend.</p>

<h2 id="how-to-submit">How to Submit</h2>

<p>The presentation length is 20 minutes with 10 minutes for Q&amp;A right after the talk. We will have lightning talk sessions with lightning of max 2 minutes. There is no deadline for the submission of lightning talks. Proposals should be submitted through the <a href="https://cfp.packaging-con.org/2023">PackagingCon 2023 pretalx site</a>; submissions will be reviewed by volunteers from the community.</p>

<h2 id="coc">Code of Conduct</h2>

<p>In the interest of fostering an open and welcoming environment, pledge to make participation in Packaging Con a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.</p>

<p>By participating in the conference you agree to abide to the NumFOCUS Code of Conduct.</p>

</div>
<footer>
</footer>
</body>
</html>