Repository navigation
Description
🐛 Bug report
Location
Section of the site where the content exists
Affected URL(s):
Note: we are still missing org custom templates for our error pages, which is a separate 🐛 that still needs to get handled…
Description
Concise explanation of the problem
/**
* @license
* Copyright OpenINF All Rights Reserved.
*
* Use of this source code is governed by an MIT-style license that can be
* found in the LICENSE file at https://open.inf.is/license
*/Earlier versions of source code in packages we shipped last year included a license blurb as a standalone JSDoc comment that consists of the @license tag, along with a link to the entire text of the license so that the license text does not need to be included in generated JavaScript files, which would cause unnecessary bloat.
This was done before determining that it would be best for the authors (i.e., contributors) to the OpenINF software be the copyright holders rather than any non-person entity (such as an org). We have since updated this as “Copyright (c) The OpenINF Authors. All Rights Reserved.” to reflect this re-distribution of rights to the contributors themselves.
This has two inescapable implications that we now need to act on:
-
Each package repository should contain an
AUTHORSfile adjacent to thepackage.jsonfile that gets deployed as part of the published package on the npm registry. The reason for this is for the purpose of both contributor attribution and their benefit as being another copyright holder of not only their code contribution or even solely to a particular project within the organization, but to all current and future software produced by this organization is licensed in this manner. This will also end up being picked up by the npm CLI tool, which will auto-populate the"contributors"stanza of thepackage.jsonthat is shipped with an array of people information about those who have contributed. This is very convenient because we don't have to continuously keep making diffs to thepackage.jsonfile adding more folks to the manifest as they contribute."contributors": [...]
If there is an
AUTHORSfile in the root of your package, npm will treat each line as aName <email> (url)format, whereemailandurlare optional. Lines that start with a#or are blank, will be ignored.
— https://docs.npmjs.com/cli/v8/configuring-npm/package-json#default-values -
The OpenINF MIT license contained in this repository must (and very quickly can) be published to that URL that we had been linking to in the past (and perhaps presently + future too) as we can no longer change any of the links in the source code of our older published packages. As of right now, that link is broken and is currently a 404 error page
(and a GitHub-pages branded one at that).

- I would like to work on this issue and submit a pull request.
Activity
DerekNonGeneric commentedon Jan 25, 2024
brief update to this issue, which i seem to have moved forward since then:
we now have a 404 page (good)
the styles are, however, not ideally implemented;
they show up on other pages when viewing the source (bad)
we need to create a custom template for them; those would live in the below dir
https://github.com/OpenINF/openinf.github.io/tree/live/_layouts
rm license link as likely bad practice; unsolved
rm license link as likely bad practice; unsolved
📖✨:publish the license our packages point at
DerekNonGeneric commentedon Aug 31, 2026
Fixed by 61604af (#1870), now live:
The page serves the MIT license the OpenINF SDK is published under,
taken from the SDK's own
LICENSE, so the header every publishedpackage carries — "an MIT-style license that can be found in the
LICENSE file at https://open.inf.is/license" — resolves to the text it
promises. The JSON-LD
licensetarget inhead.liquidresolves too.The root
LICENSE/files removed in f08a522 were not restored: thatcommit deliberately moved the project to licensing each directory where
it stands. The page instead points at where written material's terms
live, which are stated at the foot of each documentation page.
Closing by hand — this pull request was linked to this issue, but the
merge did not act on the link. See below.