Re: [twsocket] Using SourceForge for ICS ?
DZ-Jay wrote: On Oct 7, 2007, at 14:57, Arno Garrels wrote: Isn't it safe to use the Copy-Modify-Merge solution, described in the online-help ? Yes, it is very safe. Now that I checked how to merge particular changes made in branches to the main source tree under trunk I would like to suggest the following, same structure for two different repositories one for V5 and one for V6: /icsv(n) |-branches | |-ics-ssl |-tags | |-ics-ssl | | |- beta(n) | |-ics | |- release(n) |-trunk |-ics Where the ics-ssl branch and tags cannot be accessed by common ics users. AFAIK it is only possible to merge between common and SSL when the SSL code is in the same repository, is that true? It works very well and makes it very easy to maintain. If Francois does not want to put the SSL code into the project/repository as well ? I think we won't safe very much. What do you think? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Currently I don't plan to put ICS-SSL on SourceForge. I also wouldn't recommend it, until that time when you release it as open source (if ever you intend to do so). Still, it wouldn't hurt at all to set up SVN in your local machine to maintain the source :) -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
But if v6 represents the version where most development will be done, and v5 is only for legacy support That's it. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
[EMAIL PROTECTED] wrote: /icsv(n) |-branches | |-ics-ssl |-tags | |-ics-ssl | | |- beta(n) | |-ics | |- release(n) |-trunk |-ics There's a few questions I have with your suggested structure: 1. Is ICS-SSL really a branch of ICS, or should it be considered a separate project? It's no separate project. It shares most of the files with common ICS, most of the SSL code is available as .inc files compiled in conditionally. And it has its own demo-folder. Branches, in my opinion, should be temporary code paths destined to eventually merge with the main trunk, Basically that's true, however think of it as a persistent branch, you can change everything however ever only merge those changes to the main trunk effecting the shared files. People can work with either common ICS or SSL and commit their changes. Merging with the branch or the other way around was very easy (allowed to admin users only). But I just read Francois reply, so this discussion is useless in any case. 2. Does ICS v6 represent a completely different code-base than ICS v5, or is it a natural progression for it? It's the latter, however the point when V6 has been split from the common base is already some years back and hard to restore. There will be no new features in V5 so merging between V5 and V6 is most likely not required. Also revision numbers are incremented for the entire project/repository. But I could very well live with both in the same repository as well, locally I also treat them as two different projects. -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html If the former, then they indeed should be separte projects. But if the latter, they should form part of the same code base: If ICS v5 is currently the stable version, and ICS v6 represents a new version that will eventually supplant it, then I suggest ICS v5 represent the main trunk, and ICS v6 become a branch of it. Once ICS v6 matures and replaces v5, it will be merged into the main trunk, and v5 set as a Tag. But if v6 represents the version where most development will be done, and v5 is only for legacy support, then it should be the other way around. Also, keep in mind that merging is done locally in the user's working directory, not directly in the repository. To merge, you select a source path from the repository, and specify which revisions to include; SVN will then merge those changes with your working directory (representing the target repository path). Once all conflicts are resolved, the updated (merged) working directory can be commited by the user. Therefore, it is possible for users to revert accidentally changes commited previously, by commiting wrongly merged files. The good thing is that the changes were not lost (they are still in the repository history), and can easily be returned. By wrongly merged files, I mean that the user mistakenly overwrote other's changes with his own or with an older version of code. This is the scenario that I alluded to before, and it is fairly common among people who are not used to version control systems. -dZ. --- Original Message --- From: Arno Garrels[mailto:[EMAIL PROTECTED] Sent: 10/8/2007 1:03:09 PM To : twsocket@elists.org Cc : Subject : RE: Re: [twsocket] Using SourceForge for ICS ? DZ-Jay wrote: On Oct 7, 2007, at 14:57, Arno Garrels wrote: Isn't it safe to use the Copy-Modify-Merge solution, described in the online-help ? Yes, it is very safe. Now that I checked how to merge particular changes made in branches to the main source tree under trunk I would like to suggest the following, same structure for two different repositories one for V5 and one for V6: /icsv(n) |-branches | |-ics-ssl |-tags | |-ics-ssl | | |- beta(n) | |-ics | |- release(n) |-trunk |-ics Where the ics-ssl branch and tags cannot be accessed by common ics users. AFAIK it is only possible to merge between common and SSL when the SSL code is in the same repository, is that true? It works very well and makes it very easy to maintain. If Francois does not want to put the SSL code into the project/repository as well ? I think we won't safe very much. What do you think? -- Arno Garrels [TeamICS] http://www.overbyte.be/eng/overbyte/teamics.html -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] ICS on SourceForge, which license is best ?
I would like to have your opinion about which license I should select at SourceForge (http://www.opensource.org/licenses/category). I have not much time to read all possible licenses. You all know the current license displayed in each source file (see below for reminder). I would like to stay as close as possible to this simple license. Basically, I want to preserve my intellectual property while granting anyone to use and redistribute ICS source code, including in commercial applications and royalty free. Legal issues: Copyright (C) 1996-2007 by François PIETTE Rue de Grady 24, 4053 Embourg, Belgium. Fax: +32-4-365.74.56 [EMAIL PROTECTED] This software is provided 'as-is', without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented, you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. 4. You must register this software by sending a picture postcard to the author. Use a nice stamp and mention your name, street address, EMail address and any comment you like to say. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] ICS on SourceForge, which license is best ?
So far, the closest thing to your PostcardWare License that I have found is this: The Educational Community License http://www.opensource.org/licenses/ecl1.php It grants all the same rights that your license does, and has a provision to prevent confusion between derivative works and the original (i.e. modified versions cannot be claimed to be the original). The only thing missing is the postcard condition :) -dZ. --- Original Message --- From: Francois PIETTE[mailto:[EMAIL PROTECTED] Sent: 10/8/2007 2:59:47 PM To : twsocket@elists.org Cc : Subject : RE: [twsocket] ICS on SourceForge, which license is best ? I would like to have your opinion about which license I should select at SourceForge ( http://www.opensource.org/licenses/category ). I have not much time to read all possible licenses. You all know the current license displayed in each source file (see below for reminder). I would like to stay as close as possible to this simple license. Basically, I want to preserve my intellectual property while granting anyone to use and redistribute ICS source code, including in commercial applications and royalty free. Legal issues: Copyright (C) 1996-2007 by François PIETTE Rue de Grady 24, 4053 Embourg, Belgium. Fax: +32-4-365.74.56 [EMAIL PROTECTED] This software is provided 'as-is', without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented, you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. 4. You must register this software by sending a picture postcard to the author. Use a nice stamp and mention your name, street address, EMail address and any comment you like to say. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
The goal is to make development easier for a workgroup isn't it? Yes, it is. ICS can only benefit from such a concept. That must not mean to move the source to SourceForge, all we need is a server that runs SVN, 24 hours a day, ideally under your control. What are the requirement for such a server ? -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
What are the requirement for such a server ? Not much. 1. Enough disk space to hold the growing repository 2. Connected to the Internet (hopefully with a firewall :) 3. Apache (to allow for web-based repository access, which is easier to maintain) Here's a link with a discussion on the subject: http://subversion.tigris.org/servlets/BrowseList?list=usersby=threadfrom=330941 -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Using SourceForge for ICS ?
Francois PIETTE wrote: The goal is to make development easier for a workgroup isn't it? Yes, it is. ICS can only benefit from such a concept. That must not mean to move the source to SourceForge, all we need is a server that runs SVN, 24 hours a day, ideally under your control. What are the requirement for such a server ? If there are just a few users members of the development team and main distribution of the source remains dowloading archives from your website I think that a ADSL line was totally OK. There's a svnserver that can be installed as a service and also a plugin for Apache (more secure, allows SSL) both well documented in the online help. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] ICS on SourceForge, which license is best ?
So far, the closest thing to your PostcardWare License that I have found is this: The Educational Community License http://www.opensource.org/licenses/ecl1.php Indeed it looks very close to my usual license. Any known drawback with this license ? -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be - Original Message - From: [EMAIL PROTECTED] To: twsocket@elists.org Sent: Monday, October 08, 2007 9:18 PM Subject: Re: [twsocket] ICS on SourceForge, which license is best ? So far, the closest thing to your PostcardWare License that I have found is this: The Educational Community License http://www.opensource.org/licenses/ecl1.php It grants all the same rights that your license does, and has a provision to prevent confusion between derivative works and the original (i.e. modified versions cannot be claimed to be the original). The only thing missing is the postcard condition :) -dZ. --- Original Message --- From: Francois PIETTE[mailto:[EMAIL PROTECTED] Sent: 10/8/2007 2:59:47 PM To : twsocket@elists.org Cc : Subject : RE: [twsocket] ICS on SourceForge, which license is best ? I would like to have your opinion about which license I should select at SourceForge ( http://www.opensource.org/licenses/category ). I have not much time to read all possible licenses. You all know the current license displayed in each source file (see below for reminder). I would like to stay as close as possible to this simple license. Basically, I want to preserve my intellectual property while granting anyone to use and redistribute ICS source code, including in commercial applications and royalty free. Legal issues: Copyright (C) 1996-2007 by François PIETTE Rue de Grady 24, 4053 Embourg, Belgium. Fax: +32-4-365.74.56 [EMAIL PROTECTED] This software is provided 'as-is', without any express or implied warranty. In no event will the author be held liable for any damages arising from the use of this software. Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented, you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. 4. You must register this software by sending a picture postcard to the author. Use a nice stamp and mention your name, street address, EMail address and any comment you like to say. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] ICS on SourceForge, which license is best ?
Indeed it looks very close to my usual license. Any known drawback with this license ? Not that I know of, nor that I can see. It seems very close to the MIT license, except that the MIT license does not provide for the clear distinction of modifications from the original work -- which, in my opinion, is also the main point of your license. Here's a discussion I found on the license when the author was submitting it for approval by the Open Source Initiative: http://www.mail-archive.com/[EMAIL PROTECTED]/msg07630.html A quick Google search appears to show that the license is popular. And as far as I know, it is very common in academic research institutions. I also found version 2.0 of the license, which is based on the Apache license (again, adding the provision for distinction of derivative works). Its basically the same thing but with more legal-speak. I am not a lawyer, so I cannot tell whether any of that verbiage is actually necessary, but it seems to be in many software licenses nowadays, and perhaps that was the intention. However, it seems to mostly protect against patent lawsuits, which I understand would be an issue to a research institution. Educational Community License, Version 2.0 http://www.opensource.org/licenses/ecl2.php -dZ. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
