While I spent the majority of my time on QuantCo-internal (often strategic, non-code) work, my GitHub profile still hovers around 8,000 yearly contributions. Part of this is through my internal work, ...

This is a guest blog post by Jackson Oursland - a FreeCAD maintainer and esteemed member of the conda-forge and Pixi community! FreeCAD uses Conda packages to build AppImages, DMG and Windows artifacts. Pixi greatly simplifies the developer workflow.

Today, 2025-04-11, marks the 10th anniversary of the conda-forge community.

This PEP proposes a new file format for specifying dependencies to enable reproducible installation in a Python environment. The format is designed to be human-readable and machine-generated. Installe...

conda famously modifies shell profiles like .bashrc, or even the Windows registry, to register a series of shell functions that make it, allegedly, more accessible and user-friendly. Allegedly. After ...

We are in the process of switching from Boost.Python to nanobind in Pinocchio. The overall objective is, among other objectives, to: reduce the size of Python modules with similar or improved perfo...

Contribute to google-research/troyvis development by creating an account on GitHub.

None

An open-source framework for GPU-accelerated robot learning and sim-to-real transfer

Improving end-to-end learning with salient information

<p>Like so many other software projects the curl project has copyright mentions at the top of almost every file in the source code repository. Like</p> <pre class="wp-block-preformatted">Copyright (C) 1998 - 2022, Daniel Stenberg ...</pre> <p>Over the years we have used a combination of scripts and manual edits to update the ending year in that copyright line to match the year of the latest update of that file.</p> <p>As soon as we started a new year and someone updated a file, the copyright range needed update. Scripts and tools made it less uncomfortable, but it was always somewhat of a pain to remember and fix.</p> <h2 class="wp-block-heading">In 2023 this changed</h2> <p>When the year was again bumped and the first changes of the year were done to curl, we should then consequentially start updating years again to make ranges end with 2023.</p> <p>Only this time someone asked me <em>why?</em> and it made me decide that <em>what the heck, let’s completely rip them out instead!</em> Doing it at the beginning of the year is also a very good moment.</p> <h2 class="wp-block-heading">Do we need the years?</h2> <p>The <a href="https://en.wikipedia.org/wiki/Berne_Convention">Berne Convention</a> states that copyright “must be automatic; it is prohibited to require formal registration”.</p> <p>The often-used copyright lines are not necessary to protect our rights. According to the Wikipedia page mentioned above, the Berne Convention has been ratified by 181 states out of 195 countries in the world.</p> <p>They can still serve a purpose as they are informational and make the ownership question quite clear. The year ranges add questionable value though.</p> <p>I have tried to find resources that argue <strong>for</strong> the importance of the copyright years to be stated and present, but I have not found any credible sources. Possibly because I haven’t figured out where to look.</p> <h2 class="wp-block-heading">Not alone</h2> <p>It turns out quite a few projects run by many different organizations or even huge companies have already dropped the years from their source code header copyright statements. Presumably at least some of those giant corporations have had their legal departments give a green light to the idea before they went ahead and published source code that way to the world.</p> <h2 class="wp-block-heading">Low risk</h2> <p>We own the copyrights no matter if the years are stated or not. The exact years the files were created or edited can still easily be figured out since we use version control, should anyone ever actually care about it. And we give away curl for free, under an extremely liberal license.</p> <p>I don’t think we risk much by doing this move.</p> <h2 class="wp-block-heading">January 3, 2023</h2> <p>On this day I merged commit <a href="https://github.com/curl/curl/commit/2bc1d775f510196154283374284f98d3eae03544">2bc1d775f510</a>, which updated 1856 files and removed copyright years from almost everywhere in the source code repository.</p> <p>I decided to leave them in the <a href="https://github.com/curl/curl/blob/master/COPYING">main license file</a>. Partly because this is a file that lots of companies include in their products and I have had some use of seeing the year ranges in there in the past!</p> <h2 class="wp-block-heading">Bliss</h2> <p>Now we can forget about copyright years in the project. It’s a relief!</p>

Website Membership Newsletter 🌎+3M visitors / year(~50% YoY) ❤️~5000 members(~80% YoY) ✉️~15000 subscribers(~50% YoY) Blog posts Events Talks Townhalls 📝100+ 🎟️25+ 🎤20+ 💻20+ The OSI published over 100 blog posts…