-
this is why a lot of projects require JCA’s
-
presenting to Ozzie sounds far less stressful than presenting to Gates
-
“Reports indicate that episodes of random freezing during use are worse with the 2.0 version, though a cause has not yet been isolated” – there’s a lot to like in FF 2.0, but stability – in my experience – has taken a serious hit
-
i’ve been meaning to try out zmanda; this howto removes any last barrier to entry – except for time. will be giving it a whirl soon as i get back to the office
-
“I like this idea for websites, using existing Jabber IDs to log in instead of dealing with making a whole seperate sign in system.” – interesting; there are so many different things that can be done w/ Jabber
tecosystems
links for 2006-10-31
Share via Twitter Share via Facebook Share via Linkedin Share via Reddit
Luis says:
October 31, 2006 at 5:18 am
And it’s why I (and a lot of other open source contributors) would never sign a JCA without strong guarantees built into that JCA- if I chose a license for a specific reason, I chose that license, and not some other license with loopholes in it.
stephen o'grady says:
November 1, 2006 at 4:57 pm
fair enough. but it can hamstring larger projects that have to make license changes for good reasons. one project that i know had problems making a license change b/c one of its copyright holders was dead.
that seems less than ideal.