[Nasm-devel] Tagging releases on github

[Billy O'Neal (VC AIR)]

> Could you explain what you mean with "licensing scary?"
>
> It is all open source, under 2-BSD to boot. You can mirror the release directory, which means you get all the sources, too.
>
> Am I missing something?

Admittedly I didn't go so far as to look at specific licensing here; we just never mirrored anything before. We did try to mirror another project (Strawberry Perl) once before, and got told by Legal "no", and we have not tried since.

Given that I didn't get a response here for a couple months I started opening that dialogue with Legal again and they seem at least somewhat amenable given the much more straightforward 2-BSD.

At this point it's back in my court again trying to get the paperwork to create a new Azure Storage account to do the mirroring.

> As far as hosting releases on github... our build process is highly automated, and would be very hard to host elsewhere.

Makes sense.

> If you are really keen on helping us, the absolutely best thing would be to fund a CDN service that we could put in front of

Don't think our finance folks would go for that; from time to time they do do surveys on OSS projects to send money to I could nominate you folks for, can't promise anything though.

Thanks for the reply!

Billy O'Neal
Visual C++ - vcpkg
________________________________
From: H. Peter Anvin <hpa at zytor.com>
Sent: Tuesday, August 15, 2023 06:18 PM
To: Billy O'Neal (VC AIR) <bion at microsoft.com>; Cyrill Gorcunov <gorcunov at gmail.com>; nasm-devel at nasm.us <nasm-devel at nasm.us>
Subject: Re: [Nasm-devel] Tagging releases on github

[You don't often get email from hpa at zytor.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]

On 7/31/23 11:23, Billy O'Neal (VC AIR) wrote:
> Hi there!
>
> We recently had another spat of nasm.us being down causing people to
> break: https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvcpkg%2Fissues%2F2777&data=05%7C01%7Cbion%40microsoft.com%7C1bacd12322974d02b1b808db9df6a2fa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638277454862007349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7sjb0%2BwxZZX8C6ytD2jlX7RDAztMnfl5AkXx%2BCNQMBU%3D&reserved=0<https://github.com/microsoft/vcpkg/issues/2777>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fvcpkg%2Fissues%2F2777&data=05%7C01%7Cbion%40microsoft.com%7C1bacd12322974d02b1b808db9df6a2fa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638277454862007349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7sjb0%2BwxZZX8C6ytD2jlX7RDAztMnfl5AkXx%2BCNQMBU%3D&reserved=0<https://github.com/microsoft/vcpkg/issues/2777>>
>
> We would love to stop having vcpkg customers hammer nasm.us; we don't
> presently rehost that stuff because it involves ... licensing scary, but
> as the copyright holders if you added a release we would love to use
> that as a primary mirror instead.
>

Could you explain what you mean with "licensing scary?"

It is all open source, under 2-BSD to boot. You can mirror the release
directory, which means you get all the sources, too.

Am I missing something?

As far as hosting releases on github... our build process is highly
automated, and would be very hard to host elsewhere.

If you are really keen on helping us, the absolutely best thing would be
to fund a CDN service that we could put in front of https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.nasm.us%2F&data=05%7C01%7Cbion%40microsoft.com%7C1bacd12322974d02b1b808db9df6a2fa%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638277454862007349%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lsjHqj3pBKahYoFBpHXA8q33urmgm7tEx0KPq1XdUhc%3D&reserved=0<http://www.nasm.us/> of course...

        -hpa
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.nasm.us/archives/nasm-devel/attachments/20230816/e46edccb/attachment.htm>