3 Replies Latest reply on Oct 23, 2007 12:10 PM by Koen Aers

    LGPL issue

    Basim Newbie

      Hi
      If I decide to change some of the JBPM source code, where should I publish these changes in order to satisfy the LGPL terms? Also is it enough to simply publish the changed classes or do I have to say exactly where the changes are?

      Thanks

      Basim

        • 1. Re: LGPL issue
          Koen Aers Master

          Are you planning to distribute your changes? ie to fork and make the fork publicly available? If so, please can you explain what features you lack and why you needed to change the sources to implement them? jBPM is pretty flexible and extensible so it is kind of surprising to see this happen.

          Regards,
          Koen

          • 2. Re: LGPL issue
            Basim Newbie

            We found that the way the process designer deals with task and process attributes not to be convenient for our purposes. So we are considering changing the plug-in. If we do so and we are happy that the changes fulfill our needs then we will make it publicly available.

            My question is that if we reach that point, what is the mechanism of making the changes public?

            Thanks

            • 3. Re: LGPL issue
              Koen Aers Master

              Again, what are the exact lacking features? How is the way that the process designer deals with task and process attributes not convenient for your purposes? How are you planning to change the plug-in?

              The main force of open source is the possibility to discuss this and direct the project in the direction that is wanted by the community. If everybody starts forking the project because there is some feature lacking without discussing it this goes against the very nature of open source. So before thinking about forking, let's at least start a discussion about the things you want in another way.

              Regards,
              Koen