Please create an account to participate in the Slashdot moderation system

 


Forgot your password?
Close
typodupeerror
×
Communications GNU is Not Unix The Internet

Jive Software To Open Source Its Jabber Server 15

Posted by timothy from the now-you-can-jibber dept.
fernique writes "Jive Software, a leading provider of knowledge-based support software, announced today that it will license its Jive Messenger application under the GPL Open Source license. Jive Messenger, based on the open IETF standard XMPP protocol, is a Java-based server for comprehensive group chat and instant messaging (IM)."
This discussion has been archived. No new comments can be posted.

Jive Software To Open Source Its Jabber Server More

Jive Software To Open Source Its Jabber Server

Comments Filter:

  • Not a standard ... yet (Score:4, Informative)

    by dago ( 25724 ) on Wednesday September 29, 2004 @08:43AM (#10382789)
    Btw, XMPP isn't a standard yet, just a draft and soon to be published RFC.

  • Componentisation and GPL (Score:4, Interesting)

    by tod_miller ( 792541 ) on Wednesday September 29, 2004 @08:57AM (#10382911) Journal
    If I write an application that, for instance, sends faxes. You could use a closed source driver for this, or you could use a GPL'd driver for this.

    Right? Now, if I wrote a game, that wanted to use this GPL jive, what level of abstraction would allow me to use this (ditribute is as a 'suggested' compatible chat server) wihtou GPL'ing my own code?

    This is more of a query that has laid dormant in my mind, now I see this (and that open source voice recognition) and I think more abou tit. Not that I do not want to relewase the source of my own app - just wondering.

    I will look at this. (Jive software I heard about them in a negative context a while back, or was that Jive forums? blast)

    • Re:Componentisation and GPL (Score:1, Informative)

      by Anonymous Coward
      It's cool as long as you're not linking with GPL'ed code. (You can generally link with LGPL'd libs if you don't modify them).
      • in Java terms. If I don't import, but I use some kind of classloader lookup (based on user pref) and cast it to an interface (sorry to be so blunt!) so I talk to this 'mystery' GPL / nonGPL library, can I jsut let loose my code, heck, and even send a copy of the GPL stuff (redist allowed!) as a suggested thungamyjib(TM), which works with it (since I knew it would)

        Of course, problem here is, you would need to modify the GPL code to work with you interface, which is fine, because you will send your version b
        • Keeping in mind that IANAL, I think you are wrong. This isn't very "legal speak", but the general idea is that if you "need" a GPL'd library in order to build your app, then your app is a derivative work, and must also be licensed under the GPL (if you give it to anyone). In C/C++, "need" means you're including the header files and linking with the library. In Java, I guess "need" would mean the library's .jar or .class files must be present for the compiler to get method signatures.

          Your idea of a buffe
          • I am aware of LGPL - of course.

            What I am suggesting is:

            Nice Library, GPL

            Modify library, keep it GPL, but implement your interface...

            aah, I see, the interface becomes GPL... UNLESS the interface is:

            Interface (non GPL)
            |
            |
            GPL Library--- via interface ---- Your non GPL library

            THis would mean that realistically and technically, you could ENABLE GPL'd software, like drivers, to work with your proprietary code.

            The 'Interface' (which needs to be the same class loaded object for it to be the same interface) ..
    • My understanding is that if you were to write an external component that communicated with the server over tcp/ip then it doesn't matter what license that component uses, even if the server itself is gpl. But if you want to write a module that integrates with the server internally then you do need to worry about licenses...

      Jive software are the same people who put out the smack xmpp java library [jivesoftware.com] which is imho very well written, so I suspect that the server is also quite good.

      It's good to have another op
      • One thing that stops me from immediately jumping onto Jive jabber server is the seemingly absent internalisation support. [jabber.org]

        I glanced at ejabberd recently and was initially spooked by the choice of the language - Erlang [erlang.org]. Thought it was some obscure toaster programming language. Turns out its from Erricsson, opensourced, and designed for fault tolerance and things like routers and servers.

        Can someone point to a good review of the most common, free Jabber servers? (Possibly for Windows: Jabberd 1.4.x; Erlang

        • If it's part of the XMPP spec to do internationalization, then it may not...

          On the other hand, if XMPP relies on XML encodings, I'm sure it will. Java natively supports unicode as it's default character encoding. All the XML parsers support UTF-8 as well.
    • Yeah, I think abou' tit too.

      But what does that have to do with the -- Ohh!
  • If I remember right, Jive Forums used to be an GPL'd open source project? This was in the Jive 1.x or 2.x days. Then the company forked the code, and the next branch was not GPL anymore ...

    This was somewhere between 1999 and 2002, anyone remember this? I was last looking at Jive about 8 months ago, but now I can't find the history any more ....
  • ... and since it's Java, it performs almost as fast as C and C++!
    :)

Slashdot Top Deals

A committee takes root and grows, it flowers, wilts and dies, scattering the seed from which other committees will bloom. -- Parkinson

Close