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
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
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
[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
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
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
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
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
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
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
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
11 matches
Mail list logo
