Re: [sword-devel] Resuming the development of Xiphos - introducing xiphos-ng (Was: Licensing audit of SWORD for Fedora - sharing results with upstream)
On Sun, 2023-10-01 at 17:12 -0500, Aaron Rainbolt wrote: > On 10/1/23 17:02, Peter von Kaehne wrote: > > Have you spoken with Karl, have you signed up to Xiphos’ mailing > > lists? > > I don't know how to contact Karl, I figured he'd see stuff here since > Fr > mentioned him earlier. I have written to you and Karl off list directly to create an introduction. Sorry, I am mostly out of it for several years so this was a chance thing I could do, you might not see much of me else Yours Peter ___ sword-devel mailing list: sword-devel@crosswire.org http://crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
Re: [sword-devel] Resuming the development of Xiphos - introducing xiphos-ng (Was: Licensing audit of SWORD for Fedora - sharing results with upstream)
On 10/1/23 17:02, Peter von Kaehne wrote: Have you spoken with Karl, have you signed up to Xiphos’ mailing lists? I don't know how to contact Karl, I figured he'd see stuff here since Fr mentioned him earlier. The Xiphos mailing lists are either invisible or shut down. See https://www.crosswire.org/mailman/listinfo/ Xiphos has had development pauses of years and suddenly spurts , and Karl is as far as I know still very much around. I think he would welcome any new input for sure and if (I have not the foggiest) he wants to pass it on - he handled 15 years ago the transition in maintainership/lead developership from Terry to himself in the most gracious possible form. He will handle a new one from him to someone else equally graceful. Good to know, thank you! Aaron Peter Sent from my phone. Please forgive misspellings and weird “corrections” On 1 Oct 2023, at 21:50, Aaron Rainbolt wrote: The Xiphos fork has been created! https://github.com/ArrayBolt3/xiphos-ng I'm about to push a build failure fix to it in a few moments. Feel free to make new pull requests, bug reports, suggestions, etc. here. Lord willing I'll be monitoring things and getting additions made. Currently the fork is named xiphos-ng (ng for Next Generation, since that's a rather popular naming convention for when you pick up an old project), however I intend for the program name to remain Xiphos. This is because I don't expect there to ever be a release of xiphos-ng, but rather hope that it will just be absorbed into the Xiphos project and then development will resume there. In the event Xiphos is truly and permanently dead, however, we can come up with a better name for xiphos-ng and then mass-rename and rebrand everything. Also, the SWORD fixes in Fedora seem to be coming along (I'm working on getting the package through initial review currently), so we should be OK on that front if all goes well. Aaron On 10/1/23 03:34, Fr Cyrille wrote: Le 01/10/2023 à 08:59, Aaron Rainbolt a écrit : On 9/28/23 13:35, Fr Cyrille wrote: Le 28/09/2023 à 18:13, Aaron Rainbolt a écrit : Hey, thanks for your help! I was able to just repack and remove most everything offending. I figured I should share the info upstream so that if there was anything you wanted to do on your end, you could, but obviously if you're comfortable keeping things as they are, I don't have a problem with that :) I'll submit a patch for the Python bindings, the fix was fairly simple. As for ftpparse, I could potentially try writing a replacement myself and license it as GPLv2. We already probably have a good starting point since the FileZilla project is under GPL-2.0-or-later, and appears to have its own independently developed directory litsing parser written in C++ (see https://svn.filezilla-project.org/filezilla/FileZilla3/trunk/src/engine/directorylistingparser.cpp?revision=10945=markup). We could port the logic from that into something SWORD-compatible perhaps? One more question about the CMake files, you mention that FindXZ.cmake is your original contribution and would be GPLv2, but it appears to be ported from the BSD-3-Clause FindBZIP2.cmake. Just to be clear, since it contains your modifications, it should be "upgraded" to GPLv2 as it now contains your GPLv2 contributions? If so, are there any other files in the CMake folder that should be similarly "upgraded"? Potentially all of them if they've all had to be modified for SWORD? Thanks so much for your help! Also, did you also previously maintain Xiphos and Bibletime? If so, I would love to take maintainership of those too so I can keep everything SWORD-related from dropping out of Fedora. Dear Aaron, What a magnificent proposal this is!! I have been lamenting to the Lord for months, seeing Xiphos stagnate... and risking disappearing. Personally I am under Ubuntu. At the beginning of the year I asked the Lord in my prayer to give us developers for Xiphos, you could be the answer to this prayer. If Karl could react to your proposal that would be great. I will follow this proposal with great interest. I actually know C and C++, so I might be able to help there. If I have some spare time and am itching to code, I'll fiddle with it and see if I can implement requested features and fix bugs. Also I used to be an Ubuntu Developer, and intend on returning to Ubuntu development once work starts on 24.04 LTS. So I may end up being able to help accelerate the acceptance of updated SWORD-related software into Debian, Ubuntu, and Fedora if, Lord willing, all goes well. Thanks for the encouragement! You made my day! God be praised... I will help to with testing, ideas (many), compiling... May God send still 2 or 3 dev for it. Aaron God bless, and thanks again. Aaron On 9/28/23 07:05, Greg Hellings wrote: Aaron, As the previous maintainer who dropped support, thank you for picking it up. I have moved on from being a Fedora user (NixOS these days)
Re: [sword-devel] Resuming the development of Xiphos - introducing xiphos-ng (Was: Licensing audit of SWORD for Fedora - sharing results with upstream)
Have you spoken with Karl, have you signed up to Xiphos’ mailing lists? Xiphos has had development pauses of years and suddenly spurts , and Karl is as far as I know still very much around. I think he would welcome any new input for sure and if (I have not the foggiest) he wants to pass it on - he handled 15 years ago the transition in maintainership/lead developership from Terry to himself in the most gracious possible form. He will handle a new one from him to someone else equally graceful. Peter Sent from my phone. Please forgive misspellings and weird “corrections” > On 1 Oct 2023, at 21:50, Aaron Rainbolt wrote: > > The Xiphos fork has been created! https://github.com/ArrayBolt3/xiphos-ng > I'm about to push a build failure fix to it in a few moments. Feel free to > make new pull requests, bug reports, suggestions, etc. here. Lord willing > I'll be monitoring things and getting additions made. > > Currently the fork is named xiphos-ng (ng for Next Generation, since that's a > rather popular naming convention for when you pick up an old project), > however I intend for the program name to remain Xiphos. This is because I > don't expect there to ever be a release of xiphos-ng, but rather hope that it > will just be absorbed into the Xiphos project and then development will > resume there. In the event Xiphos is truly and permanently dead, however, we > can come up with a better name for xiphos-ng and then mass-rename and rebrand > everything. > > Also, the SWORD fixes in Fedora seem to be coming along (I'm working on > getting the package through initial review currently), so we should be OK on > that front if all goes well. > > Aaron > >> On 10/1/23 03:34, Fr Cyrille wrote: >> >> >>> Le 01/10/2023 à 08:59, Aaron Rainbolt a écrit : >>> On 9/28/23 13:35, Fr Cyrille wrote: Le 28/09/2023 à 18:13, Aaron Rainbolt a écrit : > Hey, thanks for your help! > > I was able to just repack and remove most everything offending. I figured > I should share the info upstream so that if there was anything you wanted > to do on your end, you could, but obviously if you're comfortable keeping > things as they are, I don't have a problem with that :) > > I'll submit a patch for the Python bindings, the fix was fairly simple. > > As for ftpparse, I could potentially try writing a replacement myself and > license it as GPLv2. We already probably have a good starting point since > the FileZilla project is under GPL-2.0-or-later, and appears to have its > own independently developed directory litsing parser written in C++ (see > https://svn.filezilla-project.org/filezilla/FileZilla3/trunk/src/engine/directorylistingparser.cpp?revision=10945=markup). > We could port the logic from that into something SWORD-compatible > perhaps? > > One more question about the CMake files, you mention that FindXZ.cmake is > your original contribution and would be GPLv2, but it appears to be > ported from the BSD-3-Clause FindBZIP2.cmake. Just to be clear, since it > contains your modifications, it should be "upgraded" to GPLv2 as it now > contains your GPLv2 contributions? If so, are there any other files in > the CMake folder that should be similarly "upgraded"? Potentially all of > them if they've all had to be modified for SWORD? > > Thanks so much for your help! Also, did you also previously maintain > Xiphos and Bibletime? If so, I would love to take maintainership of those > too so I can keep everything SWORD-related from dropping out of Fedora. Dear Aaron, What a magnificent proposal this is!! I have been lamenting to the Lord for months, seeing Xiphos stagnate... and risking disappearing. Personally I am under Ubuntu. At the beginning of the year I asked the Lord in my prayer to give us developers for Xiphos, you could be the answer to this prayer. If Karl could react to your proposal that would be great. I will follow this proposal with great interest. >>> >>> I actually know C and C++, so I might be able to help there. If I have some >>> spare time and am itching to code, I'll fiddle with it and see if I can >>> implement requested features and fix bugs. >>> >>> Also I used to be an Ubuntu Developer, and intend on returning to Ubuntu >>> development once work starts on 24.04 LTS. So I may end up being able to >>> help accelerate the acceptance of updated SWORD-related software into >>> Debian, Ubuntu, and Fedora if, Lord willing, all goes well. >>> >>> Thanks for the encouragement! >> >> You made my day! God be praised... I will help to with testing, ideas >> (many), compiling... May God send still 2 or 3 dev for it. >>> >>> Aaron >>> > > God bless, and thanks again. > > Aaron > > On 9/28/23 07:05, Greg Hellings wrote: >> Aaron, >> >> As the previous
[sword-devel] Resuming the development of Xiphos - introducing xiphos-ng (Was: Licensing audit of SWORD for Fedora - sharing results with upstream)
The Xiphos fork has been created! https://github.com/ArrayBolt3/xiphos-ng I'm about to push a build failure fix to it in a few moments. Feel free to make new pull requests, bug reports, suggestions, etc. here. Lord willing I'll be monitoring things and getting additions made. Currently the fork is named xiphos-ng (ng for Next Generation, since that's a rather popular naming convention for when you pick up an old project), however I intend for the program name to remain Xiphos. This is because I don't expect there to ever be a release of xiphos-ng, but rather hope that it will just be absorbed into the Xiphos project and then development will resume there. In the event Xiphos is truly and permanently dead, however, we can come up with a better name for xiphos-ng and then mass-rename and rebrand everything. Also, the SWORD fixes in Fedora seem to be coming along (I'm working on getting the package through initial review currently), so we should be OK on that front if all goes well. Aaron On 10/1/23 03:34, Fr Cyrille wrote: Le 01/10/2023 à 08:59, Aaron Rainbolt a écrit : On 9/28/23 13:35, Fr Cyrille wrote: Le 28/09/2023 à 18:13, Aaron Rainbolt a écrit : Hey, thanks for your help! I was able to just repack and remove most everything offending. I figured I should share the info upstream so that if there was anything you wanted to do on your end, you could, but obviously if you're comfortable keeping things as they are, I don't have a problem with that :) I'll submit a patch for the Python bindings, the fix was fairly simple. As for ftpparse, I could potentially try writing a replacement myself and license it as GPLv2. We already probably have a good starting point since the FileZilla project is under GPL-2.0-or-later, and appears to have its own independently developed directory litsing parser written in C++ (see https://svn.filezilla-project.org/filezilla/FileZilla3/trunk/src/engine/directorylistingparser.cpp?revision=10945=markup). We could port the logic from that into something SWORD-compatible perhaps? One more question about the CMake files, you mention that FindXZ.cmake is your original contribution and would be GPLv2, but it appears to be ported from the BSD-3-Clause FindBZIP2.cmake. Just to be clear, since it contains your modifications, it should be "upgraded" to GPLv2 as it now contains your GPLv2 contributions? If so, are there any other files in the CMake folder that should be similarly "upgraded"? Potentially all of them if they've all had to be modified for SWORD? Thanks so much for your help! Also, did you also previously maintain Xiphos and Bibletime? If so, I would love to take maintainership of those too so I can keep everything SWORD-related from dropping out of Fedora. Dear Aaron, What a magnificent proposal this is!! I have been lamenting to the Lord for months, seeing Xiphos stagnate... and risking disappearing. Personally I am under Ubuntu. At the beginning of the year I asked the Lord in my prayer to give us developers for Xiphos, you could be the answer to this prayer. If Karl could react to your proposal that would be great. I will follow this proposal with great interest. I actually know C and C++, so I might be able to help there. If I have some spare time and am itching to code, I'll fiddle with it and see if I can implement requested features and fix bugs. Also I used to be an Ubuntu Developer, and intend on returning to Ubuntu development once work starts on 24.04 LTS. So I may end up being able to help accelerate the acceptance of updated SWORD-related software into Debian, Ubuntu, and Fedora if, Lord willing, all goes well. Thanks for the encouragement! You made my day! God be praised... I will help to with testing, ideas (many), compiling... May God send still 2 or 3 dev for it. Aaron God bless, and thanks again. Aaron On 9/28/23 07:05, Greg Hellings wrote: Aaron, As the previous maintainer who dropped support, thank you for picking it up. I have moved on from being a Fedora user (NixOS these days) and was no longer maintaining those packages nor the apps that depend on it. I am, however, the pumpkin holder for the Python and Perl bindings. If you want to submit a patch to us that gets those working again I would be happy to include it upstream. Any files under the cmake folder were contributed by me. Those noting a license were taken from later CMake versions and would match licenses there. The FindXZ file is my original contribution and is under the GPLv2 like all other original SWORD code. The gSOAP and Objective-C bindings should be safe to remove in Fedora as there is no need for them there. The win32 files would only affect the MinGW build of sword in Fedora, which was not retired as it was unaffected by the Python changes. ftpparse is a constant thorn in our side whenever people become hung up on the commercial clause. While not strictly necessary to SWORD, as
