RE: FOray integration to FOP
Clay Leeds wrote: > It might be good to put this on the FOray web site (I looked > for licensing info and didn't find any :-)). Good idea. I just added it to the home page. You can also find it by following the menu item "SourceForge Project Page", which will take you here: http://sourceforge.net/projects/foray/ Victor Mote
Re: FOray integration to FOP
Thanks for clearing this issue up. I wanted to be sure this information was in the list archives. It might be good to put this on the FOray web site (I looked for licensing info and didn't find any :-)). Web Maestro Clay On May 21, 2004, at 8:12 AM, Victor Mote wrote: Clay Leeds wrote: As you're aware, the Apache Software License 2.0 makes it more cumbersome to include/bundle software that is not ASL. Would you comment on the FOray 'license' and how it will be affected and/or interact with ASL? FOray officially uses the Apache License 2.0. ATM, all files still have the 1.1 boilerplate. Victor Mote
RE: FOray integration to FOP
Clay Leeds wrote: > As you're aware, the Apache Software License 2.0 makes it > more cumbersome to include/bundle software that is not ASL. > Would you comment on the FOray 'license' and how it will be > affected and/or interact with ASL? FOray officially uses the Apache License 2.0. ATM, all files still have the 1.1 boilerplate. Victor Mote
Re: FOray integration to FOP
Victor, As you're aware, the Apache Software License 2.0 makes it more cumbersome to include/bundle software that is not ASL. Would you comment on the FOray 'license' and how it will be affected and/or interact with ASL? Thanks! Web Maestro Clay On May 21, 2004, at 7:23 AM, Clay Leeds wrote: Victor, On May 21, 2004, at 2:53 AM, Chris Bowditch wrote: Victor Mote wrote: FOP Devs: I apologize for intruding again. After thrashing around for a bit, I No need to apologize, your input is welcome. That goes double for me (if that's possible... :-)) concluded that there were an overwhelming number of good reasons for me to import the entire FOP maintenance branch into the FOray repository, then delete and modify as necessary for FOray integration. One of the biggest benefits is that it will greatly simplify any integration that FOP decides to do with Foray. Specifically, I don't have to be in the business of trying to coordinate such integration, and you don't have to listen to me trying to do that. Just come get it if you want it. The good news is that I will essentially be doing the maintenance branch integration for you -- there shouldn't be much to do except decide whether you want it or not. I have posted greater detail here: http://foray.sourceforge.net/fop/index.html This approach allows FOray and FOP to ignore each other most of the time. However, I obviously hope that you will check in from time to time to see whether we have anything useful for you. Please let me know if I can help in any way. This approach makes a lot of sense. I will probably unsubscribe fop-dev in the next few days, so if I don't respond here, contact me off-line or through FOray. I will check up on FOrays progress from time to time, to see if theres anything that we need to do. As my company (and probably most others as well) is already using the FOP-maintain branch in production, it makes sense to check in from time to time, to see what FOray has cooking as well. In fact, once you get some usable enhancements from FOray, it might make sense for FOP to add FOray to the Resources Page (assuming there are no objections). I wish you every success with FOray. Chris Ditto Chris's eloquence for me... Web Maestro Clay
Re: FOray integration to FOP
Victor, On May 21, 2004, at 2:53 AM, Chris Bowditch wrote: Victor Mote wrote: FOP Devs: I apologize for intruding again. After thrashing around for a bit, I No need to apologize, your input is welcome. That goes double for me (if that's possible... :-)) concluded that there were an overwhelming number of good reasons for me to import the entire FOP maintenance branch into the FOray repository, then delete and modify as necessary for FOray integration. One of the biggest benefits is that it will greatly simplify any integration that FOP decides to do with Foray. Specifically, I don't have to be in the business of trying to coordinate such integration, and you don't have to listen to me trying to do that. Just come get it if you want it. The good news is that I will essentially be doing the maintenance branch integration for you -- there shouldn't be much to do except decide whether you want it or not. I have posted greater detail here: http://foray.sourceforge.net/fop/index.html This approach allows FOray and FOP to ignore each other most of the time. However, I obviously hope that you will check in from time to time to see whether we have anything useful for you. Please let me know if I can help in any way. This approach makes a lot of sense. I will probably unsubscribe fop-dev in the next few days, so if I don't respond here, contact me off-line or through FOray. I will check up on FOrays progress from time to time, to see if theres anything that we need to do. As my company (and probably most others as well) is already using the FOP-maintain branch in production, it makes sense to check in from time to time, to see what FOray has cooking as well. In fact, once you get some usable enhancements from FOray, it might make sense for FOP to add FOray to the Resources Page (assuming there are no objections). I wish you every success with FOray. Chris Ditto Chris's eloquence for me... Web Maestro Clay
Re: FOray integration to FOP
Victor Mote wrote: FOP Devs: I apologize for intruding again. After thrashing around for a bit, I No need to apologize, your input is welcome. concluded that there were an overwhelming number of good reasons for me to import the entire FOP maintenance branch into the FOray repository, then delete and modify as necessary for FOray integration. One of the biggest benefits is that it will greatly simplify any integration that FOP decides to do with Foray. Specifically, I don't have to be in the business of trying to coordinate such integration, and you don't have to listen to me trying to do that. Just come get it if you want it. The good news is that I will essentially be doing the maintenance branch integration for you -- there shouldn't be much to do except decide whether you want it or not. I have posted greater detail here: http://foray.sourceforge.net/fop/index.html This approach allows FOray and FOP to ignore each other most of the time. However, I obviously hope that you will check in from time to time to see whether we have anything useful for you. Please let me know if I can help in any way. This approach makes a lot of sense. I will probably unsubscribe fop-dev in the next few days, so if I don't respond here, contact me off-line or through FOray. I will check up on FOrays progress from time to time, to see if theres anything that we need to do. I wish you every success with FOray. Chris
