Thread: [Freemind-developer] SimplyHTML source code should be included in FreeMind source code distribution
A premier mind-mapping software written in Java
Brought to you by:
christianfoltin,
danielpolansky
[Freemind-developer] SimplyHTML source code should be included in
FreeMind source code distributions
From: Dimitry P. <dpo...@gm...> - 2007-07-18 06:20:59
|
Because SimplyHTML is constantly lightly changed, but I produce no releases and update only SimplyHTML.jar in the FreeMind CVS and commit the source code of the SimplyHTML CVS, the last must according to GPL always be included in the FreeMind source code distributions. The appropriate tag should be created for it too. The installers task of the build.xml in FreeMind could be changed so that the source code of SimplyHTML is always obtained before making the distribution. Chris, because you have always produced the releases, I would like to ask you to care about it. Best regards, Dimitry |
From: Dan P. <dan...@gm...> - 2007-07-18 06:48:09
|
Hello Dimitry, what makes you think you need to include the source of SimplyHTML in the source distribution of FreeMind? Do you really think that any source distribution of a program under GPL must contain the sources of all the libraries used by the program? I really doubt it; it makes little sense to me. BR, Dan On 7/18/07, Dimitry Polivaev <dpo...@gm...> wrote: > > Because SimplyHTML is constantly lightly changed, but I produce no > releases and update only SimplyHTML.jar in the FreeMind CVS and commit > the source code of the SimplyHTML CVS, the last must according to GPL > always be included in the FreeMind source code distributions. The > appropriate tag should be created for it too. The installers task of the > > build.xml in FreeMind could be changed so that the source code of > SimplyHTML is always obtained before making the distribution. > > Chris, because you have always produced the releases, I would like to > ask you to care about it. > > Best regards, Dimitry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > |
From: Dan P. <dan...@gm...> - 2007-07-18 06:56:49
|
Hello Dimitry, this is not the first time you jump into wild conclusions, perform no research before, and put forward false statements in a tone allowing no doubts. So could you please do some research and thinking before you say things of the sort? The questions you should have asked yourself are: What is the practice at other open source projects? What is the basis of my statements? Can my statements be refuted? Can they be sources? Can they be made more readable by writing shorter sentences? I do not have the time to perform the research and verification for you, whenever you come up with such an idea. Best regards, Dan On 7/18/07, Dan Polansky <dan...@gm...> wrote: > > Hello Dimitry, > > what makes you think you need to include the source of SimplyHTML in the > source distribution of FreeMind? Do you really think that any source > distribution of a program under GPL must contain the sources of all the > libraries used by the program? I really doubt it; it makes little sense to > me. > > BR, > Dan > > > On 7/18/07, Dimitry Polivaev <dpo...@gm...> wrote: > > > > Because SimplyHTML is constantly lightly changed, but I produce no > > releases and update only SimplyHTML.jar in the FreeMind CVS and commit > > the source code of the SimplyHTML CVS, the last must according to GPL > > always be included in the FreeMind source code distributions. The > > appropriate tag should be created for it too. The installers task of the > > > > build.xml in FreeMind could be changed so that the source code of > > SimplyHTML is always obtained before making the distribution. > > > > Chris, because you have always produced the releases, I would like to > > ask you to care about it. > > > > Best regards, Dimitry > > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Freemind-developer mailing list > > Fre...@li... > > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > > > |
From: Krzysztof F. <wd...@fo...> - 2007-07-18 14:57:57
|
Dan Polansky wrote: > what makes you think you need to include the source of SimplyHTML in > the source distribution of FreeMind? I think, point (paragraph?) 3 of GPL v2? I'm not sure it has to be included (only if FreeMind uses a modified version of SimplyHTML) but at least it should be provided on request. What are additional advantages/disadvantages of providing the SimplyHTML source anyway? In my opinion, it surely makes the code easier to compile (no need to hunt for The Right Approved Version of SimplyHTML), and makes bug reports more consistent (ie. you don't need to say which version of SimplyHTML you used in order to compile FreeMind when reporting a bug), but also makes the sources larger - and that's probably all. Chris |
From: Dimitry P. <dpo...@gm...> - 2007-07-19 06:19:07
|
> What are additional disadvantages of providing the SimplyHTML > source anyway? (It) makes the sources larger - and that's > probably all. We need not include the SimplyHTML code in the archive file wit the FreeMind code, if we supply another archive file with SimplyHTML code in the same release package. So we make possible but to download it, but those who are not interested need not to to so. Dimitry |
From: Christian F. (GMX) <chr...@gm...> - 2007-07-21 14:04:32
|
Dear Dimitry, following problems: * TAGs: A release - and its corresponding source code - should be reproducible from CVS. This ends up that we have to tag SimplyHTML with FreeMind tags. * Checkout: Thus we can't simply checkout the current version of SimplyHTML to get its sourcecode, because this is not at all reproducible without using the same timestamp. You can't get the sources from the tag FM_0_9_0Beta17, for example, and produce the same release version two years later as the SimplyHTML sources have changed. * We don't change SimplyHTML *especially* for FreeMind as you check in every change into the SimplyHTML CVS. * Having more SimplyHTML releases is a big benefit for its users. Remember, Dimitry, that you as the project head are responsible for new and fresh releases. * In fact, there aren't so many FreeMind releases the past years. From my point of view, it sufficies to use a stable release of SimplyHTML in FreeMind only in the FM release versions. Sure, it would be nice to have it in alphas too, but this is not that essential. * Another main point: you check in the jar of SimplyHTML and I can rely on it that this jar is sufficiently stable and tested. If I add the source code from CVS some days later to make a release, this is in general different as you may have changed its sources without making a new jar (you said, that you frequently change the code). Thus it is not guaranteed that the sources I fetch from CVS do even compile! Thus, I still prefer that you make proper SimplyHTML releases, tag your source code and we don't put the sources into FreeMind. This is - by far - more easy and less error prone. If you don't agree, I would like you to add the SimplyHTML sources as a separate source package to every (stable?) release we make, to tag the SimplyHTML CVS repository with FreeMind tags and to take care that sources and jars are identical. But, from my point of view, these source packages can as well be hosted in the SimplyHTML project and are then more easily to find for everybody (not only FreeMind programmers...). Thanks for the audience, Chris > We need not include the SimplyHTML code in the archive file wit the > FreeMind code, if we supply another archive file with SimplyHTML code in > the same release package. So we make possible but to download it, but > those who are not interested need not to to so. > > Dimitry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > |
From: Dimitry P. <dpo...@gm...> - 2007-07-21 14:50:11
|
Hi Chris, > Thus, I still prefer that you make proper SimplyHTML releases, tag your > source code and we don't put the sources into FreeMind. > This is - by far - more easy and less error prone. In the present time I change SimplyHTML in one of two cases: * if somebody reports a bug, * if somebody submits a patch. In both cases I use to update both SimplyHTML CVS and FreeMind CVS. If I understand you correctly, you request that I *always* create a new release package before submitting any new version of SimplyHTML into FreeMind and write its tag in the FreeMind history. Or should I simply create a new Tag? Dimitry |
From: Christian F. (GMX) <chr...@gm...> - 2007-07-21 19:41:02
|
Hi Dimitry, I asked you to make one "official" release of SimplyHTML before we make a *final* release of FreeMind (say 0.9.0, 1.0.0, etc.). This is not very often. To create a tag each time you make a new jar that you introduce into FreeMind is of help. Does SimplyHTML has a release number built into? Can this tag reflect this release number? Then it is no problem to reconstruct the sources from CVS given the jar in FreeMind. Best regards, Chris Dimitry Polivaev schrieb: > Hi Chris, > > >> Thus, I still prefer that you make proper SimplyHTML releases, tag your >> source code and we don't put the sources into FreeMind. >> This is - by far - more easy and less error prone. >> > > In the present time I change SimplyHTML in one of two cases: > > * if somebody reports a bug, > * if somebody submits a patch. > > In both cases I use to update both SimplyHTML CVS and FreeMind CVS. > > If I understand you correctly, you request that I *always* create a new > release package before submitting any new version of SimplyHTML into > FreeMind and write its tag in the FreeMind history. Or should I simply > create a new Tag? > > Dimitry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > |
From: Dimitry P. <dpo...@gm...> - 2007-07-21 20:02:45
|
Hello Chris, > I asked you to make one "official" release of SimplyHTML before we make > a *final* release of FreeMind (say 0.9.0, 1.0.0, etc.). > This is not very often. It's OK. > > To create a tag each time you make a new jar that you introduce into > FreeMind is of help. I have created a Tag shtml_0_12_2_beta2 labeling the current version. > Does SimplyHTML has a release number built into? Can this tag reflect > this release number? Yes. This number can be obtained by Menu Help->About, and I have changed the freemind properties so that this menu item is visible. > Then it is no problem to reconstruct the sources from CVS given the jar > in FreeMind. > Dimitry |
From: Eric L. <Eric@Lavar.de> - 2007-07-23 18:49:27
|
Hi, so we agree on: - create TAG (aligned with SimplyHTML version) in SimplyHTML-CVS each time a new binary version is uploaded into FreeMind-CVS. - create release of SimplyHTML (code & binary + CVS TAG) before each _stable_ release of FreeMind is created, for binary integration into the release. OK? Fine with me (it's also important for packaging purposes). I leave the GPL & source inclusion aside, I think we should integrate all sources of all libraries we integrate, but nobody does it so let's not overcomplicate things. Dan, for reference, there were recently articles that distros derivating their work from Debian were asked by the FSF to provide the source code even though they didn't do any changes to the packages created by Debian. Reason was that Debian might die and the source code wouldn't be available anymore. Our situation is *possibly* comparable. Eric Dimitry Polivaev wrote: > Hello Chris, >> I asked you to make one "official" release of SimplyHTML before we make >> a *final* release of FreeMind (say 0.9.0, 1.0.0, etc.). >> This is not very often. > > It's OK. > >> To create a tag each time you make a new jar that you introduce into >> FreeMind is of help. > > I have created a Tag shtml_0_12_2_beta2 labeling the current version. > >> Does SimplyHTML has a release number built into? Can this tag reflect >> this release number? > > Yes. This number can be obtained by Menu Help->About, and I have changed > the freemind properties so that this menu item is visible. > >> Then it is no problem to reconstruct the sources from CVS given the jar >> in FreeMind. >> > > Dimitry > -- Gewalt ist die letzte Zuflucht der Inkompetenz. Violence is the Last Resort of the Incompetent. Gwalt jest ostatnem schronieniem niekompetencji. La violence est le dernier refuge de l'incompetence. ~ Isaac Asimov |
From: Krzysztof F. <wd...@fo...> - 2007-07-24 08:00:39
|
Eric Lavarde wrote: > - create TAG (aligned with SimplyHTML version) in SimplyHTML-CVS each > time a new binary version is uploaded into FreeMind-CVS. > > - create release of SimplyHTML (code & binary + CVS TAG) before each > _stable_ release of FreeMind is created, for binary integration into the > release. > I think it's fine (best solution so far) - as long as a person responsible for interaction with SimplyHTML project (Dimitry, right?) will ensure all necessary steps are done in right order. We can always try to rely on a script or even a paper "release checklist" in order to improve the process in case it somehow fails to work. I hope Debian project doesn't die during nearest 20 years, it would be a huge loss (I use Ubuntu and think it's great, "raw" Debian is also very useful). Hope Debian guys are just preparing for a hypothetical situation and not the imminent danger. Chris |
From: Eric@Lavar.de - 2007-07-24 12:15:00
|
Czesc, Krzysztof Foltman said: > Eric Lavarde wrote: >> - create TAG (aligned with SimplyHTML version) in SimplyHTML-CVS each >> time a new binary version is uploaded into FreeMind-CVS. >> >> - create release of SimplyHTML (code & binary + CVS TAG) before each >> _stable_ release of FreeMind is created, for binary integration into the >> release. >> > I think it's fine (best solution so far) - as long as a person > responsible for interaction with SimplyHTML project (Dimitry, right?) > will ensure all necessary steps are done in right order. We can always > try to rely on a script or even a paper "release checklist" in order to > improve the process in case it somehow fails to work. Dimitry is the main one to agree of course. > > I hope Debian project doesn't die during nearest 20 years, it would be a > huge loss (I use Ubuntu and think it's great, "raw" Debian is also very > useful). Hope Debian guys are just preparing for a hypothetical > situation and not the imminent danger. It was not Debian which complained, but the FSF, and it was _very_ theoretical. Eric > > Chris > -- Eric de France, d'Allemagne et de Navarre |
From: Eric L. <fre...@zo...> - 2007-07-31 17:59:55
|
Hi, I'm missing Dimitry (at least) and Chris agreeing on the below. Eric Eric%Lavar.de wrote: > Czesc, > > Krzysztof Foltman said: >> Eric Lavarde wrote: >>> - create TAG (aligned with SimplyHTML version) in SimplyHTML-CVS each >>> time a new binary version is uploaded into FreeMind-CVS. >>> >>> - create release of SimplyHTML (code & binary + CVS TAG) before each >>> _stable_ release of FreeMind is created, for binary integration into the >>> release. >>> >> I think it's fine (best solution so far) - as long as a person >> responsible for interaction with SimplyHTML project (Dimitry, right?) >> will ensure all necessary steps are done in right order. We can always >> try to rely on a script or even a paper "release checklist" in order to >> improve the process in case it somehow fails to work. > Dimitry is the main one to agree of course. |
From: Christian F. (GMX) <chr...@gm...> - 2007-07-31 19:15:51
|
Hi, well, I proposed that. I agree. Chris Eric Lavarde schrieb: > Hi, > > I'm missing Dimitry (at least) and Chris agreeing on the below. > > Eric > > Eric%Lavar.de wrote: > >> Czesc, >> >> Krzysztof Foltman said: >> >>> Eric Lavarde wrote: >>> >>>> - create TAG (aligned with SimplyHTML version) in SimplyHTML-CVS each >>>> time a new binary version is uploaded into FreeMind-CVS. >>>> >>>> - create release of SimplyHTML (code & binary + CVS TAG) before each >>>> _stable_ release of FreeMind is created, for binary integration into the >>>> release. >>>> >>>> >>> I think it's fine (best solution so far) - as long as a person >>> responsible for interaction with SimplyHTML project (Dimitry, right?) >>> will ensure all necessary steps are done in right order. We can always >>> try to rely on a script or even a paper "release checklist" in order to >>> improve the process in case it somehow fails to work. >>> >> Dimitry is the main one to agree of course. >> > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer > > |
From: Dimitry P. <dpo...@gm...> - 2007-07-31 20:41:56
|
Hello, 1. I agree that * a TAG (aligned with SimplyHTML version) in SimplyHTML-CVS should be created each time a new binary version is uploaded into FreeMind-CVS. * a release of SimplyHTML (code & binary + CVS TAG) should be created before each _stable_ release of FreeMind is created, for binary integration into the release. I shall obey these rules. 2. I still think that it would be better if the tagged version of SimplyHTML were distributed along with the FreeMind sources because of the following arguments: 1. SimplyHTML is essential part of FreeMind, and it is being developed to satisfy requirements arising from needs of FreeMind, 2. SimplyHTML is maintained not by external team but by me with contributions from Dan. But just including of a ant build file section automatically downloading and compiling the SimplyHTML from its CVS sources would be good enough. Dimitry |
From: Dan P. <dan...@gm...> - 2007-07-19 08:02:14
|
Hello, of course that SimplyHTML sources have to be publicly available for download. They should be available in SimplyHTML's SourceForge project, just like for any other library or component project there. They DO NOT have to be part of FreeMind source code distribution. Do you want to distribute Apache Batik source code with FreeMind? I really do not understand. SimplyHTML IS NOT a part of FreeMind. It is a HTML WYSIWYG editing component. It is one of the possible editing components that can be attached to FreeMind. BR, Dan |
From: Dan P. <dan...@gm...> - 2007-07-25 05:36:56
|
Hi Eric, Dan, for reference, there were recently articles that distros derivating > their work from Debian were asked by the FSF to provide the source code > even though they didn't do any changes to the packages created by > Debian. Reason was that Debian might die and the source code wouldn't be > available anymore. Our situation is *possibly* comparable. > Do you have links to these articles? SimplyHTML cannot disappear as long as it is on SourceForge. And if SourceForge would disappear, so would FreeMind. So this is most probably practically irrelevant argument. If indeed GNU GPL would require us to include in our CVS all the source code of all the libraries that we use, we would have in the extreme to include the source code of JavaRE in our CVS ;). Regards, Dan |
From: Krzysztof F. <wd...@fo...> - 2007-07-25 08:05:22
|
Dan Polansky wrote: > Do you have links to these articles? SimplyHTML cannot disappear as > long as it is on SourceForge. Well, this part is something I don't agree with. OK, it's not very likely, but I agree with the rest of the post, though. Having to comply with GPL is not a good argument to support including SimplyHTML sources - at least if I understand GPL correctly. There may be other arguments that support it: 1. ease of getting correct versions of all necessary sources for the release X of FreeMind 2. what if authors of SimplyHTML stop accepting contributions from FreeMind team However, those arguments support the view of "we might include" as opposed to "we must include, it's the law". I'm not sure about JRE - I don't know if it's already GPLed or not, but even if it is, it's double-licensed, and the "old" Java license allows for binary-only distribution. > And if SourceForge would disappear, so would FreeMind. So this is most > probably practically irrelevant argument. Another difference is that FreeMind+SimplyHTML would be easier to restore in this case - just take any developer's sandbox and put the sources online. You can't do the same thing with Debian. Chris |
From: Eric L. <fre...@zo...> - 2007-07-25 19:34:15
|
Dan Polansky wrote: > Hi Eric, > > Dan, for reference, there were recently articles that distros derivating > their work from Debian were asked by the FSF to provide the source code > even though they didn't do any changes to the packages created by > Debian. Reason was that Debian might die and the source code wouldn't be > available anymore. Our situation is *possibly* comparable. > > > Do you have links to these articles? SimplyHTML cannot disappear as long > as it is on SourceForge. And if SourceForge would disappear, so would > FreeMind. So this is most probably practically irrelevant argument. http://www.linux-watch.com/news/NS4218186268.html http://software.newsforge.com/software/06/06/23/1728205.shtml And I do agree that it's practically irrelevant, but legally it might not be. > > If indeed GNU GPL would require us to include in our CVS all the source > code of all the libraries that we use, we would have in the extreme to > include the source code of JavaRE in our CVS ;). No, because we don't distribute the JavaRE binaries. But, as said, let's go on, we'll see if someone knocks on our door. Eric > > Regards, > Dan |
From: Christian F. <chr...@gm...> - 2007-07-18 07:22:33
|
Hi Dimitry, I would prefer that you make the releases of SimplyHTML in its sourceforge project. Then, we are not requested to submit its source code as we neither do it with jibx, for example. Best regards, Chris -------- Original-Nachricht -------- Datum: Wed, 18 Jul 2007 08:20:45 +0200 Von: Dimitry Polivaev <dpo...@gm...> An: fre...@li... Betreff: [Freemind-developer] SimplyHTML source code should be included in FreeMind source code distributions > Because SimplyHTML is constantly lightly changed, but I produce no > releases and update only SimplyHTML.jar in the FreeMind CVS and commit > the source code of the SimplyHTML CVS, the last must according to GPL > always be included in the FreeMind source code distributions. The > appropriate tag should be created for it too. The installers task of the > > build.xml in FreeMind could be changed so that the source code of > SimplyHTML is always obtained before making the distribution. > > Chris, because you have always produced the releases, I would like to > ask you to care about it. > > Best regards, Dimitry > > ------------------------------------------------------------------------- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Freemind-developer mailing list > Fre...@li... > https://lists.sourceforge.net/lists/listinfo/freemind-developer -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail |
From: Dimitry P. <dpo...@gm...> - 2007-07-18 22:58:38
|
> I would prefer that you make the releases of SimplyHTML in its sourceforge project. > Then, we are not requested to submit its source code as we neither do it with jibx, for example. Hi Chris, there are many reasons for my request. 1. I change code of SimplyHTML in order to fix some of the bugs as they are reported. But I do not produce a label or release anytime I commit such change. So the state of the code used in FreeMind is different from the SimplyHTML release I have published in the download section of SimplyHTML. It is even not easy to get the exact state which corresponds to the SimplyHTML in the FreeMind distribution. The easiest way to synchronize the SimplyHTML code with the FreeMind releases is getting it from CVS always when the release is build. It is the easiest way, if you consider that getting the source code from the CVS is an ANT task and building it is an ANT task too. This way the consistency of the code with the SimplyHTML.jar can be insured with simplicity and certainty. On the other hand it is much more difficult to produce a Release of SimplyHTML anytime something is changed there. 2. SimplyHTML is an integrate part of FreeMind. So I think that it is better in the sense of GPL if its code is included. Best regards, Dimitry |
From: Dan P. <dan...@gm...> - 2007-07-19 07:41:48
|
Hello, again, please, are other projects doing anything of the sort? How did you come to that idea? What is the backing, the specific backing, including discussions and specific quotes? Best regards, Dan |
From: Dimitry P. <dpo...@gm...> - 2007-07-19 21:58:53
|
> Do you want to distribute Apache Batik source code with FreeMind? I see following differences between Apache Batik and SimplyHTML 1. We do not develop Apache Batik, but do develop SimplyHTML. 2. We use some stable release of Apache Batik, but we do not have any suitable release of SimplyHTML: it is still under development. 3. Apache Batik is not being developed especially to be used in FreeMind, but SimplyHTML is maintained by me with this purpose. I consider SimplyHTML as a part of my FreeMind activities. It's no more than a side-effect of my engagement for FreeMind. After we release 0.9.0 I shall produce a corresponding release of SimplyHTML. But I do not see any sense of producing beta releases of SimplyHTML before: this program does not have such numerous users. I conclude that if publishing of Source Code is required by GPL and we do not use any release to refer to, the best solution is publishing of SimplyHTML code as a part of FreeMind packages. Best regards, Dimitry |
From: Dan P. <dan...@gm...> - 2007-07-20 11:58:38
|
Hello Dimitry, the differences between Batik and SimplyHTML you are listing are irrelevant to the question whether GNU GPL requires us to distribute the sources of SimplyHTML as part of FreeMind source distribution. My point was that I have seen no reference, quote or explanation showing that GNU GPL would require us to do; I doubt that it does. My argument was not about whether it is a good idea to include the source code with FreeMind source distribution; I do not know that. I conclude that if publishing of Source Code is required by GPL and we > do not use any release to refer to, the best solution is publishing of > SimplyHTML code as a part of FreeMind packages. > The SimplyHTML is IMO published by having its source code in public CVS. All you have to do is to provide a tag. Anyway, this discussion seems pointless to me; I am giving up. Let you and Chris decide what you want to do; I find the decision to distribute the source code of SimplyHTML as part of FreeMind source code superfluous and difficult to understand. Best regards, Dan On 7/19/07, Dimitry Polivaev <dpo...@gm...> wrote: > > > Do you want to distribute Apache Batik source code with FreeMind? > > I see following differences between Apache Batik and SimplyHTML > > 1. We do not develop Apache Batik, but do develop SimplyHTML. > > 2. We use some stable release of Apache Batik, but we do not have any > suitable release of SimplyHTML: it is still under development. > > 3. Apache Batik is not being developed especially to be used in > FreeMind, but SimplyHTML is maintained by me with this purpose. I > consider SimplyHTML as a part of my FreeMind activities. It's no more > than a side-effect of my engagement for FreeMind. > > After we release 0.9.0 I shall produce a corresponding release of > SimplyHTML. But I do not see any sense of producing beta releases of > SimplyHTML before: this program does not have such numerous users. > > I conclude that if publishing of Source Code is required by GPL and we > do not use any release to refer to, the best solution is publishing of > SimplyHTML code as a part of FreeMind packages. > > Best regards, Dimitry > |
From: Dan P. <dan...@gm...> - 2007-07-25 20:17:15
|
Hi Eric, okay, so now I understand why we would not need to distribute the source code of JavaRE. We would still need to distribute the source code of Apache Batik, wouldn't we? Anyway, notice that we do not distribute FreeMind on CDs and DVDs. If I understand these articles correctly, the problem was that they distributed binaries on DVDs without providing also the source code on the same media. We, however, distribute FreeMind by means of SourceForge download; by the very same means, the source code of SimplyHTML is available. I am becoming quite unsure about what the case is. In any case, from the point of view of GNU GPL, Apache Batik and HotEqn is no less concerned than SimplyHTML. Dan |