Add Polyform NC license + Countdown addendum

[erlend-sh]

License Name

Polyform NonCommercial v1.0.0 + Countdown

License Short Identifier

PNCC-1.0.0

Links

https://polyformproject.org/licenses/countdown/1.0.0/

https://writing.kemitchell.com/2023/12/01/PolyForm-Countdown

https://writing.kemitchell.com/2023/10/24/Scheduled-Relicensing

Description

@kemitchell might have a different (and canonical) opinion on what the Short Identifier should be, I just winged it.

[ezekg]

This license doesn't seem to be widely used, but correct me if I'm wrong there. I'm not super familiar with the Polyform license suite. From a cursory glance, and @chadwhitacre correct me if I'm wrong, I think that a blanket restriction to non-commercial use leans too far from our "minimal restrictions" requirement in the Fair Source Definition and more towards source-available.

[chadwhitacre]

This license doesn't seem to be widely used

@ezekg Looks like they're planning to use it in muni-town/weird#123.

The README today says that new licenses "should also be adopted at more than one company, at least." Do you have any other companies ready to make the case for recognition with you, @erlend-sh?

[erlend-sh]

Do you have any other companies ready to make the case for recognition with you

Not yet, but now that this discussion has been started I have something I can refer other Polyform adopters to.

[chadwhitacre]

Sounds good. I'm agreed in principle to dealing in Polyform in some fashion. There's a lot of detail to get through on license specifics vis-a-vis the Fair Source Definition, we'll hash it out together. :)

[ezekg]

Agreed. I'd love to explore Polyform more and talk specifics i.r.t. the Fair Source Definition. Like I said earlier, I'm not sure if the Polyform Noncommercial is an exact fit since the restrictions are very wide, but the Polyform Perimeter and Shield variations + Polyform Countdown seem like good mostly-permissive non-competes akin to the minimal restrictions under FSL.

@kemitchell — big fan, feel free to chime in.

[chadwhitacre]

Shield is the one @hmeeker @heathermeeker suggested to me the other day.

[chadwhitacre]

@erlend-sh If you want to champion this I think it would be good to have a call together to discuss, at least the three of us (you, me, and @ezekg). My email is [email protected] if you'd like to initiate that.

[erlend-sh]

Thanks for the invite! We’re gonna be busy soft-launching our product in the next two weeks, which should also help reify this particular license combo. So if you don’t mind letting this issue linger for a bit, I’d love to do a call together early next month.

[chadwhitacre]

Not a problem, ball is in your court.

Good luck with the launch! :-)