365 karma · joined August 8, 2012
does it parse the code and store the AST, or is it just plain text ?
i don't like the exclusive buy-out that the blog post mentions since that creates risk for other users
i toyed with a non-exclusive buyout but couldn't come up with anything i felt was general enough, and i wanted to keep the license as short as practical. however, a copyright owner could choose to offer such a guarantee in addition, and i'll take another look
i did include the "reasonable effort to comply" clause to try to avoid unbounded fines
what sort of a multiplier on the "full cost" do you think would work for you ?
the original thread is locked because it's old so i can't reply there, but recently saw your comment
https://news.ycombinator.com/item?id=15425678
> me: i need to generate avatars as a jpeg
> you: The jpeg requirement seems odd. Even if it has "jpg" in the url, you can serve up a standalone SVG (with a jpg extension in the url) as long as you send the right MIME type
i tried your suggestion and it worked - thanks a lot !
i've taken a crack at writing such a license - http://db4j.org/pupl/
would love any feedback
wikipedia is great for mainstream stuff, but even technologies with vibrant communities often lack a wikipedia page. and i'm sure the problem extends well past tech
so i need to generate the avatar on the server side as a jpeg
in spite of the misleading name and the allusions to open source, this license scheme fails to capture that predictability
i've written a license that attempts to capture more of a balance: https://github.com/db4j/pupl
and that's a huge loss - those meanings, those concepts, are high level abstractions that capture critical aspects of human nature, and without them a people are less self aware and more easily manipulated
orwell foretold the loss of these words, though he envisioned it requiring force - the reality is far darker
a blank page would be an improvement - that was seizure inducing
the approach that caddy has taken appears to be a bit of good cop / bad cop. they're maintaining, at least for now, the apache license but they're also using trademark threats to prevent forks (i believe in violation of the github TOS)
the approach that i'm hoping to take is quite different. i'm interested in any feedback (my software is a database engine that in some ways is more convenient than existing dbms for java developers, but similar to caddy in that many good alternatives exist and are free)
https://github.com/db4j/pupl http://db4j.org/pupl/PUPL
- you can freely copy, modify and distribute the software
- non-production use is free, as is production use on up to 10 cores
- prices are predictable and non-discriminatory
how would you feel about using software (in the infrastructure space) under this license ?
Note: If you publish your source code in a public repository on GitHub, according to the Terms of Service, other GitHub users have the right to view and fork your repository within the GitHub site. If you have already created a public repository and no longer want users to have access to it, you can make your repository private. When you convert a public repository to a private repository, existing forks or local copies created by other users will still exist. For more information, see "Making a public repository private."
Note: If you publish your source code in a public repository on GitHub, according to the Terms of Service, other GitHub users have the right to view and fork your repository within the GitHub site. If you have already created a public repository and no longer want users to have access to it, you can make your repository private. When you convert a public repository to a private repository, existing forks or local copies created by other users will still exist. For more information, see "Making a public repository private."
that right would seem to preclude forcing the forked version to change the name
but a problem that i run into often as a user of open source software is that in many cases the readme or other promotional material makes generous claims about quality or performance that the softwares fail to live up to. and in those cases i'm quick to bash the authors
open source doesn't excuse false advertising
this may be exactly what you need for development, but it'd probably be healthy to bring in some more precocious elements ... maybe as interns so you're not committed to a culture shift
aspect ratio - 16:9 is good for media, and maybe some business use, but it's DOA for hacking
i'm not interested in arguing about whether that belief is well founded or self-consistent, or whether their vision of a hands-off gov't is sustainable (i'd argue that neither is sound, but they're not so obviously wrong as to be equivalent to asking for a handout)