To read all comments associated with this story, please click here.
Let me get this straight: The author wants the name of the WM to refer to his codebase with no additions like Ion3v462007. And any off shoots are either not to use the name or to clearly spell out they are not Ion3. Okay, seems OK. A little annoying but fair since its his name.
Where the crunch comes in is in when somebody does a patch that changes Ion3 in a significant way. You need the approval of the author to do this since, in this theory, makes it not purely Ion3. This seems to take things a bit far and this is what OpenBSD is adjecting to.
Same behaviour from Tuomo was apparent on Arch Linux's mailing lists recently as well:
http://archlinux.org/pipermail/tur-users/2007-April/004634.html
It's almost as if he wanted everybody to ignore him and ion.
Edited 2007-05-07 11:05
"Same behaviour from Tuomo was apparent on Arch Linux's mailing lists recently as well:"
Wow. Heh. What can you say? It's entertaining in some sick kind of way when people go out of their way to come across as total moronic jerks.
I think the best part was the "timely release" clause he was/is going to put in the license. Is your Ion package lagging? Watch out! Tuomo will legally threaten you!
Heh. Man. This totally made my day.
"It's almost as if he wanted everybody to ignore him and ion. "
I guess everyone does already and that's why he's so irrationally pissed off at FOSS.
It's actually really simple to understand. Various distributions distribute ion3 packages with unsupported patches. When said ion3 package doesn't work, they go to Tuomo bitching about it.
He has made it exceedingly clear that he will not support patched versions of ion3, and yet the package maintainers continue to distribute these patched versions and make no mention of the fact that it is unsupported by the author. They also continue to distribute ancient versions of ion3 with the same consequence.
All the package maintainers had to do was mention the fact that their package was non-standard and unsupported. They refused to do so; you can't really blame Tuomo for being a tad bit irritated about it.






Member since:
2005-06-29
There was some discussion about a week ago on the misc@openbsd.org mailing lists where the decision of the developer to change the license to Ion may result in it being removed from the OpenBSD ports tree. I don't know the details, but if this is true, I wonder if it will result in problems with other OS's?
License change notice:
http://article.gmane.org/gmane.comp.window-managers.ion.general/770...
OpenBSD thread:
http://archives.neohapsis.com/archives/openbsd/2007-04/2159.html