Sorry to continue the discussion, but this is an important point:
"Joseph Kesselman/CAM/Lotus" <[EMAIL PROTECTED]> wrote
> (Speaking of the license -- I've just noticed that the license
currently
> reserves the name Xalan, but does not reserve the name XSLTC. It
might be a
> Very Good
While I must say I'm quite disappointed that Jacek has decided to
create his own proprietary derivative of Xalan/XSLTC, he definitely has
the right to do that and has my good wishes at making some good code.
When it comes to licensing issues, some of them are quite simple: read
the license - it's
The future, as it has always been the case, is unknown :-) and wide open
Right now I concentrate on getting XSLTC back on track.
--Jacek
On Thursday 07 March 2002 07:27 am, Stuart Roebuck wrote:
> Do I take it that this means that the discussed improvements to XSLTC
> are no longer Apache licens
On Thursday 07 March 2002 06:30 am, [EMAIL PROTECTED] wrote:
> Jacek, good luck to you. We'll leave your committer status open for a
> while in case you change your mind.
>
> -scott
Wow! I feared that the longest string of strong words will come from you :-)
Thanks for surprising me!
--Jacek
Do I take it that this means that the discussed improvements to XSLTC
are no longer Apache license compatible and cannot therefore be relied
upon to be something that can be integrated into Cocoon in the future?
If so, it looks like, given the speed benefits, we need to encourage
participation
Stefano Mazzocchi <[EMAIL PROTECTED]> wrote:
> 1) any Apache committer has the right to propose the creation of an
> 'internal fork', stating a codename for it.
I back what Stefano said 100%. Anyone is always welcome to come into a
project and try to start a revolution, small or large. I was
Jacek, good luck to you. We'll leave your committer status open for a
while in case you change your mind.
-scott
"Jacek R. Ambroziak" wrote:
>
> Dear XSLTC users,
>
> I owe you clarification about the status of
> my XSLTC version, binaries of which are served
> from my website www.ambrosoft.com.
> The version is derived from Apache/Xalan/XSLTC 2.3.1
> which in turn is derived from my final project
> at Sun
ECTED]
> Subject: Re: experimental XSLTC-2, a clarification
>
>
> On Wednesday 06 March 2002 04:23 pm, Tom Amiro wrote:
>
> > It does not seem ethical or even legal to take open
> > source software -- even if you were the original
> > architect -- and use it for you
On Wednesday 06 March 2002 04:23 pm, Tom Amiro wrote:
> It does not seem ethical or even legal to take open
> source software -- even if you were the original
> architect -- and use it for your own purposes.
Strong words Tom.
This case has nothing to do with my being
the original XSLTC inventor
(Blush. Darn it, I could _swear_ I trimmed the to-list Nothing very
embarassing, but I really do think taking this offline while we work
through the issues would make sense. In public discussions it's
surprisingly hard not to unconsciously play to the audience, which tends to
make consensus h
Offline personal reaction -- note that I Am Not A Lawyer
>It does not seem ethical or even legal to take open
>source software -- even if you were the original
>architect -- and use it for your own purposes.
You may want to reread the Apache license. I believe it's fairly explicit
about saying
Jacek,
I am very disappointed to hear this. You were
the originator, but a lot of work has been done
by others on XSLTC since you moved on.
It does not seem ethical or even legal to take open
source software -- even if you were the original
architect -- and use it for your own purposes.
Yo
One question, Jacek: It isn't clear from your explanation whether you
intend to contribute your version back to Apache once it has stabilized.
Could you clarify?
For what it's worth, I disagree with you somewhat about whether forking off
a major rewrite while staying within the context of Apache
others to easily work with
you on the experimental XSLTC changes, and
promotes easier future use of those changes
in the baseline XSLTC product (pr
The alternative, which is effectively what
you are doing now, is to spawn a new
(presumably open-source) project out of
the XSLTC codebase. Obvious flaws
> -Original Message-
> From: Jacek R. Ambroziak [mailto:[EMAIL PROTECTED]]
>
[...]
> My current version represents an uncompromising overhaul
> of the code base and is no longer implementation compatible
> with Xalan/XSLTC (although it is API compatible).
> Therefore at this point I canno
Dear XSLTC users,
I owe you clarification about the status of
my XSLTC version, binaries of which are served
from my website www.ambrosoft.com.
The version is derived from Apache/Xalan/XSLTC 2.3.1
which in turn is derived from my final project
at Sun Microsystems.
I have returned to this topic b
>>list-post: <mailto:[EMAIL PROTECTED]>
>>Delivered-To: mailing list [EMAIL PROTECTED]
>>Subject: Re: experimental XSLTC
>>To: [EMAIL PROTECTED]
>>Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL P
ECTED]
> Boag/Cambridge/IBM)
>
>
>>list-post: <mailto:[EMAIL PROTECTED]>
>>Delivered-To: mailing list [EMAIL PROTECTED]
>>Subject: Re: experimental XSLTC
>>To: [EMAIL PROTECTED]
>>Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
>>From: [EMAIL
To: [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: experiment
ROTECTED]
M> cc: [EMAIL PROTECTED],
(bcc: Scott Boag/Cambridge/IBM)
Sent by: Subject: Re: experim
Does anyone know when Jacek and Santiago will be getting
committer status to work on XSLTC? The nomination message
went out over a week ago and they got some +1 votes.
--
Tom Amiro -- SQA Engineer
Sun XML Technology Development
voice: 781-442-0589 Fax: 781-442-1437
eMail: tom.amiro@.sun.
I am sorry if you receive this email twice;
I am experiencing troubles with email while setting up
my SOHO network :-)
-
Dear XSLTC users,
from the number of downloads of xsltc.jar from my modest website
(www.ambrosoft.com)
I see that your interest in
24 matches
Mail list logo
