ugh, do we need to fork smartos now with this parler thing?

wiedi : was there a license change?

no, but datacenterdynamics.com/en/news/righ…pt-edgio-acquires-triton-datacenter

@wiedi --> The project is still open source, nothing has nor will change there.

The people paying the folks who do the most maintenance there have. So far, I've not been asked to do anything to violate the illumos CoC, which also is the CoC SmartOS and Triton use.

I will let folks know if that changes.

I've not had to do anything different since I started at MNX in 2022. Still holds true today. (And I'm hypervigilant now... I remember Oracle all too well, e.g.)

danmcd: thanks, I really appreciate the reply and the work you and others do and have done. I also understand that this puts you and the team in a very bad position which you had no choice over.

Still, I'm afraid the SmartOS project either has to become really independent of any company and distance itself from Parler or we'll have to create our own new thing

With the CoC one could make the argument that nwilkens being quoted as wanting to "scaling Parler Social", which goes against so many things in the "Our Pledge" section, might be in scope since "an individual is representing the project or its community in public spaces"...

As I said, I've not been asked to do anything different since I started at MNX. Nothing Parler-Social-specific, per se.

Everything goes straight to the public repos, usable by anyone. Nothing being held back (like some illumos-using firms I've worked at in the past).

does this parler thing has something to do with bahamat's depart?

I'd guess yes, but she's the authoritative answer, so I won't claim to speak for her.

thanks.

sigh. i have an user on smartos zone (user1) for which i'm getting denied by "by PAM account configuration"

i can "su" to that user. but, i have "user2" that can log in normally.

disregard. fixed.

Phew!

(stale "controlmaster" socket from laptop to remote smartos zone, with improper authentication cached)

so hopefully my pkbbuild-trunk zone will be usable again (recently resumed my pkgsrc activity)