Re: Past and preview License List releases (was: 3.1 release)
On Thu, Apr 05, 2018 at 03:04:05PM -0400, Brad Edmondson wrote: > I'm in favor of solving this (making html available for old versions > of the license list). I think it will help with adoption too, > especially as we move back to a more frequent release cadence. > > Perhaps add to the errata issue? Or file a separate issue? I think the existing [1] (from last week) covers this issue. I'm arguing against addressing this in LicenseListPublisher, but I don't think we want multiple GitHub issues about past/preview HTML going at once ;). Cheers, Trevor [1]: https://github.com/spdx/LicenseListPublisher/issues/11 -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy signature.asc Description: OpenPGP digital signature ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: Past and preview License List releases (was: 3.1 release)
I'm in favor of solving this (making html available for old versions of the license list). I think it will help with adoption too, especially as we move back to a more frequent release cadence. Perhaps add to the errata issue? Or file a separate issue? -- Brad Edmondson, *Esq.* 512-673-8782 | brad.edmond...@gmail.com On Fri, Mar 23, 2018 at 4:00 PM, W. Trevor Kingwrote: > On Fri, Mar 23, 2018 at 12:14:03PM -0700, Philippe Ombredanne wrote: > > We are pushing new versions of the license lists but we are NOT > > keeping online the previous versions. They are only in git repos. > > I think it would help a lot adopters to have all the versions (at > > least starting with 2.6 and up) available online on the license list > > web page(s). > > An easy way to do this would be to push our website HTML (e.g. [1]) to > the gh-pages branch of license-list-data. I've mocked that up in > [2,3], and you can see old versions of the list in [4,5,…]. > > > It could also make sense as a further refinement to publish a > > preview of a new version list for comments/heads up before it > > becomes the latest. > > You can do this with the gh-pages approach too [6,7], although someone > (possibly a robot) would need to bump gh-pages after each master > commit (or at least whenever you wanted to refresh the preview). > > If this approach seems useful, someone with license-list-data write > access just needs to push my gh-pages branch [8] to the main > repository. > > Cheers, > Trevor > > [1]: https://github.com/spdx/license-list-data/blob/v2.6/website/0BSD > [2]: https://wking.github.io/license-list-data/ > [3]: https://github.com/wking/license-list-data/commit/ > c112d15c76e8c2f0a5c15eca8719a81a765a631f > [4]: https://wking.github.io/license-list-data/v2.6/website/ > [5]: https://wking.github.io/license-list-data/v3.0/website/ > [6]: https://wking.github.io/license-list-data/dev/website/ > [7]: https://github.com/wking/license-list-data/commit/ > 1f7322894a9e3a2a233eca9250549d3cd59f5eeb > [8]: https://github.com/wking/license-list-data/tree/gh-pages > > -- > This email may be signed or encrypted with GnuPG (http://www.gnupg.org). > For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy > > ___ > Spdx-legal mailing list > Spdx-legal@lists.spdx.org > https://lists.spdx.org/mailman/listinfo/spdx-legal > > ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Past and preview License List releases (was: 3.1 release)
On Fri, Mar 23, 2018 at 12:14:03PM -0700, Philippe Ombredanne wrote: > We are pushing new versions of the license lists but we are NOT > keeping online the previous versions. They are only in git repos. > I think it would help a lot adopters to have all the versions (at > least starting with 2.6 and up) available online on the license list > web page(s). An easy way to do this would be to push our website HTML (e.g. [1]) to the gh-pages branch of license-list-data. I've mocked that up in [2,3], and you can see old versions of the list in [4,5,…]. > It could also make sense as a further refinement to publish a > preview of a new version list for comments/heads up before it > becomes the latest. You can do this with the gh-pages approach too [6,7], although someone (possibly a robot) would need to bump gh-pages after each master commit (or at least whenever you wanted to refresh the preview). If this approach seems useful, someone with license-list-data write access just needs to push my gh-pages branch [8] to the main repository. Cheers, Trevor [1]: https://github.com/spdx/license-list-data/blob/v2.6/website/0BSD [2]: https://wking.github.io/license-list-data/ [3]: https://github.com/wking/license-list-data/commit/c112d15c76e8c2f0a5c15eca8719a81a765a631f [4]: https://wking.github.io/license-list-data/v2.6/website/ [5]: https://wking.github.io/license-list-data/v3.0/website/ [6]: https://wking.github.io/license-list-data/dev/website/ [7]: https://github.com/wking/license-list-data/commit/1f7322894a9e3a2a233eca9250549d3cd59f5eeb [8]: https://github.com/wking/license-list-data/tree/gh-pages -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy signature.asc Description: OpenPGP digital signature ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal