WelcomeUser Guide
ToSPrivacyCanary
DonateBugsLicense

©2025 Poal.co

1.4K

(post is archived)

[–] 0 pt

Its not much different honestly, We are about to kind of I don't know fork throat I guess. We have pretty different ideas of what we want for a feature set, throat is awesome no question but the direction they want to take things is different from what I want to see here, but I'm pretty sure it'll still be open source, not sure if any of the setup instructions I wrote over on phuks will work.

[–] 0 pt

Depending on their license, you probably can't take the code private - it probably has to remain open and available. I haven't checked to see what kind of licensing they used. I'd read that carefully.

[–] 0 pt

It’s MIT private, only way I would take anything private would be a complete re write and probably would still open source that. I don’t think the software is what’s important. It’s the values.

[–] 0 pt

Yeah, MIT license means you have to leave it open. You'd said, you were going to fork it and that you were pretty sure it'd still be open source - legally it has to remain open source with the MIT license.

(BSD license is a bit different, as you can close proprietary parts, as I recall.)

I'm just making sure we're on the same page.

Again, I'm not a lawyer and I'm sure as fuck not your lawyer. However, I might know a couple things about legal matters. I am also going off memory with the MIT license, but I can look it up and give it a read - if you want. I'm not scared.

If I do so, nothing I say will imply a contract nor is anything I say to be considered legal advice. As always, if you have any questions, please consult a qualified legal professional that's familiar with the subject matter and is licensed to operate in the appropriate jurisdiction.

I do have a free few minutes, 'cause I don't have to make dinner. I can look up the license and let you know what it reads like to me.